Bug#884311: gajim doesn't start after python-openssl upgrade

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#884311: gajim doesn't start after python-openssl upgrade

Dimitris
Package: gajim
Version: 0.16.8-5
Severity: normal

Dear Maintainer,

   * What led up to the situation?

upgrading python-openssl package and gajim can't start anymore

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

open gajim from menu or console.  

   * What was the outcome of this action?

error message :
~ gajim            
Traceback (most recent call last):
  File "gajim.py", line 307, in <module>
    OpenSSL.rand.load_file(str(RNG_SEED))
AttributeError: 'module' object has no attribute 'load_file'

   * What outcome did you expect instead?

normal start of gajim.

After reverting to testing version of python-openssl, gajim works as
expected.

I know it seems to be caused from python-openssl, but maybe its more
relevant to gajim instead(?) that's why i'm filling bug here. but please
reassign packages as you think best.

thanks,
d.


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

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

Versions of packages gajim depends on:
ii  dnsutils        1:9.11.2+dfsg-5
ii  python          2.7.14-3
ii  python-gtk2     2.24.0-5.1+b1
ii  python-nbxmpp   0.6.1-1
ii  python-openssl  16.2.0-1
ii  python-pyasn1   0.1.9-2

Versions of packages gajim recommends:
ii  alsa-utils                                      1.1.3-1
ii  ca-certificates                                 20170717
ii  dbus                                            1.12.2-1
ii  mate-notification-daemon [notification-daemon]  1.18.1-1
ii  notification-daemon                             3.20.0-1+b1
ii  pulseaudio-utils                                11.1-4
ii  python-crypto                                   2.6.1-8
ii  python-dbus                                     1.2.4-1+b4
ii  python-gnupg                                    0.4.1-1

Versions of packages gajim suggests:
ii  aspell-en [aspell-dictionary]  2017.08.24-0-0.1
ii  avahi-daemon                   0.7-3
pn  dvipng                         <none>
ii  gnome-keyring                  3.20.1-1
pn  gstreamer0.10-plugins-ugly     <none>
pn  kwalletcli                     <none>
ii  libgtkspell0                   2.0.16-1.1
ii  libxss1                        1:1.2.2-1+b2
pn  nautilus-sendto                <none>
ii  network-manager                1.10.2-1
pn  python-avahi                   <none>
pn  python-gconf                   <none>
pn  python-gnome2                  <none>
pn  python-gnomekeyring            <none>
pn  python-gupnp-igd               <none>
pn  python-kerberos                <none>
ii  python-pycurl                  7.43.0-2+b1
pn  texlive-latex-base             <none>

-- no debconf information

Reply | Threaded
Open this post in threaded view
|

Bug#884311: Gajim: problem with latest python-openssl

W. Martin Borgert
Dear Bjoern, dear Dimitris,

thank you for your bug reports! I ask you for a favour:

Could you please try Gajim from Debian experimental?
The plugins for the new Gajim are in experimental, too,
if you need them.

I'm not yet sure, whether I will fix this bug in a new
Gajim 0.16.8-something, because IMHO Gajim
0.16.11-somethingelse already works very fine for me.

If the new Gajim works for you as well, I would do the
next upload to unstable instead of experimental.

Thanks in advance!

Cheers, Martin

Reply | Threaded
Open this post in threaded view
|

Bug#884311: Gajim: problem with latest python-openssl

Dimitris
Hey Martin, all

Just installed it from experimental, it brings a lot of python3-*
dependencies instead of the python-* ones in unstable, but it starts
normally as expected.
got some other errors and a database error(fixed), but this bug is no
longer there. gajim starts ok.

i must say i prefer the old looks of gajim (dont really like the gnome3
approach) but that's something personal, usability is what counts more.
so i would also be in favor of porting it to unstable.

thanks,

dimitris.


On 12/15/2017 03:01 PM, W. Martin Borgert wrote:

> Dear Bjoern, dear Dimitris,
>
> thank you for your bug reports! I ask you for a favour:
>
> Could you please try Gajim from Debian experimental?
> The plugins for the new Gajim are in experimental, too,
> if you need them.
>
> I'm not yet sure, whether I will fix this bug in a new
> Gajim 0.16.8-something, because IMHO Gajim
> 0.16.11-somethingelse already works very fine for me.
>
> If the new Gajim works for you as well, I would do the
> next upload to unstable instead of experimental.
>
> Thanks in advance!
>
> Cheers, Martin
>


signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Bug#884311: Bug#884358: Bug#884311: Gajim: problem with latest python-openssl

W. Martin Borgert
Quoting Dimitris <[hidden email]>:
> i must say i prefer the old looks of gajim (dont really like the gnome3
> approach) but that's something personal, usability is what counts more.
> so i would also be in favor of porting it to unstable.

Thanks, Dimitris, for your super-fast test and reply!

Well, about the new look, that's not something I'm able to influence
and the new version is coming sooner or later anyway. But upstream
is very open to suggestions, also about making Gajim look good in
DEs other than Gnome. So it might improve!

If there are no further blockers I'll upload the new Gajim (and all
the plugins) to unstable in the next days.

Cheers

Reply | Threaded
Open this post in threaded view
|

Bug#884311: Bug#884358: Bug#884311: Gajim: problem with latest python-openssl

bes (Bugzilla)
In reply to this post by Dimitris
Hi all,

same here. The version from experimental works fine for me and I like
the new Gnome3 look&feel. Only drawback, I can no longer install
plugins directly from gajim with the plugin manager. Probably because
this is not a final release yet. But as the most important plugins are
packaged I would be fine with moving this to unstable.

Thanks!
BJörn

On Fri, 15 Dec 2017 15:51:00 +0200 Dimitris wrote:

> Hey Martin, all
>
> Just installed it from experimental, it brings a lot of python3-*
> dependencies instead of the python-* ones in unstable, but it starts
> normally as expected.
> got some other errors and a database error(fixed), but this bug is no
> longer there. gajim starts ok.
>
> i must say i prefer the old looks of gajim (dont really like the
> gnome3 approach) but that's something personal, usability is what
> counts more. so i would also be in favor of porting it to unstable.
>
> thanks,
>
> dimitris.
>
>
> On 12/15/2017 03:01 PM, W. Martin Borgert wrote:
> > Dear Bjoern, dear Dimitris,
> >
> > thank you for your bug reports! I ask you for a favour:
> >
> > Could you please try Gajim from Debian experimental?
> > The plugins for the new Gajim are in experimental, too,
> > if you need them.
> >
> > I'm not yet sure, whether I will fix this bug in a new
> > Gajim 0.16.8-something, because IMHO Gajim
> > 0.16.11-somethingelse already works very fine for me.
> >
> > If the new Gajim works for you as well, I would do the
> > next upload to unstable instead of experimental.
> >
> > Thanks in advance!
> >
> > Cheers, Martin
> >  
>
>



--
Björn Schießle <[hidden email]>
www: http://www.schiessle.org
twitter: @schiessle
gnupg/pgp key: 0x0x2378A753E2BF04F6
verify: https://keybase.io/BeS
fingerprint: 244F CEB0 CB09 9524 B21F B896 2378 A753 E2BF 04F6

Reply | Threaded
Open this post in threaded view
|

Bug#884311: Bug#884358: Bug#884311: Gajim: problem with latest python-openssl

W. Martin Borgert
Thanks, Bjoern, too!

Quoting Bjoern Schiessle <[hidden email]>:
> Only drawback, I can no longer install
> plugins directly from gajim with the plugin manager. Probably because
> this is not a final release yet.

Yes, this is something I like to repair. The plugin manager should be
disabled by default, but easy to activate.

> But as the most important plugins are
> packaged I would be fine with moving this to unstable.

Great!