Your message dated Sat, 2 Apr 2011 09:30:36 +0200
with message-id <[email protected]>
and subject line Re: Bug#608928: icedove: Cannot Attach Files with Semicolon in
Name
has caused the Debian Bug report #608928,
regarding icedove: Cannot Attach Files with Semicolon in Name
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
608928: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608928
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: icedove
Version: 3.0.10-1
Severity: normal
Tags: upstream
It is not possible to attach a file which contains a semicolon in its name.
Icedove erroneously claims that the file does not exist, truncating the name
at the semicolon. For instance, "foo;bar.txt" would result in an error
message claiming that the file "foo" does not exist.
Steps to reproduce:
1. Create a new e-mail
2. Attach any file with a semicolon in its name
3. Attempt to send the e-mail
Expected behavior: E-mail is sent appropriately.
Observed behavior: Erroneous message claiming the absence of the file.
Workaround: Create a copy or hard link of the file whose name does not contain
a semicolon and attach that.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages icedove depends on:
ii debianutils 3.4 Miscellaneous utilities specific t
ii fontconfig 2.8.0-2.1 generic font configuration library
ii libasound2 1.0.23-2.1 shared library for ALSA applicatio
ii libatk1.0-0 1.30.0-1 The ATK accessibility toolkit
ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib
ii libcairo2 1.8.10-6 The Cairo 2D vector graphics libra
ii libdbus-1-3 1.2.24-3 simple interprocess messaging syst
ii libfontconfig1 2.8.0-2.1 generic font configuration library
ii libfreetype6 2.4.2-2.1 FreeType 2 font engine, shared lib
ii libgcc1 1:4.4.5-8 GCC support library
ii libglib2.0-0 2.24.2-1 The GLib library of C routines
ii libgtk2.0-0 2.20.1-2 The GTK+ graphical user interface
ii libjpeg62 6b1-1 The Independent JPEG Group's JPEG
ii libnspr4-0d 4.8.6-1 NetScape Portable Runtime Library
ii libnss3-1d 3.12.8-1 Network Security Service libraries
ii libpango1.0-0 1.28.3-1 Layout and rendering of internatio
ii libpng12-0 1.2.44-1 PNG library - runtime
ii libsqlite3-0 3.7.3-1 SQLite 3 shared library
ii libstartup-notification 0.10-1 library for program launch feedbac
ii libstdc++6 4.4.5-8 The GNU Standard C++ Library v3
ii libx11-6 2:1.3.3-4 X11 client-side library
ii libxrender1 1:0.9.6-1 X Rendering Extension client libra
ii libxt6 1:1.0.7-1 X11 toolkit intrinsics library
ii psmisc 22.11-1 utilities that use the proc file s
ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime
Versions of packages icedove recommends:
ii hunspell-en-us [hunspell-dict 20070829-4 English_american dictionary for hu
Versions of packages icedove suggests:
ii libdbus-glib-1-2 0.88-2 simple interprocess messaging syst
ii libgconf2-4 2.28.1-6 GNOME configuration database syste
ii libgnome2-0 2.30.0-1 The GNOME library - runtime files
ii libgnomevfs2-0 1:2.24.3-1 GNOME Virtual File System (runtime
ii libgssapi-krb5-2 1.8.3+dfsg-3 MIT Kerberos runtime libraries - k
ii ttf-lyx 1.6.7-1 TrueType versions of some TeX font
-- no debconf information
--- End Message ---
--- Begin Message ---
On Fr, Apr 01, 2011 at 05:53:10 -0400, Zachary Palmer wrote:
> Thanks for looking into this. I have since upgraded to Squeeze
> stable and can no longer reproduce the bug. I'm not sure if
> something changed in 3.0.11 or if (more likely) doing the
> dist-upgrade resolved the issue. Either way, it seems we can safely
> close this one. :)
Closed as Zach requested.
--- End Message ---
