Dear Mattia,

Yes, I'm the same person. I don't know why CERN mailer does not accept your address. However, some time ago the same happened to my University e-mail - I couldn't send e-mail to any CERN address.


Regarding the bug - the problem has also disappeared in the affected system.
I'm afraid it could be caused by a partial update?
After I've performed the next "apt-get update; apt-get dist-upgrade", I was not able to reprodecue this bug any more.

So probably you can mark this bug as "fixed" or even as "invalid".

With best regards,
Wojtek

On 18.09.2016 14:13, Mattia Rizzolo wrote:
The cern.ch SMTP doesn't like my mail setup (or I wonder anybody's, if
the issue is that the debian.org domain has no SPF record..)
See the bounce I received:
https://volatile.mapreri.org/2016-09-18/6d35f3e5d7186d5276b26ef8760628cb/Inbox.pdf
So I'm forwarding your email to your other address, assuming you are the
same person :)

If you reply to this email, please put the bug address in CC.

----- Forwarded message from Mattia Rizzolo<mat...@debian.org>  -----

Date: Sun, 18 Sep 2016 10:03:33 +0000
From: Mattia Rizzolo<mat...@debian.org>
To: Wojciech Zabolotny<wojciech.zabolo...@cern.ch>
Cc:837...@bugs.debian.org
Subject: Re: Bug#837751: scribus: When I try to do "get Image" for a graphics 
frame, scribus segfaults
Message-ID:<20160918100333.7ivomcgoblhak...@chase.mapreri.org>
User-Agent: Every email client sucks, this one just sucks less.

On Wed, Sep 14, 2016 at 04:40:57PM +0200, Wojciech Zabolotny wrote:
I assume by your "whenever" that it is steadily reproducible.
Can you try to temporary move away your ~/.scribus and see if the bug is
reproducible?

Indeed, renaming of ~/.scribus has cured the problem.
I couldn't reproduce the segfault with your .sla, and if I looked up the
upstream bug tracker correctly nobody else experienced segfaults
recently.
According to the core dump the crash happens somewhere in the middle of
dbus, and I couldn't even figure how it reached that point (here gdb
says "Backtrace stopped: previous frame inner to this frame (corrupt
stack?)" after #14).

Anyway, I'm tempted to close this bug as it was really easily "fixed" by
moving away your ~/.scribus directory.  probably some file in there
somehow was corrupted or got invalid data in your computer.



--
Wojciech M Zabolotny, PhD
Faculty Coordinator for International Student Mobility
Faculty of Electronics and Information Technology
Warsaw University of Technology

Reply via email to