[plasmashell] [Bug 490175] Crash in KDE when using Meta + Shift + 0 to remove screen magnification.
https://bugs.kde.org/show_bug.cgi?id=490175 --- Comment #1 from Santiago Jose Lopez Borrazas --- Created attachment 171607 --> https://bugs.kde.org/attachment.cgi?id=171607&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 490175] New: Crash in KDE when using Meta + Shift + 0 to remove screen magnification.
https://bugs.kde.org/show_bug.cgi?id=490175 Bug ID: 490175 Summary: Crash in KDE when using Meta + Shift + 0 to remove screen magnification. Classification: Plasma Product: plasmashell Version: 5.27.11 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: sjlop...@gmx.es CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.11) (Compiled from sources) Qt Version: 5.15.13 Frameworks Version: 5.115.0 Operating System: Linux 6.9.8-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux trixie/sid DrKonqi: 5.27.11 [CoredumpBackend] -- Information about the crash: I was typing something with the web browser, and as soon as I finish, I press Meta + Shift + 0, it closes both the KDE panel and the desktop. It took me about 15~20 seconds to get both the panel and the desktop back. I didn't do anything special. Just to give me control, but the Alt + Tab combination didn't stop working. I have never seen a failure of this caliber. Also, I've been getting a weird shutdown of Discover (to update the system). The crash can be reproduced sometimes. -- Backtrace (Reduced): #5 0x7fd4bba5d733 in QQuickItem::~QQuickItem() () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 [...] #7 0x7fd4b9cfb0bb in QObject::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fd4ba962f82 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7fd4b9cce0e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fd4b9cd1801 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488709] Plasma crashed when connecting to a network with the plasma-nm applet
https://bugs.kde.org/show_bug.cgi?id=488709 --- Comment #2 from Santiago Pinto --- (In reply to Bug Janitor Service from comment #1) > Debian advises users to not submit bugs upstream > (https://www.debian.org/Bugs/Reporting). Oh, I'm sorry. Excuse me. I didn't know I had to always use reportbug and *not* report the issue to the original developers. > Could you report the bug to Debian using the report bug utility > (https://packages.debian.org/stable/utils/reportbug)? Sure! > Thanks again! Thank you too! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488709] New: Plasma crashed when connecting to a network with the plasma-nm applet
https://bugs.kde.org/show_bug.cgi?id=488709 Bug ID: 488709 Summary: Plasma crashed when connecting to a network with the plasma-nm applet Classification: Plasma Product: plasmashell Version: 5.20.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: santiagopi...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.20.5) Qt Version: 5.15.2 Frameworks Version: 5.78.0 Operating System: Linux 5.10.0-22-686-pae i686 Windowing system: X11 Distribution: Debian GNU/Linux 11 (bullseye) -- Information about the crash: - What I was doing when the application crashed: I opened KRunner to write a password there because the plasma-nm applet changes the network selected to connect to while writing the password: if the network list refreshes, the selected network is the one that happens to end in the same position as the previously selected one. This happens consistently on this version of KDE/Plasma, which is outdated and I don't know if the issue has been corrected already, so I'm not reporting that issue. The issue here happened when I selected the password in KRunner, copied it, closed KRunner with the Escape key, then clicked on the plasma-nm tray icon, selected the network I wanted to connect to, and quickly pasted the password in the field with Ctrl+V and pressed Enter. The whole desktop flickered a bit and DrKonqui informed me that Plasma crashed; the connection to the network didn't succeed. - Unusual behavior I noticed: The problem with changing selected networks in plasma-nm applet. I could connect to the network later with no problems. Also, I couldn't reproduce the issue again by doing the same. One particular thing to note is that I experience frequent disconnects from WiFi, possibly related to this driver bug: https://bugzilla.kernel.org/show_bug.cgi?id=203709 I reviewed the other bug reports suggested as possible duplicates, both the suggested ones and the ones originally reporting the same bug; while the stack trace is very similar at the top and in the middle compared to those reports, they are not exactly equal; also the context of the crashes are rather different. As such, I am reporting this crash as a separate bug report since I am not sure whether the suggested duplicates are really that. PD: KDE is great, good work! The crash does not seem to be reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #5 std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x9) at /usr/include/c++/10/bits/atomic_base.h:741 #6 std::atomic::load (__m=std::memory_order_relaxed, this=0x9) at /usr/include/c++/10/atomic:523 #7 QAtomicOps::loadRelaxed (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239 #8 QBasicAtomicPointer::loadRelaxed (this=0x9) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:248 #9 QObjectPrivate::maybeSignalConnected (this=0x40aa0e0, signalIndex=19) at kernel/qobject.cpp:482 #10 0xb5abf3b7 in doActivate (sender=0x3829b70, signal_index=19, argv=0xbffe4a18) at kernel/qobject.cpp:3788 #11 0xb5ab848f in QMetaObject::activate (sender=, m=, local_signal_index=, argv=0x0) at kernel/qobject.cpp:3946 #12 0xb5ab84fc in QMetaObject::activate (sender=0x3829b70, signal_index=21, argv=0x0) at kernel/qobject.cpp:3971 #13 0xb4d5c9fd in VDMModelDelegateDataType::notify (this=, items=..., index=, count=, roles=...) at qqmladaptormodel.cpp:175 #14 0xb4d6519b in QQmlAdaptorModel::notify (roles=..., count=33, index=0, items=..., this=0x3b050ac) at ../../include/QtQmlModels/5.15.2/QtQmlModels/private/../../../../../src/qmlmodels/qqmladaptormodel_p.h:159 #15 QQmlDelegateModel::_q_itemsChanged (this=0x3ae6ff0, index=0, count=33, roles=...) at qqmldelegatemodel.cpp:1472 #16 0xb4d6e1bb in QQmlDelegateModel::_q_layoutChanged (this=0x3ae6ff0, parents=..., hint=QAbstractItemModel::VerticalSortHint) at qqmldelegatemodel.cpp:1987 #17 0xb4d6e471 in QQmlDelegateModel::qt_static_metacall (_o=0x3ae6ff0, _c=QMetaObject::InvokeMetaMethod, _id=14, _a=0xbffe5d00) at .moc/moc_qqmldelegatemodel_p.cpp:219 #18 0xb4d6e95e in QQmlDelegateModel::qt_metacall (this=0x3ae6ff0, _c=QMetaObject::InvokeMetaMethod, _id=14, _a=0xbffe5d00) at .moc/moc_qqmldelegatemodel_p.cpp:357 #19 0xb5abf517 in doActivate (sender=, signal_index=, argv=0xbffe5d00) at kernel/qobject.cpp:3912 #20 0xb5ab848f in QMetaObject::activate (sender=, m=, local_signal_index=, argv=0xbffe5d00) at kernel/qobject.cpp:3946 #21 0xb5a1be06 in QAbstractItemModel::layoutChanged (this=0x3bc79e0, _t1=..., _t2=) at .moc/moc_qabstractitemmodel.cpp:571 #22 0xb5a5893f in QSortFilterProxyModelPrivate::_q_sourceDataChanged (this=, source_top_left
[kwin] [Bug 488640] Kwin (wayland) crashes after idle for about one hour
https://bugs.kde.org/show_bug.cgi?id=488640 --- Comment #1 from Leandro Santiago da Silva --- It seems this bug is a duplicate of https://bugs.kde.org/show_bug.cgi?id=485318 and should have been fixed on commit cadf16b12e10c591b746d6f8228a16ec0101362b I will wait until this changes gets to my distro to test it again, as it seems to be a quite fresh change. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488640] New: Kwin (wayland) crashes after idle for about one hour
https://bugs.kde.org/show_bug.cgi?id=488640 Bug ID: 488640 Summary: Kwin (wayland) crashes after idle for about one hour Classification: Plasma Product: kwin Version: 6.0.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: leandrosansi...@gmail.com Target Milestone: --- Created attachment 170581 --> https://bugs.kde.org/attachment.cgi?id=170581&action=edit backtrace from all threads obtained from attaching gdb to kwin_wayland SUMMARY KWin crashes when my monitors go off due to the energy saving policy. I have three screens connected to HDMI and DisplayPort. I can reproduce this bug since the Plasma 5 days and have reported it already months ago, but it was closed as I could not get more info (https://bugs.kde.org/show_bug.cgi?id=480992). I now can reproduce the bug quite easily. It simply takes me hours to to so, as the bug happens after I stay away from the computer for a long time :-( It turns out I managed to attach gdb to kwin_wayland (connected from another computer, via ssh, as drkonqi is not triggered) and get a backtrace and a coredump. I am posting a backtrace here (thread apply all bt -full). I can submit the coredump upon request. STEPS TO REPRODUCE 1. have three screens connected to hdmi and displayports 2. set the energy policies to shutdown the screens after some time (I put in 5min in this case) 3. stay away from the computer until the screen turns off. It might flicker and turn off and on multiple times (no idea why) 4. be patient 5. kwin crashes and all non-qt applications are closed. Only Qt applications keep open. OBSERVED RESULT Kwin crashes (and restarts) and all non-qt applications close EXPECTED RESULT Kwin not crashing or at least all applications (qt or not) keep open after the crash. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Operating System: Manjaro Linux KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.9.3-3-MANJARO (64-bit) Graphics Platform: Wayland Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: AMD Radeon RX 6600 Manufacturer: ASUS ADDITIONAL INFORMATION In the attached backtrace, look for (this=0x0), which is the call that triggers the crash. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 484762] DigiKam doesn't recognize XMP video tags.
https://bugs.kde.org/show_bug.cgi?id=484762 --- Comment #8 from Santiago Figarola --- (In reply to Maik Qualmann from comment #7) > We already have a bug report as a request to create a configuration for this. > But if you don't activate writing metadata with ExifTool and activate "Only > in read-only entries" as an option for writing in sidecar, it should work. > Read-only means not only that the files are read-only, but also that Exiv2 > cannot write this file type. > > Maik Alright. Thank you so much. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 484762] DigiKam doesn't recognize XMP video tags.
https://bugs.kde.org/show_bug.cgi?id=484762 --- Comment #6 from Santiago Figarola --- (In reply to Maik Qualmann from comment #4) > Then you need to enable the option for “Sidecar filenames compatible with > commercial programs”. After re-reading the metadata, everything will be > available. > > Maik One question: is it possible to make DigiKam write to the item and sidecar, ONLY when the item is a video? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 484762] DigiKam doesn't recognize XMP video tags.
https://bugs.kde.org/show_bug.cgi?id=484762 --- Comment #5 from Santiago Figarola --- (In reply to Maik Qualmann from comment #4) > Then you need to enable the option for “Sidecar filenames compatible with > commercial programs”. After re-reading the metadata, everything will be > available. > > Maik It seems to be finally working. I had to manually prompt DigiKam to re-read the metafiles. Thanks for the help. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 484762] DigiKam doesn't recognize XMP video tags.
https://bugs.kde.org/show_bug.cgi?id=484762 --- Comment #3 from Santiago Figarola --- (In reply to Maik Qualmann from comment #2) > Ok, saving metadata is only possible in the Pro version, I won't buy F-spot > now. But they should be sidecars. > Have you activated sidecar reading in digiKam? Have you considered that > there are different sidecar formats, i.e. BASENAME.EXT.xmp and BASENAME.xmp > (mostly commercial programs). Have you selected the corresponding option in > the digiKam settings? > > Maik Hi. Yes, in "Sidecards", I have "Read from sidecar files" checked. The sidecar filename format on F-stop is "image.xmp" -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 484762] New: DigiKam doesn't recognize XMP video tags.
https://bugs.kde.org/show_bug.cgi?id=484762 Bug ID: 484762 Summary: DigiKam doesn't recognize XMP video tags. Classification: Applications Product: digikam Version: 8.4.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Tags-Keywords Assignee: digikam-bugs-n...@kde.org Reporter: santiagofigarola2...@gmail.com Target Milestone: --- SUMMARY I put the tags on my images and videos using F-stop on Android. DigiKam perfectly recognizes the tags of the images, but the videos' (which are in XMP files) go ignored. STEPS TO REPRODUCE 1. Add tags to videos, which creates an XMP file. 2. Open DigiKam and search for tags. 3. The videos do not show the assigned tags, nor you can find the video by its tag. OBSERVED RESULT DigiKam doesn't recognize XMP video tags. EXPECTED RESULT DigiKam recognizes XMP video tags. SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480992] New: Kwin (wayland) crashes after idle for about one hour
https://bugs.kde.org/show_bug.cgi?id=480992 Bug ID: 480992 Summary: Kwin (wayland) crashes after idle for about one hour Classification: Plasma Product: kwin Version: 5.27.10 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: leandrosansi...@gmail.com Target Milestone: --- Created attachment 165641 --> https://bugs.kde.org/attachment.cgi?id=165641&action=edit energy settings SUMMARY Kwin_wayland Crashes on no activity. I've noticed that kwin logs to syslog when Kwin tries to put my two screens to sleep. One screen is on a HDMI port and the other on a Display Port. The line I often see on `dmesg` is: ``` [272940.976297] traps: VizCompositorTh[2705470] trap invalid opcode ip:560a520d6d6e sp:7f2a2bffe8c0 error:0 in signal-desktop[560a4d6b2000+7e36000] ``` The screens are configured in the KDE settings to go to sleep after 10min. They never go though, instead flickering and finally turning on again. This time though, after leaving the computer doing nothing for about one hour, when I returned, Plasma was on a "reset" state, with no windows open. The screen was unlocked though, so I suspect that the plasma session did not restart (I did not have to unlock it or go back to SDDM). The applications set on autostart did not restart. Upon checking `dmesg`, unfortunately this is the best info I can get: ``` [229252.822425] traps: GlobalQueue[26][2674503] general protection fault ip:7fe76a2c1ddd sp:7fe7015fefd8 error:0 in libQt5Core.so.5.15.12[7fe76a09f000+2dd000] [230033.962062] traps: VizCompositorTh[2567709] trap int3 ip:7fbe4111290d sp:7fbded5fd2d0 error:0 in libcef.so[7fbe37a15000+9aec000] [230644.965366] traps: VizCompositorTh[2556985] trap invalid opcode ip:560a520d6d6e sp:7f2a2c9fe490 error:0 in signal-desktop[560a4d6b2000+7e36000] [230725.867704] traps: VizCompositorTh[2687472] trap invalid opcode ip:560a520d6d6e sp:7f2a2c9fe8c0 error:0 in signal-desktop[560a4d6b2000+7e36000] [232955.172067] traps: VizCompositorTh[2682322] trap int3 ip:7fbe4111290d sp:7fbdecbfd090 error:0 in libcef.so[7fbe37a15000+9aec000] [232993.119132] traps: VizCompositorTh[2688239] trap invalid opcode ip:560a520d6d6e sp:7f2a2bffe8c0 error:0 in signal-desktop[560a4d6b2000+7e36000] [269637.931822] traps: VizCompositorTh[2549760] trap invalid opcode ip:56323b7a7afd sp:7f0e919fe8b0 error:0 in joplin[5632370c7000+79c7000] [270246.887782] traps: VizCompositorTh[2959470] trap invalid opcode ip:56323b7a7afd sp:7f0e919fe8b0 error:0 in joplin[5632370c7000+79c7000] [272940.976097] traps: VizCompositorTh[2963805] trap invalid opcode ip:56323b7a7afd sp:7f0e919fe8b0 error:0 in joplin[5632370c7000+79c7000] [272940.976297] traps: VizCompositorTh[2705470] trap invalid opcode ip:560a520d6d6e sp:7f2a2bffe8c0 error:0 in signal-desktop[560a4d6b2000+7e36000] [272942.646675] traps: VizCompositorTh[2983487] trap invalid opcode ip:56323b7a7afd sp:7f0e919fe8b0 error:0 in joplin[5632370c7000+79c7000] [273551.878088] kwin_wayland[2279]: segfault at 0 ip 7f69ed36939a sp 73e2c930 error 4 in libkwin.so.5.27.10[7f69ed369000+327000] likely on CPU 31 (core 15, socket 0) [273551.878099] Code: 04 25 00 00 00 00 0f 0b 48 8b 04 25 00 00 00 00 0f 0b 8b 04 25 20 00 00 00 0f 0b 90 8b 04 25 20 00 00 00 0f 0b 90 f3 0f 1e fa <48> 8b 04 25 00 00 00 00 0f 0b 31 ff ff 15 14 ed 48 00 0f b7 04 25 [273551.882364] traps: VizCompositorTh[2983700] trap invalid opcode ip:560a520d6d6e sp:7f2a2bffe8c0 error:0 in signal-desktop[560a4d6b2000+7e36000] [273585.084529] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [273585.084533] Bluetooth: BNEP filters: protocol multicast [273585.084537] Bluetooth: BNEP socket layer initialized ``` STEPS TO REPRODUCE 1. Configure the screens to switch off after 10min, as in the attached image. 2. let the computer idle. In my case, I left two dolphin windows, each with an embedded terminal (F4) open, doing some work (in my case, computing md5sum of some large files). 3. Go have breakfast and return after about 1 hour. 4. The workspace is empty, with no windows open. All previously running processes were killed. OBSERVED RESULT Plasma workspace empty, no windows open. All previously opened windows were killed. EXPECTED RESULT The screens should've been switched off. Maybe the screens would be locked, asking for authentication to unlock. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.7.0-0-MANJARO (amd64) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.12 ADDITIONAL INFORMATION Kwin Info: ``` KWin Support Information: The following information should be used when requesting support on e.g. https://forum.kde.org. It provides information about the currently running instance, which options are used, what OpenGL driver and which effects are running. Please post the information provided underne
[krfb] [Bug 472453] New: krfb-virtualmonitor asserts when a client connects
https://bugs.kde.org/show_bug.cgi?id=472453 Bug ID: 472453 Summary: krfb-virtualmonitor asserts when a client connects Classification: Applications Product: krfb Version: 23.04.3 Platform: Archlinux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: grundleb...@googlemail.com Reporter: santiagocezar2...@gmail.com Target Milestone: --- SUMMARY krfb-virtualmonitor crashes right after a client connects, no image is send to the client. STEPS TO REPRODUCE 1. run `bin/krfb-virtualmonitor --name "banana" --resolution 1200x400 --password --port 5900` 2. connect from another device (using bVNC on Android in this case) 3. boom OBSERVED RESULT the program crashes when a new client connects EXPECTED RESULT the program should make a virtual monitor and display it on the client SOFTWARE/OS VERSIONS Linux: 6.4.3-arch1-2 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Graphics: Mesa Intel® UHD Graphics 620 Commit: ce562e82bb6524b558ca9f41ac81758d6c3d34e4 terminal output: ``` new client request /usr/include/c++/13.1.1/optional:477: constexpr _Tp& std::_Optional_base_impl<_Tp, _Dp>::_M_get() [with _Tp = PipeWireCursor; _Dp = std::_Optional_base]: Assertion 'this->_M_is_engaged()' failed. fish: Job 1, 'bin/krfb-virtualmonitor --name …' terminated by signal SIGABRT (Abort) ``` ``` #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x75e9f2d3 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78 #2 0x75e4fa08 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x75e38538 in __GI_abort () at abort.c:79 #4 0x760dd3b2 in std::__glibcxx_assert_fail(char const*, int, char const*, char const*) (file=file@entry=0x7fffe805b2e0 "/usr/include/c++/13.1.1/optional", line=line@entry=477, function=function@entry=0x7fffe805b248 "constexpr _Tp& std::_Optional_base_impl<_Tp, _Dp>::_M_get() [with _Tp = PipeWireCursor; _Dp = std::_Optional_base]", condition=condition@entry=0x7fffe805b000 "this->_M_is_engaged()") at /usr/src/debug/gcc/gcc/libstdc++-v3/src/c++11/debug.cc:61 #5 0x7fffe804fa5c in std::_Optional_base_impl >::_M_get() (this=) at /usr/include/c++/13.1.1/optional:477 #6 std::_Optional_base_impl >::_M_get() (this=) at /usr/include/c++/13.1.1/optional:475 #7 std::optional::operator->() (this=) at /usr/include/c++/13.1.1/optional:966 #8 PWFrameBuffer::cursorPosition() (this=) at /usr/src/debug/krfb/krfb-23.04.3/framebuffers/pipewire/pw_framebuffer.cpp:546 #9 0x55568abd in RfbServerManager::updateScreens() (this=0x555846b0 <(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder>) at /home/santi/Cositas/Contrib/krfb/krfb/rfbservermanager.cpp:148 #10 0x5556b8a9 in QtPrivate::FunctorCall, QtPrivate::List<>, void, void (RfbServerManager::*)()>::call(void (RfbServerManager::*)(), RfbServerManager*, void**) (f=(void (RfbServerManager::*)(class RfbServerManager * const)) 0x55568a5a , o=0x555846b0 <(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder>, arg=0x7fffd440) at /usr/include/qt/QtCore/qobjectdefs_impl.h:152 #11 0x5556b51b in QtPrivate::FunctionPointer::call, void>(void (RfbServerManager::*)(), RfbServerManager*, void**) (f=(void (RfbServerManager::*)(class RfbServerManager * const)) 0x55568a5a , o=0x555846b0 <(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder>, arg=0x7fffd440) at /usr/include/qt/QtCore/qobjectdefs_impl.h:185 #12 0x5556ae67 in QtPrivate::QSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1, this_=0x5572b810, r=0x555846b0 <(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder>, a=0x7fffd440, ret=0x0) at /usr/include/qt/QtCore/qobjectdefs_impl.h:418 #13 0x766d1237 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7fffd440, r=, this=0x5572b810, this=, r=, a=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #14 doActivate(QObject*, int, void**) (sender=0x556daee0, signal_index=3, argv=0x7fffd440) at kernel/qobject.cpp:3925 #15 0x766d2d6f in QTimer::timeout(QTimer::QPrivateSignal) (this=, _t1=...) at .moc/moc_qtimer.cpp:205 #16 0x766c3cee in QObject::event(QEvent*) (this=0x556daee0, e=0x7fffd5b0) at kernel/qobject.cpp:1324 #17 0x7737893f in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x556daee0, e=0x7fffd5b0) at kernel/qapplication.cpp:3640 #18 0x7669c2f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x556daee0, event=0x7fffd5b0) at kernel/qcoreapplication.cpp:1064 #19 0x766ea9bb in QTimerInfoList::activateT
[digikam] [Bug 471299] Al pulsar configurar digikam, se cierra y no puedo entrar.
https://bugs.kde.org/show_bug.cgi?id=471299 santiago cacho changed: What|Removed |Added Assignee|unassigned-b...@kde.org |digikam-bugs-n...@kde.org Product|kde |digikam Version|unspecified |7.10.0 Component|general |general --- Comment #1 from santiago cacho --- Ha sido al cambiar de PC. Viene con windows 11 y me da este fallo. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 471299] New: Al pulsar configurar digikam, se cierra y no puedo entrar.
https://bugs.kde.org/show_bug.cgi?id=471299 Bug ID: 471299 Summary: Al pulsar configurar digikam, se cierra y no puedo entrar. Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: santiagocac...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 11 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 7.10.0 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 426541] Please clarify error message "SFTP: No storage locations configured"
https://bugs.kde.org/show_bug.cgi?id=426541 santiago changed: What|Removed |Added CC||santiag...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444398] Application Launcher (KickOff) not working with Wacom tablets
https://bugs.kde.org/show_bug.cgi?id=444398 --- Comment #2 from Santiago Shang --- (In reply to Nate Graham from comment #1) > Can confirm. Hover with a stylus works, click does not. So strange... Because hover doesn't work for me the most of time. check this: https://twitter.com/kdecommunity/status/1452764870718459907 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444398] Application Launcher (KickOff) not working with Wacom tablets
https://bugs.kde.org/show_bug.cgi?id=444398 Santiago Shang changed: What|Removed |Added CC||santiagosh...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444398] New: Application Launcher (KickOff) not working with Wacom tablets
https://bugs.kde.org/show_bug.cgi?id=444398 Bug ID: 444398 Summary: Application Launcher (KickOff) not working with Wacom tablets Product: plasmashell Version: 5.23.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: santiagosh...@gmail.com CC: mikel5...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 SUMMARY I can't click inside the icons to open an application in favorite or navigate in the side bar categories menu. STEPS TO REPRODUCE 1. Using a Wacom tablet, Click on Plasma Kickoff Menu 2. Click in any Application Icon or section inside the menu(i.e. Favorites) 3. Any icon doesn't respond to the action. OBSERVED RESULT The kickoff menu is useless with a wacom tablet at this time. In the Past version it worked perfectly. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439004] New: BorderlessMaximizedWindows=true bugs maximized window on Wayland
https://bugs.kde.org/show_bug.cgi?id=439004 Bug ID: 439004 Summary: BorderlessMaximizedWindows=true bugs maximized window on Wayland Product: kwin Version: 5.22.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: santiagogonzalezbog...@gmail.com Target Milestone: --- SUMMARY I'm on Arch, running Plasma 5.22.1, KDE frameworks 5.83.0, qt version 5.12.2, only Intel on Wayland. I use a option on my kwinrc that hides decorations when you maximize the window, after you put in in your config file and reboot it does it only the first time on the window that is maximized. What happens? The first window that you maximize it you can't use your mouse, it hides the title bar as it should and it still plays audio or use your keyboard but it does not let you use your mouse. STEPS TO REPRODUCE 1. Add BorderlessMaximizedWindows=true 2. Reboot 3. Open anything like a browser or dolphin (it does not happen on konsole tho) 4. Maximize a window (It will not let you use your mouse, it's like it doesn't exists) 5. Open another instance of the same app tho make it stop and make it work as it should again OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 --- Comment #28 from Santiago Cézar --- Here is the info I got from coredumpctl for plasmashell PID: 53482 (plasmashell) UID: 1002 (santi) GID: 1002 (santi) Signal: 6 (ABRT) Timestamp: Thu 2021-05-06 17:16:29 -03 (7min ago) Command Line: plasmashell -d -n Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1002.slice/user@1002.service/app.slice/app-org.kde.konsole-c7898390fcab48f4a33a7b08fc3b0fb5.scope Unit: user@1002.service User Unit: app-org.kde.konsole-c7898390fcab48f4a33a7b08fc3b0fb5.scope Slice: user-1002.slice Owner UID: 1002 (santi) Boot ID: a7fa3af3286c470485bf9405b9833b2a Machine ID: 82ad6e578fd041e19a9ca05f32db1210 Hostname: mini Storage: /var/lib/systemd/coredump/core.plasmashell.1002.a7fa3af3286c470485bf9405b9833b2a.53482.162033218900.zst (present) Disk Size: 14.1M Message: Process 53482 (plasmashell) of user 1002 dumped core. Stack trace of thread 53482: #0 0x7f54c1a2b292 raise (libc.so.6 + 0x3d292) #1 0x7f54c1a148a4 abort (libc.so.6 + 0x268a4) #2 0x7f54c1e8f42d _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5 + 0xb142d) #3 0x7f54bfd9b4d4 _ZNK15QtWaylandClient15QWaylandDisplay10checkErrorEv (libQt5WaylandClient.so.5 + 0x804d4) #4 0x7f54bfd9b6ea _ZN15QtWaylandClient15QWaylandDisplay13flushRequestsEv (libQt5WaylandClient.so.5 + 0x806ea) #5 0x7f54bfda8ace _ZN15QtWaylandClient14QWaylandWindow10setVisibleEb.part.0 (libQt5WaylandClient.so.5 + 0x8dace) #6 0x7f54c24a2aab _ZN14QWindowPrivate10setVisibleEb (libQt5Gui.so.5 + 0x172aab) #7 0x55d8f59fb755 _ZN11ShellCorona20primaryOutputChangedEv (plasmashell + 0x44755) #8 0x7f54c208d4b0 _Z10doActivateILb0EEvP7QObjectiPPv (libQt5Core.so.5 + 0x2af4b0) #9 0x7f54c248b606 _ZN15QGuiApplication20primaryScreenChangedEP7QScreen (libQt5Gui.so.5 + 0x15b606) #10 0x7f54c24bb9bf _ZN7QScreenD1Ev (libQt5Gui.so.5 + 0x18b9bf) #11 0x7f54c24bbc7d _ZN7QScreenD0Ev (libQt5Gui.so.5 + 0x18bc7d) #12 0x7f54c2478d0b _ZN22QWindowSystemInterface19handleScreenRemovedEP15QPlatformScreen (libQt5Gui.so.5 + 0x148d0b) #13 0x7f54bfd9e8c6 _ZN15QtWaylandClient15QWaylandDisplay22registry_global_removeEj (libQt5WaylandClient.so.5 + 0x838c6) #14 0x7f54c04a0c04 ffi_call_unix64 (libffi.so.6 + 0x6c04) #15 0x7f54c04a0107 ffi_call (libffi.so.6 + 0x6107) #16 0x7f54c1929d10 wl_closure_invoke.constprop.0 (libwayland-client.so.0 + 0x6d10) #17 0x7f54c192a42b dispatch_event.isra.0 (libwayland-client.so.0 + 0x742b) #18 0x7f54c192a61c wl_display_dispatch_queue_pending (libwayland-client.so.0 + 0x761c) #19 0x7f54bfd9b6d3 _ZN15QtWaylandClient15QWaylandDisplay13flushRequestsEv (libQt5WaylandClient.so.5 + 0x806d3) #20 0x7f54c208d4fd _Z10doActivateILb0EEvP7QObjectiPPv (libQt5Core.so.5 + 0x2af4fd) #21 0x7f54c208fb3a _ZN15QSocketNotifier9activatedE17QSocketDescriptorNS_4TypeENS_14QPrivateSignalE (libQt5Core.so.5 + 0x2b1b3a) #22 0x7f54c20902d4 _ZN15QSocketNotifier5eventEP6QEvent (libQt5Core.so.5 + 0x2b22d4) #23 0x7f54c2ccbe73 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x1ade73) #24 0x7f54c205cf48 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x27ef48) #25 0x7f54c20aa17f _ZL28socketNotifierSourceDispatchP8_GSourcePFiPvES1_ (libQt5Core.so.5 + 0x2cc17f) #26 0x7f54c05314cf g_main_context_dispatch (libglib-2.0.so.0 + 0x554cf) #27 0x7f54c05854e8 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0xa94e8) #28 0x7f54c052ec03 g_main_context_iteration (libglib-2.0.so.0 + 0x52c03) #29 0x7f54c20a96f8 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2cb6f8) #30 0x7f54c205b9b2 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x27d9b2) #31 0x7f54c2063544 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x285544) #32 0x55d8f59ddfd1 main (plasmashell + 0x26fd1) #33 0x7f54c1a15b75 __libc_start_main (libc.so.6 + 0x27b75) #34 0x55d8f59de3ee _start (plasmashell + 0x273ee) Stack trace of thread 53483: #0 0x7f54c1ae39ff __poll (libc.so.6 + 0xf59ff) #1 0x7f54c058547c g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0xa947c
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 --- Comment #27 from Santiago Cézar --- > I just tried to turn off my monitor and after this i successfully returned > back, only plasmashell is gone I've recently tried running Plasma on Wayland again and had exactly this behaviour > with plasma from master, on stable its still a crash probably I've installed Plasma 5.21.4 from Fedora 34 repositories -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 434799] New: kdeinit5 crashes when saving screenshot from Flameshot
https://bugs.kde.org/show_bug.cgi?id=434799 Bug ID: 434799 Summary: kdeinit5 crashes when saving screenshot from Flameshot Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: carlos.santi...@outlook.com Target Milestone: --- Using Garuda Linux KDE. kdeinit5 crashes every time a screenshot is saved using Flameshot. STEPS TO REPRODUCE 1. Open Flameshot and take a screenshot. 2. Save to disk. 3. kdeinit5 crashes OBSERVED RESULT Application: kdeinit5 (kdeinit5), signal: Segmentation fault [KCrash Handler] #4 0x7f431748c78c in __memmove_avx_unaligned_erms () from /usr/lib/libc.so.6 #5 0x7f4318351492 in ?? () from /usr/lib/qt/plugins/kf5/kio/thumbnail.so #6 0x7f4313b086ef in KIO::SlaveBase::dispatch(int, QByteArray const&) () from /usr/lib/libKF5KIOCore.so.5 #7 0x7f4313b09016 in KIO::SlaveBase::dispatchLoop() () from /usr/lib/libKF5KIOCore.so.5 #8 0x7f431834f026 in kdemain () from /usr/lib/qt/plugins/kf5/kio/thumbnail.so #9 0x55793156f5bd in ?? () #10 0x557931570a59 in ?? () #11 0x557931571237 in ?? () #12 0x55793156cb54 in ?? () #13 0x7f431734fb25 in __libc_start_main () from /usr/lib/libc.so.6 #14 0x55793156d6be in ?? () [Inferior 1 (process 162186) detached] -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432712] Aurorae window decoration icon themes using .svgz files do not work in GTK apps with client side decorations
https://bugs.kde.org/show_bug.cgi?id=432712 Santiago Cézar changed: What|Removed |Added CC||santiagocezar2...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Santiago Cézar changed: What|Removed |Added CC||santiagocezar2...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 428732] Yakuake does not correctly save on which screen it should open
https://bugs.kde.org/show_bug.cgi?id=428732 --- Comment #2 from Santiago Podestá --- Sorry, I changed that to unspecified now. I'm on KDE Frameworks 5.75. Maybe this is solved when using 5.76? -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 428732] Yakuake does not correctly save on which screen it should open
https://bugs.kde.org/show_bug.cgi?id=428732 Santiago Podestá changed: What|Removed |Added Version|Git (Frameworks 5) |unspecified -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 428732] New: Yakuake does not correctly save on which screen it should open
https://bugs.kde.org/show_bug.cgi?id=428732 Bug ID: 428732 Summary: Yakuake does not correctly save on which screen it should open Product: yakuake Version: Git (Frameworks 5) Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: santiagol...@gmail.com Target Milestone: --- SUMMARY Yakuake does not correctly save on which screen it should open. STEPS TO REPRODUCE 1. Open Yakuakea and go to Configure Yakuake... 3. Set "Open on screen" to Screen 1. 4. Close Yakuake and reopen Yakuake. 5. Go to Configure Yakuake... OBSERVED RESULT Open in screen is set to Screen 2. EXPECTED RESULT Open in screen should be set to Screen 1. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.20.2 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION I'm using a Nvidia GPU, driver version 455.28. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351687] Desktop grid expands onto other screens during zoom-in animation
https://bugs.kde.org/show_bug.cgi?id=351687 Santiago Podestá changed: What|Removed |Added Version|5.14.1 |5.19.5 CC||santiagol...@gmail.com --- Comment #6 from Santiago Podestá --- (In reply to Vlad Zahorodnii from comment #4) > I think it's not a good idea to unset PAINT_SCREEN_TRANSFORMED because KWin > checks that flag when deciding what method to use for clipping windows. What problems would that bring? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425118] Incorrect use of "Ctrl+" in the UI
https://bugs.kde.org/show_bug.cgi?id=425118 Santiago Munoz changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/b4577f3be ||5ada324ac04525362a1d80d9187 ||10f1 --- Comment #1 from Santiago Munoz --- Git commit b4577f3be5ada324ac04525362a1d80d918710f1 by Santiago A M Rodriguez. Committed on 30/08/2020 at 14:47. Pushed by rempt into branch 'master'. Show shortcuts in native format where applicable Instead of statically showing "Ctrl+N" and the sorts in all platforms, display shortcuts in a native way for each. M +1-1libs/ui/KisPart.cpp M +1-1libs/ui/KisViewManager.cpp M +4-2libs/ui/KisWelcomePageWidget.cpp M +1-1plugins/python/tenscripts/Manual.html M +2-1plugins/python/tenscripts/uitenscripts.py https://invent.kde.org/graphics/krita/commit/b4577f3be5ada324ac04525362a1d80d918710f1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 400618] Compositions order cant be changed
https://bugs.kde.org/show_bug.cgi?id=400618 Santiago Munoz changed: What|Removed |Added CC||smr.ram...@gmail.com --- Comment #2 from Santiago Munoz --- I have opened a merge request to add support for this: https://invent.kde.org/graphics/krita/-/merge_requests/484 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361814] Hold shift + drag to change brush size to snap to whole numbers
https://bugs.kde.org/show_bug.cgi?id=361814 Santiago Munoz changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/0a8bdbe71 ||69a465e87e6d380cc42fa8e716b ||0ab5 Resolution|--- |FIXED --- Comment #3 from Santiago Munoz --- Git commit 0a8bdbe7169a465e87e6d380cc42fa8e716b0ab5 by Santiago A M Rodriguez. Committed on 16/08/2020 at 12:24. Pushed by dkazakov into branch 'master'. New shortcut: Resize brush in full pixel increments This introduces a new shortcut to resize the brush like the default Shift+Left click, but snapping to the closest full pixel. The default Shift+Left Click now becomes the 'Normal' action under 'Change Primary Setting' of Canvas shortcut, and this addition becomes the 'Snap' action. M +23 -8libs/ui/input/kis_change_primary_setting_action.cpp M +9-0libs/ui/input/kis_change_primary_setting_action.h M +2-0libs/ui/tool/kis_tool.h M +11 -7libs/ui/tool/kis_tool_freehand.cc M +1-1libs/ui/tool/kis_tool_polyline_base.cpp M +3-3plugins/tools/basictools/kis_tool_multihand.cpp M +8-5plugins/tools/tool_transform2/kis_liquify_transform_strategy.cpp https://invent.kde.org/graphics/krita/commit/0a8bdbe7169a465e87e6d380cc42fa8e716b0ab5 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 421127] New: Unicode shortcut Ctrl-Shift-U not working at all.
https://bugs.kde.org/show_bug.cgi?id=421127 Bug ID: 421127 Summary: Unicode shortcut Ctrl-Shift-U not working at all. Product: kde Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: santiago...@outlook.com Target Milestone: --- SUMMARY Hi, when I want to add a character with the previous shortcut it only works in some applications like Google Chrome or Visual Studio Code. Is it possible in can work in all Qt applications? Like Kate or Konsole? STEPS TO REPRODUCE 1. Open an application that accepts text. e.g. Sublime Text, Kate, Konsole. 2. Press Ctrl-Shift-U and input a number, after that add a space. OBSERVED RESULT It doesn't show the Unicode character, instead shows the number you input. EXPECTED RESULT Show the Unicode character from the hex number introduced. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION I know this is a Gnome feature when pressing the shortcut appears a 'u_' and then you type the hex code, can this be considered too? Or maybe a special setting to show that for certain users? Thank you. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415631] New: Crash when i try resolve Desktop Configurations
https://bugs.kde.org/show_bug.cgi?id=415631 Bug ID: 415631 Summary: Crash when i try resolve Desktop Configurations Product: plasmashell Version: 5.17.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: canaisdosanti...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.4) Qt Version: 5.13.2 Frameworks Version: 5.65.0 Operating System: Linux 5.4.5-arch1-1 x86_64 Distribution: Arch Linux -- Information about the crash: Hello, first, sorry for my bad english. I have a problem with a Desktop Configurations. When I touch Alt+D, the desktop makes black and i have to restart the plasma shell. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f122b5064c0 (LWP 16968))] Thread 14 (Thread 0x7f11de470700 (LWP 17004)): [KCrash Handler] #6 0x7f12311ce471 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f12311d0581 in () at /usr/lib/libQt5Qml.so.5 #8 0x7f12311c8ff0 in QQmlTypeLoader::setData(QQmlDataBlob*, QQmlDataBlob::SourceCodeData const&) () at /usr/lib/libQt5Qml.so.5 #9 0x7f12311c994f in QQmlTypeLoader::setData(QQmlDataBlob*, QString const&) () at /usr/lib/libQt5Qml.so.5 #10 0x7f12311c9a8f in QQmlTypeLoader::loadThread(QQmlDataBlob*) () at /usr/lib/libQt5Qml.so.5 #11 0x7f12311d77c6 in void QQmlTypeLoader::doLoad(PlainLoader const&, QQmlDataBlob*, QQmlTypeLoader::Mode) () at /usr/lib/libQt5Qml.so.5 #12 0x7f12311c9d17 in QQmlTypeLoader::load(QQmlDataBlob*, QQmlTypeLoader::Mode) () at /usr/lib/libQt5Qml.so.5 #13 0x7f12311caaa9 in QQmlTypeLoader::getType(QUrl const&, QQmlTypeLoader::Mode) () at /usr/lib/libQt5Qml.so.5 #14 0x7f12311cb4a7 in () at /usr/lib/libQt5Qml.so.5 #15 0x7f12311cb980 in () at /usr/lib/libQt5Qml.so.5 #16 0x7f12311c90eb in QQmlTypeLoader::setData(QQmlDataBlob*, QQmlDataBlob::SourceCodeData const&) () at /usr/lib/libQt5Qml.so.5 #17 0x7f12311c994f in QQmlTypeLoader::setData(QQmlDataBlob*, QString const&) () at /usr/lib/libQt5Qml.so.5 #18 0x7f12311c9a8f in QQmlTypeLoader::loadThread(QQmlDataBlob*) () at /usr/lib/libQt5Qml.so.5 #19 0x7f12311d77c6 in void QQmlTypeLoader::doLoad(PlainLoader const&, QQmlDataBlob*, QQmlTypeLoader::Mode) () at /usr/lib/libQt5Qml.so.5 #20 0x7f12311c9d17 in QQmlTypeLoader::load(QQmlDataBlob*, QQmlTypeLoader::Mode) () at /usr/lib/libQt5Qml.so.5 #21 0x7f12311caaa9 in QQmlTypeLoader::getType(QUrl const&, QQmlTypeLoader::Mode) () at /usr/lib/libQt5Qml.so.5 #22 0x7f12311cb4a7 in () at /usr/lib/libQt5Qml.so.5 #23 0x7f12311cb980 in () at /usr/lib/libQt5Qml.so.5 #24 0x7f12311c90eb in QQmlTypeLoader::setData(QQmlDataBlob*, QQmlDataBlob::SourceCodeData const&) () at /usr/lib/libQt5Qml.so.5 #25 0x7f12311c994f in QQmlTypeLoader::setData(QQmlDataBlob*, QString const&) () at /usr/lib/libQt5Qml.so.5 #26 0x7f12311c9a8f in QQmlTypeLoader::loadThread(QQmlDataBlob*) () at /usr/lib/libQt5Qml.so.5 #27 0x7f12311c9cae in () at /usr/lib/libQt5Qml.so.5 #28 0x7f123123d78a in () at /usr/lib/libQt5Qml.so.5 #29 0x7f123123de82 in () at /usr/lib/libQt5Qml.so.5 #30 0x7f123062d4e5 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #31 0x7f1230636e11 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #32 0x7f122faead12 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #33 0x7f122faeda89 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #34 0x7f122fb43514 in () at /usr/lib/libQt5Core.so.5 #35 0x7f122debf39e in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #36 0x7f122dec11b1 in () at /usr/lib/libglib-2.0.so.0 #37 0x7f122dec11f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #38 0x7f122fb42b13 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #39 0x7f122fae983c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #40 0x7f122f91b305 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #41 0x7f123123d449 in () at /usr/lib/libQt5Qml.so.5 #42 0x7f122f91c530 in () at /usr/lib/libQt5Core.so.5 #43 0x7f122ee0a4cf in start_thread () at /usr/lib/libpthread.so.0 #44 0x7f122f5a62d3 in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7f11dedee700 (LWP 17001)): #0 0x7f122ee10c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f122f922610 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f122f922702 in QWaitCond
[ktorrent] [Bug 395525] Share ratio is in scientific format
https://bugs.kde.org/show_bug.cgi?id=395525 Santiago Munoz changed: What|Removed |Added CC||smr.ram...@gmail.com --- Comment #1 from Santiago Munoz --- I submitted a Phabricator patch for this: https://phabricator.kde.org/D14070 Cheers! -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 396023] New: Yakuake crashes on random text selection
https://bugs.kde.org/show_bug.cgi?id=396023 Bug ID: 396023 Summary: Yakuake crashes on random text selection Product: yakuake Version: 3.0.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: h...@kde.org Reporter: leandrosansi...@gmail.com Target Milestone: --- Application: yakuake (3.0.5) Qt Version: 5.11.1 Frameworks Version: 5.47.0 Operating System: Linux 4.14.51-1-lts x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I have the habit to quicly select and unselecy text while reading them on my laptop using the touchpad, and while I was doing it, yakuake crashed. I believe I selected some text and unintentionally dragged it, and then yakuake crashed. - Custom settings of the application: I am using kwin_wayland. -- Backtrace: Application: Yakuake (yakuake), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3973f6f800 (LWP 906))] Thread 3 (Thread 0x7f3953650700 (LWP 960)): #0 0x7f396a4c2ffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f395442c124 in () at /usr/lib/dri/i965_dri.so #2 0x7f395442be18 in () at /usr/lib/dri/i965_dri.so #3 0x7f396a4bd075 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f396e4be53f in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f395e926700 (LWP 935)): #0 0x7f396e4b3ea9 in poll () at /usr/lib/libc.so.6 #1 0x7f39686a2523 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f39686a263e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f396edd0054 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f396ed7b94c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f396ebc4a99 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f39709e5976 in () at /usr/lib/libQt5DBus.so.5 #7 0x7f396ebceb45 in () at /usr/lib/libQt5Core.so.5 #8 0x7f396a4bd075 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f396e4be53f in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f3973f6f800 (LWP 906)): [KCrash Handler] #6 0x7f396eda1e20 in QMimeData::text() const () at /usr/lib/libQt5Core.so.5 #7 0x7f39527ad6ea in Konsole::TerminalDisplay::doDrag() () at /usr/lib/libkonsoleprivate.so.18 #8 0x7f39527ae25b in Konsole::TerminalDisplay::mouseMoveEvent(QMouseEvent*) () at /usr/lib/libkonsoleprivate.so.18 #9 0x7f396fb302b8 in QWidget::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #10 0x7f39527b5034 in Konsole::TerminalDisplay::event(QEvent*) () at /usr/lib/libkonsoleprivate.so.18 #11 0x7f396faf0a74 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #12 0x7f396faf858a in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #13 0x7f396ed7ccb9 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #14 0x7f396faf7871 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () at /usr/lib/libQt5Widgets.so.5 #15 0x7f396fb4b5ec in () at /usr/lib/libQt5Widgets.so.5 #16 0x7f396fb4e235 in () at /usr/lib/libQt5Widgets.so.5 #17 0x7f396faf0a74 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #18 0x7f396faf8341 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #19 0x7f396ed7ccb9 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #20 0x7f396f322e34 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /usr/lib/libQt5Gui.so.5 #21 0x7f396f324df6 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /usr/lib/libQt5Gui.so.5 #22 0x7f396f2feb7c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /usr/lib/libQt5Gui.so.5 #23 0x7f39620bd57d in () at /usr/lib/libQt5WaylandClient.so.5 #24 0x7f396ed7b94c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #25 0x7f396ed83c46 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #26 0x55616091ac92 in () #27 0x7f396e3e906b in __libc_start_main () at /usr/lib/libc.so.6 #28 0x55616091ad2a in _start () The reporter indicates this bug may be a duplicate of or related to bug 395666. Possible duplicates by query: bug 395666. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 395666] yakuake crashes on multiple touches on the touchscreen
https://bugs.kde.org/show_bug.cgi?id=395666 --- Comment #1 from Leandro Santiago da Silva --- I mean, "whose screen supports up to 10 simultaneous touches" :-) -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 395666] New: yakuake crashes on multiple touches on the touchscreen
https://bugs.kde.org/show_bug.cgi?id=395666 Bug ID: 395666 Summary: yakuake crashes on multiple touches on the touchscreen Product: yakuake Version: 3.0.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: h...@kde.org Reporter: leandrosansi...@gmail.com Target Milestone: --- Application: yakuake (3.0.5) Qt Version: 5.11.0 Frameworks Version: 5.47.0 Operating System: Linux 4.14.49-1-lts x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I have a dell laptop which supports up to 10 touches. I am using kwin_wayland and and tried touching with several (maybe 8) fingers when yakuake is in full screen. - Unusual behavior I noticed: yakuake crashed - Custom settings of the application: kwin_wayland, yakuake in fullscreen The crash can be reproduced every time. -- Backtrace: Application: Yakuake (yakuake), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f02bdb2d800 (LWP 14727))] Thread 3 (Thread 0x7f029d22f700 (LWP 14730)): #0 0x7f02b4085ffc in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f029e00b0a4 in ?? () from /usr/lib/dri/i965_dri.so #2 0x7f029e00ad98 in ?? () from /usr/lib/dri/i965_dri.so #3 0x7f02b4080075 in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f02b808153f in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7f02a84ec700 (LWP 14728)): #0 0x7f02b8072934 in read () from /usr/lib/libc.so.6 #1 0x7f02b22aaed1 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f02b2264ff8 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #3 0x7f02b22654c6 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x7f02b226563e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0x7f02b8992e64 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7f02b893e85c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #7 0x7f02b8787ac9 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #8 0x7f02ba5a3976 in ?? () from /usr/lib/libQt5DBus.so.5 #9 0x7f02b8791b95 in ?? () from /usr/lib/libQt5Core.so.5 #10 0x7f02b4080075 in start_thread () from /usr/lib/libpthread.so.0 #11 0x7f02b808153f in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7f02bdb2d800 (LWP 14727)): [KCrash Handler] #6 0x7f02b8964d30 in QMimeData::text() const () from /usr/lib/libQt5Core.so.5 #7 0x7f029c38c6ea in Konsole::TerminalDisplay::doDrag() () from /usr/lib/libkonsoleprivate.so.18 #8 0x7f029c38d25b in Konsole::TerminalDisplay::mouseMoveEvent(QMouseEvent*) () from /usr/lib/libkonsoleprivate.so.18 #9 0x7f02b96ef058 in QWidget::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #10 0x7f029c394034 in Konsole::TerminalDisplay::event(QEvent*) () from /usr/lib/libkonsoleprivate.so.18 #11 0x7f02b96af984 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #12 0x7f02b96b746a in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #13 0x7f02b893fbc9 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #14 0x7f02b96b6781 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () from /usr/lib/libQt5Widgets.so.5 #15 0x7f02b970a38c in ?? () from /usr/lib/libQt5Widgets.so.5 #16 0x7f02b970cfd5 in ?? () from /usr/lib/libQt5Widgets.so.5 #17 0x7f02b96af984 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #18 0x7f02b96b725b in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #19 0x7f02b893fbc9 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #20 0x7f02b8ee7596 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /usr/lib/libQt5Gui.so.5 #21 0x7f02b8ee67f8 in QGuiApplicationPrivate::processTouchEvent(QWindowSystemInterfacePrivate::TouchEvent*) () from /usr/lib/libQt5Gui.so.5 #22 0x7f02b8ee94e6 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib/libQt5Gui.so.5 #23 0x7f02b8ec0a5c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /usr/lib/libQt5Gui.so.5 #24 0x7f02abc80f7d in ?? () from /usr/lib/libQt5WaylandClient.so.5 #25 0x7f02b893e85c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #26 0x7f02b8946b56 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #27 0x5654f1d02c92 in ?? () #28 0x7f02b7fac06b in __libc_start_main () from /usr/lib/
[wacomtablet] [Bug 395617] New: Plasmoids scrollbars not work with Wacom Pen
https://bugs.kde.org/show_bug.cgi?id=395617 Bug ID: 395617 Summary: Plasmoids scrollbars not work with Wacom Pen Product: wacomtablet Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: jazzv...@gmail.com Reporter: santiagosh...@gmail.com Target Milestone: --- When I try to use the stylus pen over a scrollbar in the plasmoids (for example on Stick note or KDE app menu) is imposible to drag the scrollbar. It can be reproduced in Plasma 5.12.5, and Plasma 5.13. The problem affects some scrollbars besides the plasmoids (in the desktop effects stack for example). All softwars as Krita, dolphin, kmail, etc, work fine. Here I recorded my Screen https://youtu.be/yWslqgDhZ0o My Wacom is a CTH480 Intuos Pen and Touch. I tried with KDE Neon 5.13 and Opensuse Leap 15 same results. In Opensuse 43.2 with plasma 5.8 LTS all works perfectly. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394927] New: KWin crashes when, during 'expose' mode, I try to filter the windows by using a composite key combination
https://bugs.kde.org/show_bug.cgi?id=394927 Bug ID: 394927 Summary: KWin crashes when, during 'expose' mode, I try to filter the windows by using a composite key combination Product: kwin Version: 5.12.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: leandrosansi...@gmail.com Target Milestone: --- Application: kwin_x11 (5.12.5) Qt Version: 5.11.0 Frameworks Version: 5.46.0 Operating System: Linux 4.14.41-1-lts x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: enabled 'expose', typed the keys ` and then a, in a pt_BR (abnt2) keyboard, expecting to filter windows with the letter 'à' in the name. - Unusual behavior I noticed: KWin crashed and restarted. The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0606c53840 (LWP 806))] Thread 7 (Thread 0x7f05d3dd1700 (LWP 4304)): #0 0x7f06065ecfa6 in ppoll () at /usr/lib/libc.so.6 #1 0x7f06039f7d1b in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f06039f920b in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f06039a785c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f06037f0ac9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f05fe0a6559 in () at /usr/lib/libQt5Qml.so.5 #6 0x7f06037fab95 in () at /usr/lib/libQt5Core.so.5 #7 0x7f05ff65b075 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f06065f753f in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f05e4f70700 (LWP 1488)): #0 0x7f06039f908e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #1 0x7f06039a785c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #2 0x7f06037f0ac9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #3 0x7f05fe0a6559 in () at /usr/lib/libQt5Qml.so.5 #4 0x7f06037fab95 in () at /usr/lib/libQt5Core.so.5 #5 0x7f05ff65b075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f06065f753f in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f05d35d0700 (LWP 916)): #0 0x7f05ff660ffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f0602920bbc in () at /usr/lib/libQt5Script.so.5 #2 0x7f0602920bd9 in () at /usr/lib/libQt5Script.so.5 #3 0x7f05ff65b075 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f06065f753f in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f05d700 (LWP 895)): #0 0x7f06065ecfa6 in ppoll () at /usr/lib/libc.so.6 #1 0x7f06039f7d1b in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f06039f920b in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f06039a785c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f06037f0ac9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f05fe0a6559 in () at /usr/lib/libQt5Qml.so.5 #6 0x7f06037fab95 in () at /usr/lib/libQt5Core.so.5 #7 0x7f05ff65b075 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f06065f753f in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f05e67e7700 (LWP 868)): #0 0x7f06037ed74c in QMutex::lock() () at /usr/lib/libQt5Core.so.5 #1 0x7f06039f908e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #2 0x7f06039a785c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f06037f0ac9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #4 0x7f05fcf9d976 in () at /usr/lib/libQt5DBus.so.5 #5 0x7f06037fab95 in () at /usr/lib/libQt5Core.so.5 #6 0x7f05ff65b075 in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f06065f753f in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f05ecd67700 (LWP 846)): #0 0x7f06065ecea9 in poll () at /usr/lib/libc.so.6 #1 0x7f0605516180 in () at /usr/lib/libxcb.so.1 #2 0x7f0605517e4b in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7f05ede55f1a in () at /usr/lib/libQt5XcbQpa.so.5 #4 0x7f06037fab95 in () at /usr/lib/libQt5Core.so.5 #5 0x7f05ff65b075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f06065f753f in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f0606c53840 (LWP 806)): [KCrash Handler] #6 0x7f06039a8ac4 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #7 0x7f05e6c8171d in () at /usr/lib/qt/plugins/platforminputcontexts/libcomposeplatforminputcontextpl
[yakuake] [Bug 380497] Yakuake KeepOpen=false doesn't work with Wayland
https://bugs.kde.org/show_bug.cgi?id=380497 Santiago Tabares changed: What|Removed |Added CC||santiago.taba...@gmail.com --- Comment #1 from Santiago Tabares --- Confirm. My guess is that in x11 it checks if it loses focus to hide, but in wayland that's not supported. It would need cooperation with kwin to fix. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 382466] New: Theme Crash
https://bugs.kde.org/show_bug.cgi?id=382466 Bug ID: 382466 Summary: Theme Crash Product: systemsettings Version: 5.9.4 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ryud...@gmail.com Target Milestone: --- Application: systemsettings5 (5.9.4) (Compiled from sources) Qt Version: 5.7.1 Frameworks Version: 5.31.0 Operating System: Linux 4.10.0-28-generic x86_64 Distribution: Ubuntu 17.04 -- Information about the crash: - What I was doing when the application crashed: Changing theme from deafult to Arc. I downloaded Arc from the theme shop, but when i try to apply the them, the window crashes. I am using Kubuntu 17.04. - Custom settings of the application: The Arc theme The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fdeceb188c0 (LWP 2791))] Thread 4 (Thread 0x7fdea5866700 (LWP 2795)): #0 0x7fdeca8a2d8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fdec4a60576 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fdec4a6068c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fdecb1c5f2b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fdecb16f88a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fdecaf9cfe3 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fdec92e7df5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fdecafa1c98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fdec6b916da in start_thread (arg=0x7fdea5866700) at pthread_create.c:456 #9 0x7fdeca8aed7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 3 (Thread 0x7fdeb2ded700 (LWP 2793)): #0 0x7fdec4a5d5af in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fdec4a5fec4 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fdec4a60514 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fdec4a6068c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fdecb1c5f2b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fdecb16f88a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fdecaf9cfe3 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fdecbac95c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7fdecafa1c98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fdec6b916da in start_thread (arg=0x7fdeb2ded700) at pthread_create.c:456 #10 0x7fdeca8aed7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 2 (Thread 0x7fdebb688700 (LWP 2792)): #0 0x7fdeca8a2d8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fdec7408c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fdec740a8d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fdebdbdfed9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7fdecafa1c98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fdec6b916da in start_thread (arg=0x7fdebb688700) at pthread_create.c:456 #6 0x7fdeca8aed7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 1 (Thread 0x7fdeceb188c0 (LWP 2791)): [KCrash Handler] #6 0x7fdece587a39 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5KCMUtils.so.5 #7 0x7fdecb19d81e in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fdecc532805 in QGuiApplication::paletteChanged(QPalette const&) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #9 0x7fdeba6324a5 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platformthemes/KDEPlasmaPlatformTheme.so #10 0x7fdeba63f315 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platformthemes/KDEPlasmaPlatformTheme.so #11 0x7fdecbad3650 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #12 0x7fdecb19e359 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fdecccd035c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7fdecccd7b11 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7fdecb1718a0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7fdecb17402d in QCor
[kdevelop] [Bug 364816] New: KDevelop crashes on saving file on vim mode
https://bugs.kde.org/show_bug.cgi?id=364816 Bug ID: 364816 Summary: KDevelop crashes on saving file on vim mode Product: kdevelop Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: leandrosansi...@gmail.com Application: kdevelop (4.90.92) Qt Version: 5.5.1 Frameworks Version: 5.22.0 Operating System: Linux 4.6.0-040600-generic x86_64 Distribution: Ubuntu 16.04 LTS -- Information about the crash: - What I was doing when the application crashed: I just typed ESC, :x, and KDevelop suddenly crashed. >From lastest ktexeditor, kdevplatform and kdevelop master branch. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5f947ab900 (LWP 3154))] Thread 13 (Thread 0x7f5f41fa7700 (LWP 4848)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f5fa5e51bd4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f5fa5e51c19 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f5faa2636fa in start_thread (arg=0x7f5f41fa7700) at pthread_create.c:333 #4 0x7f5fb0e70b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 12 (Thread 0x7f5f5dffb700 (LWP 4830)): #0 __syscall_clock_gettime () at ../sysdeps/unix/syscall-template.S:66 #1 0x7f5fb0e7efb6 in __GI___clock_gettime (clock_id=1, tp=0x7f5f5dffaa10) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7f5fb160ac16 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f5fb178f529 in QTimerInfoList::updateCurrentTime() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f5fb178fa95 in QTimerInfoList::timerWait(timespec&) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f5fb1790e7e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f5fa93cd92d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f5fa93ce2cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f5fa93ce4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f5fb1791a9b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f5fb1738dea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f5fb15558a4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f5fae63d3c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #13 0x7f5fb155a84e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f5faa2636fa in start_thread (arg=0x7f5f5dffb700) at pthread_create.c:333 #15 0x7f5fb0e70b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 11 (Thread 0x7f5f5effd700 (LWP 3297)): #0 0x7f5fb0e64e8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f5fa93ce39c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5fa93ce4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5fb1791a9b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f5fb1738dea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f5fb15558a4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f5fb155a84e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f5faa2636fa in start_thread (arg=0x7f5f5effd700) at pthread_create.c:333 #8 0x7f5fb0e70b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 10 (Thread 0x7f5f5e7fc700 (LWP 3251)): #0 __syscall_clock_gettime () at ../sysdeps/unix/syscall-template.S:66 #1 0x7f5fb0e7efb6 in __GI___clock_gettime (clock_id=1, tp=0x7f5f5e7fba30) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7f5fb160ac16 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f5fb178f529 in QTimerInfoList::updateCurrentTime() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f5fb178fa95 in QTimerInfoList::timerWait(timespec&) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f5fb1790e7e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f5fa93cd92d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f5fa93ce2cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f5fa93ce4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f5fb1791a9b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f5fb1738dea in QEventLoop::exec(QFlags) () from /usr/li
[plasma4] [Bug 363643] New: graphic element error adding to the taskbar
https://bugs.kde.org/show_bug.cgi?id=363643 Bug ID: 363643 Summary: graphic element error adding to the taskbar Product: plasma4 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: yopride...@gmail.com Application: plasma-desktop (4.11.20) KDE Platform Version: 4.14.9 Qt Version: 4.8.6 Operating System: Linux 3.16.7-35-desktop x86_64 Distribution: "openSUSE 13.2 (Harlequin) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Quise agregar un elemento grafico a la barra de tareas y me salto el error. -- Backtrace: Application: Shell de escritorio Plasma (plasma-desktop), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f02c3051780 (LWP 1532))] Thread 4 (Thread 0x7f0298a49700 (LWP 1542)): #0 0x7f02c190e03f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f02b3f868cb in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0x7f02b4284f00 ) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359 #2 0x7f02b3f86909 in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464 #3 0x7f02c190a0a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f02c067600d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f021284c700 (LWP 1543)): #0 0x7f02c1910a7d in read () from /lib64/libpthread.so.0 #1 0x7f02bd7c1750 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f02bd780714 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f02bd780b7b in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f02bd780cec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f02c1ccf0de in QEventDispatcherGlib::processEvents (this=0x7f020c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #6 0x7f02c1ca0e6f in QEventLoop::processEvents (this=this@entry=0x7f021284be20, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f02c1ca1165 in QEventLoop::exec (this=this@entry=0x7f021284be20, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f02c1b9e0bf in QThread::exec (this=this@entry=0x9bd4e0) at thread/qthread.cpp:538 #9 0x7f02c1c82783 in QInotifyFileSystemWatcherEngine::run (this=0x9bd4e0) at io/qfilesystemwatcher_inotify.cpp:265 #10 0x7f02c1ba079f in QThreadPrivate::start (arg=0x9bd4e0) at thread/qthread_unix.cpp:349 #11 0x7f02c190a0a4 in start_thread () from /lib64/libpthread.so.0 #12 0x7f02c067600d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f021167f700 (LWP 1544)): #0 0x7f02c1910a7d in read () from /lib64/libpthread.so.0 #1 0x7f02bd7c1750 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f02bd780714 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f02bd780b7b in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f02bd780cec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f02c1ccf0de in QEventDispatcherGlib::processEvents (this=0x7f02040008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #6 0x7f02c1ca0e6f in QEventLoop::processEvents (this=this@entry=0x7f021167ee20, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f02c1ca1165 in QEventLoop::exec (this=this@entry=0x7f021167ee20, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f02c1b9e0bf in QThread::exec (this=this@entry=0x1607450) at thread/qthread.cpp:538 #9 0x7f02c1c82783 in QInotifyFileSystemWatcherEngine::run (this=0x1607450) at io/qfilesystemwatcher_inotify.cpp:265 #10 0x7f02c1ba079f in QThreadPrivate::start (arg=0x1607450) at thread/qthread_unix.cpp:349 #11 0x7f02c190a0a4 in start_thread () from /lib64/libpthread.so.0 #12 0x7f02c067600d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f02c3051780 (LWP 1532)): [KCrash Handler] #6 0x00d1 in ?? () #7 0x7f021742da80 in DeclarativeMimeData::DeclarativeMimeData (this=0x7ffc87e82c30, copy=0x347c750) at /usr/src/debug/kde-runtime-15.08.3/plasma/declarativeimports/draganddrop/DeclarativeMimeData.cpp:50 #8 0x7f021742d411 in DeclarativeDragDropEvent::DeclarativeDragDropEvent (this=0x7ffc87e82c10, e=0x7ffc87e83040, parent=0x1042bc0) at /usr/src/debug/kde-runtime-15.08.3/plasma/declarativeimports/draganddrop/DeclarativeDragDropEvent.cpp:33 #9 0x7f021742d504 in DeclarativeDropArea::dragLeaveEvent (this=0x1042bc0, event=) at /usr/src/debug/kde-runtime-15.08.3/plasma/declarativeimports/draganddrop/DeclarativeDropArea.cpp:44 #10 0x7f02c13c2dc2 in QGraphicsItem::sceneEvent (this=this@entry=0x1042bd0, event=event@entry=0x7ffc87e83040) at graphicsview/qgraphicsitem.cpp:6734 #11 0x7f02b3766364 in QDeclarativeItem::sceneEvent (this=0x
[plasmashell] [Bug 361250] New: Plasma randomly freezes and eventually crashes and restarts
https://bugs.kde.org/show_bug.cgi?id=361250 Bug ID: 361250 Summary: Plasma randomly freezes and eventually crashes and restarts Product: plasmashell Version: 5.5.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: sdeleo...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.1.15-8-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - Unusual behavior I noticed: This happens to me every day without any particular triggers that I can identify. The taskbar freezes. I can't click or get mouseover feedback from: the Pager widget; any of the task widgets at the bottom right of my task manager; the Application Menu (launcher). Sometimes, actions on the folder views in my desktop are also disabled. When the plasma environment is frozen I can still use yakuake or krunner to fire up programs. I can also switch between windows and Virtual Desktops with my usual hotkeys. The programs I have up most of the time are PyCharm, VirtualBox/Vagrant, Firefox, Chrome, Thunderbird, Slack, the hangouts taskbar widget and Amarok. This all started when I installed a fresh copy of Leap (I kept my home folder but overwrote previous OS, which was OpenSUSE 13.2). This random bug is really wrecking my experience with Leap. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc805ef37c0 (LWP 2018))] Thread 6 (Thread 0x7fc7ecd05700 (LWP 2049)): #0 0x7fc7ff402bbd in poll () at /lib64/libc.so.6 #1 0x7fc7fbae3e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fc7fbae3f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fc7ffd2dd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fc7ffcd4d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fc7ffaf661a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fc802e08df8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7fc7ffafb32f in () at /usr/lib64/libQt5Core.so.5 #8 0x7fc7fec0c0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fc7ff40afed in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7fc7db8f7700 (LWP 2051)): #0 0x7fc7ff402bbd in poll () at /lib64/libc.so.6 #1 0x7fc7fbae3e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fc7fbae3f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fc7ffd2dd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fc7ffcd4d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fc7ffaf661a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fc802e08df8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7fc7ffafb32f in () at /usr/lib64/libQt5Core.so.5 #8 0x7fc7fec0c0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fc7ff40afed in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fc7da092700 (LWP 2053)): #0 0x7fc7fbae1254 in () at /usr/lib64/libglib-2.0.so.0 #1 0x7fc7fbae344b in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7fc7fbae3d80 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fc7fbae3f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7fc7ffd2dd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fc7ffcd4d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fc7ffaf661a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7fc802e08df8 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7fc7ffafb32f in () at /usr/lib64/libQt5Core.so.5 #9 0x7fc7fec0c0a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7fc7ff40afed in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fc7d3fff700 (LWP 2064)): #0 0x7fc7fec1003f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc8055d086b in () at /usr/lib64/libQt5Script.so.5 #2 0x7fc8055d0899 in () at /usr/lib64/libQt5Script.so.5 #3 0x7fc7fec0c0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fc7ff40afed in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fc7d0ebd700 (LWP 2110)): #0 0x7fc7fec10e8b in pthread_getspecific () at /lib64/libpthread.so.0 #1 0x7fc7fbb09400 in g_thread_self () at /usr/lib64/libglib-2.0.so.0 #2 0x7fc7fbae2ecc in g_main_context_acquire () at /usr/lib64/libglib-2.0.so.0 #3 0x7fc7fbae3d25 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fc7fbae3f7c in g_main_context_iteration () at /usr/lib64/libgl
