Bug#823297: libbotan: security update breaks monotone

2016-05-09 Thread Tim Weippert
HI, 

On Mon, May 09, 2016 at 11:18:42AM +0200, Tim Weippert wrote:
> On Wed, May 04, 2016 at 06:19:25PM +0200, Markus Koschany wrote:
 
[ ... ]
 
> I try to rebuild monotone on the system against the updated lib and get back 
> to you. 

Rebuild of monotone fixed the issue. For more informations ldd/informations of 
mtn pull:

Before Security Update:

root@lab-server01:~/XXX# mtn pull
mtn: doing anonymous pull; use -kKEYNAME if you need authentication
mtn: connecting to 'mtn://XXX/'
mtn:   include pattern  'XXX.*'
mtn:   exclude pattern  ''
mtn: finding items to synchronize:
mtn: certificates | keys | revisions
mtn:   51,019 |  118 |16,837
mtn:  bytes in | bytes out | certs in | revs in
mtn: 1.4 k | 1.5 k |  0/0 | 0/0
mtn: successful exchange with 'XXX'

root@lab-server01:~/XXX# ldd `which mtn`
linux-vdso.so.1 (0x7ffdac731000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x7fee7d5d3000)
libbotan-1.10.so.0 => /usr/lib/libbotan-1.10.so.0 (0x7fee7d0d5000)
liblua5.1.so.0 => /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 
(0x7fee7cea8000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7fee7cbdf000)
libidn.so.11 => /usr/lib/x86_64-linux-gnu/libidn.so.11 
(0x7fee7c9ab000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fee7c79)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7fee7c485000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fee7c184000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7fee7bf6e000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fee7bbc3000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fee7b9a6000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7fee7b796000)
libcrypto.so.1.0.0 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0 
(0x7fee7b39b000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fee7b197000)
libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 
(0x7fee7af14000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fee7ad0c000)
/lib64/ld-linux-x86-64.so.2 (0x7fee7d841000)


After Security Update:

root@lab-server01:~/XXX# mtn pull
mtn: Symbol `_ZTVN5Botan17DataSource_MemoryE' has different size in shared 
object, consider re-linking
mtn: doing anonymous pull; use -kKEYNAME if you need authentication
mtn: connecting to 'mtn://XXX/'
mtn:   include pattern  'XXX'
mtn:   exclude pattern  ''
mtn: finding items to synchronize:
mtn: certificates | keys | revisions
mtn:   51,019 |  118 |16,837
mtn: fatal signal: Segmentation fault
this is almost certainly a bug in monotone.
please send this error message, the output of 'mtn version --full',
and a description of what you were doing to 
<https://code.monotone.ca/p/monotone/issues/>
do not send a core dump, but if you have one, 
please preserve it in case we ask you for information from it.
Segmentation fault

root@lab-server01:~/XXX# ldd `which mtn`
linux-vdso.so.1 (0x7fff3d39)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x7fb7a19f3000)
libbotan-1.10.so.0 => /usr/lib/libbotan-1.10.so.0 (0x7fb7a14f2000)
liblua5.1.so.0 => /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 
(0x7fb7a12c5000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7fb7a0ffc000)
libidn.so.11 => /usr/lib/x86_64-linux-gnu/libidn.so.11 
(0x7fb7a0dc8000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fb7a0bad000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7fb7a08a2000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fb7a05a1000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7fb7a038b000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fb79ffe)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fb79fdc3000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7fb79fbb3000)
libcrypto.so.1.0.0 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0 
(0x7fb79f7b7000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fb79f5b3000)
libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 
(0x7fb79f33)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fb79f128000)
/lib64/ld-linux-x86-64.so.2 (0x7fb7a1c61000)

After Rebuild of monotone:

root@lab-server01:~/XXX# mtn pull
mtn: doing anonymous pull; use -kKEYNAME if you need authentication
mtn: connecting to 'mtn://XXX/'
mtn:   include pattern  'XXX.*'
mtn:   exclude pattern  ''
mtn: finding items to synchronize:
mtn: certificates | keys | revisions
mtn:   51,019 |  118 |16,837
mtn:  bytes in | bytes out | cert

Bug#823297: libbotan: security update breaks monotone

2016-05-09 Thread Tim Weippert
On Wed, May 04, 2016 at 06:19:25PM +0200, Markus Koschany wrote:

[ ... ]

> I can't reproduce the segmentation fault on my system. Could you share
> some information about your setup? What exactly did you do before the
> segfault happened? Did you restart the monotone-server after the
> upgrade? Can you confirm that a rebuild fixes the issue?

It is not the monotone-server i running, it is an mtn update/pull/sync action 
from an
monotone-server. The System is an basic jessie vm on an kvm environment located 
by an hoster.

> I haven't seen other issues with the security update of libbotan1.10 so
> far but if monotone needs a rebuild, this bug should be reassigned to
> monotone.

I try to rebuild monotone on the system against the updated lib and get back to 
you. 

cheers, 
tim

-- 
Tim Weippert
http://weiti.org - we...@weiti.org
GPG Fingerprint - E704 7303 6FF0 8393 ADB1  398E 67F2 94AE 5995 7DD8



Bug#823297: libbotan: security update breaks monotone

2016-05-03 Thread Tim Weippert
Package: libbotan-1.10-0
Version: 1.10.8-2+deb8u1
Severity: grave
File: libbotan
Justification: renders package unusable

Dear Maintainer,

it seems that the recent security update breaks monotone:

mtn: Symbol `_ZTVN5Botan17DataSource_MemoryE' has different size in shared 
object, consider re-linking
mtn: updating along branch 'net.dn42.registry'
mtn: fatal signal: Segmentation fault
this is almost certainly a bug in monotone.
please send this error message, the output of 'mtn version --full',
and a description of what you were doing to 

do not send a core dump, but if you have one, 
please preserve it in case we ask you for information from it.
Segmentation fault

Maybe the bug should also be sent to monotone for rebuilding?

cheers, 
tim

-- System Information:
Debian Release: 8.4
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libbotan-1.10-0 depends on:
ii  libbz2-1.0   1.0.6-7+b3
ii  libc62.19-18+deb8u4
ii  libgcc1  1:4.9.2-10
ii  libgmp10 2:6.0.0+dfsg-6
ii  libssl1.0.0  1.0.1k-3+deb8u4
ii  libstdc++6   4.9.2-10
ii  zlib1g   1:1.2.8.dfsg-2+b1

libbotan-1.10-0 recommends no packages.

libbotan-1.10-0 suggests no packages.

-- no debconf information



Bug#295847: gnome-icon-theme: almost all gnome icons missing or not found!?

2005-02-18 Thread Tim Weippert
hi Loic, 

On Fri, 2005-02-18 at 16:30 +0100, Loïc Minier wrote:
 severity 295847 grave
 reassign 295847 libgtk2.0-bin
 merge 295815 295847
 thanks
 
 Hi,
 
 On ven, fév 18, 2005, Tim Weippert wrote:
  After upgrading the icon theme package i have lots of icons within
  gnome-control-center or evolution ... some applications may not be
  involved (like firefox).
 
  This has been reported against libgtk2.0-bin, we're working on it.
  Workaround: remove the caches.

Thanks for this, the workaround works, is there anything i can help
with?


-- 
Tim Weippert [EMAIL PROTECTED]
GnuPG Fingerprint 63E3 AA72 B3BC D0AB 583E  0382 AEA0 A1F9 AFF9 DC52
http://www.topf-sicret.org/ http://www.luug-hn.org/


signature.asc
Description: This is a digitally signed message part


Bug#295847: gnome-icon-theme: almost all gnome icons missing or not found!?

2005-02-18 Thread Tim Weippert
Hi, 

On Fri, 2005-02-18 at 17:05 +0100, Loïc Minier wrote:
 Hi,
 
 On Fri, Feb 18, 2005, Tim Weippert wrote:
  
  Thanks for this, the workaround works, is there anything i can help
  with?
 
  Thanks to offer your help, some people attempted to find out what is
  wrong, but the developers which were willing to track this down have
  higher priority tasks now and won't debug this further until tomorrow.

Ok, no harm with the workaround :)

  If you know how to debug this, feel free to join #gnome-debian on
  irc.gimp.org (gimpnet), I don't have a PPC Debian myself.

Ok, i think i can't debug this problem alone, but i will look at the
evening in #gnome-debian and offer my help to test or look forward.

bye, 

tim

-- 
Tim Weippert [EMAIL PROTECTED]
GnuPG Fingerprint 63E3 AA72 B3BC D0AB 583E  0382 AEA0 A1F9 AFF9 DC52
http://www.topf-sicret.org/ http://www.luug-hn.org/


signature.asc
Description: This is a digitally signed message part