From: Thorsten Wilms <t_w_@freenet.de>
To: help-guix@gnu.org
Subject: Foreign distro Unity desktop broken after guix update
Date: Mon, 27 Dec 2021 16:18:34 +0100 [thread overview]
Message-ID: <20211227161834.6b171ee658fcf26fd7c70a42@freenet.de> (raw)
Hi!
Unity desktop stopped working after the first ’guix pull && guix
package -u’ in maybe 2 weeks. There has been no update on the Ubuntu
side between the last succesfull run and now, as far as I can tell.
Unity desktop causes a few redraws, then exits back to the session
greeter (lightdm).
Now I would have assumed that there is no interaction between Unity and
guix, since the former is entirely on the dpkg side. But via journalctl,
I found a whole lot of:
```
Dec 27 15:44:51 charly compiz[2198]: ERROR 2021-12-27 15:44:51
nux.gltexture.resource.manager GLTextureResourceManager.cpp:
54 Invalid target, impossible to generate a new texture.
Impossible to generate a pixbuf: Unable to load image-loading
module:
/gnu/store/2dza2psfbrrbvsni8jjqzzqx3hmm8kw8-librsvg-2.50.7/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so:
/lib/x86_64-linux-gnu/libpthread.so.0: version `GLIBC_PRIVATE' not found
(required by
/gnu/store/2fk1gz2s7ppdicynscra9b19byrrr866-glibc-2.33/lib/librt.so.1)
```
It looks like compiz segfaults shortly after a bunch of those, followed
by unity7.service.
Any ideas why dpkg-compiz tries to use guix-librsvg and what to do
about it, or what else is going on here?
--
Thorsten Wilms <t_w_@freenet.de>
next reply other threads:[~2021-12-27 15:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-27 15:18 Thorsten Wilms [this message]
2021-12-27 19:37 ` Foreign distro Unity desktop broken after guix update Fredrik Salomonsson
2021-12-27 21:17 ` Thorsten Wilms
2021-12-28 10:16 ` Thorsten Wilms
2021-12-28 21:45 ` Fredrik Salomonsson
2021-12-29 8:59 ` Thorsten Wilms
2021-12-30 1:11 ` Fredrik Salomonsson
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=20211227161834.6b171ee658fcf26fd7c70a42@freenet.de \
--to=t_w_@freenet.de \
--cc=help-guix@gnu.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.
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).