Bug#977890: libcinnamon-menu-3-0: Upgrade 4.6.1-1->4.8.2-2 causes segfault when launching any application

[Jeffrey Ratcliffe]

Package: libcinnamon-menu-3-0
Version: 4.8.2-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

Upgraded libcinnamon-menu-3-0 and gir1.2-cmenu-3.0 4.6.1-1->4.8.2-2 and
cinnamon-l10n from 4.6.2-1->4.8.2-2

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

Tried to launch any application from the menus or panel launcher buttons.

   * What was the outcome of this action?

cinnamon segfaulted with casting error, I assume because not all of cinnamon
upgraded.

   * What outcome did you expect instead?

That cinnamon launched the applications with no problem

*** End of the template - remove these template lines ***



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

Kernel: Linux 5.9.0-4-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libcinnamon-menu-3-0 depends on:
ii  libc6 2.31-5
ii  libglib2.0-0  2.66.3-2

libcinnamon-menu-3-0 recommends no packages.

libcinnamon-menu-3-0 suggests no packages.

-- no debconf information

Bug#944995: gtkimageview FTBFS: error: ‘GTypeDebugFlags’ is deprecated

[Jeffrey Ratcliffe]

reassign 944995 ftp.debian.org
thanks

Please remove gtkimageview from unstable. There is no gtk3
version. Upstream is dead. I can't find any reverse dependencies.
It has a popcon vote+old+recent score of 42.



signature.asc
Description: OpenPGP digital signature

Bug#785553: Processed: severity of 785553 is serious, tagging 785553

[Jeffrey Ratcliffe]

On 26/11/17 16:08, Damyan Ivanov wrote:
> [added maintainer of gscan2pdf to CC. gscan2pdf is the only reverse 
> dependency of libgoo-canvas-perl]
>
> goocanvas is deprecated & replaced by goocanvas-2.0. gscan2pdf depends 
> on libgoo-canvas-perl, which uses goocanvas.
>
> Are there any plans to migrate gscanpdf away from 
> libgoocanvas-perl/goocanvas to goocanvas-2.0?
>

I hadn't realised that there was an urgent need to remove goocanvas, and I 
don't understand the severity of the bug, and therefore why gscan2pdf has to be 
removed from testing in December.

I just quickly tested GooCanvas2, and I can't make it work with Gtk2.

This implies to me that I would have to migrate all of gscan2pdf to Gtk3. This 
is certainly a medium-term goal, but is non-trivial.

In particular, I do not know of a Gtk3 equivalent of Gtk2-ImageView.

https://martin.hoppenheit.info/blog/2014/image-scaling-with-gtk3-and-perl/

I'd be grateful if the removal date could be delayed to give me a chance to 
port the Gtk2 stuff to Gtk3. I'd be willing to commit to doing it for Buster.




signature.asc
Description: OpenPGP digital signature

Bug#782361: netgen crashes on launch

[Jeffrey Ratcliffe]

Package: netgen
Version: 4.9.13.dfsg-8+b3
Severity: grave
Justification: renders package unusable

$ netgen 
NETGEN-4.9.13
Developed at RWTH Aachen University, Germany
and Johannes Kepler University Linz, Austria
Including OpenCascade geometry kernel
Parsing ng.tcl
optfile ./ng.opt does not exist - using default values
X Error of failed request:  BadValue (integer parameter out of range for 
operation)
  Major opcode of failed request:  156 (GLX)
  Minor opcode of failed request:  3 (X_GLXCreateContext)
  Value in failed request:  0x0
  Serial number of failed request:  498
  Current serial number in output stream:  499


-- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages netgen depends on:
ii  libc6 2.19-17
ii  libgcc1   1:4.9.2-10
ii  libgl1-mesa-glx [libgl1]  10.3.2-1
ii  libglu1-mesa [libglu1]9.0.0-2
ii  libjpeg62-turbo   1:1.3.1-12
ii  libnglib-4.9.13   4.9.13.dfsg-8+b3
ii  liboce-foundation80.15-5
ii  liboce-modeling8  0.15-5
ii  liboce-ocaf-lite8 0.15-5
ii  liboce-ocaf8  0.15-5
ii  liboce-visualization8 0.15-5
ii  libstdc++64.9.2-10
ii  libtcl8.5 8.5.17-1
ii  libtk8.5  8.5.17-1
ii  libtogl1  1.7-12
ii  libxmu6   2:1.1.2-1
ii  tix   8.4.3-5
ii  tix-dev   8.4.3-5

netgen recommends no packages.

netgen suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#682818: Fwd: Bug#682818: gscan2pdf: Presets aren't working

[Jeffrey Ratcliffe]

On 29 July 2012 04:11, John Goerzen  wrote:
> One more bug: I have to manually change the backend from libsane-perl to
> scanimage-perl each time I run it.  My preference no longer saves, and

That's not a bug - it's a feature. I wrote scanimage-perl as a way of
debugging the libsane-perl module by direct comparison to the
scanimage CLI tool. Please use the scanimage frontend instead.

> libsane-perl doesn't even show the presets at all, and shows tons more
> options than I want in lots of tabs.

I've implemented profiles for the libsane-perl frontend in my
development version, which I think is stable enough to be released
with 1.0.7 - obviously, this won't make wheezy, and I won't upload it
to unstable until after wheezy is released in case we need to fix more
bugs in 1.0.4.

Not presenting all the available options (which is basically what
gscan2pdf does with the CLI frontends) is on my list of things to do.
I'll probably put something in Edit/Preferences to select which
options to present.

Regards

Jeff


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#682100: gscan2pdf Recommends cuneiform which is in non-free

[Jeffrey Ratcliffe]

On 19 July 2012 17:53, Evgeni Golov  wrote:
> From this I think cuneiform can be perfectly moved to Suggests.

I hadn't realised that cuneiform was non-free.

I don't understand why

Recommends: gocr, tesseract-ocr, cuneiform

is not ok. but

Recommends: gocr | tesseract-ocr | cuneiform

is.

Should this be corrected for wheezy?


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#678911: gscan2pdf: Device-dependent options disappear after selecting Lineart mode

[Jeffrey Ratcliffe]

clone 678911 -1
severity -1 normal
retitle -1 profiles not working
thanks

> That did fix that one, though my presents still aren't working (even
> if I resave a new one) -- a much smaller problem, for sure.  For
> instance, if I set threshold and save a preset, then select that
> preset, the threshold is back to 0.  New log attached.

It's not clear to me what is going on here.

Please apply the attached patches to add some extra logging messages.


0004-Log-changing-profile-with-CLI-frontend.patch
Description: Binary data


0001-Support-profiles-from-libsane-perl-dialog-with-scani.patch
Description: Binary data


0003-Fixed-warning-in-lib-Gscan2pdf-Scanner-Options.pm.patch
Description: Binary data

Bug#626019: libsane-perl: Proposal on how to track this down

[Jeffrey Ratcliffe]

On 14 May 2012 22:48, Willi Mann  wrote:
>> I am in half a mind to disable the tests and then deal with any
>> bug reports from the problematic archectures. At least there then
>> might be a user on a suitable machine and motivated to help.
>
> At least for the wheezy release, this sounds like a sane approach to
> me - as long as nobody reports a hang in a real-world scenario.

OK. If I haven't heard any dissenting voices in a few days time, then
I'll go ahead and disable the tests.

Regards

Jeff



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#626019: libsane-perl: Proposal on how to track this down

[Jeffrey Ratcliffe]

It is certainly doable, but my first problem is that I have not
managed to reproduce the issue.

If I could get access to a machine which reliably reproduced the
problem, it would certainly be quicker to add some print statements to
the .xs to work out what was going on rather than spend time on
porting the tests to c.

I am in half a mind to disable the tests and then deal with any bug
reports from the problematic archectures. At least there then might be
a user on a suitable machine and motivated to help.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#669557: ocropus: FTBFS: configure: error: Could not find tesseract! Choose --without-tesseract if you do not want to use it.

[Jeffrey Ratcliffe]

Does anyone have any objections to fixing this by uploaded 0.4.4 from
experimental to unstable?



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#651402: Symbols in iulib

[Jeffrey Ratcliffe]

You seem to be distinguishing between functions declared as inline,
and those inlined by the compiler. My understanding that the compiler
was under no obligation to follow the inline directive, and I don't
see an easy way to check when functions have been inlined or not.

Taking an example - this symbol has disappeared and is not marked as optional:

- _ZN5iulib11ChainTracer9nextpixelEv@Base 0.4.4

It is a function in a struct. I assume it should be optional.

Can you explain?



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#651402: Symbols in iulib

[Jeffrey Ratcliffe]

I've attached the build log.


iulib_0.4.4+ds-2_i386.build
Description: Binary data

Bug#651402: Symbols in iulib

[Jeffrey Ratcliffe]

On 1 April 2012 22:34, Jakub Wilk  wrote:
>> The suggested patch indeed fixes the problem. However, the symbols
>> exported are now updated.
>
> What do you mean?

I get a diff that starts like this, and carries on for a couple of
hundred lines:

dpkg-gensymbols: warning: some new symbols appeared in the symbols
file: see diff output below
dpkg-gensymbols: warning: some symbols or patterns disappeared in the
symbols file: see diff output below
dpkg-gensymbols: warning: debian/libiulib0d/DEBIAN/symbols doesn't
match completely debian/libiulib0d.symbols
--- debian/libiulib0d.symbols (libiulib0d_0.4.4+ds-2_i386)
+++ dpkg-gensymbols9n1RFj   2012-03-31 21:36:53.332455360 +0200
@@ -2,53 +2,67 @@
  _ZN14SDL_extensions13SDL_draw_lineEP11SDL_Surfacej@Base 0.4.4
  
(optional)_ZN5colib4copyIN6imgrle6RLERunES2_EEvRNS_6narrayIT_EERKNS3_IT0_EE@Base
0.4.4
  (optional)_ZN5colib4copyIffEEvRNS_6narrayIT_EERKNS1_IT0_EE@Base 0.4.4
- (optional)_ZN5colib4copyIhfEEvRNS_6narrayIT_EERKNS1_IT0_EE@Base 0.4.4
- (optional)_ZN5colib4copyIhhEEvRNS_6narrayIT_EERKNS1_IT0_EE@Base 0.4.4
- (optional)_ZN5colib4copyIiiEEvRNS_6narrayIT_EERKNS1_IT0_EE@Base 0.4.4
- (optional)_ZN5colib4moveIfEEvRNS_6narrayIT_EES4_@Base 0.4.4
- (optional)_ZN5colib4moveIhEEvRNS_6narrayIT_EES4_@Base 0.4.4
- (optional)_ZN5colib4moveIiEEvRNS_6narrayIT_EES4_@Base 0.4.4
- _ZN5colib5stdioD1Ev@Base 0.4.4
+#MISSING: 0.4.4+ds-2#
(optional)_ZN5colib4copyIhfEEvRNS_6narrayIT_EERKNS1_IT0_EE@Base 0.4.4
+#MISSING: 0.4.4+ds-2#
(optional)_ZN5colib4copyIhhEEvRNS_6narrayIT_EERKNS1_IT0_EE@Base 0.4.4
+#MISSING: 0.4.4+ds-2#
(optional)_ZN5colib4copyIiiEEvRNS_6narrayIT_EERKNS1_IT0_EE@Base 0.4.4
+#MISSING: 0.4.4+ds-2#
(optional)_ZN5colib4moveIfEEvRNS_6narrayIT_EES4_@Base 0.4.4
+#MISSING: 0.4.4+ds-2#
(optional)_ZN5colib4moveIhEEvRNS_6narrayIT_EES4_@Base 0.4.4
+#MISSING: 0.4.4+ds-2#
(optional)_ZN5colib4moveIiEEvRNS_6narrayIT_EES4_@Base 0.4.4
+#MISSING: 0.4.4+ds-2# _ZN5colib5stdioD1Ev@Base 0.4.4



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#651402: Symbols in iulib

[Jeffrey Ratcliffe]

The suggested patch indeed fixes the problem. However, the symbols
exported are now updated. I assume this means that the SONAME should
be bumped.

To what? 0e? How was 0d chosen? d for debian?

The packaging for ocropus should then be updated to fix the dependency
on libiulib0d.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#626019: libsane-perl: FTBFS on kfreebsd-amd64 (test hang?)

[Jeffrey Ratcliffe]

On 26 February 2012 00:44, Jeffrey Ratcliffe  wrote:
> I'm trying to debug the FTBFS of libsane-perl on kfreebsd-amd64[1].
>
> I've KiBi was kind enough to install the build-depends on asdfasdf,
> but I can't reproduce the problem - it builds fine.
>
> Does anyone have any clue what might be causing the FTBFS on
> the kfreebsd-amd64 (and mips, and occasionally sparc) buildd, when on
> asdfasdf, kfreebsd-i386 and all the other architectures things are fine?

Or on another tack - why might the package build fine on asdfasdf,
when it doesn't on the kfreebsd-amd64 buildd?

Regards

Jeff



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#626019: libsane-perl: FTBFS on kfreebsd-amd64 (test hang?)

[Jeffrey Ratcliffe]

I'm trying to debug the FTBFS of libsane-perl on kfreebsd-amd64[1].

I've KiBi was kind enough to install the build-depends on asdfasdf,
but I can't reproduce the problem - it builds fine.

Does anyone have any clue what might be causing the FTBFS on
the kfreebsd-amd64 (and mips, and occasionally sparc) buildd, when on
asdfasdf, kfreebsd-i386 and all the other architectures things are fine?

In all cases, the FTBFS is caused by the tests failing, not the compilation.

Please keep me in CC, as I am not subscribed.

Regards

Jeff

[1] https://buildd.debian.org/status/package.php?p=libsane-perl


signature.asc
Description: Digital signature

Bug#626019: libsane-perl: FTBFS on sparc (test hang?)

[Jeffrey Ratcliffe]

On 15 February 2012 16:35, Salvatore Bonaccorso  wrote:
> I just uploaded libsane-perl 0.04-1 to the archive. And it builded now
> fine on sparc.

Thanks for this.

> *But*: Trying to build the package on smetana.d.o still, sometimes the
> tests hang. I'm not sure if we should downgrade severity here, as the
> cause is not yet clear.

On 9 June 2011 08:19, Salvatore Bonaccorso  wrote:
> t/err.t ... 1/38
>
> Hanging here then.
>
> libsane-dev 1.0.22-3 is installed in the unstable chroot.

In that set of tests, #1 checks that the Sane Perl library can be
found. This must have passed, as all the other tests would have failed
otherwise. #2 checks the status having opened the test backend. I
assume opening the test backend is hanging.

If this continues to be a problem, the next check would be to try the
tests built into scanimage.

Thanks for your work on this.

Regards

Jeff



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#612032: tesseract: rewrite arbitrary user file

[Jeffrey Ratcliffe]

On 23 July 2011 22:42, Jonathan Wiltshire  wrote:
> I'm tying up loose ends and this bug is still outstanding for Squeeze. Do
> you have plans for an upload and would you like any help?

I apologise for not revisiting this in any sane length of time. All of
my (little) time has been taken up with gscan2pdf upstream
development.

I will get to this, but cannot promise when.

Please feel free to NMU this if you wish.

Regards

Jeff



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#626019: libsane-perl: FTBFS on sparc (test hang?)

[Jeffrey Ratcliffe]

Or am I being slow, and this is just because of the Perl 5.12
transition (that being the only change)?



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#626019: libsane-perl: FTBFS on sparc (test hang?)

[Jeffrey Ratcliffe]

I see you are building against libsane 1.0.22-2. Were the previous
successful builds against libsane 1.0.22-2, or another?



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#612032: tesseract: rewrite arbitrary user file

[Jeffrey Ratcliffe]

On 22 March 2011 22:42, Adam D. Barratt  wrote:
> Any news on either of the uploads?

Apologies for the delay. RL is throwing up some issues which are
taking my time at the moment. I hope to get to it at the weekend.

Regards

Jeff



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#612032: tesseract: rewrite arbitrary user file

[Jeffrey Ratcliffe]

On 6 March 2011 23:56, Jakub Wilk  wrote:
> Adam is correct, I bumped b-d to shut up lintian:

Thanks for confirming that.

Jeff



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#612032: tesseract: rewrite arbitrary user file

[Jeffrey Ratcliffe]

Hi Adam,

On 6 March 2011 00:18, Adam D. Barratt  wrote:
> - Testing and unstable have tesseract 2.04-2.1, so the package for
> stable would need to have a lower version than that.  I'd suggest 2.04-2
> +squeeze1, which is conventional.

Sure. This will be my first contribution directly to stable or
oldstable, as I am sure you can tell. I've updated the oldstable
package to also conform.

There was no mention of the convention in the Developers'
Reference[1]. Is this worth a bug report?

> - It would be nice if the reasoning for the quilt build-dep bump was
> mentioned.  My suspicion is that this is due to the use of "dh
> --with-quilt" triggering a lintian warning but this isn't really
> necessary for stable as the relevant quilt version is already included
> there (and the warning has thus been dropped by the version of lintian
> in experimental).

I've dropped it, assuming you are correct, and asked Jakub Wilk, who
prepared the original NMU, to confirm.

>> Would you like separate bugs to be opened for each distribution? At
>> the moment, the same sid/wheezy bug is quoted/closed.
>
> That's fine (and the right way to do it).

Sorry, but your answer is ambigious. Would you like the extra two bugs
opened (and closed)?

I would also suggest that the Developers' Reference could be improved
to confirm this, one way or the other.

Regards

Jeff

[1]http://www.debian.org/doc/developers-reference/pkgs.html#upload-stable


tesseract_2.03-2+lenny1.debdiff
Description: Binary data


tesseract_2.04-2+squeeze1.debdiff
Description: Binary data

Bug#612032: tesseract: rewrite arbitrary user file

[Jeffrey Ratcliffe]

Attached are debdiffs to fix #612032 for the relevant packages in
lenny and squeeze.

Are you happy for these to be uploaded to stable/oldstable?

Would you like separate bugs to be opened for each distribution? At
the moment, the same sid/wheezy bug is quoted/closed.

Regards

Jeff Ratcliffe


tesseract_2.03-3.debdiff
Description: Binary data


tesseract_2.04-3.debdiff
Description: Binary data

Bug#612032: tesseract: diff for NMU version 2.04-2.1

[Jeffrey Ratcliffe]

> I've prepared an NMU for tesseract (versioned as 2.04-2.1) and uploaded it
> to DELAYED/5. Please feel free to tell me if I should delay it longer.

Upload it immediately, if you wish. Thanks for preparing it.

> This xterm-based debug window feature looked very awkward to me, is
> undocumented and not used by default; so I went ahead and disabled it
> entirely.

I didn't even know it existed.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#590453: libgtk2-perl: Gtk2::FileChooserDialog signal produces different response to ->run()

[Jeffrey Ratcliffe]

On 30 July 2010 07:22, Salvatore Bonaccorso
 wrote:
> I wonder, when we uploaded 1.230 I had checked as part, some of the
> patches applied, and dropped these:
>
>  * debian/patches:
>    - Drop gtktreeview_expand.patch applied upstream.
>    - t/GtkPrintSettings.t fixed upstream, drop
>      gtkprintsettings_default_return_values patch.
>    - Drop git-fix-gtkassistant.patch applied upstream.
>    - Drop git-fix-gtkbuildable.patch applied upstream.
>    - Drop git-fix-test-failures-gtkaction.patch. t/GtkAction.t
>      fixed upstream.
>
> Are some of them maybe needed again now? They surely where fixed in
> 1.230.

No. They have all been applied upstream in 1.222.

Regards

Jeff



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#590453: libgtk2-perl: Gtk2::FileChooserDialog signal produces different response to ->run()

[Jeffrey Ratcliffe]

On 28 July 2010 00:42, gregor herrmann  wrote:
>> If no one objects, then I will prepare them for upload.

I've done this now. I spent the best part of a day scratching my head
over how best to deal with the manpage-has-bad-whatis-entry lintian
warnings for the manpages whose PODs don't correspond to a GLib type,
but I've not come up with anything useful.

So if someone would take a look, then I'd be grateful.

Regards

Jeff



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#590453: libgtk2-perl: Gtk2::FileChooserDialog signal produces different response to ->run()

[Jeffrey Ratcliffe]

On 27 July 2010 22:18, Ansgar Burchardt  wrote:
> But versioning seems to follow a scheme: 1.2xy is unstable if and only
> if x is odd.  That should be something we can filter on.  We should make
> sure upstream really uses this system before though.

Well spotted! Thanks. This is true.

http://sf.net/gtk2-perl/Gtk2-(\d+\.\d[02468]\d)\.tar\.gz

works a treat. We should update the watchfiles for the other modules
in the same manner.

I've now tested Gtk2-1.222 and Glib-1.223, where, as expected, the bug
is not present.

If no one objects, then I will prepare them for upload.



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#590453: libgtk2-perl: Gtk2::FileChooserDialog signal produces different response to ->run()

[Jeffrey Ratcliffe]

On 27 July 2010 19:31, gregor herrmann  wrote:
>> I'll talk to upstream about maybe rearranging things so that the tools
>> can distinguish between unstable and stable.
>
> Cool, thanks!
> Let's wait for the outcome before making any further decisions, ok?

Looking further, I see the download page puts 'unstable' fairly
clearly on the appropriate entries:

http://sourceforge.net/projects/gtk2-perl/files/

I'm not a uscan wiz - can you think how to use this to filter them out?

Regards

Jeff



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#590453: libgtk2-perl: Gtk2::FileChooserDialog signal produces different response to ->run()

[Jeffrey Ratcliffe]

On 27 July 2010 16:18, gregor herrmann  wrote:
> What make me a bit unhappy about that is uscan will again show us
> 1.230 if they are in the same directory (and use the same
> filename/versioning scheme).

I'll talk to upstream about maybe rearranging things so that the tools
can distinguish between unstable and stable.

> And 1.230 is not yet in testing, so we now have an unstable version
> in unstable :)

If we package their unstable branch, I think it should be in
experimental. If I understand the system correctly, upstream's
unstable is head, and they cherry-pick patches into stable.

> Either that, or use 1:1.230+is+really+1.220-1.

That would confuse everyone, IMHO.

Regards

Jeff



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#590453: libgtk2-perl: Gtk2::FileChooserDialog signal produces different response to ->run()

[Jeffrey Ratcliffe]

Upstream thinks that it is a new problem with Gtk2/Glib 1.230:

http://mail.gnome.org/archives/gtk-perl-list/2010-July/msg00012.html

At the moment, there is no patch.

I'll test the new stable branches, but I assume they are unaffected,
so I suggest that we upload these. We would have to bump the epoch to
upload 1.222 over 1.230, wouldn't we?



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#590453: libgtk2-perl: Gtk2::FileChooserDialog signal produces different response to ->run()

[Jeffrey Ratcliffe]

This looks a great deal like

https://bugzilla.gnome.org/show_bug.cgi?id=549138

But I'm not sure why we suddenly seeing a problem spotted 2 years ago now.

I also don't understand why we have the unstable branch of Gtk2-Perl
packaged. Surely we should have Gtk2 1.222 and Glib 1.223, which are
the latest stable branches from the end of May.

I've started a discussion on the gtk-perl mailing list.

Todo:

1. try out the patch in the above upstream tracker
2. try out the stable branches
3. decide what to do



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#590453: libgtk2-perl: Gtk2::FileChooserDialog signal produces different response to ->run()

[Jeffrey Ratcliffe]

retitle 590453 libgtk2-perl: Gtk2::Dialog and descendents signal
produces different response to ->run()
thanks

as per attached script


dialog.pl
Description: Binary data

Bug#589796: Bug#590453: libgtk2-perl: Gtk2::FileChooserDialog signal produces different response to ->run()

[Jeffrey Ratcliffe]

severity 590453 serious
block 589796 by 590453
thanks

I've made 590453 serious because 589796 is grave.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#589796: [gscan2pdf-help] Bug#589796: Can't save PDF with gscan2pdf

[Jeffrey Ratcliffe]

On 26 July 2010 09:05, Jeffrey Ratcliffe  wrote:
> I'll install the relevant packages from sid and see why...

It is the Perl bindings for GTK that are the problem. I'll work up a
patch, or if necessary a test case and submit the appropriate bugs.

In the mean time, if you downgrade libgtk2-perl and libglib-perl, then
you should be able to save again.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#589796: [gscan2pdf-help] Can't save PDF with gscan2pdf

[Jeffrey Ratcliffe]

On 25 July 2010 23:53, A. Costa  wrote:
> Scanned a blank page, tried to save as a .PDF and quit.  The log
> is attached.

Thanks for this. It seems the problem is related to GTK2 or the Perl
bindings - the file browser should return 'ok' or 'cancel' on
selecting the filename, but:

DEBUG - PDF save filename dialog returned -5

I'll install the relevant packages from sid and see why...



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#589796: [gscan2pdf-help] Can't save PDF with gscan2pdf

[Jeffrey Ratcliffe]

The logging system was previously just print and warn calls. I've now
replaced all that using Log::Log4perl and added a couple of command
line options to support it. I've uploaded a .deb to
http://launchpadlibrarian.net/52500599/gscan2pdf_0.9.32~1_all.deb

There are no other significant changes, apart from a couple of extra
debugging messages. Please install. You might need a

$ sudo apt-get install liblog-log4perl-perl

first.

If you start the program with

$ gscan2pdf --log=

It will default to 'debug' level messages, which will be printed to
the terminal window and to .

Please do so, reproduce the bug, quit, and post .



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#589796: [Bug 608695] Re: gscan2pdf doesn't save files

[Jeffrey Ratcliffe]

On 24 July 2010 15:19, Christopher <608...@bugs.launchpad.net> wrote:
> Please let me know exactly how to apply patches, as i haven't yet

sudo patch /usr/bin/gscan2pdf < debug.patch



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#589796: [gscan2pdf-help] Can't save PDF with gscan2pdf

[Jeffrey Ratcliffe]

On 24 July 2010 16:14, martin f krafft  wrote:
> Importing does not work either, here is the output:
>
>  Importing /tmp/zweizeiler.pdf
>  Format Portable Document Format
>  Creator:        TeX
>  Producer:       pdfTeX-1.40.10

Although assuming this was a two-liner from pdfTex, it probably didn't
have an image in it, and therefore would have imported nothing anyway.
Can you import an image (PNM, PNG, etc.) or a PDF with an image in it?

Did you apply the patch before producing the debug output?



--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#589796: [gscan2pdf-help] Can't save PDF with gscan2pdf

[Jeffrey Ratcliffe]

Apologies for crossposting the gscan2pdf-help list, Debian, and Ubuntu
bugs, but it makes no sense to have the same conversation three times.

I've installed the main dependencies from sid and still can't reproduce this.

Does it make a difference if the image is imported or scanned?

Please apply the attached patch, which simply adds a couple of
debugging messages so that I can home in on where this coming from,
start gscan2pdf with the --debug option, try to save a PDF, quit, and
post the output from the command line.

Regards

Jeff
diff --git a/bin/gscan2pdf b/bin/gscan2pdf
index 0b03600..881caed 100755
--- a/bin/gscan2pdf
+++ b/bin/gscan2pdf
@@ -3155,7 +3155,9 @@ sub save_PDF {
 $SETTING{'cwd'} = dirname($filename);
 
 # Create the PDF
+print "Started saving $filename...\n" if $debug;
 create_PDF($filename);
+print "Finished saving $filename\n" if $debug;
 
 $windowi->hide if defined $windowi;
}

Bug#589796: saving does not work

[Jeffrey Ratcliffe]

On 22 July 2010 09:03, Nephila  wrote:
> Same problem here. I just updated to 0.9.31-1, but still i I can only save in
> gif, jpeg, png and pnm formats. PDF does not work with any compression format

This is a problem with one of the dependencies, and affects Maverick
too, but not Lucid:

https://bugs.launchpad.net/debian/+source/gscan2pdf/+bug/608695

Can someone test this with squeeze?

Also, please start gscan2pdf with the --debug option, reproduce the
problem, quit, and post the output from the command line.

In the mean time, I'll install the dependencies from sid one by one
and see if I can reproduce the problem.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#589796: saving does not work

[Jeffrey Ratcliffe]

On 21 July 2010 10:14, martin f krafft  wrote:
> PNG works, DjVu/PS or Session does not!

Can you save a PDF with PNG compression?



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#589796: saving does not work

[Jeffrey Ratcliffe]

Can you save any type of file from gscan2pdf? PNG? DjVu?



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#504885: Bug #504885 [tesseract] FTBFS with GCC 4.4: missing #include

[Jeffrey Ratcliffe]

tags 504885 pending
thanks

Thanks for the patch


signature.asc
Description: Digital signature

Bug#531213: gscan2pdf: Hangs saving files with latest imagemagick

[Jeffrey Ratcliffe]

On Tue, Dec 01, 2009 at 08:23:52AM -0800, Michael Vrable wrote:
> For me, the problem went away when ImageMagick was upgraded from
> version 7:6.5.5.3-1 to 7:6.5.7.8-1.  (But I haven't tried
> downgrading to verify that the problem returns with the old
> version.)

That is excellent news. Is anyone still seeing this with the latest
version of ImageMagick in testing or unstable?

Regards

Jeff


signature.asc
Description: Digital signature

Bug#538233: Bug #538233: more info

[Jeffrey Ratcliffe]

severity 538233 normal
tags 538233 moreinfo
thanks

Can you compare the versions of gscan2pdf and its dependencies on your
sid (non-working) desktop and ubuntu (working) laptop?


signature.asc
Description: Digital signature

Bug#531213: gscan2pdf: Hangs saving files with latest imagemagick

[Jeffrey Ratcliffe]

On Tue, Nov 17, 2009 at 04:30:18PM +, Stephen Denton wrote:
> Please let me know if I can provide any information that will help to solve
> the problem.

I cannot reproduce this, but it is certainly a problem with
imagemagick, which gscan2pdf uses for image processing. However, in
order to be able to pass on the problem I need a test image.

Please provide me with an image that, when imported, reproduces the
problem.

Regards

Jeff


signature.asc
Description: Digital signature

Bug#531213: gscan2pdf: Hangs saving files with latest imagemagick

[jeffrey . ratcliffe]

tags 531213 moreinfo
thanks

Bug#538233: Output file diff - the cause

[Jeffrey Ratcliffe]

2009/7/26 Jeffrey Ratcliffe :
> As the PDF creation code hasn't been changed between 0.9.27 and
> 0.9.29, it must be PDF::API2. 0.72 seems to be OK, and 0.73 not.

No. I've tried 0.73 on a couple of machines with no problems.

What is strange is that evidently from the size of the PDF::API2 does
embed the image, but there should be output in the debug log
documenting it.

PDF::API2 depends on libcompress-zlib-perl. What version are you using
with gscan2pdf v0.9.29? Did you have a different version with
gscan2pdf v0.9.27?



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#538233: Output file diff - the cause

[Jeffrey Ratcliffe]

2009/7/26 Robert Kawecki :
> I've generated PDF files from the same source JPEG image (exact same settings:
> JPEG 95%, downsample to 300DPI) on 2 different versions of gscan2pdf: 0.9.29
> and 0.9.27 (from Ubuntu 9.04 on my laptop).

Thanks for all your investigations.

As the PDF creation code hasn't been changed between 0.9.27 and
0.9.29, it must be PDF::API2. 0.72 seems to be OK, and 0.73 not.

I'll do some testing.



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#538233: gscan2pdf exports blank PDF files - debug output

[Jeffrey Ratcliffe]

2009/7/25 Robert Kawecki :
> gscan2pdf was run as: gscan2pdf --debug >debug.log 2>&1
> What I did was importing a JPEG file (tried many times with arbitrary scanned
> and on-disk images, the problem persists), choosing Save and saving it on disk
> as PDF, 300 dpi, 95 embedded JPEG quality.
> I'm attaching the debug log to this message.

Is the jpg imported correctly, i.e. can you see it in the image window?

Argument "\x{30}\x{2c}..." isn't numeric in numeric eq (==) at
/usr/bin/gscan2pdf line 1769.

is a very strange error message for that line number. Would you mind
posting that line of the code to make sure that it is the same line
that I am looking at.

Can you post your jpg so that I can test it?



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#538233: gscan2pdf exports blank PDF files

[jeffrey . ratcliffe]

Please start gscan2pdf with the --debug option, reproduce the problem, and  
post the output from the command line.

Bug#531213: gscan2pdf: Hangs saving files with latest imagemagick

[jeffrey . ratcliffe]

On May 30, 2009 11:57pm, Cameron Hutchison  wrote:

gscan2pdf hangs when saving files. The progress bar just sits at "Saving
page 1 of 1" and does not advance.



When I downgraded package perlmagick from 7:6.5.1.0-1.1 to
7:6.3.7.9.dfsg2-1+b1 (which also required installing libmagick10), the
save functionality returned and the problem was fixed.


I can't reproduce this. I installed 7:6.5.1.0-1.1 and am able to save OK.

Please attach a test image that I can import and which hangs gscan2pdf on  
saving.

Bug#527695: libsane-perl: FTBFS: Sane.xs:372: error: 'SANE_CAP_ALWAYS_SETTABLE' undeclared (first use in this function)

[Jeffrey Ratcliffe]

2009/5/8 Niko Tyni :
> sane-backends 1.0.20 removed SANE_CAP_ALWAYS_SETTABLE, because "is _not_ part 
> of the current
> stable API."

The really frustrating part about this is that when I wrote the
bindings, I deliberately started with SANE 1.0.19, and not what was in
HEAD. I expected, therefore, to have to add things, but never to have
to remove them unless there was a API change.

The next question is whether SANE_CAP_ALWAYS_SETTABLE is actually used
by any of the backends in 1.0.19. If not, then I can just remove it
from libsane-perl. Otherwise, I've got to go for the #ifdefs.

I guess that for sid, though, they can just be removed, as sid is
never going to see 1.0.19 again.

I'll ask on sane-devel.

Regards

Jeff



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#479922: libxml-sax-writer-perl: FTBFS: rmdir: failed to remove `/build/user/libxml-sax-writer-perl-0.50/debian/libxml-sax-writer-pe rl/usr/lib/perl5': No such file or directory

[Jeffrey Ratcliffe]

tags 479922 + patch
thanks

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

The attached patch seems to fix this in my sid chroot

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: http://getfiregpg.org

iD8DBQFIQGjqVDAgnE3XzJMRAmmsAKC1BNU0Uqcu/BxBGngwOT0QZzYWhQCdHnJj
Uz0V8vGiFyLcL/NVa2b/Goc=
=wgf6
-END PGP SIGNATURE-
--- libxml-sax-writer-perl-0.50.orig/debian/rules
+++ libxml-sax-writer-perl-0.50/debian/rules
@@ -32,7 +32,7 @@
 	dh_clean -k
 	$(MAKE) test
 	$(MAKE) install DESTDIR=$(TMP) PREFIX=/usr
-	rmdir --ignore-fail-on-non-empty --parents $(TMP)/usr/lib/perl5
+	[ ! -d $(TMP)/usr/lib/perl5 ] || rmdir --ignore-fail-on-non-empty --parents $(TMP)/usr/lib/perl5
 	touch install-stamp
 
 binary-arch:
--- libxml-sax-writer-perl-0.50.orig/debian/changelog
+++ libxml-sax-writer-perl-0.50/debian/changelog
@@ -1,3 +1,12 @@
+libxml-sax-writer-perl (0.50-1.2) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * debian/rules:
++ Don't fail when perl is smart enough not to create empty dirs. (Closes:
+  #479922)
+
+ -- Jeffrey Ratcliffe <[EMAIL PROTECTED]>  Fri, 30 May 2008 22:40:15 +0200
+
 libxml-sax-writer-perl (0.50-1.1) unstable; urgency=low
 
   * Non-maintainer upload.

Bug#479934: renrot: FTBFS: rmdir: failed to remove `/build/user/renrot-0.25/debian/renrot/usr/lib/perl5': No such file or directory

[Jeffrey Ratcliffe]

tags 479934 + patch
thanks

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

The attached patch seems to fix the FTBFS in my newly-build sid chroot.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: http://getfiregpg.org

iD8DBQFIPxxpVDAgnE3XzJMRAmkgAKDsshWUr2tINp0zDPjNQdSUV7mKSQCfWXWF
Pu4W02IyK3+EjZj07CTIizM=
=5XCN
-END PGP SIGNATURE-
--- renrot-0.25.orig/debian/rules
+++ renrot-0.25/debian/rules
@@ -61,9 +61,9 @@
 	# Add here commands to install the package into debian/renrot.
 	$(MAKE) install PREFIX=$(CURDIR)/debian/renrot/usr
 	# remove empty dirs
-	rmdir $(CURDIR)/debian/renrot/usr/lib/perl5
-	rmdir $(CURDIR)/debian/renrot/usr/lib
-	rmdir $(CURDIR)/debian/renrot/usr/share/perl5
+	[ ! -d $(CURDIR)/debian/renrot/usr/lib/perl5 ] || rmdir $(CURDIR)/debian/renrot/usr/lib/perl5
+	[ ! -d $(CURDIR)/debian/renrot/usr/lib ] || rmdir $(CURDIR)/debian/renrot/usr/lib
+	[ ! -d $(CURDIR)/debian/renrot/usr/share/perl5 ] || rmdir $(CURDIR)/debian/renrot/usr/share/perl5
 	# install sample configuration files
 	install -m644 etc/colors.conf $(CURDIR)/debian/renrot/etc/renrot/
 	install -m644 etc/copyright.tag $(CURDIR)/debian/renrot/etc/renrot/
--- renrot-0.25.orig/debian/changelog
+++ renrot-0.25/debian/changelog
@@ -1,3 +1,10 @@
+renrot (0.25-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Fix FTBFS against Perl 5.10 (closes: #479934)
+
+ -- Jeffrey Ratcliffe <[EMAIL PROTECTED]>  Thu, 29 May 2008 22:05:34 +0200
+
 renrot (0.25-1) unstable; urgency=low
 
   * Initial release (Closes: #397577)

Bug#464205: Error compressing empty files

[Jeffrey Ratcliffe]

The test program submitted did not show the bug (which nevertheless
exists). So here is a patch for the test program, plus a patch to fix
the bug.
--- bzip2test.orig	2008-05-21 23:25:24.0 +0200
+++ bzip2test	2008-05-21 23:25:19.0 +0200
@@ -36,12 +36,12 @@
 print "Error reading from '$file': $!";
 close SOURCE;
 }
-last if $bytesread == 0;
 my $byteswritten = $bz->bzwrite($buffer);
 if ($byteswritten < $bytesread) {
 print "Error bzwriting to temporary file: " . $bz->bzerror;
 close SOURCE;
 }
+last if $bytesread == 0;
 }
 
 my $bzflush = $bz->bzflush(BZ_FINISH);
--- libcompress-bzip2-perl-2.09.orig/Bzip2.xs
+++ libcompress-bzip2-perl-2.09/Bzip2.xs
@@ -1485,8 +1485,6 @@
 return -2;
   }
 
-  if (nUncompressed == 0) return 0;
-
   while (True) {
 if ( obj->run_progress == 0 ) {
   ret = BZ2_bzCompressInit ( &(obj->strm), obj->blockSize100k, obj->verbosity, obj->workFactor );
@@ -2253,12 +2251,10 @@
 else
   bufp = SvPV(buf, len);
 
-if (len) {
-  RETVAL = bzfile_write( obj, bufp, len);
+RETVAL = bzfile_write( obj, bufp, len);
 
-  if ( RETVAL > 0 )
+if ( RETVAL > 0 )
 	SvCUR_set( buf, RETVAL );
-}
   }
 
   OUTPUT:
--- libcompress-bzip2-perl-2.09.orig/debian/changelog
+++ libcompress-bzip2-perl-2.09/debian/changelog
@@ -0,0 +1,26 @@
+libcompress-bzip2-perl (2.09-1.2) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Fix bug compressing empty files (closes: #464205)
+
+ -- Jeffrey Ratcliffe <[EMAIL PROTECTED]>  Wed, 21 May 2008 20:55:33 +0200
+
 libcompress-bzip2-perl (2.09-1.1) unstable; urgency=low
 
   * Non-maintainer upload.

Bug#451042: Should be marked as replaces: tesseract-ocr-data

[Jeffrey Ratcliffe]

> the packages for tesseract 2.0 have changed, and tesseract-ocr now
> provides some of the same files that tesseract-ocr-data 1.02-3 provided.

> This makes the 2.0 package un-installable for those that have
> tesseract-ocr-data 1.02-3 installed due to a file conflict.

tesseract-ocr 2.01 depends on a language pack, e.g. tesseract-ocr-eng.
All the language packs have

Replaces: tesseract-ocr-data



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