Bug 1063 – Bug writing to files using "QTextStream + QFile + QTextEdit" on Linux

PySide Bugzilla Closed for New Bugs

PySide is now a Qt Add-on and uses the Qt Project's JIRA Bug Tracker instead of this Bugzilla instance. This Bugzilla is left for reference purposes.

Bug 1063 - Bug writing to files using "QTextStream + QFile + QTextEdit" on Linux

Summary:

Bug writing to files using "QTextStream + QFile + QTextEdit" on Linux

Status:	CLOSED FIXED

Product:	PySide
Classification:	Unclassified
Component:	QtCore
Version:	1.0.8
Platform:	PC Linux

Importance:	P1 major
Assigned To:	Paulo Alcantara

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2011-11-17 17:20 EET by Giovanni Max Gaspar Filho
Modified:	2012-01-02 21:44 EET (History)
CC List:	10 users (show)

See Also:

Attachments
Bug's example (3.60 KB, application/x-rar) 2011-11-17 17:20 EET, Giovanni Max Gaspar Filho	Details
Add an attachment (proposed patch, testcase, etc.)

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

Description Giovanni Max Gaspar Filho 2011-11-17 17:20:41 EET

Created attachment 451 [details]
Bug's example

When using a QTextStream to write to files a "QTextEdit's text", the file will
be blank. I tested on Linux and Windows and it just happened on Linux (Ubuntu
10.04). Anyway, it started to happen just when I updated the PySide from
version 1.0.7 to version 1.0.8... 

For more details, see the example in the attachment

Comment 1 Paulo Alcantara 2011-12-06 17:27:34 EET

Hi Giovanni,

I can't reproduce this bug here. The saved file contains the data I wrote in
the text area. Which Python version did you test it with ?

Comment 2 Giovanni Max Gaspar Filho 2011-12-06 17:30:08 EET

(In reply to comment #1)
> Hi Giovanni,
> 
> I can't reproduce this bug here. The saved file contains the data I wrote in
> the text area. Which Python version did you test it with ?

I used the version 1.0.8 and tested with the version 1.0.9... This "bug" can
just be reproduced on ubuntu (I used the version 10.04). Windows is "OK" (100%
working).

Comment 3 Giovanni Max Gaspar Filho 2011-12-06 17:31:02 EET

(In reply to comment #2)
> (In reply to comment #1)
> > Hi Giovanni,
> > 
> > I can't reproduce this bug here. The saved file contains the data I wrote in
> > the text area. Which Python version did you test it with ?
> 
> I used the version 1.0.8 and tested with the version 1.0.9... This "bug" can
> just be reproduced on ubuntu (I used the version 10.04). Windows is "OK" (100%
> working).

Sorry... I forgot to put the Python version: Python 2.6.5

Comment 4 Paulo Alcantara 2011-12-06 17:40:29 EET

(In reply to comment #3)
> (In reply to comment #2)
> > (In reply to comment #1)
> > > Hi Giovanni,
> > > 
> > > I can't reproduce this bug here. The saved file contains the data I wrote in
> > > the text area. Which Python version did you test it with ?
> > 
> > I used the version 1.0.8 and tested with the version 1.0.9... This "bug" can
> > just be reproduced on ubuntu (I used the version 10.04). Windows is "OK" (100%
> > working).

Was the Python version 2.6.5 used on both Windows and Linux ?

> 
> Sorry... I forgot to put the Python version: Python 2.6.5

Comment 5 Giovanni Max Gaspar Filho 2011-12-06 17:42:55 EET

(In reply to comment #4)
> (In reply to comment #3)
> > (In reply to comment #2)
> > > (In reply to comment #1)
> > > > Hi Giovanni,
> > > > 
> > > > I can't reproduce this bug here. The saved file contains the data I wrote in
> > > > the text area. Which Python version did you test it with ?
> > > 
> > > I used the version 1.0.8 and tested with the version 1.0.9... This "bug" can
> > > just be reproduced on ubuntu (I used the version 10.04). Windows is "OK" (100%
> > > working).
> 
> Was the Python version 2.6.5 used on both Windows and Linux ?
> 
> > 
> > Sorry... I forgot to put the Python version: Python 2.6.5

yes... I also tested that program on a cleaned Virtual Machine running ubuntu
10.04 too and i had the same issue

Comment 6 Paulo Alcantara 2011-12-09 19:15:29 EET

Hi,

Thanks for the report!

This bug has been fixed on PySide commit
0a4d2f272c084354b3ae74dc9f060dd41e868b8c.