bugbananapos - Bugs: bug #4529, Switching between open...

 
 

bug #4529: Switching between open transactions with F4 frequently causes a segmentation fault

Submitted by:  Rick Richard <rrichard>
Submitted on:  Tue 29 Jul 2003 10:33:50 PM UTC  
 
Category: ClientSeverity: 9 - Critical
Item Group: NoneStatus: Fixed
Privacy: PublicAssigned to: Al Kingsley <bananas>
Open/Closed: Closed

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Thu 31 Jul 2003 08:05:34 AM UTC, comment #5:

Ok, done.

Al Kingsley <bananas>
Project AdministratorIn charge of this item.
Wed 30 Jul 2003 05:03:28 PM UTC, comment #4:

Half of why I was using multitrans mode was for that reason--to disable on-the-fly printing... Just my $0.02: with the speed of modern POS printers, on-the-fly is probably not necessary. If it is kept for whatever reason, however, is there another way to disable it than enabling multitrans?

Rick Richard <rrichard>
Project Member
Wed 30 Jul 2003 10:14:10 AM UTC, comment #3:

I should probably clarify this point - it's another unrelated bug. But related in a minor way to trans swap payment summaries in multiopen trans mode, and single trans mode. The former works fine in most cases, but sometimes fucks up on swap printing. The latter is similiar, but on the fly printing is dodgey at best, and might be dropped (trans cancel?, item removal?, etc. - printed receipt corrections can make for a long receipt - and make it almost unreadable with heavy editing).

Al Kingsley <bananas>
Project AdministratorIn charge of this item.
Wed 30 Jul 2003 09:49:32 AM UTC, comment #2:

Ok, the seg fault wasn't hard to clear up, and the swap works up to the point of operation. But it's going take a little more time yet, as the printer has a minor spew problem on payment types on a swap with on the fly printing (a long overdue bug). It's in progress.

Al Kingsley <bananas>
Project AdministratorIn charge of this item.
Wed 30 Jul 2003 03:46:19 AM UTC, comment #1:

OK, I realize my statement is a little ambiguous. It's not frequent switching, rather switching frequently segfaults.

Scan an item, F4, scan another item, F4 again and the first item is either missing or the client will segfault. If the first item is missing, scan again and client will segfault.

Rick Richard <rrichard>
Project Member
Tue 29 Jul 2003 10:33:50 PM UTC, original submission:
Rick Richard <rrichard>
Project Member

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

Do you think this task is very important?
If so, you can click here to add your encouragement to it.
This task has 0 encouragements so far.

Only logged-in users can vote.

 

Please enter the title of George Orwell's famous dystopian book (it's a date):

 

 

Follow 4 latest changes.

Date Changed By Updated Field Previous Value => Replaced By
Thu 31 Jul 2003 08:05:34 AM UTCbananasStatusNone=>(Error - Not Found)
  Open/ClosedOpen=>(Error - Not Found)
Wed 30 Jul 2003 10:14:10 AM UTCbananasSeverity5 - Major=>(Error - Not Found)
Wed 30 Jul 2003 07:10:51 AM UTCbananasAssigned toNone=>NA

Back to the top


Powered by Savane 3.1-cleanup1