unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Jaft <wamm_kd_schmelingski@yahoo.com>
Cc: "52044@debbugs.gnu.org" <52044@debbugs.gnu.org>
Subject: bug#52044: Various Program Settings not Saving and Icons not Recognized
Date: Thu, 02 Dec 2021 20:33:40 +0100	[thread overview]
Message-ID: <2b84f12fceaa4dfa8a99be7d4eb7823bf36d0f0e.camel@gmail.com> (raw)
In-Reply-To: <418282920.375546.1638411045114@mail.yahoo.com>

Hi,

Am Donnerstag, den 02.12.2021, 02:10 +0000 schrieb Jaft:
> I had noticed that the core-updates-frozen branch had been merged so
> I upgraded but found things pretty much the same as before.
Please come back, you're within the wrong timeline.

> I saw an old patch (
> http://git.savannah.gnu.org/cgit/guix.git/commit/?id=e311ef4f87f7ad8db2114e5f89961eea0240893b
> ) and, while I'd checked rofi for gdk-pixbuf+svg – before –, –
> somehow – it made me think to check librsvg, this time, and found
> that it was using gdk-pixbuf, rather than gdk-pixbuf+svg. I then made
> a package inheriting librsvg but using gdk-pixbuf+svg, instead, and
> made a package which inherited rofi but used my librsvg package and,
> with that installed, rofi worked with .svgs, then.
> 
> Am I right in assuming librsvg ought to be using the latter, as the
> library deals directly with handling SVGs? If so, I can put together
> a patch to submit.
Have you checked using gdk-pixbuf+svg as input to rofi directly?  I
don't see why we would have to go in circles for librsvg, the component
you're trying to use is gdk-pixbuf.

Cheers





  reply	other threads:[~2021-12-02 19:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1962172575.272360.1637610844717.ref@mail.yahoo.com>
2021-11-22 19:54 ` bug#52044: Various Program Settings not Saving and Icons not Recognized Jaft via Bug reports for GNU Guix
2021-11-26 16:45   ` Liliana Marie Prikler
2021-11-28 12:52     ` Jaft via Bug reports for GNU Guix
2021-11-28 13:57       ` Liliana Marie Prikler
2021-11-29  4:01         ` Jaft via Bug reports for GNU Guix
2021-11-29  5:20           ` Liliana Marie Prikler
2021-12-02  2:10             ` Jaft via Bug reports for GNU Guix
2021-12-02 19:33               ` Liliana Marie Prikler [this message]
2021-12-02 20:16                 ` Jaft via Bug reports for GNU Guix
2021-12-02 20:50                   ` Liliana Marie Prikler
2021-12-02 23:30                     ` Jaft via Bug reports for GNU Guix
2021-12-17  6:56                       ` Jaft via Bug reports for GNU Guix
2021-12-17  9:00                         ` Josselin Poiret via Bug reports for GNU Guix
2022-01-03 22:05                           ` Jaft via Bug reports for GNU Guix
2022-01-04 20:00                             ` Liliana Marie Prikler

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=2b84f12fceaa4dfa8a99be7d4eb7823bf36d0f0e.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=52044@debbugs.gnu.org \
    --cc=wamm_kd_schmelingski@yahoo.com \
    /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).