Your message dated Tue, 5 Sep 2006 13:24:04 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Closing
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: pgadmin3
Version: 1.4.1-1
Severity: normal

Hi,

I tried to follow some adwises written for pgAdmin3 running on a Win machine
as user postgres.  This has some drawbacks because user postgres under Debian
has no writable home directory.  I switched to postgres using

     su -c "su -s /bin/sh postgres"

At first I had to do

     psql template1 -c "ALTER ROLE WITH ENCRYPTED PASSWORD 'password' ;"

to enable user postgres logging into a server using pgAdmin3.  It is
boring in general that pgAdmin3 does not seem to support ident authentication.
At least I had not found out how to log into localhost as a user with
no password which is the default in Debian.  (Should I report this as a
separate bug?)

Then I tried to Edit pg_hba.conf (regarding to the advise mentioned above)
and tried to load the file.  This crashed pgAdmin3 and on the console
I've got the following output:

(pgadmin3:18905): libgnomevfs-WARNING **: Unable to create ~/.gnome2 directory: 
Permission denied
(pgadmin3:18905): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table 
!= NULL' failed
(pgadmin3:18905): libgnomevfs-WARNING **: Internal error: the configuration 
system was not initialized. Did you call _gnome_vfs_configuration_init?
(pgadmin3:18905): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table 
!= NULL' failed
(pgadmin3:18905): libgnomevfs-WARNING **: Internal error: the configuration 
system was not initialized. Did you call _gnome_vfs_configuration_init?
** (pgadmin3:18905): CRITICAL **: ORBit_POA_new_from: assertion `parent != 
CORBA_OBJECT_NIL' failed
** (pgadmin3:18905): CRITICAL **: ORBit_ObjectAdaptor_set_thread_hintv: 
assertion `adaptor != NULL' failed
(pgadmin3:18905): Bonobo-WARNING **: Could not create/get poa 
'BonoboPOAHintPerObject'
libgnomevfs-ERROR **: Can't allocate gnome-vfs client POA
aborting...

This sounds reasonable because user postgres is not able to write into its $HOME
directory by default.  I did not wanted to change this and tried to trick 
pgAdmin3
by just setting

    HOME=/tmp pgadmin3

Unfortunately even this did not really help.  I don't now really whether 
pgAdmin3
is intended to be run as user postgres, but this is nearly the only chance to
edit pg_hba.conf (if you do not want to do it as root).

Kind regards

          Andreas.


-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (501, 'testing'), (50, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages pgadmin3 depends on:
ii  libc6                         2.3.5-8    GNU C Library: Shared libraries an
ii  libgcc1                       1:4.0.2-5  GCC support library
ii  libpq4                        8.1.0-3    PostgreSQL C client library
ii  libstdc++6                    4.0.2-5    The GNU Standard C++ Library v3
ii  libwxgtk2.6-0                 2.6.1.2    wxWidgets Cross-platform C++ GUI t
ii  pgadmin3-data                 1.4.1-1    Graphical administration tool for 

pgadmin3 recommends no packages.

-- debconf-show failed


--- End Message ---
--- Begin Message ---
Hi!

> More than two months have passed without an answer. 
> 
>   drwxr-xr-x 2 postgres postgres 48 2006-07-23 17:55 /var/lib/postgresql
> 
> is the default mode of this directory. I cannot find anything in the
> postgresql-common sources that would change the ownership of it.
> 
> Without any recipe for reproducing this, nor any additional data there
> is nothing I can do about this issue, and I will just close the bug.

Another > 2 months have passed without further information, thus I am
closing this bug now. Please reopen if you have a recipe for
reproducing this bug.

Thank you for your report!

Martin

-- 
Martin Pitt        http://www.piware.de
Ubuntu Developer   http://www.ubuntu.com
Debian Developer   http://www.debian.org

In a world without walls and fences, who needs Windows and Gates?

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to