I'm using jhbuild to build and run gnome-music.
I'm having a successful build but when I run the command
jhbuild run gnome-music
I get the following error
One of the errors is
1.GstTag was imported without specifying a version first
The rest are in the link above.
I'm not sure how to proceed further,can someone help me out?(I'm using Ubuntu 17.04).
I'm following the steps given on:
https://github.com/GNOME/gnome-music
Gst just warns you against not mentioning a version number. Hence, that's not the error.
The error you are facing is regarding Tracker. As you are on Ubuntu distribution, you should know that Ubuntu disables Tracker by default. Hence jhbuild run gnome-music refuses to start. Tracker is a file-indexing service based on file's metadata.
However, Ubuntu is deciding to enable Tracker by default as many GNOME's core apps relies on it. Read here.
Enable Tracker and jhbuild will pick it up from the host system.
Related
I keep totally failing to update an etherpad-lite server. The problem: Even a Google search for the update procedure brings up hardly any information, only that one should run "git pull origin".
I have now tried this in many different ways. The update usually works, but afterwards one of these errors occurs:
Plugins can no longer be installed
The service can no longer be started (TypeError: log4js.replaceConsole is not a function)
The entire admin panel no longer works.
I tried uninstalling or updating all plug-ins before, but both hardly brought any improvements, only other errors. The update of the plugins in the admin console fails, I tried it via the updatePlugins.sh script. Here a message appears that at least etherpad-lite 1.8,6 must be installed. I am currently at version 1.8.4 and would like to update to the latest version 1.8.12. However, some of the plug-ins are still updated. A very strange behaviour.
I would be happy if someone could tell me how to properly update the etherpad-lite instance step by step. (ubuntu 20)
Thank you!
I have recently updated Etherpad-lite from version 1.8.6 to 1.8.13.
For me, executing git pull origin and then checking out the 1.8.13 release tag, with git checkout 1.8.13, made the work.
It is important, despite having Etherpad configured as a service, to run it for the first time using:
src/bin/run.sh.
Node v12.22.1
npm 6.14.12
Ubuntu 20.04.2
I hope it has been useful to you.
I'm working on the sources of an application an have the release version of the application installed on the system.
How can i test the modified (and possibly buggy) application without conflicting with the version installed ?
What I want is basically virtual env but for generic applications.
I tried Docker but this has several issues :
I can't get the X11 redirection working. I tried commands like docker run -ti --net=host -e DISPLAY=:0.0 test-docker-geany or docker run -ti -e DISPLAY=$DISPLAY -v /tmp/.X11-unix:/tmp/.X11-unix test-docker-geany according to some forum threads.
The docker build involves copying the whole codebase to the image as well as installing all the tools and libraries needed to compile which some are not stored in cache and installed each time. So the script takes several minutes each time you want to compile and run.
So my questions are :
Is docker the best solution for such task ? I'm sure this is a problem a lot open source contributors faces but I couldn't find other cases on the net.
If it is not the best solution what are the alternatives ?
Detailed error :
I ran the commands xhost + and the first one I gave in my first issue and I got :
The program 'geany' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
(Details: serial 173 error_code 2 request_code 130 minor_code 3)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
The Dockerfile : https://pastebin.com/p03vaWbU
The warning was finally the cause : i just had to install gtk2-engines-pixbuf according to this thread
EDIT : I misunderstood the success. I get it to work that time because I ran an other GUI program in the docker before. In fact, I finally discovered that trying geany a second time just works although the first try give the error.
I have spent hours trying to fix this problem on my own but am getting nowhere and can't seem to see any other questions/solutions regarding my specific problem.
I successfully installed nodist via chocalatey via Powershell admin.
I used the following script in attempting to install the Squarespace development server per Squarespace documentation:
npm install -g #squarespace/server -y
Please noted I added the -y parameter to for yes to accept license agreement but previously didn't add this parameter but still received same result.
When trying to install the local Squarespace development server via Powershell admin, the script keeps getting hung up at the following:
Using this software requires accepting the Squarespace Developer Terms
of Use and Oracle Binary Code License Agreement . See LICENSE.txt.
The following is a screenshot of all the scripts that ran beginning from my install script:
I have done everything from reinstalling nodist several times to rebooting machine and everything else to troubleshoot.
Please note that I have also waited for more than an hour to see if the script fully executes but remains hung at the above noted line.
Why is this happening and how can I fix this?
Regards.
I’ve written a very small application in Go, and configured an AWS Linux AMI to host. The application is a very simple web server. I’ve installed Go on the Linux VM by following the instructions in the official documentation to the letter. My application runs as expected when invoked with the “go run main.go” command.
However, I receive an “Invalid argument” error when I attempt to manually launch the binary file generated as a result of running “go install”. Instead, if I run “go build” (which I understand to be essentially the same thing, with a few exceptions) and then invoke the resulting binary, the application launches as expected.
I’m invoking the file from within the $GOPATH/bin/ folder as follows:
./myapp
I’ve also added $GOPATH/bin to the $PATH variable.
I have also moved the binary from $GOPATH/bin/ to the src folder, and successfully run it from there.
The Linux instance is a 64-bit instance, and I have installed the corresponding Go 64-bit installation.
go build builds everything (that is, all dependent packages), then produces the resulting executable files and then discards the intermediate results (see this for an alternative take; also consider carefully reading outputs of go help build and go help install).
go install, on the contrary, uses precompiled versions of the dependent packages, if it finds them; otherwise it builds them as well, and installs under $PATH/pkg. Hence I might suggest that go install sees some outdated packages which screw the resulting build.
Consider running go install ./... in your $GOPATH/src.
Or may be just selective go install uri/of/the/package for each dependent package, and then retry building the executable.
I am currently trying to run Coverity Prevent and I believe I have everything set up appropriately on my windows 7 build machine. I have run it with AnthillPro and when my code finishes and gets to Coverity it says that everything was built fine and the only error I get is:
Warning: Cygwin pathname conversion ignored; no applicable
'bash'/'mount', 'cygpath', or registry keys found.
I have even tried to install Cygwin to see if this could rectify the problem and I still end up with the same error.
I am currently using AnthillPro 3.7 and Coverity 5.5.3. The build log says that I have warnings but no errors and that it hasn't emitted anything. I have tried to run a script directly from the machine (not server) itself and I have the same error as I do using the Coverity Prevent in Anthill
This is the only information I get at the bottom of the build log.
Run from AnthillPro:
Build time (cov-build overall): 00:00:17.753597
[WARNING] No files were emitted. This may be due to a problem with your configuration
or because no files were actually compiled by your build command.
Please make sure you have configured the compilers actually used in the compilation.
For more details, please look at:
d:\Coverity\Intermediate\AllToolsProjects.sln_pc_vs2010\build-log.txt
Run from Script:
The cov-build FAILED.
This may be because less than 90 percent of units were successfully compiled
Check for errors here:
D:\\Coverity\Scripts\build_AllToolsProjects.sln_pc_vs2010.bat
D:\\Coverity\Intermediate\AllToolsProjects.sln_pc_vs2010\build-log.txt
D:\\Coverity\Configuration\pc_vs2010
It sounds like you haven't configured the compiler - that's when you tell your Coverity Analysis installation which compiler you are using. devenv is not a compiler, cl.exe is.
Run the following command:
coverity-analysis-dir/bin/cov-configure --msvc
This will say that you are using the cl.exe compiler and it's of type msvc no matter where it's installed.
Then rerun your Coverity build and see if it captures more of your compilations.