[plasmashell] [Bug 405921] Plasma crashes when dragging task from taskmanager to a different virtual desktop
https://bugs.kde.org/show_bug.cgi?id=405921 --- Comment #5 from Franz Fellner --- Created attachment 124856 --> https://bugs.kde.org/attachment.cgi?id=124856=edit New crash information added by DrKonqi plasmashell (5.17.4) using Qt 5.13.2 I am now at 5.17.4, this still happens - What I was doing when the application crashed: As before I tried to move a task to a different VT. If you can't reproduce just hesitate before dropping. It also crashes when you just hover the VT widget and slowly move the mouse, keeping the left mouse button pressed. -- Backtrace (Reduced): #7 0x7fdc7cc8d416 in qNumVariantToHelper (handlerManager=..., val=, ok=0x7ffdeb7d82df, d=...) at kernel/qvariant.cpp:3140 #8 0x7fdc7cc8d416 in QVariant::toInt(bool*) const (this=0x6e6f, ok=0x7ffdeb7d82df) at kernel/qvariant.cpp:3140 #9 0x7fdc7516f2a7 in TaskManager::VirtualDesktopInfo::XWindowPrivate::requestActivate(QVariant const&) (this=, desktop=...) at /var/tmp/portage/kde-plasma/plasma-workspace-5.17.4-r1/work/plasma-workspace-5.17.4/libtaskmanager/virtualdesktopinfo.cpp:172 #10 0x7fdc5e72cc17 in PagerModel::changePage(int) (this=, page=2) at /var/tmp/portage/kde-plasma/plasma-desktop-5.17.4-r1/work/plasma-desktop-5.17.4/applets/pager/plugin/pagermodel.cpp:566 #11 0x7fdc5e72dc24 in PagerModel::qt_metacall(QMetaObject::Call, int, void**) (this=0x2a47d50, _c=QMetaObject::InvokeMetaMethod, _id=12, _a=0x7ffdeb7d84c0) at applets/pager/pagerplugin_autogen/include/moc_pagermodel.cpp:354 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405921] Plasma crashes when dragging task from taskmanager to a different virtual desktop
https://bugs.kde.org/show_bug.cgi?id=405921 Franz Fellner changed: What|Removed |Added CC||alpine.art...@googlemail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 403582] double click to enter/leave fullscreen sometimes crashes gwenview
https://bugs.kde.org/show_bug.cgi?id=403582 --- Comment #6 from Franz Fellner --- While I also get those Drag-indicator-crashes it as well happens when the mouse isn't moved. Reproduced with one hand locking the mouse on the table, the other one doing the double click. Probably it's the geometry change of the window that confuses the mouse handler? (Just a guess). I get these crashes frequently (70% of the time going fullscreen) which really makes it a pain to use. Please could a DEV at least try to have a look at this? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405921] New: Plasma crashes when dragging task from taskmanager to a different virtual desktop
https://bugs.kde.org/show_bug.cgi?id=405921 Bug ID: 405921 Summary: Plasma crashes when dragging task from taskmanager to a different virtual desktop Product: plasmashell Version: 5.15.3 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: alpine.art...@googlemail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.15.3) (Compiled from sources) Qt Version: 5.12.2 Frameworks Version: 5.56.0 Operating System: Linux 4.19.27-gentoo-r1 x86_64 Distribution: "Gentoo Base System release 2.6" -- Information about the crash: - What I was doing when the application crashed: I wanted to move a konsole window from VT 1 to VT 2. So I wanted to dragged the task from the taskmanager (the default window list in the bottom panel, hope that's how it is called) to a different desktop in the VT-Plasmoid. This worked in the past, now it crashes. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff98aa2d340 (LWP 616))] Thread 11 (Thread 0x7ff9270e9700 (LWP 1284)): #0 0x7ff976ea2db6 in pa_atomic_load (a=) at /var/tmp/portage/media-sound/pulseaudio-12.2/work/pulseaudio-12.2/src/pulsecore/pstream.c:855 #1 do_read (p=p@entry=0x7ff91bc0, re=re@entry=0x7ff91d88) at /var/tmp/portage/media-sound/pulseaudio-12.2/work/pulseaudio-12.2/src/pulsecore/pstream.c:856 #2 0x7ff976ea5cdb in do_pstream_read_write (p=0x7ff91bc0) at /var/tmp/portage/media-sound/pulseaudio-12.2/work/pulseaudio-12.2/src/pulsecore/pstream.c:248 #3 0x7ff976ea6079 in srb_callback (srb=0x7ff910004090, userdata=0x7ff91bc0) at /var/tmp/portage/media-sound/pulseaudio-12.2/work/pulseaudio-12.2/src/pulsecore/pstream.c:287 #4 0x7ff976ea68ca in srbchannel_rwloop (sr=0x7ff910004090) at /var/tmp/portage/media-sound/pulseaudio-12.2/work/pulseaudio-12.2/src/pulsecore/srbchannel.c:190 #5 0x7ff97ba5fb98 in dispatch_pollfds (m=0xa6dbf80) at /var/tmp/portage/media-sound/pulseaudio-12.2/work/pulseaudio-12.2/src/pulse/mainloop.c:140 #6 pa_mainloop_dispatch (m=m@entry=0xa6dbf80) at /var/tmp/portage/media-sound/pulseaudio-12.2/work/pulseaudio-12.2/src/pulse/mainloop.c:898 #7 0x7ff97ba5fe6c in pa_mainloop_iterate (m=0xa6dbf80, block=, retval=0x0) at /var/tmp/portage/media-sound/pulseaudio-12.2/work/pulseaudio-12.2/src/pulse/mainloop.c:929 #8 0x7ff97ba5ff10 in pa_mainloop_run (m=0xa6dbf80, retval=retval@entry=0x0) at /var/tmp/portage/media-sound/pulseaudio-12.2/work/pulseaudio-12.2/src/pulse/mainloop.c:945 #9 0x7ff97ba6df59 in thread (userdata=0xa690f50) at /var/tmp/portage/media-sound/pulseaudio-12.2/work/pulseaudio-12.2/src/pulse/thread-mainloop.c:100 #10 0x7ff976eb68d8 in internal_thread_func (userdata=0xa736cc0) at /var/tmp/portage/media-sound/pulseaudio-12.2/work/pulseaudio-12.2/src/pulsecore/thread-posix.c:81 #11 0x7ff98113d96a in start_thread (arg=0x7ff9270e9700) at pthread_create.c:463 #12 0x7ff983f261bf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7ff927d99700 (LWP 1283)): #0 0x7ff98114456c in futex_wait_cancelable (private=, expected=0, futex_word=0x9098714) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x90986c0, cond=0x90986e8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x90986e8, mutex=0x90986c0) at pthread_cond_wait.c:655 #3 0x7ff9846b3573 in QWaitConditionPrivate::wait (deadline=..., this=0x90986c0) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x7ff96c00f3f0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7ff9846b35f9 in QWaitCondition::wait (this=this@entry=0x7ff96c00f3f8, mutex=mutex@entry=0x7ff96c00f3f0, time=time@entry=18446744073709551615) at ../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68 #6 0x7ff9888c71c9 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x7ff96c00f3e8) at scenegraph/qsgthreadedrenderloop.cpp:245 #7 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x7ff96c00f370) at scenegraph/qsgthreadedrenderloop.cpp:710 #8 0x7ff9888c742a in QSGRenderThread::run (this=0x7ff96c00f370) at scenegraph/qsgthreadedrenderloop.cpp:739 #9 0x7ff9846add52 in QThreadPrivate::start (arg=0x7ff96c00f370) at thread/qthread_unix.cpp:361 #10 0x7ff98113d96a in start_thread (arg=0x7ff927d99700) at pthread_create.c:463 #11 0x7ff983f261bf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7ff940837700 (LWP 785)): #0 0x7ff98114456c in futex_wait_cancelable (private=, expected=0,
[gwenview] [Bug 403582] New: double click to enter/leave fullscreen sometimes crashes gwenview
https://bugs.kde.org/show_bug.cgi?id=403582 Bug ID: 403582 Summary: double click to enter/leave fullscreen sometimes crashes gwenview Product: gwenview Version: 18.12.1 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: alpine.art...@googlemail.com Target Milestone: --- Application: gwenview (18.12.1) (Compiled from sources) Qt Version: 5.12.0 Frameworks Version: 5.54.0 Operating System: Linux 4.19.16-gentoo x86_64 Distribution: "Gentoo Base System release 2.6" -- Information about the crash: - What I was doing when the application crashed: I double clicked the displayed image to make the application fullscreen. This happens sometimes but not always. It also can happen when doubleclicking to leave fullscreen. The crash can be reproduced sometimes. -- Backtrace: Application: Gwenview (gwenview), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5f292646c0 (LWP 4156))] Thread 4 (Thread 0x7f5efbfff700 (LWP 4162)): #0 0x7f5f1ee7756c in futex_wait_cancelable (private=, expected=0, futex_word=0x261c7d8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x261c788, cond=0x261c7b0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x261c7b0, mutex=0x261c788) at pthread_cond_wait.c:655 #3 0x7f5f00a98e1b in cnd_wait (mtx=0x261c788, cond=0x261c7b0) at ../mesa-18.3.2/src/../include/c11/threads_posix.h:155 #4 util_queue_thread_func (input=input@entry=0x293bc40) at ../mesa-18.3.2/src/util/u_queue.c:270 #5 0x7f5f00a98b27 in impl_thrd_routine (p=) at ../mesa-18.3.2/src/../include/c11/threads_posix.h:87 #6 0x7f5f1ee7096a in start_thread (arg=0x7f5efbfff700) at pthread_create.c:463 #7 0x7f5f242491bf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f5f09e3f700 (LWP 4160)): #0 0x7f5f2423d5f3 in __GI___poll (fds=0x7f5f04012a20, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f5f1d24d9c9 in g_main_context_poll (priority=, n_fds=1, fds=0x7f5f04012a20, timeout=, context=0x7f5f04000bf0) at /var/tmp/portage/dev-libs/glib-2.58.3/work/glib-2.58.3/glib/gmain.c:4221 #2 g_main_context_iterate (context=context@entry=0x7f5f04000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.58.3/work/glib-2.58.3/glib/gmain.c:3915 #3 0x7f5f1d24dadc in g_main_context_iteration (context=0x7f5f04000bf0, may_block=may_block@entry=1) at /var/tmp/portage/dev-libs/glib-2.58.3/work/glib-2.58.3/glib/gmain.c:3981 #4 0x7f5f24ba809b in QEventDispatcherGlib::processEvents (this=0x7f5f04000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #5 0x7f5f24b511ca in QEventLoop::exec (this=this@entry=0x7f5f09e3ec70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #6 0x7f5f249b063a in QThread::exec (this=this@entry=0x7f5f230b8d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:531 #7 0x7f5f22e40fb5 in QDBusConnectionManager::run (this=0x7f5f230b8d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #8 0x7f5f249b1cf6 in QThreadPrivate::start (arg=0x7f5f230b8d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:361 #9 0x7f5f1ee7096a in start_thread (arg=0x7f5f09e3f700) at pthread_create.c:463 #10 0x7f5f242491bf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f5f11061700 (LWP 4158)): #0 0x7f5f2423d5f3 in __GI___poll (fds=fds@entry=0x7f5f11060bb8, nfds=nfds@entry=1, timeout=timeout@entry=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f5f1cfe27f7 in poll (__timeout=-1, __nfds=1, __fds=0x7f5f11060bb8) at /usr/include/bits/poll2.h:46 #2 _xcb_conn_wait (c=c@entry=0x24b7c20, cond=cond@entry=0x24b7c60, vector=vector@entry=0x0, count=count@entry=0x0) at /var/tmp/portage/x11-libs/libxcb-1.13.1/work/libxcb-1.13.1/src/xcb_conn.c:479 #3 0x7f5f1cfe442a in xcb_wait_for_event (c=c@entry=0x24b7c20) at /var/tmp/portage/x11-libs/libxcb-1.13.1/work/libxcb-1.13.1/src/xcb_in.c:697 #4 0x7f5f131e9cda in QXcbEventQueue::run (this=0x24c38d0) at qxcbeventqueue.cpp:225 #5 0x7f5f249b1cf6 in QThreadPrivate::start (arg=0x24c38d0) at thread/qthread_unix.cpp:361 #6 0x7f5f1ee7096a in start_thread (arg=0x7f5f11061700) at pthread_create.c:463 #7 0x7f5f242491bf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f5f292646c0 (LWP 4156)): [KCrash Handler] #6 QCursor::shape (this=this@entry=0x0) at kernel/qcursor.cpp:539 #7 0x7f5f25b1c0d0 in QBasicDrag::updateCursor
[plasmashell] [Bug 402700] Pressing TAB in kickoff freezes plasma
https://bugs.kde.org/show_bug.cgi?id=402700 --- Comment #4 from Franz Fellner --- Created attachment 117454 --> https://bugs.kde.org/attachment.cgi?id=117454=edit kickoff before pressing TAB -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402700] Pressing TAB in kickoff freezes plasma
https://bugs.kde.org/show_bug.cgi?id=402700 --- Comment #3 from Franz Fellner --- plasmashell uses 100%. Screenshot attached as requested. There were updates in the meantime, so different backtrace: #0 QtPrivate::RefCount::deref (this=0x562e08802330) at /usr/include/qt5/QtCore/qrefcount.h:68 #1 QList::~QList (this=0x7ffdd58b6570, __in_chrg=) at /usr/include/qt5/QtCore/qlist.h:829 #2 0x7f13457c8bcb in QQuickItemPrivate::nextTabChildItem (item=item@entry=0x562e08bf14b0, start=, start@entry=0) at items/qquickitem.cpp:2505 #3 0x7f13457c9672 in QQuickItemPrivate::nextPrevItemInTabFocusChain (item=item@entry=0x562e07db2d20, forward=forward@entry=true) at items/qquickitem.cpp:2594 #4 0x7f13457cc5f4 in QQuickItemPrivate::focusNextPrev (item=item@entry=0x562e07db2d20, forward=forward@entry=true) at items/qquickitem.cpp:2489 #5 0x7f13457cc712 in QQuickItemPrivate::deliverKeyEvent (this=0x562e07db2de0, e=0x7ffdd58b6f30) at items/qquickitem.cpp:5169 #6 0x7f13457cc985 in QQuickItem::event (this=0x562e07db2d20, ev=0x7ffdd58b6f30) at items/qquickitem.cpp:8057 #7 0x7f1342f7d7ac in QApplicationPrivate::notify_helper (this=this@entry=0x562e057e5870, receiver=receiver@entry= 0x562e07db2d20, e=e@entry=0x7ffdd58b6f30) at kernel/qapplication.cpp:3752 #8 0x7f1342f84d10 in QApplication::notify (this=0x7ffdd58b7350, receiver=0x562e07db2d20, e=0x7ffdd58b6f30) at kernel/qapplication.cpp:3499 #9 0x7f13417233d7 in QCoreApplication::notifyInternal2 (receiver=0x562e07db2d20, event=0x7ffdd58b6f30) at kernel/qcoreapplication.cpp:1061 #10 0x7f134172366e in QCoreApplication::sendEvent (receiver=receiver@entry=0x562e07db2d20, event=event@entry=0x7ffdd58b6f30) at kernel/qcoreapplication.cpp:1451 #11 0x7f13457d940f in QQuickWindowPrivate::deliverKeyEvent (this=this@entry=0x7f132c007090, e=e@entry=0x7ffdd58b6f30) at items/qquickwindow.cpp:1699 #12 0x7f13457de61f in QQuickWindow::keyPressEvent (this=, e=0x7ffdd58b6f30) at items/qquickwindow.cpp:1682 [and so on] I assume you want me to go into QQuickItem::event: (gdb) print this->metaObject()->className() $4 = 0x562e07dc8478 "TextField_QMLTYPE_129_QML_136" -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 402966] New: kwrite crashed when creating a dir in save dialog
https://bugs.kde.org/show_bug.cgi?id=402966 Bug ID: 402966 Summary: kwrite crashed when creating a dir in save dialog Product: kate Version: 18.12.0 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: kwrite Assignee: kwrite-bugs-n...@kde.org Reporter: alpine.art...@googlemail.com Target Milestone: --- Application: kwrite (18.12.0) (Compiled from sources) Qt Version: 5.12.0 Frameworks Version: 5.53.0 Operating System: Linux 4.19.13-gentoo x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: I wanted to save a new and empty file. I wanted to save it in a new directory. Creating the directory lead to kwrite crashing. -- Backtrace: Application: KWrite (kwrite), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc23d2fac80 (LWP 6748))] Thread 4 (Thread 0x7fc2171b5700 (LWP 6751)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x563d03a61ec8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x563d03a61e78, cond=0x563d03a61ea0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x563d03a61ea0, mutex=0x563d03a61e78) at pthread_cond_wait.c:655 #3 0x7fc217b0de1b in cnd_wait (mtx=0x563d03a61e78, cond=0x563d03a61ea0) at ../mesa-18.3.1/src/../include/c11/threads_posix.h:155 #4 util_queue_thread_func (input=input@entry=0x563d03d6c970) at ../mesa-18.3.1/src/util/u_queue.c:270 #5 0x7fc217b0db27 in impl_thrd_routine (p=) at ../mesa-18.3.1/src/../include/c11/threads_posix.h:87 #6 0x7fc234cf096a in start_thread (arg=0x7fc2171b5700) at pthread_create.c:463 #7 0x7fc2393c21bf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fc2210c7700 (LWP 6750)): #0 0x7fc2393b65f3 in __GI___poll (fds=0x7fc21c004db0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fc232c499c9 in g_main_context_poll (priority=, n_fds=1, fds=0x7fc21c004db0, timeout=, context=0x7fc21c000bf0) at /var/tmp/portage/dev-libs/glib-2.58.2/work/glib-2.58.2/glib/gmain.c:4221 #2 g_main_context_iterate (context=context@entry=0x7fc21c000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.58.2/work/glib-2.58.2/glib/gmain.c:3915 #3 0x7fc232c49adc in g_main_context_iteration (context=0x7fc21c000bf0, may_block=may_block@entry=1) at /var/tmp/portage/dev-libs/glib-2.58.2/work/glib-2.58.2/glib/gmain.c:3981 #4 0x7fc239d2109b in QEventDispatcherGlib::processEvents (this=0x7fc21c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #5 0x7fc239cca1ca in QEventLoop::exec (this=this@entry=0x7fc2210c6d70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #6 0x7fc239b2963a in QThread::exec (this=this@entry=0x7fc2363ccd80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:531 #7 0x7fc236154fb5 in QDBusConnectionManager::run (this=0x7fc2363ccd80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #8 0x7fc239b2acf6 in QThreadPrivate::start (arg=0x7fc2363ccd80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:361 #9 0x7fc234cf096a in start_thread (arg=0x7fc2210c7700) at pthread_create.c:463 #10 0x7fc2393c21bf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fc229573700 (LWP 6749)): #0 0x7fc2393b65f3 in __GI___poll (fds=fds@entry=0x7fc229572cb8, nfds=nfds@entry=1, timeout=timeout@entry=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fc231f007f7 in poll (__timeout=-1, __nfds=1, __fds=0x7fc229572cb8) at /usr/include/bits/poll2.h:46 #2 _xcb_conn_wait (c=c@entry=0x563d0348f8a0, cond=cond@entry=0x563d0348f8e0, vector=vector@entry=0x0, count=count@entry=0x0) at /var/tmp/portage/x11-libs/libxcb-1.13.1/work/libxcb-1.13.1/src/xcb_conn.c:479 #3 0x7fc231f0242a in xcb_wait_for_event (c=c@entry=0x563d0348f8a0) at /var/tmp/portage/x11-libs/libxcb-1.13.1/work/libxcb-1.13.1/src/xcb_in.c:697 #4 0x7fc22bd27cda in QXcbEventQueue::run (this=0x563d0349bbf0) at qxcbeventqueue.cpp:225 #5 0x7fc239b2acf6 in QThreadPrivate::start (arg=0x563d0349bbf0) at thread/qthread_unix.cpp:361 #6 0x7fc234cf096a in start_thread (arg=0x7fc229573700) at pthread_create.c:463 #7 0x7fc2393c21bf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fc23d2fac80 (LWP 6748)): [KCrash Handler] #6 0x7fc238253286 in std::__atomic_base::operator-- (this=0x20) at /usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/include/g++-v7/bits/atomic_base.h:304 #7 QAtomicOps::deref (_q_value=...) at /usr/include/qt5/QtCore/qatomic_cxx11.h:271 #8
[plasmashell] [Bug 402700] New: Pressing TAB in kickoff freezes plasma
https://bugs.kde.org/show_bug.cgi?id=402700 Bug ID: 402700 Summary: Pressing TAB in kickoff freezes plasma Product: plasmashell Version: 5.14.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: alpine.art...@googlemail.com CC: plasma-b...@kde.org Target Milestone: 1.0 STEPS TO REPRODUCE 1. Open kicker (e.g. with META_KEY) 2. Press TAB_KEY OBSERVED RESULT Plasma freezes with 100% CPU usage. Backtrace: #0 QQuickItemPrivate::nextPrevItemInTabFocusChain (item=item@entry=0x55ae7f611f20, forward=forward@entry=true) at items/qquickitem.cpp:2665 #1 0x7f9ed70225f4 in QQuickItemPrivate::focusNextPrev (item=item@entry=0x55ae7f611f20, forward=forward@entry=true) at items/qquickitem.cpp:2489 #2 0x7f9ed7022712 in QQuickItemPrivate::deliverKeyEvent (this=0x55ae7f611fe0, e=0x7ffe6051b230) at items/qquickitem.cpp:5169 #3 0x7f9ed7022985 in QQuickItem::event (this=0x55ae7f611f20, ev=0x7ffe6051b230) at items/qquickitem.cpp:8057 #4 0x7f9ed47d37ac in QApplicationPrivate::notify_helper (this=this@entry=0x55ae7dd859a0, receiver=receiver@entry=0x55ae7f611f20, e=e@entry=0x7ffe6051b230) at kernel/qapplication.cpp:3752 #5 0x7f9ed47dad10 in QApplication::notify (this=0x7ffe6051b650, receiver=0x55ae7f611f20, e=0x7ffe6051b230) at kernel/qapplication.cpp:3499 #6 0x7f9ed2f793d7 in QCoreApplication::notifyInternal2 (receiver=0x55ae7f611f20, event=0x7ffe6051b230) at kernel/qcoreapplication.cpp:1061 #7 0x7f9ed2f7966e in QCoreApplication::sendEvent (receiver=receiver@entry=0x55ae7f611f20, event=event@entry=0x7ffe6051b230) at kernel/qcoreapplication.cpp:1451 #8 0x7f9ed702f40f in QQuickWindowPrivate::deliverKeyEvent (this=this@entry=0x7f9ebc0057d0, e=e@entry=0x7ffe6051b230) at items/qquickwindow.cpp:1699 #9 0x7f9ed703461f in QQuickWindow::keyPressEvent (this=, e=0x7ffe6051b230) at items/qquickwindow.cpp:1682 #10 0x7f9ed3523fb5 in QWindow::event (this=this@entry=0x55ae7ea17be0, ev=ev@entry=0x7ffe6051b230) at kernel/qwindow.cpp:2336 #11 0x7f9ed703ee15 in QQuickWindow::event (this=this@entry=0x55ae7ea17be0, e=e@entry=0x7ffe6051b230) at items/qquickwindow.cpp:1673 #12 0x7f9ed8d66a2b in PlasmaQuick::Dialog::event (this=0x55ae7ea17be0, event=0x7ffe6051b230) at /var/tmp/portage/kde-frameworks/plasma-5.53.0/work/plasma-framework-5.53.0/src/plasmaquick/dialog.cpp:1304 #13 0x7f9ed47d37ac in QApplicationPrivate::notify_helper (this=this@entry=0x55ae7dd859a0, receiver=receiver@entry=0x55ae7ea17be0, e=e@entry=0x7ffe6051b230) at kernel/qapplication.cpp:3752 #14 0x7f9ed47dad10 in QApplication::notify (this=0x7ffe6051b650, receiver=0x55ae7ea17be0, e=0x7ffe6051b230) at kernel/qapplication.cpp:3499 #15 0x7f9ed2f793d7 in QCoreApplication::notifyInternal2 (receiver=0x55ae7ea17be0, event=0x7ffe6051b230) at kernel/qcoreapplication.cpp:1061 #16 0x7f9ed2f7967e in QCoreApplication::sendSpontaneousEvent (receiver=receiver@entry=0x55ae7ea17be0, event=event@entry=0x7ffe6051b230) at kernel/qcoreapplication.cpp:1463 #17 0x7f9ed351551b in QGuiApplicationPrivate::processKeyEvent (e=0x55ae80b74c10) at kernel/qguiapplication.cpp:2228 #18 0x7f9ed351a4f5 in QGuiApplicationPrivate::processWindowSystemEvent (e=e@entry=0x55ae80b74c10) at kernel/qguiapplication.cpp:1843 #19 0x7f9ed34f575b in QWindowSystemInterface::sendWindowSystemEvents (flags=flags@entry=...) at kernel/qwindowsysteminterface.cpp:1068 #20 0x7f9ec4dc8cca in xcbSourceDispatch (source=source@entry=0x55ae7dddf4d0) at qxcbeventdispatcher.cpp:105#21 0x7f9ecc666817 in g_main_dispatch (context=0x7f9ebc004ff0) at /var/tmp/portage/dev-libs/glib-2.58.2/work/glib-2.58.2/glib/gmain.c:3182 #22 g_main_context_dispatch (context=context@entry=0x7f9ebc004ff0) at /var/tmp/portage/dev-libs/glib-2.58.2/work/glib-2.58.2/glib/gmain.c:3847 #23 0x7f9ecc666a50 in g_main_context_iterate (context=context@entry=0x7f9ebc004ff0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.58.2/work/glib-2.58.2/glib/gmain.c:3920 #24 0x7f9ecc666adc in g_main_context_iteration (context=0x7f9ebc004ff0, may_block=may_block@entry=1) at /var/tmp/portage/dev-libs/glib-2.58.2/work/glib-2.58.2/glib/gmain.c:3981 #25 0x7f9ed2fcf07f in QEventDispatcherGlib::processEvents (this=0x55ae7dde01e0, flags=...) at kernel/qeventdispatcher_glib.cpp:422 #26 0x7f9ed2f781ca in QEventLoop::exec (this=this@entry=0x7ffe6051b530, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #27 0x7f9ed2f80bc0 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1364 #28 0x55ae7d97af25 in main (argc=, argv=) at
[plasmashell] [Bug 395919] Youtube "fullscreen" video shows plasma panel and browser title bar
https://bugs.kde.org/show_bug.cgi?id=395919 Franz Fellner changed: What|Removed |Added CC||alpine.art...@googlemail.co ||m --- Comment #3 from Franz Fellner --- Could be a kde issue: * Gwenview fullscreen shows plasma panel and window title bar. * Okular "Presentation" (which goes into fullscreen mode) shows plasma panel but somehow gets rid of the window title bar. * firefox works fine * RawTherapee works fine Interestingly Cantata, which is a pure Qt5-application, does nothing when triggering Fullscreen (besides showing a clickable label with the message "leave fullscreen"). So it could be that also Qt is invloved. This is with all the latest and greatest (ATM) stable releases available: * plasma-5.13.3 * frameworks-5.48.0 * Qt-5.11.1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 388583] Tooltip placement sometimes obscures the file
https://bugs.kde.org/show_bug.cgi?id=388583 Franz Fellner changed: What|Removed |Added CC||alpine.art...@googlemail.co ||m --- Comment #11 from Franz Fellner --- Wanted to ask how this is going. For me this issue makes dolphin under wayland completely unusable. After dolphin startup tooltip ALWAYS pops up in the top left corner of the dolphin window. After clicking somewhere in the icon view tooltip placement kind of works, as long as there is enough space for it to the bottom screen edge. If there is not enough space tooltip shifts up but not far enough. It looks like it simply aligns the bottom edge at the position where it would align the top edge if the tooltip would be placed below the icon. So it seems the actual item height is cmpletely ignored (or badly calculated under wayland). To make it clear: This is an issue under wayland, for me dolphin under X11 performs perfectly fine. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396526] New: Unable to mount a device when another user is logged in.
https://bugs.kde.org/show_bug.cgi?id=396526
Bug ID: 396526
Summary: Unable to mount a device when another user is logged
in.
Product: plasmashell
Version: 5.13.2
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Device Notifier
Assignee: plasma-b...@kde.org
Reporter: alpine.art...@googlemail.com
Target Milestone: 1.0
user1 logged in at TTY1 with plasma session. Then user2 logs in on TTY2 (via
action "change user" - user2 also on plasma). I then change to user1 and insert
a USB device (sd card reader in this case). Trying to "open with file manager"
just shows a spinning icon. user2 gets a notification that it requires the root
password to mount the device. If I cancel that passwd-dialog it appears for
user1 (that initially triggered the mount request). If I then cancel it also
for user1 it seems I can access it without any issue - no further passwd-dialog
is shown.
If I enter the password from within user2's session only user2 can access the
mounted device, user1 receives the message "file or folder
/run/media/user2/DEVICENAME does not exist" - Of course it exists but user1
doesn't have sufficient rights.
In my opinion if user1 inserts a device and requests access to the content it
should be granted also if other users are logged in.
Furthermore the errormessage should show the correct message ("not sufficient
rights" instead of "does not exist"). Giving the other users only read access
could be possible, too - but that is probably a security issue, though we are
talking of desktop machines - other users could just unplug that device as they
have physical access.
As I have the passwords for both users I can workaround this issue. For "real"
multi-user desktops the described behaviour of the device notifier makes it
impossible to work with external devices.
--
You are receiving this mail because:
You are watching all bug changes.
[gwenview] [Bug 396186] No setting for "toggle fullscreen" key binding
https://bugs.kde.org/show_bug.cgi?id=396186 Franz Fellner changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #2 from Franz Fellner --- Thx. Was false expectation (and I didn't use the search bar). It appears in the "VIEW" menu, so I expected it to also appear in that section of the shortcut editor, where you also can find "Leave Fullscreen". But it seems "toggle fullscreen" is a toplevel-shortcut. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396183] Selecting a timezone randomly selects other timezones
https://bugs.kde.org/show_bug.cgi?id=396183 --- Comment #2 from Franz Fellner --- (In reply to David Edmundson from comment #1) > Can't reproduce and not seen any other reports. > > can you make a video and upload? Here you are: https://www.dropbox.com/s/m6mbzqx752cbzl9/configure_timezone.ogv?dl=0 Nothing but local (Bukarest) selected in the beginning. Selected Berlin and just scrolled down until Rothera (~30 sec). Then scrolled back up until selected Kaliningrad becomes visible. Then scrolled down and up several times - note how with every direction change different timezones are selected. Finally scrolled further up and deselected Honolulu - and finally all auto-selected are gone, just Berlin selected. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 396189] New: Meta+Shift+2 (and 3) does not work anymore
https://bugs.kde.org/show_bug.cgi?id=396189 Bug ID: 396189 Summary: Meta+Shift+2 (and 3) does not work anymore Product: systemsettings Version: 5.13.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_khotkeys Assignee: k...@michael-jansen.biz Reporter: alpine.art...@googlemail.com Target Milestone: --- I had set Meta+Shift+# to move the active window to desktop number #. plasma before 5.13 worked fine, with 5.13 it only works for desktop # 1 and 4, moving to 2 and 3 does not work anymore. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 396188] New: shortcut editor doesn't show up in certain circumstances
https://bugs.kde.org/show_bug.cgi?id=396188 Bug ID: 396188 Summary: shortcut editor doesn't show up in certain circumstances Product: systemsettings Version: 5.13.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_khotkeys Assignee: k...@michael-jansen.biz Reporter: alpine.art...@googlemail.com Target Milestone: --- Created attachment 113774 --> https://bugs.kde.org/attachment.cgi?id=113774=edit screenshot If the window is too small it just shows an empty space. After using the scrollbar the editor shows up but isn't correctly aligned. See attached screenshot. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 396187] New: hotkey module for kwin shows up as "systemsettings"
https://bugs.kde.org/show_bug.cgi?id=396187 Bug ID: 396187 Summary: hotkey module for kwin shows up as "systemsettings" Product: systemsettings Version: 5.13.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_khotkeys Assignee: k...@michael-jansen.biz Reporter: alpine.art...@googlemail.com Target Milestone: --- Makes it hard to locate. It also prevents it (I think) from showing up in windowmanager settings when opening it via rightclick on the window titlebar. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 396186] New: No setting for "toggle fullscreen" key binding
https://bugs.kde.org/show_bug.cgi?id=396186 Bug ID: 396186 Summary: No setting for "toggle fullscreen" key binding Product: gwenview Version: 18.04.2 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: alpine.art...@googlemail.com Target Milestone: --- There is only "leave fullscreen" available. AFAIR it was possible to configure this in the past. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396183] New: Selecting a timezone randomly selects other timezones
https://bugs.kde.org/show_bug.cgi?id=396183 Bug ID: 396183 Summary: Selecting a timezone randomly selects other timezones Product: plasmashell Version: 5.13.2 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: alpine.art...@googlemail.com Target Milestone: 1.0 I am currently on Local (which is set to Bukarest). I wanted to change to Berlin/Europe. Selecting that also selects many other timezones, currently Detroit, Jayapura, Maputo, and so on. It also seems like the checked checkboxes change while scrolling, now Cancun is selected and Detroit not anymore - this is really wild and quite unusable! However it seems it doesn't use all those auto-selected timezones, just those that I manually selected. Also deselecting one of the auto-selected timeszones disables all of them. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 364840] Dolphin reads CD or DVD with every application that uses solid
https://bugs.kde.org/show_bug.cgi?id=364840 --- Comment #1 from Franz Fellner <alpine.art...@googlemail.com> --- And there actually is an issue when auto-mounting discs: Ejecting with the hardware button instead of the plasma applet the next inserted DVD can't be played. I have to eject it again with the plasma applet, close the drive - then I can play the DVD. The other thing that constantly bugs my dad is the file dialog re-spinning the disc (as already described), which allows to open several file dialogs (which really happens every day). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 364840] New: Dolphin reads CD or DVD with every application that uses solid
https://bugs.kde.org/show_bug.cgi?id=364840 Bug ID: 364840 Summary: Dolphin reads CD or DVD with every application that uses solid Product: frameworks-solid Version: 5.23.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: lu...@kde.org Reporter: alpine.art...@googlemail.com CC: alpine.art...@googlemail.com, aspotas...@gmail.com, di...@betriebsdirektor.de, fabioam...@gmail.com, fa...@kde.org, j...@gentoo.org, kaabud-...@yahoo.de, kaiuwebroul...@hotmail.com, kdelibs-b...@kde.org, kensing...@gentoo.org, lambd...@gmail.com, martin+...@serafean.cz, ma...@gmx.net, mezin.alexan...@gmail.com, payableondeat...@gmail.com, peter.pen...@gmail.com, rdie...@math.unl.edu, sebast...@sebastian-doerner.de, t.ki...@gmail.com, timo.g...@gmail.com, toddrme2...@gmail.com, war...@gmx.de It looks like there is no global cache implemented anymore but caching of devices takes place only per application. This is all latest stuff - plasma 5.6.5, kde-apps-16.04.2, frameworks 5.23 - inside a plasma5 env, device notifier sits in the tray and shows the optical disc. * Open dolphin and the disk starts spinning which leads to noticable delay * Work with dolphin and close it again. * Open dolphin again and disk spins up again. While dolphin is running open another application that uses solid (e.g. every file dialog in any app) and the disk doesn't spin up, so it might be the cache gets deleted when the last application closes that uses that cache. Though I just see it works for kate but not for ksnapshot. Weird.. Automount reduces the spinups to two: One when inserting (Device Notifier pops up) and another one for the first application launch that uses solid. IMHO should only spin up once but hey, better than at every launch of dolphin, etc. I will go the automount route this time as I can't wait another 2.x years for a fix. +++ This bug was initially created as a clone of Bug #261552 +++ Version: unspecified (using KDE 4.5.90) OS:Linux Ever time I change to a new folder in Dolphin with a CD or DVD in my drive, the light and the drive comes on and the drive spins up. Dolphin then locks up until it is finished with whatever it is doing with the drive. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
