Debian Bug report logs - #243219
debconf: Initialises frontend even when not using it

Reply or subscribe to this bug.

Display info messages

Message #5 received at [email protected] (full text, mbox, reply):

From: Morten Brix Pedersen <[email protected]>

To: Debian Bug Tracking System <[email protected]>

Subject: debconf: Initialises frontend even when not using it

Date: Sun, 11 Apr 2004 23:44:19 +0200

Package: debconf
Version: 1.4.21
Severity: minor

Hi,

Debconf tries to initialise a frontend, even when not showing a debconf
note. For example:

Preparing to replace flex 2.5.31-23 (using .../flex_2.5.31-24_i386.deb) ...
Gtk-WARNING **: cannot open display:   at /usr/share/perl5/Debconf/FrontEnd/Gnome.pm line 47.
debconf: unable to initialize frontend: Gnome
debconf: (DISPLAY problem?)
debconf: falling back to frontend: Dialog
Unpacking replacement flex ...


There is no reason for this warning, because debconf didn't even show a
note here (might be some low-priority question that isn't being shown?).

If you need more info, please don't hesitate to ask.


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.5
Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8

Versions of packages debconf depends on:
ii  debconf-i18n                  1.4.21     full internationalization support 
ii  perl-base                     5.8.3-3    The Pathologically Eclectic Rubbis

-- debconf information:
* debconf/priority: medium
* debconf/frontend: Gnome

Message #10 received at [email protected] (full text, mbox, reply):

From: Alexis Sukrieh <[email protected]>

To: [email protected]

Cc: Joey Hess <[email protected]>, Morten Brix Pedersen <[email protected]>

Subject: Analysis

Date: Sun, 3 Oct 2004 01:42:27 +0200

Well, after looking at the debconf code, it really seems that this
problem cannot be avoided without changing the way debconf initializes
Frontends.

When debconf is called, it first tries to initialize the user-choosen
frontend, which means including the appropriate Perl API.

If this include fails, debconf send a warning to the user, which is
quite normal.

The bug undelined here, would require to implement the availability of
knowing if we will use the frontend at least one time before ending the
debconf process...

In ohter words, we should first look at what will be done in the debconf
session, and then, initialize or not the frontend if we have at least
one communication to make with the user...

That sounds really like a big architectural revolution and I'm not sure
that's what we (patch submitters) are supposed to do...

Tell me if I'm wrong Jo ;)

Alexis.

-- 
Alexis Sukrieh <[email protected]>
 * Another Linux Debian Geek Enthusiast
 * http://www.sukria.net
   

Send a report that this bug log contains spam.