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

Bug#813570: marked as done (krita-1.2.8.5+dfsg-1: Krita crashes by creating a new workspace)

Your message dated Thu, 24 Dec 2020 19:18:32 +0100
with message-id <7434464.MhkbZ0Pkbq@thyrus>
and subject line Re: Bug#813570: krita-1.2.8.5+dfsg-1: Krita crashes by creating a new workspace
has caused the Debian Bug report #813570,
regarding krita-1.2.8.5+dfsg-1: Krita crashes by creating a new workspace
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 owner@bugs.debian.org
immediately.)


-- 
813570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813570
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: krita-1.2.8.5+dfsg-1
Version: krita-1.2.8.5+dfsg
Severity: normal

Dear Maintainer,

   * What led up to the situation?
First Start of Krita after installation
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
Started program and tried to create a new workspace
   * What was the outcome of this action?
The Program crashed and the KDE-Crash-Handler opened
   * What outcome did you expect instead?
start working with Krita

KDE-crash-handler output:
Application: Krita (krita), signal: Segmentation fault
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
[Current thread is 1 (Thread 0x733a8000 (LWP 2312))]

Thread 6 (Thread 0x6e8cc410 (LWP 2327)):
#0  0x742797a4 in __pthread_cond_wait (cond=0x17573c0, mutex=0x17573a8) at pthread_cond_wait.c:187
#1  0x76dc6688 in __pthread_cond_wait (cond=<optimized out>, mutex=<optimized out>) at forward.c:149
#2  0x75ac9318 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/arm-linux-gnueabihf/libQtCore.so.4
#3  0x75ac4f54 in QSemaphore::acquire(int) () from /usr/lib/arm-linux-gnueabihf/libQtCore.so.4
#4  0x7556419c in ?? () from /usr/lib/libkritaimage.so.13
#5  0x755645ac in ?? () from /usr/lib/libkritaimage.so.13
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 5 (Thread 0x6e0cc410 (LWP 2328)):
#0  0x742797a4 in __pthread_cond_wait (cond=0x1757608, mutex=0x17575f0) at pthread_cond_wait.c:187
#1  0x76dc6688 in __pthread_cond_wait (cond=<optimized out>, mutex=<optimized out>) at forward.c:149
#2  0x75ac9318 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/arm-linux-gnueabihf/libQtCore.so.4
#3  0x75ac53dc in QSemaphore::tryAcquire(int, int) () from /usr/lib/arm-linux-gnueabihf/libQtCore.so.4
#4  0x75581a54 in KisTileDataSwapper::run() () from /usr/lib/libkritaimage.so.13
#5  0x75ac8d74 in ?? () from /usr/lib/arm-linux-gnueabihf/libQtCore.so.4
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 4 (Thread 0x6ccff410 (LWP 2340)):
#0  0x74279b30 in __pthread_cond_timedwait (cond=0x1bc0398, mutex=0x1bc0380, abstime=0x6ccfed6c) at pthread_cond_timedwait.c:199
#1  0x76dc66e4 in __pthread_cond_timedwait (cond=<optimized out>, mutex=<optimized out>, abstime=<optimized out>) at forward.c:162
#2  0x75ac92f0 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/arm-linux-gnueabihf/libQtCore.so.4
#3  0x75abc0a0 in ?? () from /usr/lib/arm-linux-gnueabihf/libQtCore.so.4
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 3 (Thread 0x6c2ff410 (LWP 2341)):
#0  0x742797a4 in __pthread_cond_wait (cond=0x1ee0ef8, mutex=0x1ee0ee0) at pthread_cond_wait.c:187
#1  0x76dc6688 in __pthread_cond_wait (cond=<optimized out>, mutex=<optimized out>) at forward.c:149
#2  0x75ac9318 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/arm-linux-gnueabihf/libQtCore.so.4


-- System Information:
Distributor ID:	Raspbian on Raspberry Pi Version 2 B
Description:	Raspbian GNU/Linux 8.0 (jessie)
Release:	8.0
Codename:	jessie
Architecture: armv7l

Kernel: Linux 4.1.13-v7+ (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---
--- Begin Message --- 
Hi,

sorry for the late answer.

In data mercoledì 3 febbraio 2016 09:14:35 CET, hai scritto:
> Dear Maintainer,
> 
>    * What led up to the situation?
> First Start of Krita after installation
>    * What exactly did you do (or not do) that was effective (or
>      ineffective)?
> Started program and tried to create a new workspace
>    * What was the outcome of this action?
> The Program crashed and the KDE-Crash-Handler opened
>    * What outcome did you expect instead?
> start working with Krita
> 
> KDE-crash-handler output:
> Application: Krita (krita), signal: Segmentation fault
> Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
> [Current thread is 1 (Thread 0x733a8000 (LWP 2312))]
> 
> [...]
> -- System Information:
> Distributor ID:	Raspbian on Raspberry Pi Version 2 B
> Description:	Raspbian GNU/Linux 8.0 (jessie)
> Release:	8.0
> Codename:	jessie
> Architecture: armv7l

This crash was reported against an old version of krita, back when it
was part of the calligra source.

Starting from krita 3.0, it was split as own source; unfortunately,
because of the OpenGL requirement, it has not been ever buildable on
the armel & armhf architectures, so there is no newer version of krita
on 32bit arm to try; this, plus considering the huge development
efforts that go constantly into krita, unfortunately make this old bug
report of not much of use, sorry.

Thanks anyway for your report,
-- 
Pino Toscano

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
Reply to: