Fresh install of ubuntu 18.04 then standard apt-install of awesome with awesome-extra.
Awesome --version returns
awesome v4.2 (Human after all)
• Compiled against Lua 5.3.3 (running with Lua 5.3)
• D-Bus support: ✔
• execinfo support: ✔
• xcb-randr version: 1.5
• LGI version: 0.9.2
gnome-control-center sound -v
** (gnome-control-center:14812): DEBUG: 14:27:19.737: Enabling debugging
** (gnome-control-center:14812): DEBUG: 14:27:19.850: No extra argument
** (gnome-control-center:14812): WARNING **: 14:27:19.850: Could not find settings panel "sound"
Basically there is no settings whatsoever.
Anyone can suggest what went wrong?
Everything else works just fine, I have sound, keyboard, multiple displays. I just lost control over settings, cannot mute sound, cannot dim a screen, cannot lock my laptop.
PS
Previous ubuntu (16.04) had unity-control-center and it was working just fine (but with older version of awesome I think)
gnome-control center can be run by tricking it into thinking it is in a gnome desktop
env XDG_CURRENT_DESKTOP=GNOME gnome-control-center
or by editing the .desktop files for each control app.
for example
/usr/share/applications/gnome-display-panel.desktop
find the line OnlyShowIn=GNOME;Unity; add awesomewm
I reached to Awesome irc channel to figure out what might be wrong. Explanation I was given (I am not quoting, I am answering as I understand the problem) is that nowadays gnome is more and more strict over it's architecture. So in the past you could replace window manager on gnome with another tool and retain whatever underlying solution was (mentioned control panel, sound widgets and etc). But nowadays gnome has approach all or nothing.
So real solution to my problem is, because sound and screen is working and I am only missing settings-control over them, is to install widgets and/or tools. For example pavucontrol was mentioned as good tool for a sound and bind key shortcuts to control brightness.
Previous iteration of Ubuntu worked, because exactly it was running unity, not gnome.
Related
I used to Atom editor for coding Golang, PHP,...
When I am coding, sometimes it is automatic close. I install it on Window 10.
Maybe when I switch tab or move mouse but I don't know why so.
UPDATE:
Version: 1.18.0 (before, it is older version but It also so)
Atom : 1.18.0
Electron: 1.3.15
Chrome : 52.0.2743.82
Node : 6.5.0
Do you have any more information? Anything special you did when installing? Have you followed the suggestions in the Debugging document? Also, could you give the following information?
Which version of Atom are you using?
Can you reproduce the issue after completely exiting Atom and restarting using atom --safe?
On its website OpenFlipper says it can be compiled in three steps as:
cd build
cmake ..
make # or, even better, make -j8
However I get an error saying Qt is unable to be found at the cmake step and that I should specify a QT5_INSTALL_PATH. However even if I do this OpenFlipper is still issuing the same complaint!
You are not supposed to specify where Qt is installed in the QT5_INSTALLED_DIR but prior to that as environment variable in your terminal:
# assuming Qt was installed in your home directory, as is default
export CMAKE_PREFIX_PATH=~/Qt5.7.0/5.7/gcc_64/
# note that you now have to call cmake etc from that process
Compiling and running it after that you might get errors telling you GL_ARB_vertex_buffer_object is not present, even if your glxinfo | grep ARB_vertex_buffer is telling you it is.* Clicking "Ignore" results in a crash. To mitigate this, you have to manually change (4,3) to (3,0) in
OpenFlipper/widgets/coreWidget/CoreWidget.cc
If you still experience errors, try deleting your cmake cache, this is accomplished by using cmake-gui (was in the package cmake-qt-gui for me) and hitting "Delete Cache"
(optional) remove the very annoying warning message you get at every start of OpenFlipper by removing the line concerning "renderers shipped" in
OpenFlipper/Core/Core.cc
*: My teaching assistant told me that there is a bug in Qt (<5.9) that forces OpenFlipper to use the OpenGL Compatibility Profile. Additionally Intel and AMD drivers hand back an OpenGL 3.0 Core Context when asked for an OpenGL 4.3 Compatibility Context (my TA described this behavior as a "bug", I'm not so sure about this), leading to a crash in Qt. So this should be resolved in Qt 5.9 (not out yet). This seems to affect also mainly integrated graphics, so one could try using a dedicated GPU.
I don't like the 3.6 version at all. It has too many bugs and it's too slow compared with the previous versions, so I'd like to install to a previous version and wait till they fix the problems. I can't downgrade the installation, so no, not an option.
I know that in this web: https://wiki.appcelerator.org/display/guides2/Reverting+to+a+Previous+Version there is a list of old versions, but this are VERY old, I'd like to download at least the 3.4.2 version or newer (like 3.5), but I can't see any link from wich I can download it. Can anyone give me a link or way to get previous versions of aptana?
Oh yes, oh yes, finally I found them:
MAC OS
http://d1iwq2e2xrohf.cloudfront.net/tools/studio/standalone/3.4.2.201308081805/mac/Aptana_Studio_3_Setup_3.4.2.dmg
WINDOWS
http://d1iwq2e2xrohf.cloudfront.net/tools/studio/standalone/3.4.2.201308081805/win/Aptana_Studio_3_Setup_3.4.2.exe
Linux 32 bits
http://d1iwq2e2xrohf.cloudfront.net/tools/studio/standalone/3.4.2.201308081805/linux/Aptana_Studio_3_Setup_Linux_x86_3.4.2.zip
Linux 64 bits
http://d1iwq2e2xrohf.cloudfront.net/tools/studio/standalone/3.4.2.201308081805/linux/Aptana_Studio_3_Setup_Linux_x86_64_3.4.2.zip
Can't get the plugin, sorry.
You could find Aptana 3.4.2 as Eclipse plugin at the following URL: http://d1iwq2e2xrohf.cloudfront.net/tools/studio/plugin/update/studio3/3.4.2.201308081736/com.aptana.feature.studio-3.4.2.201308081736-7W7I57boG98RAi489ctbvKi7VXbq.zip
When you are installing it from the zip, make sure you un-tick "Group Items by Category"
i was trying to build "brackets sprint 40" from source code (by following #jasonsanjose instructions look #4816 and the official wiki's page here) in my 32bit Wheezy, Using CEF3 (Verion 3.1547.1406_linux32_release with glibc 2.13) and everything was OK .
when i ran grunt build and grunt installer the output was: Running "build" task
Running "build-linux" task
Done, without errors.
and when i installed .deb package and executed it in the terminal , this error has been thrown:brackets: libcef_dll/wrapper/libcef_dll_wrapper.cc:120: int CefExecuteProcess(const CefMainArgs&, CefRefPtr): Assertion `false' failed.
Aborted
I did rebuild it many times, but the problem persist.
And this is where i stopped, i don't know where the problem lies.
some help will be appreciated, thank you in advance.
There's a duplicate of this question with longer discussion posted here - https://github.com/adobe/brackets/issues/8170.
Note: This problem shouldn't affect a "vanilla" brackets-shell build on Linux -- it's specific to a hack some people have developed to support an older version of Debian than Brackets officially supports. This requires swapping in a newer version of the CEF library, which is not always easy to do since they are not usually backwards-compatible.
I'm using a Macbook Pro (Snow Leopard, 10.6.8) and have been a regular emacs user for the past few months. I'm trying to install a modified version of Emacs 24.2 provided here to utilize Emacs Speaks Statistics (ESS) from the downloads page. I currently have 22.1.1:
M-x emacs-version
GNU Emacs 22.1.1 (mac-apple-darwin) of 2011-06-07 on b1030.apple.com
I installed the emacs linked earlier, put it in Applications, and set this in .bashrc:
alias emacs="/Applications/Emacs.app/Contents/MacOS/Emacs -nw"
So it seems like it's working correctly as I wrote and successfully ran a short R program.
M-x emacs-version
GNU Emacs 24.2.1 (x86_64-apple-darwin, NS apple-appkit-1038.36) of 2012-08-27 on bob.porkrind.org
Is this the usual way to upgrade to a "newer version" of Emacs? Sorry if this question seems trivial, but I've never done this before (I typically used emacs on a different computer) and the Installation step on the previous website consists of just one sentence. The all-in-one installation method also isn't explained in the official documentation.
A brief side note while I was searching on the web: I believe calling 'emacs file_name' should open a GUI version, while 'emacs -nw file_name' is the console, so I remain using the terminal. But on my Mac, using emacs has the same effect as using emacs -nw. In other words, I can't get a GUI or separate window to show up. Can anyone confirm that this Super User question has the 'correct' answer? (I don't really have a problem with this, as I hate having another pop-up window, but it would be nice to know for completeness.)
The Emacs that comes with Mac OS X /usr/bin/emacs does not have a graphical interface, just the terminal one, so calling emacs is the same as emacs -nw.
Your upgraded Emacs by default starts with the graphical interface, so you need to specify -nw to force it to use the terminal.
There is no "usual" way to upgrade OS X's default Emacs (i.e. Apple does not provide an upgraded Emacs); what you've done is fine. Or you could install a binary from http://emacsformacosx.com/ or use a package manager like homebrew.