Bug 246085 - Can't create attachment using Seamonkey 1.0.9 on FC6
Summary: Can't create attachment using Seamonkey 1.0.9 on FC6
Status: CLOSED WORKSFORME
Alias: None
Product: Bugzilla
Classification: Community
Component: User Interface   
(Show other bugs)
Version: 2.18
Hardware: i386 Linux
low
low vote
Target Milestone: ---
Assignee: David Lawrence
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-06-28 13:40 UTC by John E. Harbold
Modified: 2007-09-04 16:21 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-09-04 16:21:12 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description John E. Harbold 2007-06-28 13:40:33 UTC
Description of problem:

For Bugzilla #242604, whenever I tried to create an attachment and send it, a 
message window would say I didn't specify a file.


Version-Release number of selected component (if applicable):

Bugzilla 2.18-rh


How reproducible:

Every time.

Steps to Reproduce:
1. Click on the "create attachment".
2. Enter the pathname and filename of file to attach.
3. Enter file description text.
4. Enter summary text.
5. Submit change.
  
Actual results:

No File Specified
You did not specify a file to attach.

Please press Back and try again.

Expected results:

The attachment should have been accepted.

Additional info:

My system is Fedora Core 6, kernel 2.6.20-1.2952.fc6, Pentium II 450 MHz.
I'm using Seamonkey 1.0.9.  I switched to Konqueror 3.5.6-0.1.fc6 and set the 
patch checkbox and was able to send.

Comment 1 David Lawrence 2007-09-04 16:11:06 UTC
I will need to install seamonkey 1.0.9 and attempt to verify this is a problem.

Comment 2 David Lawrence 2007-09-04 16:21:12 UTC
I was able to attach properly using latest version of SeaMonkey 1.1.3. Please
try this with the latest version and reopen if still a problem.


Note You need to log in before you can comment on or make changes to this bug.