[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#570254: openoffice.org-calc: consistently crashes on sheet operations



# maybe even 3.1.0, but of course the info is not enough...
found 570254 1:3.1.1-8
reassign 570254 openoffice.org-kde
# maybe even earlier, but this is tested
close 570254 1:3.2.0-1
thanks

On Wed, Feb 17, 2010 at 02:49:30PM -0200, pedro bulach gapski wrote:
> Package: openoffice.org-calc
> Version: 1:3.1.1-15+squeeze1
> Severity: grave
> Justification: causes non-serious data loss
> 
> oocalc consistently crashes on Sheet operations. For instance, open a new 
> calc window, and drag Sheet1 to between Sheets 2 and 3: it crashes with 
> the following message on de console:
> gapski@kalma:~$ SAL_SYNCHRONIZE=1 oocalc
> gapski@kalma:~$ QPixmap: It is not safe to use pixmaps outside the GUI thread
> QPixmap: It is not safe to use pixmaps outside the GUI thread
> QPixmap: It is not safe to use pixmaps outside the GUI thread
> QPainter::begin: Cannot paint on a null pixmap
> X-Error: BadDrawable (invalid Pixmap or Window parameter)
>         Major opcode: 62 (X_CopyArea)
>         Resource ID:  0x0
>         Serial No:    23130 (23130)

Aha. KDE.

> This bug is not new for me, although I have not reported it earlier. This 
> behavior has been present at least in the last 3 squeeze versions.

Aha. OK. WTF did you then not mark that as such instead of marking it as
a version not even in testing but blocking -16 with loads of other fixes
from entering testing?
Last three squeeze versions? So this dates back to 3.1.0 or so? (The versions
which migrated to testing were 3.1.1-8 and 3.1.1-14 and what you report
against is the version in testing-security)
And of course this is all not helpful at all then since how should it
*now* be able to trace back when this was introduced?

Anyway, can confirm this crash in a squeeze/i386 chroot with
OOO_FORCE_DESKTOP="kde".

Interestingly, it works in 3.2.0-1 for me. Thus closing. I'll not debug
this any further. I'll not do anything anymore for 3.1.1 and thnakfully
this bug will not block future versions from entering testing as it's no
regression anymore. If you want to see it fixed, use 3.2.0.

Grüße/Regards,

René
-- 
 .''`.  René Engelhard -- Debian GNU/Linux Developer
 : :' : http://www.debian.org | http://people.debian.org/~rene/
 `. `'  rene@debian.org | GnuPG-Key ID: D03E3E70
   `-   Fingerprint: E12D EA46 7506 70CF A960 801D 0AA0 4571 D03E 3E70



Reply to: