unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: 27264@debbugs.gnu.org, Kei Kebreau <kei@openmailbox.org>
Subject: bug#27264: gnome-shell-3.24.2 consistently dies during initialization
Date: Thu, 08 Jun 2017 18:13:48 +0200	[thread overview]
Message-ID: <87vao6mp8j.fsf@fastmail.com> (raw)
In-Reply-To: <878tl3q9g1.fsf@netris.org>


[-- Attachment #1.1: Type: text/plain, Size: 1196 bytes --]

Mark H Weaver <mhw@netris.org> writes:

> Marius Bakke <mbakke@fastmail.com> writes:
>
>> Mark H Weaver <mhw@netris.org> writes:
>>
>>> I have a question: Does GNOME 3 work for *anyone* in Guix now?  If so,
>>> that would be useful information.  If not, I wonder why this got merged
>>> into master.
>>
>> I'm sorry, I don't actually use GNOME and should have tested it before
>> pushing. I have been busy lately and didn't want to hold up the branch.
>
> In the future, I think that pushing an updated desktop environment to
> master should only be performed by someone who is able and willing to
> test it.  Modern desktop environments are quite complex, and many things
> can go wrong even if the code compiles.

I agree completely and take full responsibility for this breakage. There
were a couple of unfortunate events leading up to this: first the
'gnome-updates' branch got "destroyed"; causing it to be merged into
'staging', which in turn was holding up the 'core-updates' progress.

In the future I won't go through with such a large update without
getting feedback from actual users.

Mark, others: Can you try these patches and see if they work for you
(extracted from Keis patch).


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: gnome-shell-fix.patch --]
[-- Type: text/x-patch, Size: 1951 bytes --]

From 66dbac1f0faa75fc60c75cb1375cd9283ef1c7ed Mon Sep 17 00:00:00 2001
From: Marius Bakke <mbakke@fastmail.com>
Date: Thu, 8 Jun 2017 18:00:01 +0200
Subject: [PATCH 1/2] gnu: geoclue: Create typelib files.

* gnu/packages/gnome.scm (geoclue)[native-inputs]: Add GOBJECT-INTROSPECTION.
---
 gnu/packages/gnome.scm | 1 +
 1 file changed, 1 insertion(+)

diff --git a/gnu/packages/gnome.scm b/gnu/packages/gnome.scm
index 84ae1cf2f..4069abab8 100644
--- a/gnu/packages/gnome.scm
+++ b/gnu/packages/gnome.scm
@@ -2634,6 +2634,7 @@ output devices.")
                          (("/bin/true") (which "true"))))))))
     (native-inputs
      `(("pkg-config" ,pkg-config)
+       ("gobject-introspection" ,gobject-introspection)
        ("intltool" ,intltool)))
     (inputs
      `(("avahi" ,avahi)
-- 
2.13.1


From 668bb232493ffa8518b6f5f43e04224ae017d062 Mon Sep 17 00:00:00 2001
From: Marius Bakke <mbakke@fastmail.com>
Date: Thu, 8 Jun 2017 18:04:20 +0200
Subject: [PATCH 2/2] gnu: gnome-shell: Fix startup failure.

Fixes <https://bugs.gnu.org/27264>.

* gnu/packages/gnome.scm (gnome-shell)[inputs]: Add LIBRSVG and GEOCLUE.
---
 gnu/packages/gnome.scm | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/gnu/packages/gnome.scm b/gnu/packages/gnome.scm
index 4069abab8..9ea3bb07a 100644
--- a/gnu/packages/gnome.scm
+++ b/gnu/packages/gnome.scm
@@ -5111,6 +5111,10 @@ properties, screen resolution, and other GNOME parameters.")
        ("startup-notification" ,startup-notification)
        ("telepathy-logger" ,telepathy-logger)
        ("upower" ,upower)
+       ;; XXX: These requirements were added in 3.24, but no mention in NEWS.
+       ;; Missing propagation? See also: <https://bugs.gnu.org/27264>
+       ("librsvg" ,librsvg)
+       ("geoclue" ,geoclue)
        ;; XXX: required by libgjs.la.
        ("readline" ,readline)))
     (synopsis "Desktop shell for GNOME")
-- 
2.13.1


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  parent reply	other threads:[~2017-06-08 16:14 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-06  4:59 bug#27264: gnome-shell-3.24.2 consistently dies during initialization Mark H Weaver
2017-06-07 10:37 ` Ludovic Courtès
2017-06-07 13:15   ` Roel Janssen
2017-06-07 21:58     ` Mark H Weaver
2017-06-08  6:03       ` Marius Bakke
2017-06-08  6:29         ` Mark H Weaver
2017-06-08 12:35           ` Kei Kebreau
2017-06-08 16:13           ` Marius Bakke [this message]
2017-06-08 16:29             ` Marius Bakke
2017-06-09  6:23               ` Chris Marusich
2017-06-09  7:02               ` Mark H Weaver
2017-06-08  7:39         ` Ben Sturmfels
2017-06-08  6:48       ` pelzflorian (Florian Pelz)
2017-06-08 12:01       ` Ludovic Courtès
2017-06-08 12:23         ` Kei Kebreau
2017-06-08 13:09           ` Roel Janssen
2017-06-08 18:08           ` Roel Janssen
2017-06-08 18:34             ` Kei Kebreau
2017-06-08 14:01         ` Mark H Weaver
2017-06-08 14:54           ` Chris Marusich
2017-06-08 17:08           ` Leo Famulari
2017-06-08 17:19             ` Marius Bakke
2017-06-08 17:29             ` Catonano
2017-06-08 17:45               ` Leo Famulari
2017-06-08 18:12             ` Leo Famulari
2017-06-08 20:47           ` Ludovic Courtès
2017-06-11  8:57             ` Mark H Weaver
2017-06-11 13:16               ` Ludovic Courtès
2017-06-08 14:20         ` pelzflorian (Florian Pelz)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vao6mp8j.fsf@fastmail.com \
    --to=mbakke@fastmail.com \
    --cc=27264@debbugs.gnu.org \
    --cc=kei@openmailbox.org \
    --cc=mhw@netris.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).