From: ng0 <ng0@libertad.pw>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: hplip: Add qt5 gui.
Date: Thu, 29 Dec 2016 12:29:34 +0000 [thread overview]
Message-ID: <87mvfe6hqp.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20161229125651.7ea77af3@scratchpost.org>
Danny Milosavljevic <dannym@scratchpost.org> writes:
> Hi,
>
>> + "--enable-dbus-build"
>> ;; TODO: Make hp-setup find python-dbus.
>
> Does that mean that dbus now works in hp-setup?
>
I don't know. Before and afterwards I ran into the problem where
no user (in groups lp and lpadmin, even root) is authenticated
enough to finally add the printer (hp-setup -i -a -g).
I guess this is the source of this problem...?
I'm still looking into some problems with the gui, possibly
caused by some Guix specifics. The gui works in general, but what
doesn't work is adding your own ppd (you can select it in the
file-browser but it never gets displayed, therefore you can not
proceed beyond the first page), so I really assume this is dbus
or some other problem too. Nothing new, but the gui functionality
is expected by (some) users.
--
♥Ⓐ ng0
PGP keys and more: https://n0is.noblogs.org/ http://ng0.chaosnet.org
next prev parent reply other threads:[~2016-12-29 12:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 11:50 hplip: Add qt5 gui ng0
2016-12-29 11:50 ` [PATCH] gnu: " ng0
2016-12-29 11:56 ` Danny Milosavljevic
2016-12-29 12:29 ` ng0 [this message]
2016-12-29 13:27 ` ng0
2016-12-29 14:05 ` hplip: Add qt5 gui, try to fix policykit support ng0
2016-12-29 14:05 ` [PATCH 1/2] gnu: hplip: Add qt5 gui ng0
2017-01-02 21:04 ` Ludovic Courtès
2016-12-29 14:05 ` [PATCH 2/2] gnu: hplip: Add policykit support ng0
2017-01-15 21:56 ` hplip: Add qt5 gui, try to fix " Andy Patterson
2017-01-15 23:47 ` ng0
2017-01-16 9:58 ` CUPS and HP printers Ludovic Courtès
2017-01-24 1:27 ` ng0
2017-01-27 23:14 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mvfe6hqp.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me \
--to=ng0@libertad.pw \
--cc=dannym@scratchpost.org \
--cc=guix-devel@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.