Bug#843344: Additional package Information

2016-11-05 Thread Bernhard Rieder
I forgot to mention that I am using a custom version of the package with
the described bugfix in place. Therefore the package version number -2
instead of -1.



Bug#843344: pgadmin3 segfaults on start

2016-11-05 Thread Bernhard Rieder
Package: pgadmin3
Version: 1.22.1-2
Severity: grave
Justification: renders package unusable

pgadmin crashes in plugin.cc:383 when obj->GetConnection() returns 0


instead of:
if (!obj || !(obj->GetConnection()->GetStatus() == PGCONN_OK))

it should read:
if (!obj || !obj->GetConnection() || !(obj->GetConnection()->GetStatus() ==
PGCONN_OK))

maybe this is related to my recent upgrade from pg9.5 to pg9.6 (including all
libraries)
another reason could be that I enabled PG debugging of stored procedures
forpg9.5 but not yet for pg9.6

Since it will probably not be fixed on upstream please could you kindly fix it
for the debian package



-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.7.0-rc7-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pgadmin3 depends on:
ii  libc6 2.24-3
ii  libgcc1   1:6.2.0-1
ii  libpq59.6.1-2
ii  libssl1.0.2   1.0.2j-1
ii  libstdc++66.2.0-1
ii  libwxbase3.0-0v5  3.0.2+dfsg-2
ii  libwxgtk3.0-0v5   3.0.2+dfsg-2
ii  libxml2   2.9.4+dfsg1-1
ii  libxslt1.11.1.29-2
ii  pgadmin3-data 1.22.1-2
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages pgadmin3 recommends:
ii  pgagent3.4.1-3
ii  postgresql-client-9.6 [postgresql-client]  9.6.1-2

Versions of packages pgadmin3 suggests:
ii  postgresql-contrib  9.6+177

-- no debconf information



Bug#479528: [xdialog] xdialog does not respect the --editable command line switch

2008-05-05 Thread Bernhard Rieder
Package: xdialog
Version: 2.3.1.dfsg.1-1
Severity: normal

--- Please enter the report below this line. ---

Xdialog --title TEST --editable --combobox enter a number 0x0  1 \
2 3 5 6 7 8

try to enter 4 in the combo box created by the example above


--- System information. ---
Architecture: i386
Kernel:   Linux 2.6.23.12

Debian Release: lenny/sid
  500 unstablewww.emdebian.org 
  500 unstablegd.tuwien.ac.at 
  500 testing www.emdebian.org 
  500 stable  www.emdebian.org 
  500 stable  gd.tuwien.ac.at 
1 experimentalgd.tuwien.ac.at 

--- Package information. ---
Depends (Version) | Installed
=-+-===
libatk1.0-0   (= 1.13.2) | 1.22.0-1
libc6  (= 2.6-1) | 2.7-10
libcairo2  (= 1.4.0) | 1.6.4-1+b1
libfontconfig1 (= 2.4.0) | 2.5.0-2ubuntu3
libglib2.0-0  (= 2.12.9) | 2.16.3-2
libgtk2.0-0(= 2.10.12-3) | 2.12.9-3
libpango1.0-0 (= 1.16.5) | 1.20.2-2
libx11-6  | 2:1.1.3-1
libxcursor1( 1.1.2) | 1:1.1.9-1
libxext6  | 2:1.0.4-1
libxfixes3   (= 1:4.0.1) | 1:4.0.3-2
libxi6| 2:1.1.3-1
libxinerama1  | 2:1.0.3-1
libxrandr2   (= 2:1.2.0) | 2:1.2.2-1
libxrender1   | 1:0.9.4-1





-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#469465: ooimpress eats up all memory when opening a ppt file

2008-03-05 Thread Bernhard Rieder
Hi Rene,

 Eh? So you say Impress is *completely* unusable?

Im not 100% familiar with the bug tracking system but a bug bringing
down the whole system (continously swapping) seems at least to my intuition
grave.

However, I figured it out, that this only occurs, when ooimpress is
started from mutt (I'm not sure if it is run via run-mailcap). I'll try
to figure out what happens exactly.

 Opens fine for me (tried on ppc and amd64).
 I currently can't test with the upstream version to test whether it's
 there, too as it's completely broken (crashes with the message from
 http://www.openoffice.org/issues/show_bug.cgi?id=86268 which we already
 have the fix for in).

When opened directly all works fine (except that the Layout is messed up
since some fonts are missing but I would not consider this a bug), I
just did not try to open it directly.

Thanks for your fast reply,
Bernhard





-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]