2017-02-11 15:31 GMT+01:00 ng0 :
> So, I am not 100% sure if I encouter hardware failures or software
> failures here. But I need to solve wether this is a GNOME bug to exclude
> or include the hardware failure.
>
> The following is the log output of a session with SSDM where I
> succesfully log i
On 17-03-03 10:02:52, Catonano wrote:
> 2017-02-11 15:31 GMT+01:00 ng0 :
>
> > So, I am not 100% sure if I encouter hardware failures or software
> > failures here. But I need to solve wether this is a GNOME bug to exclude
> > or include the hardware failure.
> >
> > The following is the log outpu
On 17-03-02 22:20:44, ng0 wrote:
> On 17-03-02 16:58:35, Leo Famulari wrote:
> > On Sat, Feb 11, 2017 at 03:00:13PM +, ng0 wrote:
> > > This is the ~120 lines of today. It reminded me of the real issue, which
> > > is dbus could not be started, which very likely could be the reason for
> > > th
hello,
I use GNOME on a laptop with NVIDIA graphic card, sometimes GNOME stops
working; graphic mode and console do not respond!.
Then proceed to turn it off with the keyboard button, since I have no
option!. This error is due to the graphics card.
El Thu, 2 Mar 2017 17:17:39 -0500
Leo Fa
I have misplaced my log for this, but it is easy to reproduce:
configure offloading on master and build-machine, comment the entire
content of the file which holds the build-machines, run "guix build
hello" and see the error.
This should even work when you haven't configured offloading, just with
This came up in a help-guix thread, and Ricardo Wurmus asked me to
post here requesting that Mesa be built with LLVM to improve Gallium's
performance.
The original post is here:
https://lists.gnu.org/archive/html/help-guix/2017-02/msg00141.html
but in short, when running GuixSD on my system, Gnome
Leo Famulari writes:
>> Anyway, this bug has been a massive pain and I'm going to merge it
>> tomorrow so I can get on with life. The 'master' jobset should be
>> started afterwards; perhaps you can merge and start the evaluation?
>
> Okay, let me know when you push the merge and I'll start the e
substitute: updating list of substitutes from 'https://mirror.hydra.gnu.org'...
substitute: updating list of substitutes from 'https://mirror.hydra.gnu.org'...
100.0%
substitute: updating list of substitutes from 'https://mirror.hydra.gnu.org'...
substitute: updating list of substitutes from 'h
On Fri, Mar 03, 2017 at 05:52:34PM +0100, Marius Bakke wrote:
> Leo Famulari writes:
>
> >> Anyway, this bug has been a massive pain and I'm going to merge it
> >> tomorrow so I can get on with life. The 'master' jobset should be
> >> started afterwards; perhaps you can merge and start the evalua
On Fri, Mar 03, 2017 at 02:04:14AM -0600, Matthew Brooks wrote:
> This came up in a help-guix thread, and Ricardo Wurmus asked me to
> post here requesting that Mesa be built with LLVM to improve Gallium's
> performance.
>
> The original post is here:
> https://lists.gnu.org/archive/html/help-guix
Leo Famulari writes:
> On Fri, Mar 03, 2017 at 02:04:14AM -0600, Matthew Brooks wrote:
>> This came up in a help-guix thread, and Ricardo Wurmus asked me to
>> post here requesting that Mesa be built with LLVM to improve Gallium's
>> performance.
>>
>> The original post is here:
>> https://lists
When using the same process with a good bandwidth connection, there is
no problem with
guix system reconfigure /etc/config.scm
or with
guix pull
or with sending emails in Claws-Mail
Our gitolite package currently creates all
(including gitolite-admin.git) git repositories with references to
"/usr/bin/perl" as shebang, which makes it completely useless on
serverside.
Given that the server side in the case of a gitolite from Guix runs an
environment where you will not run perl f
What makes this worse, with every update (push) of gitolite-admin
repository the shebang of "hooks/update" is reset.
Other repositories seem to keep changes in the hooks shebangs so
far.
If you try to drag an application to the floating bar on the left in Gnome,
the Gnome Shell will crash, it will be started again and you will have to
login again
I first reported this here
https://lists.gnu.org/archive/html/help-guix/2017-02/msg00128.html
Installing adwaita-icon-theme didn't help
With a good bandwidth connection, errors are none in
guix pull
and do not pop up immediately in
guix system reconfigure /etc/config.scm
But finally at the end, I get these failures:
FAILURES:
--ion-eager
/tmp/guix-build-mozjs-24.2.0.drv-0/mozjs-24.2.0/js/src/jit-test/tests/basic/bug698584.js
Forgot to CC this when sending.
-- Forwarded message --
From: Matthew Brooks
Date: Fri, Mar 3, 2017 at 4:11 PM
Subject: Re: bug#25953: [Mesa] Very low Gallium performance compared to Trisquel
To: Marius Bakke
> What are your hardware specs?
I'm using an AMD Phenom II X6 1100T
I get the following error after
guix pull
and
guix system reconfigure /etc/config.scm
FAILURES:
--ion-eager
/tmp/guix-build-mozjs-24.2.0.drv-0/mozjs-24.2.0/js/src/jit-test/tests/basic/bug698584.js
--no-baseline
--no-ion
/tmp/guix-build-mozjs-24.2.0.drv-0/mozjs-24.2.0/js/src/jit-test/test
Hello! I'm getting this error while trying to compile latest guix
master on one of my machines (fortunately, not my main one). I don't
know why I'm hitting this error, since I'm not hitting it on my main
machine. I'm upgrading from a few months back.
I spoke on irc and found that Ricardo had th
19 matches
Mail list logo
