I have been trying to fix a composer error which didn't allow me to download due to ssl not being enabled and I simply removed the ";" from the php.ini file and restarted my computer.
However I now get an error
"XAMPP's Apache can not start while Web Sharing is on! Please go to System Preferences > Sharing and turn it off."
when trying to start apache... however I do not even have a setting for "Web Sharing" in my System Preferences. How can I fix this issue?
Thank you.
open Terminal and enter this command:
sudo apachectl stop
Related
I'm trying to set up Starlink v2018A on Mac OS Monterey. I followed the install instructions on the Starlink website and so the installation seemed to go smoothly. However, now that Starlink is installed, whenever I try to launch gaia I get " "<file_name>" cannot be opened because the developer cannot be verified. ".
I know how to manually work around this for individual files, but when I fix it for one file, the error simply re-occurs for another file.
Has anyone else had this issue and know a quick fix? Or will I just have to manually approve each file?
Thanks!
I'm having trouble running the following command in the Terminal:
xcode-select --install
After agreeing to the T&Cs, I get the following error pop up:
Can't download the software because of a network problem.
As I am behind a corporate proxy for the company I work for, I've correctly set this up on my Mac in System Preferences and I can browse the web normally. I also added the proxy settings via these commands that I was given (real URL removed):
export http_proxy="http://example.net:80"
export https_proxy="$http_proxy"
I tried following this thread on Reddit, which suggested deleting App Store preference files, but that didn't work.
I'm a bit lost now because I don't know how else to approach the issue. Perhaps there is something around installing things via the Terminal that I don't know of, in relation to proxy settings?
Xcode's Command Line Tools can be downloaded directly from https://developer.apple.com/download/more/
I have two gnome-shell extensions that don't appear to be loading after upgrading to 3.24. In gnome-tweak-tool they have a warning sign icon with "Error loading extension", and nothing else. I tried using looking glass (lg), and it just says "Error", and that the extension "has not reported any errors".
How can I debug the extension to find out why exactly it's not loading?
I found the error in the systemd journal:
$ sudo journalctl /usr/bin/gnome-shell
Just simply run this on terminal:
gnome-extensions-app
and enable it to make the extensions work.
Works perfectly with GNOME 40
As mentioned on the Github page.
A Shell reload is required. Press Alt+F2 r Enter and the extension has to be enabled with gnome-tweak-tool or with dconf.
As mentioned on Dash to Dock's User reviews. Make sure you disable Ubuntu Dock if you are using this in Ubuntu, otherwise you are going to have conflicts.
To disable Ubuntu Dock type the following in terminal:
gnome-extensions disable ubuntu-dock#ubuntu.com
I also experienced the same error. I think I will like to state the procedures that I took to make mine to work, and then you can check to see if you got it wrong somewhere.
Here are the steps
First install the Gnome shell extensions package from the terminal
sudo apt install gnome-shell-extensions
And then reboot your system. After that, start GNOME Tweaks and you’ll find a few extensions installed. You can just toggle the button to start using an installed extension.
Next, go to GNOME Extensions website (GNOME User Themes Extensions) and download the extension with the latest version (Although, I often prefer to download the version next to the latest version, since it may be more stable).
Extract the downloaded file to the ~/.local/share/gnome-shell/extensions (home/.local/share/gnome-shell/extensions) directory. You can press Ctrl + H to show hidden folders. Create the extensions folder if you don't have it yet.
Now restart GNOME Shell. Press Alt+F2 and enter r to restart GNOME Shell.
Restart GNOME Tweaks tool as well. You should see the manually installed GNOME extension in the Tweak tool now. You can configure or enable the newly installed extension here.
That's all
I hope this helps
Loging in without wayland works for me.
My extension was not enabling. I just log out and log in back and ran this command.
gnome-extensions enable example#hammad.example.com
It worked in my case.
So I've been using MAMP just fine for an Apache server on Yosemite for some time now. I only need one local host, so I'm using regular MAMP and not MAMP Pro. I am on MAMP 3.4
When I click the "start servers" button, it doesn't respond to the click. It just shows the colored spinner like the application froze, and then nothing happens. Only the SQL server will start but not the Apache.(I don't even use SQL)
I can click through the preferences window just fine, and I can click the quit button, but the start servers button just gives that error.
The Apache box in the top right isn't filled in, and wont let me fill it in either. SQL box is filled it, if that matters. No error message at all. Totally lost.
I ran into the same problem as well after upgrading Mavericks to El Capitan. Mysql did start, but Apache failed starting. I'm running MAMP 3.0.5 (regular version).
I managed to fix this issue by renaming a file in the folder /Applications/MAMP/Library/bin. Rename envvars to _envvars and restart Apache. This made Apache running again on my machine.
Ok im new here but i figured it out.
sudo apachectl stop
Just ran that command.
Try copying the pre update version of your httpd.conf file and restarting apache as recommended above.
sudo cp /private/etc/apache2/httpd.conf.pre-update /etc/apache2/httpd.conf
sudo apachectl restart
This worked for me. I had issues getting MAMP (Pro) to start Apache and when it was running it took a while to shutdown Apache, which is odd since it didn't start.
I blame El Capitan, always blame the captain if things go wrong. Except Captain Morgan, that's your own fault.
Reinstalling MAMP was the easiest way for me as terminal still scares me. But make sure you follow the steps below so you don't lose all of your files and databases!
1. Rename your MAMP folder in Applications/ to "MAMPOLD" so that you don't overwrite your htdocs and databases.
2. Downloaded and install a fresh copy of MAMP from https://www.mamp.info/en/.
3. Replace the 'htdocs' and 'db' folders in your newly installed MAMP with the ones from your "MAMPOLD" folder.
Note that for the db folder I just transferred any folders and files that didn't exist in the new db folder so I didn't replace anything important. This may not be necessary but I didn't want to risk it.
4. Finally when you launch MAMP again you may have to change the ports to default if it isn't working. I had them orginally set to 80 and 3306 which is no longer working so now I have to put up with seeing localhost:8888 which is annoying but at least it's working! If anyone can help me with this I would be grateful.
I found that the ServerRoot in http.conf used the path "/usr" Most Macs use "/users". Soon as I changed it and restart apache MAMP went live
I have installed Firefox on my Server (running Debian 6.0) but when I try to launch it I get the following message:
Error: no display specified
After googling I installed xvfb and now I have this error;
Xlib: extension "RANDR" missing on display ":99.0".
and it freezes.
Can anybody help me?
Update: I'm now able to run Firefox, but I don't want it to open up a local window but everything should be done on the server side. It should just open up, play a macro (made with iMacros) and then shut down. The opening and the closing will be handled by a script.
Thanks
You are connecting with SSH to that Debian machine? Then call next time the ssh-command with -X as argument, this will pass the correct display options to the server.
Launch this from your box's xterm:
ssh -X debian-server dbus-launch firefox