emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#24188: closed (gnucash needs gtk+ in propagated-in


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#24188: closed (gnucash needs gtk+ in propagated-inputs)
Date: Fri, 09 Sep 2016 22:40:01 +0000

Your message dated Sat, 10 Sep 2016 00:38:52 +0200
with message-id <address@hidden>
and subject line Re: bug#24188: gnucash needs gtk+ in propagated-inputs
has caused the debbugs.gnu.org bug report #24188,
regarding gnucash needs gtk+ in propagated-inputs
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
24188: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=24188
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: gnucash needs gtk+ in propagated-inputs Date: Mon, 08 Aug 2016 23:15:50 +0530 User-agent: mu4e 0.9.16; emacs 24.5.1
I installed gnucash with `guix package -i gnucash`. When I attempt to
run it, it fails with the following error message:

**
gnc.gui:ERROR:gnc-icons.c:96:gnc_add_stock_icon_pair: assertion failed: 
(pixbuf1 && pixbuf2)
fish: 'gnucash' terminated by signal SIGABRT (Abort)

However within an environment created by `guix environment --ad-hoc
gtk+`, gnucash runs fine. So, I'm guessing gtk+ needs to be in gnucash's
propagated-inputs.

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- Subject: Re: bug#24188: gnucash needs gtk+ in propagated-inputs Date: Sat, 10 Sep 2016 00:38:52 +0200 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)
Arun Isaac <address@hidden> skribis:

>>> To actually fix this package (and some others) we can:
>>>
>>> - Wrap them with shared-mime-info in XDG_DATA_DIRS or propagated it.
>>>
>>> - Make sure 'xdg-mime-database' always run if glib applications are
>>>   there even without shared-mime-info referenced by profile.  
>>>   IIRC, this was suggested by ludo, but I ignored, now patch sent :-)
>>
>> Apparently the 2nd item is what commit
>> 801d316b20b05a4d0687873ad8e438e6238e23ce does.
>>
>> Are we done, or do we need to do item #1 too?
>
> We are done. No need to do item #1. The issue has been fixed.

I like that.  :-)  Thanks!

Ludo’.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]