[Bug 1874096] Re: Closing Krita normally always result in "Krita closed unexpectedly" notification on Plasma

2021-09-29 Thread Ivnitskii Andrei
What about version 4.2.9 for Ubuntu 20.04 ? Needs to recompile with a
patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874096

Title:
  Closing Krita normally always result in "Krita closed unexpectedly"
  notification on Plasma

To manage notifications about this bug go to:
https://bugs.launchpad.net/krita/+bug/1874096/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874096] Re: Closing Krita normally always result in "Krita closed unexpectedly" notification on Plasma

2021-06-19 Thread Bug Watch Updater
** Changed in: krita
   Status: Won't Fix => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874096

Title:
  Closing Krita normally always result in "Krita closed unexpectedly"
  notification on Plasma

To manage notifications about this bug go to:
https://bugs.launchpad.net/krita/+bug/1874096/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874096] Re: Closing Krita normally always result in "Krita closed unexpectedly" notification on Plasma

2020-06-02 Thread Bug Watch Updater
Launchpad has imported 16 comments from the remote bug at
https://bugs.kde.org/show_bug.cgi?id=417465.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2020-02-12T00:54:25+00:00 genstorm wrote:

Application: krita (4.2.8)
 (Compiled from sources)
Qt Version: 5.14.1
Frameworks Version: 5.67.0
Operating System: Linux 5.5.2-gentoo-r1 x86_64
Windowing system: X11
Distribution: "Gentoo Base System release 2.7"

-- Information about the crash:
- What I was doing when the application crashed:

Just starting krita, then closing again (without doing anything else)
will lead to it crashing every time. I hope the stacktrace contains
enough information.

The crash can be reproduced every time.

-- Backtrace:
Application: Krita (krita), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7efeb29487c0 (LWP 11875))]

Thread 8 (Thread 0x7efe8b7fe700 (LWP 11900)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7efeb78ca530 in QtLinuxFutex::_q_futex (val3=0, addr2=0x0, val2=0, 
val=, op=0, addr=) at thread/qfutex_p.h:133
#2  QtLinuxFutex::futexWait > 
(expectedValue=, futex=...) at thread/qfutex_p.h:135
#3  futexSemaphoreTryAcquire_loop (u=..., curValue=, 
nn=8589934593, timeout=) at thread/qsemaphore.cpp:219
#4  0x7efeb78ca2a6 in futexSemaphoreTryAcquire (timeout=, n=, u=...) at 
/usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/include/g++-v9/bits/atomic_base.h:539
#5  QSemaphore::tryAcquire (this=0x55c9b72a8fb0, n=, 
timeout=) at thread/qsemaphore.cpp:484
#6  0x7efeb8d1668a in KisTileDataSwapper::run() () from 
/usr/lib64/libkritaimage.so.18
#7  0x7efeb78c836b in QThreadPrivate::start (arg=0x7efeb90060e0) at 
thread/qthread_unix.cpp:342
#8  0x7efeb55752d7 in start_thread (arg=) at 
pthread_create.c:479
#9  0x7efeb74a3a5f in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 7 (Thread 0x7efea8fd0700 (LWP 11897)):
#0  0x7efeb7497bc3 in __GI___poll (fds=0x7efe98004200, nfds=1, timeout=-1) 
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7efeb4da85de in g_main_context_poll (priority=, 
n_fds=1, fds=0x7efe98004200, timeout=, context=0x7efe98000c20) 
at ../glib-2.60.7/glib/gmain.c:4228
#2  g_main_context_iterate (context=context@entry=0x7efe98000c20, 
block=block@entry=1, dispatch=dispatch@entry=1, self=) at 
../glib-2.60.7/glib/gmain.c:3922
#3  0x7efeb4da86ff in g_main_context_iteration (context=0x7efe98000c20, 
may_block=may_block@entry=1) at ../glib-2.60.7/glib/gmain.c:3988
#4  0x7efeb7ac5cbb in QEventDispatcherGlib::processEvents 
(this=0x7efe98000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7efeb7a70a9b in QEventLoop::exec (this=this@entry=0x7efea8fcfdb0, 
flags=..., flags@entry=...) at 
../../include/QtCore/../../src/corelib/global/qflags.h:136
#6  0x7efeb78c733e in QThread::exec (this=this@entry=0x7efeb5629da0 
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at 
../../include/QtCore/../../src/corelib/global/qflags.h:118
#7  0x7efeb55a7507 in QDBusConnectionManager::run (this=0x7efeb5629da0 
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at 
qdbusconnection.cpp:179
#8  0x7efeb78c836b in QThreadPrivate::start (arg=0x7efeb5629da0 <(anonymous 
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at 
thread/qthread_unix.cpp:342
#9  0x7efeb55752d7 in start_thread (arg=) at 
pthread_create.c:479
#10 0x7efeb74a3a5f in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 6 (Thread 0x7efea9856700 (LWP 11896)):
#0  futex_wait_cancelable (private=0, expected=0, futex_word=0x7efe94002f58) at 
../sysdeps/unix/sysv/linux/futex-internal.h:80
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7efe94002f08, 
cond=0x7efe94002f30) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x7efe94002f30, mutex=0x7efe94002f08) at 
pthread_cond_wait.c:638
#3  0x7efeb0e7d46b in cnd_wait (mtx=0x7efe94002f08, cond=0x7efe94002f30) at 
../mesa-20.0.0-rc2/include/c11/threads_posix.h:155
#4  util_queue_thread_func (input=input@entry=0x7efe940032d0) at 
../mesa-20.0.0-rc2/src/util/u_queue.c:275
#5  0x7efeb0e7d087 in impl_thrd_routine (p=) at 
../mesa-20.0.0-rc2/include/c11/threads_posix.h:87
#6  0x7efeb55752d7 in start_thread (arg=) at 
pthread_create.c:479
#7  0x7efeb74a3a5f in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 5 (Thread 0x7efeabfff700 (LWP 11895)):
#0  futex_wait_cancelable (private=0, expected=0, futex_word=0x7efe94002f58) at 
../sysdeps/unix/sysv/linux/futex-internal.h:80
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7efe94002f08, 
cond=0x7efe94002f30) at pthread_cond_wait.c:508
#2  

[Bug 1874096] Re: Closing Krita normally always result in "Krita closed unexpectedly" notification on Plasma

2020-05-25 Thread Kai Kasurinen
** Bug watch added: KDE Bug Tracking System #417465
   https://bugs.kde.org/show_bug.cgi?id=417465

** Also affects: krita via
   https://bugs.kde.org/show_bug.cgi?id=417465
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874096

Title:
  Closing Krita normally always result in "Krita closed unexpectedly"
  notification on Plasma

To manage notifications about this bug go to:
https://bugs.launchpad.net/krita/+bug/1874096/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874096] Re: Closing Krita normally always result in "Krita closed unexpectedly" notification on Plasma

2020-05-06 Thread Paul White
** Tags added: focal groovy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874096

Title:
  Closing Krita normally always result in "Krita closed unexpectedly"
  notification on Plasma

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krita/+bug/1874096/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874096] Re: Closing Krita normally always result in "Krita closed unexpectedly" notification on Plasma

2020-05-06 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: krita (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874096

Title:
  Closing Krita normally always result in "Krita closed unexpectedly"
  notification on Plasma

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krita/+bug/1874096/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874096] Re: Closing Krita normally always result in "Krita closed unexpectedly" notification on Plasma

2020-04-21 Thread Rik Mills
** Changed in: krita (Ubuntu)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874096

Title:
  Closing Krita normally always result in "Krita closed unexpectedly"
  notification on Plasma

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krita/+bug/1874096/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs