[systemsettings] [Bug 484682] Since 6.0.3, global shortcuts do not persist settings across sessions and behave erratically
https://bugs.kde.org/show_bug.cgi?id=484682 Evgeny changed: What|Removed |Added CC||kurnev...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 478549] Nerd fonts are not rendered on plasma 6 when using detached font
https://bugs.kde.org/show_bug.cgi?id=478549 Evgeny changed: What|Removed |Added CC||kurnev...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479986] Plasma crashed when clicking on the system tray
https://bugs.kde.org/show_bug.cgi?id=479986 --- Comment #11 from Evgeny --- Created attachment 167014 --> https://bugs.kde.org/attachment.cgi?id=167014=edit Backtrace of the crash Here is my backtrace, not sure if useful. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479986] Plasma crashed when clicking on the system tray
https://bugs.kde.org/show_bug.cgi?id=479986 Evgeny changed: What|Removed |Added CC||kurnev...@gmail.com --- Comment #9 from Evgeny --- For me it happens quite regularly when I click on weather widget (and only on it) after some time not touching it, like a day of working. In this case either it crashes or hangs consuming 100% of one core of cpu. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481607] In Plasma 6 absent module to integration with external calendar events
https://bugs.kde.org/show_bug.cgi?id=481607 Evgeny changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |NOT A BUG --- Comment #2 from Evgeny --- Thank you! After installing kdepim-addons package, everything is working again. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481335] Edge trigger (hot corner) for Overview effect cycles between Overview and "Grid View", with no way to change this
https://bugs.kde.org/show_bug.cgi?id=481335 --- Comment #12 from Evgeny --- I think I found it: https://invent.kde.org/plasma/kwin/-/merge_requests/5298 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481335] Edge trigger (hot corner) for Overview effect cycles between Overview and "Grid View", with no way to change this
https://bugs.kde.org/show_bug.cgi?id=481335 --- Comment #11 from Evgeny --- Do you mind specifying the commit/MR? I'd probably like to backport it to 6.0 for myself :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481335] Edge trigger (hot corner) for Overview effect cycles between Overview and "Grid View", with no way to change this
https://bugs.kde.org/show_bug.cgi?id=481335 Evgeny changed: What|Removed |Added CC||kurnev...@gmail.com --- Comment #9 from Evgeny --- > In hindsight, we should have added different screen edge actions for > overview and grid modes. This can be done in 6.1. Is there an issue for that? I'd really like to have grid mode available from hot corner - I always used it but now it's not available. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481607] In Plasma 6 absent module to integration with external calendar events
https://bugs.kde.org/show_bug.cgi?id=481607 Evgeny changed: What|Removed |Added CC||atx...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481607] New: In Plasma 6 absent module to integration with external calendar events
https://bugs.kde.org/show_bug.cgi?id=481607 Bug ID: 481607 Summary: In Plasma 6 absent module to integration with external calendar events Classification: Plasma Product: plasmashell Version: master Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: atx...@gmail.com Target Milestone: 1.0 SUMMARY *** In Plasma 6 absent module to integration with external calendar events, like a Plasma 5 *** SOFTWARE/OS VERSIONS Lnux: Fedora KDE Rawhide KDE Plasma Version: 5.93.0 (6.0rc2) KDE Frameworks Version: 5.249.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 476319] New: Okular crashes when trying to edit form fields
https://bugs.kde.org/show_bug.cgi?id=476319 Bug ID: 476319 Summary: Okular crashes when trying to edit form fields Classification: Applications Product: okular Version: 23.08.1 Platform: Debian testing OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: xeng...@mail.ru Target Milestone: --- Application: okular (23.08.1) Qt Version: 5.15.10 Frameworks Version: 5.107.0 Operating System: Linux 6.5.9-dirty x86_64 Windowing System: X11 Distribution: Debian GNU/Linux trixie/sid DrKonqi: 5.27.8 [KCrashBackend] -- Information about the crash: Open document with forms Click on any field Reproducable crash The crash can be reproduced every time. -- Backtrace: Application: Okular (okular), signal: Segmentation fault [KCrash Handler] #4 0x7fdfec36109c in GfxResources::doLookupFont(char const*) const () from /lib/x86_64-linux-gnu/libpoppler.so.126 #5 0x7fdfec3611ad in GfxResources::lookupFont(char const*) () from /lib/x86_64-linux-gnu/libpoppler.so.126 #6 0x7fdfec346f28 in Form::ensureFontsForAllCharacters(GooString const*, std::__cxx11::basic_string, std::allocator > const&, GfxResources*) () from /lib/x86_64-linux-gnu/libpoppler.so.126 #7 0x7fdfec347576 in ?? () from /lib/x86_64-linux-gnu/libpoppler.so.126 #8 0x7fdfefdd7de7 in Poppler::FormFieldText::setText(QString const&) () from /lib/x86_64-linux-gnu/libpoppler-qt5.so.1 #9 0x7fe008f73e88 in ?? () from /lib/x86_64-linux-gnu/libOkular5Core.so.11 #10 0x7fe017903b35 in QUndoStack::push(QUndoCommand*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7fdffc7151b2 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/okularpart.so #12 0x7fe0168fba32 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fdffc6839ea in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/okularpart.so #14 0x7fdffc70c752 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/okularpart.so #15 0x7fe0168fba32 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7fe0176a8415 in QLineEdit::textEdited(QString const&) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7fe0176a5a94 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7fe0168fb74d in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7fe0176afbd5 in QWidgetLineControl::textEdited(QString const&) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7fe0176b32cb in QWidgetLineControl::finishChange(int, bool, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7fe0176b604d in QWidgetLineControl::processKeyEvent(QKeyEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7fe0176a859f in QLineEdit::keyPressEvent(QKeyEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7fe0175a5b5f in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7fe017562d2e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x7fe01756ac38 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x7fe0168c30d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7fe0175c0d0a in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #28 0x7fe017562d2e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #29 0x7fe0168c30d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #30 0x7fe016d3a8b9 in QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #31 0x7fe016d12d5c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #32 0x7fe0118fb8ba in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #33 0x7fe014d111b4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #34 0x7fe014d142d7 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #35 0x7fe014d148f0 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #36 0x7fe01691c8d6 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #37 0x7fe0168c1b7b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #38 0x7fe0168ca020 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #39 0x563ec4bc1398 in ?? () #40 0x7fe0160456ca in __libc_start_call_main (main=main@entry=0x563ec4bc0c20, argc=argc@entry=1, argv=argv@entry=0x7ffc3db29298) at ../sysdeps/nptl/libc_start_call_main.h:58 #41 0x7fe016045785 in __libc_start_main_impl (main=0x563ec4bc0c20, argc=1, argv=0x7ffc3db29298, init=, fini=,
[ark] [Bug 415723] [libzip] Ark doesn't preserve symlinks in zip files
https://bugs.kde.org/show_bug.cgi?id=415723 Evgeny Brazgin changed: What|Removed |Added CC||k...@xapie.nz -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 340283] please add possibility to sort results returned by krunner by type
https://bugs.kde.org/show_bug.cgi?id=340283 evgeny changed: What|Removed |Added CC||m...@ch1p.io -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449840] On X11, sometimes WindowHeap-based effects stop accepting keyboard input
https://bugs.kde.org/show_bug.cgi?id=449840 evgeny changed: What|Removed |Added CC||m...@ch1p.io -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 472592] Desktop crashed on network manager icon click
https://bugs.kde.org/show_bug.cgi?id=472592 --- Comment #1 from evgeny --- Created attachment 160507 --> https://bugs.kde.org/attachment.cgi?id=160507=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 472592] New: Desktop crashed on network manager icon click
https://bugs.kde.org/show_bug.cgi?id=472592 Bug ID: 472592 Summary: Desktop crashed on network manager icon click Classification: I don't know Product: kde Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: m...@ch1p.io Target Milestone: --- Application: plasmashell (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-10-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [CoredumpBackend] -- Information about the crash: I was connected to Wi-Fi + OpenVPN. Then I attached ethernet cable. Few seconds later, I opened the networks panel in the statusbar, and that was the moment when it crashed. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #13 0x7f773f9ca808 in QDBusArgument::beginMap() const () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 [...] #15 0x7f773f9cf8a5 in QDBusMetaType::demarshall(QDBusArgument const&, int, void*) () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 [...] #17 0x7f773eedd6f0 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f773fb62fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f773eeb16f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 Reported using DrKonqi This report was filed against 'kde' because the product 'plasmashell' could not be located in Bugzilla. Add it to drkonqi's mappings file! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470113] Main keyboard layout switching shortcuts fire on press instead of on release
https://bugs.kde.org/show_bug.cgi?id=470113 Evgeny Kravchenko changed: What|Removed |Added CC||cravc...@yandex.ru -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 462307] File icons are drawn at wrong position if desktop scaling is active
https://bugs.kde.org/show_bug.cgi?id=462307 --- Comment #24 from Evgeny Brazgin --- I tried to look into the problem about colorful 16 and 22, mentioned above, and I think I came a little bit closer to actual reason of the current bug. The reason is that when you request icon of size 16, its requested size is converted by Qt to icon of size 32 before reaching `IconEngine` (Krusader's icon.cpp), and it loads icon of size 32 from the system theme, disregarding already applied scale ratio. And icon of size 32 is already colorful. And in the end looks like icons are double-scaled (which caused the original issue of this bug, all loaded icons are 4x size of requested icon size, even though my screen is 2x density). At first, `KrView::getIcon` calls `QIcon::pixmap(size)`, which internally multiplies size by 2 because of `Qt::AA_UseHighDpiPixmaps` flag and returns double-sized icon size, see Qt source details here: https://github.com/qt/qtbase/blob/5.15/src/gui/image/qicon.cpp#L911 Then, Krusader's `IconEngine::pixmap` (icon.cpp), which is part of `Icon` implementation (and is called within `QIcon::pixmap`), and which gets that double size as input argument, calls `QIcon::pixmap(size)` again on a found theme icon. It doubles icon size again for the same reason, and quadruple-sized icon is loaded. I found that overriding `IconEngine::scaledPixmap` (via `QIconEngine::virtualHook`) and bringing back the size to original (because we can't avoid scaling under `Qt::AA_UseHighDpiPixmaps`) helps to fix the issue, and correctly colored icons are returned. Moreover, it partially makes workaround from https://invent.kde.org/utilities/krusader/-/merge_requests/118 unnecessary (partially, because even though icon sizes are correct, icon positions are still wrong, so it is not final solution). Looks like Qt6 has some better apis for setting explicit devicePixelRatio, and it would help to make less hacky approach (https://doc.qt.io/qt-6/qicon.html#pixmap-3). Without that, need a hack to override `scaledPixmap` and bring size down. I'll try to clean up my code soon, test it a little bit and make another PR. It will incrementally improve state of things (e.g. fix colored icons usage), and partially fix root cause of current bug, but not completely fix it. (Note: all multipliers in my comment above are 2, because my screen density reports 2 in Qt. For some other configurations, numbers can be different, so don't consider that value as universally used) -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 462307] File icons are drawn at wrong position if desktop scaling is active
https://bugs.kde.org/show_bug.cgi?id=462307 --- Comment #18 from Evgeny Brazgin --- PR: https://invent.kde.org/utilities/krusader/-/merge_requests/118 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 462307] File icons are drawn at wrong position if desktop scaling is active
https://bugs.kde.org/show_bug.cgi?id=462307
Evgeny Brazgin changed:
What|Removed |Added
CC||k...@xapienz.ru
--- Comment #17 from Evgeny Brazgin ---
Thanks Benjamin for finding the cause!
I found a shorter workaround — just wrap a pixmap into QIcon.
diff --git a/app/Panel/PanelView/listmodel.cpp
b/app/Panel/PanelView/listmodel.cpp
index d6ad6c5f..7731e895 100644
--- a/app/Panel/PanelView/listmodel.cpp
+++ b/app/Panel/PanelView/listmodel.cpp
@@ -177,7 +177,7 @@ QVariant ListModel::data(const QModelIndex& index, int
role) const
if (properties()->displayIcons) {
if (_justForSizeHint)
return QPixmap(_view->fileIconSize(),
_view->fileIconSize());
-return _view->getIcon(fileitem);
+return QIcon(_view->getIcon(fileitem));
}
break;
}
It might be more efficient to change all the inner calls of it to directly
return QIcon (because this is what the things inside operate with), however
that would be a lot more complicated solution.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 358231] desktop locks up when moving lots of files
https://bugs.kde.org/show_bug.cgi?id=358231 Evgeny changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #43 from Evgeny --- I can't confirm when dragging a directory with lots of files (740 pictures) from dolphin to desktop, BUT can confirm when dragging a single big file (1.7 GB) from dolphin to desktop. Plasmashell freezes for about 10 seconds, then context menu appears. File is on HDD, system & desktop on NVME SSD. Just like in the attached video by Zhora Zmeikin https://bugs.kde.org/attachment.cgi?id=151631 dolphin/lunar,now 4:22.12.2-0ubuntu1 amd64 Operating System: Kubuntu 23.04 KDE Plasma Version: 5.27.0 (there are some 5.26.5 and 5.26.90 packages) KDE Frameworks Version: 5.103.0 (there are some 5.102 and even 5.101 packages, Kubuntu Lunar is a mess) Qt Version: 5.15.8 Kernel Version: 5.19.0-21-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor Memory: 31.3 ГиБ of RAM Graphics Processor: AMD Radeon RX 590 Series Manufacturer: ASUS -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 465719] Suggestion to change caption on "Update all" button in Discover interface
https://bugs.kde.org/show_bug.cgi?id=465719 --- Comment #1 from Evgeny --- Sorry, i mean "Установить все" on package update button caption -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 465719] New: Suggestion to change caption on "Update all" button in Discover interface
https://bugs.kde.org/show_bug.cgi?id=465719 Bug ID: 465719 Summary: Suggestion to change caption on "Update all" button in Discover interface Classification: Translations Product: i18n Version: unspecified Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ru Assignee: aspotas...@gmail.com Reporter: tavi-...@yandex.ru CC: kekc...@gmail.com Target Milestone: --- Created attachment 156232 --> https://bugs.kde.org/attachment.cgi?id=156232=edit Buttons have simular names, that can confuse users SUMMARY *** I suggest to change caption "Обновить все" to "Загрузить все", because two buttons with simular name and very different actions can confuse user *** OBSERVED RESULT Simular button captions EXPECTED RESULT Caption on button for update packages changed to "Загрузить все" SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-60-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz Memory: 15.4 ГиБ of RAM Graphics Processor: Mesa Intel® Xe Graphics -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358231] desktop locks up when moving lots of files
https://bugs.kde.org/show_bug.cgi?id=358231 Evgeny changed: What|Removed |Added CC||s404.gor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 461423] New: При запуске Системного монитора, приоисходят фризы, затем она вылетает When you start the System Monitor, the friezes come down, then it crashes
https://bugs.kde.org/show_bug.cgi?id=461423 Bug ID: 461423 Summary: При запуске Системного монитора, приоисходят фризы, затем она вылетает When you start the System Monitor, the friezes come down, then it crashes Classification: Plasma Product: plasma-systemmonitor Version: 5.25.5 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: e.mail.evg@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Application: plasma-systemmonitor (5.25.5) (Compiled from sources) Qt Version: 5.15.6 Frameworks Version: 5.98.0 Operating System: Linux 5.19.0-23-generic x86_64 Windowing System: X11 Distribution: Ubuntu 22.10 DrKonqi: 5.25.5 [KCrashBackend] -- Information about the crash: My name is Eugeny, and I want to improve the kde by ridding it of errors The crash can be reproduced every time. -- Backtrace: Application: Системный монитор (plasma-systemmonitor), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x7f815363bc46 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7f81536227fc in __GI_abort () at ./stdlib/abort.c:79 #9 0x7f814509e142 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #10 0x7f8145d68c47 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #11 0x7f814518af9a in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #12 0x7f81450b4bee in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #13 0x7f8146b07ec2 in glPrimitiveBoundingBox () from /lib/x86_64-linux-gnu/libGLX_mesa.so.0 #14 0x7f8146afaa25 in ?? () from /lib/x86_64-linux-gnu/libGLX_mesa.so.0 #15 0x7f8146ae9d5f in ?? () from /lib/x86_64-linux-gnu/libGLX_mesa.so.0 #16 0x7f8146b60d71 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/xcbglintegrations/libqxcb-glx-integration.so #17 0x7f814ee157cb in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #18 0x7f814ee15dd7 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #19 0x7f8153eccc51 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f8153690402 in start_thread (arg=) at ./nptl/pthread_create.c:442 #21 0x7f815371f590 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 13 (Thread 0x7f812a5fa6c0 (LWP 4809) "plasma-s:gdrv0"): #1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x55bc9f0882e0) at ./nptl/futex-internal.c:87 #2 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x55bc9f0882e0, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ./nptl/futex-internal.c:139 #3 0x7f815368f338 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55bc9f088290, cond=0x55bc9f0882b8) at ./nptl/pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=0x55bc9f0882b8, mutex=0x55bc9f088290) at ./nptl/pthread_cond_wait.c:627 #5 0x7f814510c29d in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #6 0x7f81450bfb9b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #7 0x7f814510c1cb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #8 0x7f8153690402 in start_thread (arg=) at ./nptl/pthread_create.c:442 #9 0x7f815371f590 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 12 (Thread 0x7f812adfb6c0 (LWP 4805) "Thread (pooled)"): #1 __futex_abstimed_wait_common (cancel=true, private=-1479802112, abstime=0x7f812adfabb0, clockid=0, expected=0, futex_word=0x55bc9f4f23d4) at ./nptl/futex-internal.c:87 #2 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x55bc9f4f23d4, expected=expected@entry=0, clockid=clockid@entry=1, abstime=abstime@entry=0x7f812adfabb0, private=private@entry=0) at ./nptl/futex-internal.c:139 #3 0x7f815368f7aa in __pthread_cond_wait_common (abstime=0x7f812adfabb0, clockid=1, mutex=0x55bc9f4f2380, cond=0x55bc9f4f23a8) at ./nptl/pthread_cond_wait.c:503 #4 ___pthread_cond_timedwait64 (cond=0x55bc9f4f23a8, mutex=0x55bc9f4f2380, abstime=0x7f812adfabb0) at ./nptl/pthread_cond_wait.c:652 #5 0x7f8153ed2ab0 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f8153ed00e5 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f8153eccc51 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f8153690402 in start_thread (arg=) at ./nptl/pthread_create.c:442 #9 0x7f815371f590 in clone3 () at
[kwin] [Bug 455450] Slide desktop animation is slower in 5.25, especially compared to other animations
https://bugs.kde.org/show_bug.cgi?id=455450 --- Comment #20 from Evgeny --- The problem here is not just that the slide animation is slow. The main problem is that its time is not aligned with other animations, so it's impossible to configure it with global animations speed setting. I believe it should be somewhere around 400 to be close to the speed of other animations. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455450] Slide desktop animation is slower in 5.25, especially compared to other animations
https://bugs.kde.org/show_bug.cgi?id=455450 --- Comment #18 from Evgeny --- (In reply to Bug Janitor Service from comment #17) > A possibly relevant merge request was started @ > https://invent.kde.org/plasma/kwin/-/merge_requests/3009 Well, for myself I increased it to 500 :) I have a feeling that increasing to 250 won't make a big difference, probably those who created issues can comment as well. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457844] Applications are launched with shortcuts have cap_sys_nice=eip capabilities
https://bugs.kde.org/show_bug.cgi?id=457844 Evgeny changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |NOT A BUG --- Comment #18 from Evgeny --- Alright, there is already a fix with explanation: https://github.com/NixOS/nixpkgs/pull/185579 Thanks for looking into this anyway. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457867] Alacritty can't be opened in maximized mode on Wayland when using "Maximized" Window Placement mode
https://bugs.kde.org/show_bug.cgi?id=457867 --- Comment #6 from Evgeny --- Just tried gedit - it seems it works fine. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457844] Applications are launched with shortcuts have cap_sys_nice=eip capabilities
https://bugs.kde.org/show_bug.cgi?id=457844 --- Comment #17 from Evgeny --- Here is original MR for gnome: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/460 It seems they had to deal with this too, though I'm not sure from where it gets inheritance. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457844] Applications are launched with shortcuts have cap_sys_nice=eip capabilities
https://bugs.kde.org/show_bug.cgi?id=457844 --- Comment #16 from Evgeny --- Found this change for gnome: https://github.com/NixOS/nixpkgs/commit/9742df15950a4c53e89fcc79feabd3a1a78827e2 so it indeed could be something with NixOS. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457867] Alacritty can't be opened in maximized mode on Wayland when using "Maximized" Window Placement mode
https://bugs.kde.org/show_bug.cgi?id=457867 --- Comment #4 from Evgeny --- Yes, that's right. Alacritty has client side decorations, so probably this has something to do with the problem. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457844] Applications are launched with shortcuts have cap_sys_nice=eip capabilities
https://bugs.kde.org/show_bug.cgi?id=457844 --- Comment #15 from Evgeny --- > I'm confused by this. You should see something like cap_sys_nice=ep. Actually `getcap` has this format: ~ ➜ getcap /run/wrappers/bin/kwin_wayland /run/wrappers/bin/kwin_wayland cap_setpcap,cap_sys_nice=ep > Can you double-check that the distro doesn't do anything extra with > capabilities? KWin is made to work with cap_sys_nice only in "ep" not "eip". According to getcap it's ep, not eip. But I'm not sure, how else distro can affect it? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457844] Applications are launched with shortcuts have cap_sys_nice=eip capabilities
https://bugs.kde.org/show_bug.cgi?id=457844 --- Comment #13 from Evgeny --- > I'm confused by this. You should see something like cap_sys_nice=ep. Also, > getpcaps takes the pid instead of the filepath of the executable. `getpcaps` can take file path, it seems in this case it's the same as `getcap`. But not sure how the output format should look like. Here is the output for kwin_wayland pid: ~ ➜ getpcaps 309072 309072: cap_setpcap,cap_sys_nice=i > Does your distro add capabilities to the inherited set auto-magically? It sets them to `ep`, see the link in my previous comment. Not sure, maybe inheritance is somehow implied by that. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457844] Applications are launched with shortcuts have cap_sys_nice=eip capabilities
https://bugs.kde.org/show_bug.cgi?id=457844 --- Comment #11 from Evgeny --- Here how it's assigned in NixOS: https://github.com/NixOS/nixpkgs/blob/985524984f344a382519416f42f562eae165ddfb/nixos/modules/services/x11/desktop-managers/plasma5.nix#L255-L260 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457844] Applications are launched with shortcuts have cap_sys_nice=eip capabilities
https://bugs.kde.org/show_bug.cgi?id=457844 --- Comment #10 from Evgeny --- ~ ➜ getpcaps /var/run/wrappers/bin/kwin_wayland /var/run/wrappers/bin/kwin_wayland: cap_setpcap,cap_sys_nice=i konsole doesn't have capabilities. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457867] Alacritty can't be opened in maximized mode
https://bugs.kde.org/show_bug.cgi?id=457867 Evgeny changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455450] Slide desktop animation is slower in 5.25, especially compared to other animations
https://bugs.kde.org/show_bug.cgi?id=455450 --- Comment #13 from Evgeny --- I created one more duplicate of this issue, sorry for that. I ended up patching kwin to make slide faster, here how it can be done in nix in case somebody is interested: https://github.com/kurnevsky/nixfiles/commit/c77a7662428cfa988a624f9db0e442669242fb93 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457867] Alacritty can't be opened in maximized mode
https://bugs.kde.org/show_bug.cgi?id=457867 --- Comment #2 from Evgeny --- Just checked - with X11 it works correctly. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457875] New: Animation time is not balanced
https://bugs.kde.org/show_bug.cgi?id=457875 Bug ID: 457875 Summary: Animation time is not balanced Product: kwin Version: 5.25.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: kurnev...@gmail.com Target Milestone: --- Not really a bug but an inconvenience. Plasma 5.25 has new desktops slide animation which takes 0.5 seconds to play. It's way too slow compared to other animations like desktop grid or present windows (which take ~100-200ms to play). In previous version it was possible to configure slide speed separately from other animations, but not anymore. So if I adjust common animation speed to be twice faster for slide it makes desktop grid/present windows almost instantaneous which looks like no animation at all. It would be nice to increase default slide speed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457844] Applications are launched with shortcuts have cap_sys_nice=eip capabilities
https://bugs.kde.org/show_bug.cgi?id=457844 Evgeny changed: What|Removed |Added Version|unspecified |5.25.4 Assignee|unassigned-b...@kde.org |kwin-bugs-n...@kde.org Product|kde |kwin Component|general |wayland-generic -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 457844] Applications are launched with shortcuts have cap_sys_nice=eip capabilities
https://bugs.kde.org/show_bug.cgi?id=457844 --- Comment #6 from Evgeny --- Just checked - reverting this commit fixes the problem. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457867] New: Alacritty can't be opened in maximized mode
https://bugs.kde.org/show_bug.cgi?id=457867 Bug ID: 457867 Summary: Alacritty can't be opened in maximized mode Product: kwin Version: 5.25.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: kurnev...@gmail.com Target Milestone: --- Alacritty can't be opened in maximized mode. STEPS TO REPRODUCE 1. Set the setting System Settings -> Window Management -> Advanced -> Window placement: Maximized 2. Launch alacritty OBSERVED RESULT It's opened in windowed mode, but `restore` button in the header shows that it's maximized. Only after toggle it 2 times the window becomes maximized. EXPECTED RESULT The window is opened in maximized mode. SOFTWARE/OS VERSIONS Linux: NixOS KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION It used to work as expected in plasma 5.24 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 457844] Applications are launched with shortcuts have cap_sys_nice=eip capabilities
https://bugs.kde.org/show_bug.cgi?id=457844 --- Comment #5 from Evgeny --- (actually it's about realtime scheduling, so it looks like this commit caused this problem) -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 457844] Applications are launched with shortcuts have cap_sys_nice=eip capabilities
https://bugs.kde.org/show_bug.cgi?id=457844 --- Comment #4 from Evgeny --- According to this commit message it shouldn't leak this capability: https://github.com/KDE/kwin/commit/a601a08ba7a65ebb4df46cf1f94f3fff2c0553cd -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 457844] Applications are launched with shortcuts have cap_sys_nice=eip capabilities
https://bugs.kde.org/show_bug.cgi?id=457844 --- Comment #3 from Evgeny --- In nixos kwin_wayland had this capability since 5.12 release: https://github.com/NixOS/nixpkgs/commit/1de98e85681e7d1028fe866fa220c05ce1ed842f So it seems something changed in kwin that caused this. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 457844] Applications are launched with shortcuts have cap_sys_nice=eip capabilities
https://bugs.kde.org/show_bug.cgi?id=457844 --- Comment #1 from Evgeny --- Issue in nixpkgs that can have additional details: https://github.com/NixOS/nixpkgs/issues/185582 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 457844] New: Applications are launched with shortcuts have cap_sys_nice=eip capabilities
https://bugs.kde.org/show_bug.cgi?id=457844 Bug ID: 457844 Summary: Applications are launched with shortcuts have cap_sys_nice=eip capabilities Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: kurnev...@gmail.com Target Milestone: --- Not sure for which component to report it so report here. Starting from plasma 5.25 launched from shortcuts applications have cap_sys_nice=eip capabilities while if you run them with krunner/launch menu they don't. This doesn't seem right. To reproduce launch konsole with shortcut and with krunner and check `capsh --current` or `getpcaps $$`. You will see: Current: cap_sys_nice=eip cap_setpcap+i Current IAB: cap_setpcap,^cap_sys_nice and Current: = Current IAB: -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448229] Xwayland stops working after switching users
https://bugs.kde.org/show_bug.cgi?id=448229 Evgeny changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #13 from Evgeny --- I just checked plasma 5.24 and it works fine here (though the issue with kwin consuming 100% of cpu core remains) so I think this can be closed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448229] Xwayland stops working after switching users
https://bugs.kde.org/show_bug.cgi?id=448229 --- Comment #12 from Evgeny --- > Can you check whether hostname is alright, e.g. hostnamectl status output and > /etc/hostname file? Yes, it's correct. > Can you also clarify what version of sddm you have on computer? 0.19.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448229] Xwayland stops working after switching users
https://bugs.kde.org/show_bug.cgi?id=448229 --- Comment #11 from Evgeny --- Created attachment 145967 --> https://bugs.kde.org/attachment.cgi?id=145967=edit strace glxgears -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448229] Xwayland stops working after switching users
https://bugs.kde.org/show_bug.cgi?id=448229 --- Comment #8 from Evgeny --- Some more info - apps are complaining about invalid MIT-MAGIC-COOKIE-1: Invalid MIT-MAGIC-COOKIE-1 keyDisplay :1 unavailable But at the same time xauth list shows: dell/unix:1 MIT-MAGIC-COOKIE-1 12333bcf3f7de137aa43e19008b66f6c ###:1 MIT-MAGIC-COOKIE-1 12333bcf3f7de137aa43e19008b66f6c And it doesn't change before/after switch. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448229] Xwayland stops working after switching users
https://bugs.kde.org/show_bug.cgi?id=448229 --- Comment #7 from Evgeny --- The strange thing is that it happens only when I use switch user functionality and start new session with it. If I start plasma manually via `dbus-run-session startplasma-wayland` and switch between different tty with switch user or via ctrl+alt+f1-2 everything works fine. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448229] Xwayland stops working after switching users
https://bugs.kde.org/show_bug.cgi?id=448229 Evgeny changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 435338] Krfb on Wayland doesn't accept remote keyboard input
https://bugs.kde.org/show_bug.cgi?id=435338 Evgeny changed: What|Removed |Added CC||kurnev...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448229] Xwayland stops working after switching users
https://bugs.kde.org/show_bug.cgi?id=448229 --- Comment #4 from Evgeny --- XAUTHORITY=/run/user/1000/xauth_TEtNwZ - it doesn't change after user switch, and another user has different XAUTHORITY value. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448229] Xwayland stops working after switching users
https://bugs.kde.org/show_bug.cgi?id=448229 --- Comment #2 from Evgeny --- Created attachment 145324 --> https://bugs.kde.org/attachment.cgi?id=145324=edit wayland session logs Here are the logs, but I don't think xwayland crashes because xwayland apps launched before user switch works fine. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448229] New: Xwayland stops working after switching users
https://bugs.kde.org/show_bug.cgi?id=448229 Bug ID: 448229 Summary: Xwayland stops working after switching users Product: kwin Version: 5.23.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: kurnev...@gmail.com Target Milestone: --- SUMMARY It's not possible to launch new xwayland apps after switching users. Launched before switch apps are working fine. STEPS TO REPRODUCE 1. Run plasma with sddm with user 1 2. Press "Switch User" and login as user 2 3. Press "Switch User" and login back as user 1 4. Try to run any xwayland app OBSERVED RESULT It doesn't run (with errors like can't open display :1). EXPECTED RESULT It should run. SOFTWARE/OS VERSIONS Linux/KDE Plasma: NixOS 21.11 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.87 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447917] Switching between two different tty with running plasma-wayland causes alacritty crash
https://bugs.kde.org/show_bug.cgi?id=447917 --- Comment #1 from Evgeny --- Forgot to mention that I run plasma with different users in different tty. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447917] New: Switching between two different tty with running plasma-wayland causes alacritty crash
https://bugs.kde.org/show_bug.cgi?id=447917 Bug ID: 447917 Summary: Switching between two different tty with running plasma-wayland causes alacritty crash Product: kwin Version: 5.23.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: kurnev...@gmail.com Target Milestone: --- SUMMARY Alacritty crashes sometimes when switching between different tty on wayland. See the bug report for additional details: https://github.com/alacritty/alacritty/issues/5684 STEPS TO REPRODUCE To reproduce you can run dbus-run-session startplasma-wayland in 2 different tty, launch alacritty there and try to switch between them. It doesn't happen consistently, but after several attempts it crashes. OBSERVED RESULT Alacritty crashes EXPECTED RESULT Alacritty doesn't crash SOFTWARE/OS VERSIONS Linux/KDE Plasma: NixOS 21.11 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.87 ADDITIONAL INFORMATION Sometimes after switching kwin starts to consume 100% cpu until you switch back, but it could be a separate issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429765] New: Bottom icons move to top every time plasmashell restarts
https://bugs.kde.org/show_bug.cgi?id=429765 Bug ID: 429765 Summary: Bottom icons move to top every time plasmashell restarts Product: plasmashell Version: 5.20.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: s404.gor...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 133703 --> https://bugs.kde.org/attachment.cgi?id=133703=edit screenshots before and after restart SUMMARY Bottom icons move to top every time plasmashell restarts STEPS TO REPRODUCE 0. make sure the panel is on bottom of the screen (i didn't test with top panel) 1. create some folders near the panel 2. log out and log in OBSERVED RESULT Folders moved to top EXPECTED RESULT Folders stay in the same place where they were created SOFTWARE/OS VERSIONS Operating System: Kubuntu 21.04 KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.1 Kernel Version: 5.10.0-051000rc5-generic OS Type: 64-bit ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 390079] System tray layout indicator does not show chosen layout under Wayland
https://bugs.kde.org/show_bug.cgi?id=390079 Evgeny changed: What|Removed |Added CC||s404.gor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 427814] Problem with localization of KFormat
https://bugs.kde.org/show_bug.cgi?id=427814 Evgeny changed: What|Removed |Added Version|unspecified |5.75.0 CC||s404.gor...@gmail.com --- Comment #1 from Evgeny --- Yes, can confirm. In kinfocenter (and systemsettings) copied text contains Russian "ГиБ" instead of "GiB" when clicked on "Copy to clipboard in English" with LANGUAGE=ru_RU For example: Operating System: Manjaro Linux KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 Kernel Version: 5.9.6-2-MANJARO OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz Memory: 15.6 ГиБ of RAM Graphics Processor: Radeon RX 590 Series -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 417729] Can't paste correctly if history is limited to 1 entry
https://bugs.kde.org/show_bug.cgi?id=417729 Evgeny changed: What|Removed |Added Version|5.18.0 |5.20.3 -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 417729] Can't paste correctly if history is limited to 1 entry
https://bugs.kde.org/show_bug.cgi?id=417729 Evgeny changed: What|Removed |Added CC||s404.gor...@gmail.com --- Comment #1 from Evgeny --- Can confirm, but only on Wayland. There are no issues on X11. Operating System: Manjaro Linux KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 Kernel Version: 5.9.6-2-MANJARO OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426329] Applications fade until they disappear completely in Application Launcher
https://bugs.kde.org/show_bug.cgi?id=426329 Evgeny changed: What|Removed |Added CC||s404.gor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427776] New: Plasma crashed after click in "Show Desktop" mode
https://bugs.kde.org/show_bug.cgi?id=427776 Bug ID: 427776 Summary: Plasma crashed after click in "Show Desktop" mode Product: plasmashell Version: 5.18.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: k...@xapienz.ru CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.5) Qt Version: 5.14.2 Frameworks Version: 5.73.0 Operating System: Linux 5.8.14-200.fc32.x86_64 x86_64 Windowing system: X11 Distribution: "Fedora release 32 (Thirty Two)" -- Information about the crash: - What I was doing when the application crashed: "Show Desktop" (Meta+D / Ctrl+F12) mode was opened after some random keyboard pressures (by the cat). I tried to press Esc to close it, but it didn't react. Then I clicked in the middle of desktop with the mouse, and it crashed. Cannot reproduce it by doing same things again. The crash does not seem to be reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1fef19a280 (LWP 3656))] Thread 18 (Thread 0x7f1fad046700 (LWP 146592)): #0 0x7f1ff25bf1b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f1ff3142d0a in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib64/libQt5Core.so.5 #2 0x7f1ff3142e0b in QWaitCondition::wait(QMutex*, unsigned long) () from /lib64/libQt5Core.so.5 #3 0x7f1ff3140f45 in QThreadPoolThread::run() () from /lib64/libQt5Core.so.5 #4 0x7f1ff313d690 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7f1ff25b8432 in start_thread () from /lib64/libpthread.so.0 #6 0x7f1ff2dbc913 in clone () from /lib64/libc.so.6 Thread 17 (Thread 0x7f1f9eb13700 (LWP 56961)): #0 0x7f1ff25bee92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f1ff3142dab in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib64/libQt5Core.so.5 #2 0x7f1ff4c5cbc2 in QSGRenderThread::processEventsAndWaitForMore() () from /lib64/libQt5Quick.so.5 #3 0x7f1ff4c5f109 in QSGRenderThread::run() () from /lib64/libQt5Quick.so.5 #4 0x7f1ff313d690 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7f1ff25b8432 in start_thread () from /lib64/libpthread.so.0 #6 0x7f1ff2dbc913 in clone () from /lib64/libc.so.6 Thread 16 (Thread 0x7f1f9c9be700 (LWP 41704)): #0 0x7f1ff2db1aaf in poll () from /lib64/libc.so.6 #1 0x7f1fafc6b246 in poll_func () from /lib64/libpulse.so.0 #2 0x7f1fafc5c991 in pa_mainloop_poll () from /lib64/libpulse.so.0 #3 0x7f1fafc5d013 in pa_mainloop_iterate () from /lib64/libpulse.so.0 #4 0x7f1fafc5d0c0 in pa_mainloop_run () from /lib64/libpulse.so.0 #5 0x7f1fafc6b31d in thread () from /lib64/libpulse.so.0 #6 0x7f1fafc015cc in internal_thread_func () from /usr/lib64/pulseaudio/libpulsecommon-13.99.so #7 0x7f1ff25b8432 in start_thread () from /lib64/libpthread.so.0 #8 0x7f1ff2dbc913 in clone () from /lib64/libc.so.6 Thread 15 (Thread 0x7f1f9fd55700 (LWP 6582)): #0 0x7f1ff25bee92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f1ff3142dab in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib64/libQt5Core.so.5 #2 0x7f1ff4c5cbc2 in QSGRenderThread::processEventsAndWaitForMore() () from /lib64/libQt5Quick.so.5 #3 0x7f1ff4c5f109 in QSGRenderThread::run() () from /lib64/libQt5Quick.so.5 #4 0x7f1ff313d690 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7f1ff25b8432 in start_thread () from /lib64/libpthread.so.0 #6 0x7f1ff2dbc913 in clone () from /lib64/libc.so.6 Thread 14 (Thread 0x7f1f8f3ff700 (LWP 5736)): #0 0x7f1ff25bee92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f1ff3142dab in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib64/libQt5Core.so.5 #2 0x7f1ff4c5cbc2 in QSGRenderThread::processEventsAndWaitForMore() () from /lib64/libQt5Quick.so.5 #3 0x7f1ff4c5f109 in QSGRenderThread::run() () from /lib64/libQt5Quick.so.5 #4 0x7f1ff313d690 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7f1ff25b8432 in start_thread () from /lib64/libpthread.so.0 #6 0x7f1ff2dbc913 in clone () from /lib64/libc.so.6 Thread 13 (Thread 0x7f1f8dc0b700 (LWP 5384)): #0 0x7f1ff25bee92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f1ff3142dab in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib64/libQt5Core.so.5 #2 0x7f1ff4c5cbc2 in QSGRenderThread::processEventsAndWaitForMore() () from /lib64/libQt5Quick.so.5 #3 0x7f1ff4c5f109 in QSGRenderThread::run() () from
[kdenlive] [Bug 419952] New: Crash while adding video/picture with 0 tracks on timeline
https://bugs.kde.org/show_bug.cgi?id=419952 Bug ID: 419952 Summary: Crash while adding video/picture with 0 tracks on timeline Product: kdenlive Version: 19.12.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: s404.gor...@gmail.com Target Milestone: --- Application: kdenlive (19.12.3) Qt Version: 5.12.5 Frameworks Version: 5.68.0 Operating System: Linux 5.4.0-21-generic x86_64 Windowing system: X11 Distribution: Ubuntu Focal Fossa (development branch) -- Information about the crash: - What I was doing when the application crashed: go to configure kdenlive -> project defaults set video & audio tracks to 0 create new project add video or picture to project media The crash can be reproduced every time. -- Backtrace: Application: Kdenlive (kdenlive), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7890708900 (LWP 4104))] Thread 43 (Thread 0x7f77be7fc700 (LWP 4172)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x7f77ec069244) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f77ec0692a8, cond=0x7f77ec069218) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x7f77ec069218, mutex=0x7f77ec0692a8) at pthread_cond_wait.c:638 #3 0x7f7873064ca6 in () at /lib/x86_64-linux-gnu/libavcodec.so.58 #4 0x7f789743d609 in start_thread (arg=) at pthread_create.c:477 #5 0x7f7897bd5103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 42 (Thread 0x7f77beffd700 (LWP 4171)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x7f77ec069094) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f77ec0690f8, cond=0x7f77ec069068) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x7f77ec069068, mutex=0x7f77ec0690f8) at pthread_cond_wait.c:638 #3 0x7f7873064ca6 in () at /lib/x86_64-linux-gnu/libavcodec.so.58 #4 0x7f789743d609 in start_thread (arg=) at pthread_create.c:477 #5 0x7f7897bd5103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 41 (Thread 0x7f77bf7fe700 (LWP 4170)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x7f77ec068ee4) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f77ec068f48, cond=0x7f77ec068eb8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x7f77ec068eb8, mutex=0x7f77ec068f48) at pthread_cond_wait.c:638 #3 0x7f7873064ca6 in () at /lib/x86_64-linux-gnu/libavcodec.so.58 #4 0x7f789743d609 in start_thread (arg=) at pthread_create.c:477 #5 0x7f7897bd5103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 40 (Thread 0x7f77b700 (LWP 4169)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x7f77ec068d30) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f77ec068d98, cond=0x7f77ec068d08) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x7f77ec068d08, mutex=0x7f77ec068d98) at pthread_cond_wait.c:638 #3 0x7f7873064ca6 in () at /lib/x86_64-linux-gnu/libavcodec.so.58 #4 0x7f789743d609 in start_thread (arg=) at pthread_create.c:477 #5 0x7f7897bd5103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 39 (Thread 0x7f77e4ca1700 (LWP 4168)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x7f77ec068b80) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f77ec068be8, cond=0x7f77ec068b58) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x7f77ec068b58, mutex=0x7f77ec068be8) at pthread_cond_wait.c:638 #3 0x7f7873064ca6 in () at /lib/x86_64-linux-gnu/libavcodec.so.58 #4 0x7f789743d609 in start_thread (arg=) at pthread_create.c:477 #5 0x7f7897bd5103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 38 (Thread 0x7f77e54a2700 (LWP 4167)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x7f77ec0689d0) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f77ec068a38, cond=0x7f77ec0689a8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x7f77ec0689a8, mutex=0x7f77ec068a38) at pthread_cond_wait.c:638 #3 0x7f7873064ca6 in () at /lib/x86_64-linux-gnu/libavcodec.so.58 #4 0x7f789743d609 in start_thread (arg=) at pthread_create.c:477 #5 0x7f7897bd5103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 37 (Thread 0x7f77e5ca3700 (LWP 4166)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x7f77ec068820) at ../sysdeps/nptl/futex-internal.h:183 #1
[yakuake] [Bug 402634] New: Hotkey to open/retract yakuake doesn't work in Wayland if flag "Use Open/Retract action to focus window" is set
https://bugs.kde.org/show_bug.cgi?id=402634 Bug ID: 402634 Summary: Hotkey to open/retract yakuake doesn't work in Wayland if flag "Use Open/Retract action to focus window" is set Product: yakuake Version: 3.0.5 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: k...@xapienz.ru Target Milestone: --- SUMMARY If I toggle the option "Use Open/Retract action to focus window" on (in Yakuake settings - Behaviour), then my hotkey for opening Yakuake will not work in plasma-wayland. Yakuake window becomes visible and will not be hidden anymore. Also hotkey will not work to focus the window again. STEPS TO REPRODUCE 1. Log into plasma-wayland 2. Enable option "Use Open/Retract action to focus window" in Yakuake settings 3. Try to use hotkey to open/retract Yakuake. OBSERVED RESULT Once the window appears, it does not disappear and cannot be focused by hotkey anymore. EXPECTED RESULT Window should be hidable and focusable by assigned hotkey. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.14, plasma 5.14.4.1. KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.53.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION Reproduces in Ubuntu 19.04 and KDE Neon User Edition 20181227. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 390304] New: Konqueror crashes while writing message in "Instant business network"
https://bugs.kde.org/show_bug.cgi?id=390304 Bug ID: 390304 Summary: Konqueror crashes while writing message in "Instant business network" Product: konqueror Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: ydgins...@gmail.com Target Milestone: --- Application: konqueror (4.14.25) KDE Platform Version: 4.14.30 Qt Version: 4.8.7 Operating System: Linux 4.13.16-100.fc25.x86_64 x86_64 Distribution: "Fedora release 25 (Twenty Five)" -- Information about the crash: - Open IBN site (corporate resource https://ibn.rec-etu.com) - Open some task - Open task conversation tab - Add message - Try to write message in the pop-up window - Crash The crash can be reproduced sometimes. -- Backtrace: Application: Konqueror (konqueror), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 84 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7f343c841900 (LWP 6162))] Thread 4 (Thread 0x7f33ce854700 (LWP 6175)): #0 0x7f3435ac6060 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #1 0x7f3435ac627c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #2 0x7f343b27c47e in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f33c8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #3 0x7f343b24a7bf in QEventLoop::processEvents(QFlags) (this=this@entry=0x7f33ce853c90, flags=...) at kernel/qeventloop.cpp:149 #4 0x7f343b24ab25 in QEventLoop::exec(QFlags) (this=this@entry=0x7f33ce853c90, flags=...) at kernel/qeventloop.cpp:204 #5 0x7f343b139af9 in QThread::exec() (this=) at thread/qthread.cpp:538 #6 0x7f3427cd5b60 in KIO::NameLookUpThread::run() () at /lib64/libkio.so.5 #7 0x7f343b13c3ca in QThreadPrivate::start(void*) (arg=0x5611c9b96e40) at thread/qthread_unix.cpp:352 #8 0x7f343ae9d73a in start_thread (arg=0x7f33ce854700) at pthread_create.c:333 #9 0x7f34393afe7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 3 (Thread 0x7f33cf455700 (LWP 6173)): #0 0x7f343aea3480 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f341a1ec729 in JSC::BlockAllocator::blockFreeingThreadMain() () at /lib64/libQtWebKit.so.4 #2 0x7f341a4f120e in WTF::wtfThreadEntryPoint(void*) () at /lib64/libQtWebKit.so.4 #3 0x7f343ae9d73a in start_thread (arg=0x7f33cf455700) at pthread_create.c:333 #4 0x7f34393afe7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 2 (Thread 0x7f341d063700 (LWP 6165)): #0 0x7f34393a3f3d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f3435ac6166 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f3435ac627c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f343b27c47e in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f33d8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #4 0x7f343b24a7bf in QEventLoop::processEvents(QFlags) (this=this@entry=0x7f341d062cd0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f343b24ab25 in QEventLoop::exec(QFlags) (this=this@entry=0x7f341d062cd0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f343b139af9 in QThread::exec() (this=) at thread/qthread.cpp:538 #7 0x7f343b13c3ca in QThreadPrivate::start(void*) (arg=0x5611c9113f60) at thread/qthread_unix.cpp:352 #8 0x7f343ae9d73a in start_thread (arg=0x7f341d063700) at pthread_create.c:333 #9 0x7f34393afe7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 1 (Thread 0x7f343c841900 (LWP 6162)): [KCrash Handler] #6 0x7f341fb0c8e3 in khtml::InsertNodeBeforeCommandImpl::doApply() () at /lib64/libkhtml.so.5 #7 0x7f341fb0d46a in khtml::EditCommandImpl::apply() () at /lib64/libkhtml.so.5 #8 0x7f341fb0fa3c in khtml::CompositeEditCommandImpl::applyCommandToComposite(WTF::PassRefPtr) () at /lib64/libkhtml.so.5 #9 0x7f341fb0fbb3 in khtml::CompositeEditCommandImpl::insertNodeBefore(DOM::NodeImpl*, DOM::NodeImpl*) () at /lib64/libkhtml.so.5 #10 0x7f341fb1642a in khtml::InputTextCommandImpl::prepareForTextInsertion(bool) () at /lib64/libkhtml.so.5 #11 0x7f341fb1680b in khtml::InputTextCommandImpl::execute(DOM::DOMString const&) () at /lib64/libkhtml.so.5 #12 0x7f341fb176bf in khtml::TypingCommandImpl::insertText(DOM::DOMString const&) () at /lib64/libkhtml.so.5 #13 0x7f341fb17f1b in khtml::TypingCommandImpl::insertText0(DOM::DocumentImpl*, DOM::DOMString const&) () at /lib64/libkhtml.so.5 #14 0x7f341fb0a9bf in DOM::Editor::handleKeyEvent(QKeyEvent*) () at /lib64/libkhtml.so.5 #15 0x7f341f98023a in DOM::ElementImpl::defaultEventHandler(DOM::EventImpl*)
[systemsettings] [Bug 379930] kcm_keyboard kills ibus daemon, entirely breaking the keyboard
https://bugs.kde.org/show_bug.cgi?id=379930 Evgeny Brazgin <k...@xapienz.ru> changed: What|Removed |Added CC||k...@xapienz.ru -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379889] Crash when opening XCF file (Problematic file is available by link).
https://bugs.kde.org/show_bug.cgi?id=379889 --- Comment #7 from Evgeny <m...@vragam.net> --- (In reply to Boudewijn Rempt from comment #4) > Okay, it's worse than I thought. The new gimp 2.9 file format is now > incompatible with XCF v0003, but the Gimp developers haven't increased the > version number, so that cannot be detected. Both gimp 2.8 and krita think > that this is a gimp file, but cannot load it. Krita aborts on this file > because the xcftools library aborts the process if it encounters a malformed > xcf file, instead of returning an error code. > > This really should be reported as a bug with the gimp project, because > changing the file format but then not changing the version number is really > bad. My knowledge of english is hardly enough to describe the problem to the GIMP developers. Thanks for the help ;) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379889] New: Crash when opening XCF file (Problematic file is available by link).
https://bugs.kde.org/show_bug.cgi?id=379889 Bug ID: 379889 Summary: Crash when opening XCF file (Problematic file is available by link). Product: krita Version: 3.1.2 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: m...@vragam.net Target Milestone: --- Krita crashes when trying to open an XCF file. Problematic file: https://drive.google.com/file/d/0B6NW7LP-fpbxaWZVNl9hVl91d0E/view?usp=sharing --- Kubuntu 17.04 (amd64) with latest updates. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 375738] New: Crash on exit
https://bugs.kde.org/show_bug.cgi?id=375738 Bug ID: 375738 Summary: Crash on exit Product: kdevelop Version: 4.7.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: xeng...@mail.ru Target Milestone: --- Application: kdevelop (4.7.3) KDE Platform Version: 4.14.22 Qt Version: 4.8.7 Operating System: Linux 4.8.0-36-generic x86_64 Distribution: Ubuntu 16.10 -- Information about the crash: - What I was doing when the application crashed: kdevelop crashes when closing application. Not always but very often reproducable. The crash can be reproduced every time. -- Backtrace: Application: KDevelop (kdevelop), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6638407900 (LWP 13289))] Thread 22 (Thread 0x7f64f3fff700 (LWP 24742)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f66351dc3a6 in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x6cf6860) at thread/qwaitcondition_unix.cpp:86 #2 QWaitCondition::wait (this=this@entry=0x79ec0c8, mutex=0x78b2d00, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158 #3 0x7f662af65180 in ThreadWeaver::WeaverImpl::blockThreadUntilJobsAreBeingAssigned (this=0x79ec0a0, th=0x11bf2200) at ./threadweaver/Weaver/WeaverImpl.cpp:370 #4 0x7f662af679e3 in ThreadWeaver::WorkingHardState::applyForWork (this=0x67c74c0, th=0x11bf2200, previous=0xf3cf0c0) at ./threadweaver/Weaver/WorkingHardState.cpp:68 #5 0x7f662af664dd in ThreadWeaver::Thread::run (this=0x11bf2200) at ./threadweaver/Weaver/Thread.cpp:98 #6 0x7f66351dbe3c in QThreadPrivate::start (arg=0x11bf2200) at thread/qthread_unix.cpp:352 #7 0x7f66310016ca in start_thread (arg=0x7f64f3fff700) at pthread_create.c:333 #8 0x7f6634b1a0af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 21 (Thread 0x7f64f8a8d700 (LWP 24741)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f66351dc3a6 in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x6cf6860) at thread/qwaitcondition_unix.cpp:86 #2 QWaitCondition::wait (this=this@entry=0x79ec0c8, mutex=0x78b2d00, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158 #3 0x7f662af65180 in ThreadWeaver::WeaverImpl::blockThreadUntilJobsAreBeingAssigned (this=0x79ec0a0, th=0x10638ad0) at ./threadweaver/Weaver/WeaverImpl.cpp:370 #4 0x7f662af679e3 in ThreadWeaver::WorkingHardState::applyForWork (this=0x67c74c0, th=0x10638ad0, previous=0x0) at ./threadweaver/Weaver/WorkingHardState.cpp:68 #5 0x7f662af679fc in ThreadWeaver::WorkingHardState::applyForWork (this=0x67c74c0, th=0x10638ad0, previous=0x0) at ./threadweaver/Weaver/WorkingHardState.cpp:71 #6 0x7f662af679fc in ThreadWeaver::WorkingHardState::applyForWork (this=0x67c74c0, th=0x10638ad0, previous=0x0) at ./threadweaver/Weaver/WorkingHardState.cpp:71 #7 0x7f662af679fc in ThreadWeaver::WorkingHardState::applyForWork (this=0x67c74c0, th=0x10638ad0, previous=0x0) at ./threadweaver/Weaver/WorkingHardState.cpp:71 #8 0x7f662af679fc in ThreadWeaver::WorkingHardState::applyForWork (this=0x67c74c0, th=0x10638ad0, previous=0x1a680270) at ./threadweaver/Weaver/WorkingHardState.cpp:71 #9 0x7f662af664dd in ThreadWeaver::Thread::run (this=0x10638ad0) at ./threadweaver/Weaver/Thread.cpp:98 #10 0x7f66351dbe3c in QThreadPrivate::start (arg=0x10638ad0) at thread/qthread_unix.cpp:352 #11 0x7f66310016ca in start_thread (arg=0x7f64f8a8d700) at pthread_create.c:333 #12 0x7f6634b1a0af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 20 (Thread 0x7f651cce9700 (LWP 22589)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f66351dc3a6 in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x6cf6860) at thread/qwaitcondition_unix.cpp:86 #2 QWaitCondition::wait (this=this@entry=0x79ec0c8, mutex=0x78b2d00, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158 #3 0x7f662af65180 in ThreadWeaver::WeaverImpl::blockThreadUntilJobsAreBeingAssigned (this=0x79ec0a0, th=0xaa3d000) at ./threadweaver/Weaver/WeaverImpl.cpp:370 #4 0x7f662af679e3 in ThreadWeaver::WorkingHardState::applyForWork (this=0x67c74c0, th=0xaa3d000, previous=0x0) at ./threadweaver/Weaver/WorkingHardState.cpp:68 #5 0x7f662af679fc in ThreadWeaver::WorkingHardState::applyForWork (this=0x67c74c0, th=0xaa3d000, previous=0x0) at ./threadweaver/Weaver/WorkingHardState.cpp:71 #6 0x7f662af679fc in ThreadWeaver::WorkingHardState::applyForWork (this=0x67c74c0, th=0xaa3d000,
[kmail2] [Bug 375387] New: Crash after wrong recipient name while forwarding message
https://bugs.kde.org/show_bug.cgi?id=375387 Bug ID: 375387 Summary: Crash after wrong recipient name while forwarding message Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: ydgins...@gmail.com Target Milestone: --- Application: kmail (4.14.10) KDE Platform Version: 4.14.9 Qt Version: 4.8.6 Operating System: Linux 3.16.7-48-desktop x86_64 Distribution: "openSUSE 13.2 (Harlequin) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: 1. Forward message in body 2. Type "ivy" in recepient address 3. Switch to Russian layout The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f913365a800 (LWP 2126))] Thread 5 (Thread 0x7f910ddb8700 (LWP 2148)): #0 0x7f912e76403f in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f9123e5d686 in WTF::TCMalloc_PageHeap::scavengerThread() () at /usr/lib64/libQtWebKit.so.4 #2 0x7f9123e5d6b9 in () at /usr/lib64/libQtWebKit.so.4 #3 0x7f912e7600a4 in start_thread (arg=0x7f910ddb8700) at pthread_create.c:309 #4 0x7f91309616ed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 4 (Thread 0x7f90ccc25700 (LWP 2206)): #0 0x7f912e76403f in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f9123bcfe7d in JSC::BlockAllocator::blockFreeingThreadMain() () at /usr/lib64/libQtWebKit.so.4 #2 0x7f9123e851e6 in WTF::wtfThreadEntryPoint(void*) () at /usr/lib64/libQtWebKit.so.4 #3 0x7f912e7600a4 in start_thread (arg=0x7f90ccc25700) at pthread_create.c:309 #4 0x7f91309616ed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 3 (Thread 0x7f90c7bff700 (LWP 2211)): #0 0x7f91309592bd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f912868bbe4 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f912868bcec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f9131fb40de in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f90c8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #4 0x7f9131f85e6f in QEventLoop::processEvents(QFlags) (this=this@entry=0x7f90c7bfede0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f9131f86165 in QEventLoop::exec(QFlags) (this=this@entry=0x7f90c7bfede0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f9131e830bf in QThread::exec() (this=) at thread/qthread.cpp:538 #7 0x7f9131e8579f in QThreadPrivate::start(void*) (arg=0x27416f0) at thread/qthread_unix.cpp:349 #8 0x7f912e7600a4 in start_thread (arg=0x7f90c7bff700) at pthread_create.c:309 #9 0x7f91309616ed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 2 (Thread 0x7f90c4db3700 (LWP 4706)): #0 0x7f91309592bd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f912868bbe4 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f912868bcec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f9131fb40de in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f90bc003380, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #4 0x7f9131f85e6f in QEventLoop::processEvents(QFlags) (this=this@entry=0x7f90c4db2da0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f9131f86165 in QEventLoop::exec(QFlags) (this=this@entry=0x7f90c4db2da0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f9131e830bf in QThread::exec() (this=this@entry=0x66fdb70) at thread/qthread.cpp:538 #7 0x7f9131f67783 in QInotifyFileSystemWatcherEngine::run() (this=0x66fdb70) at io/qfilesystemwatcher_inotify.cpp:265 #8 0x7f9131e8579f in QThreadPrivate::start(void*) (arg=0x66fdb70) at thread/qthread_unix.cpp:349 #9 0x7f912e7600a4 in start_thread (arg=0x7f90c4db3700) at pthread_create.c:309 #10 0x7f91309616ed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7f913365a800 (LWP 2126)): [KCrash Handler] #5 0x7f91308af0a7 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #6 0x7f91308b0458 in __GI_abort () at abort.c:78 #7 0x7f9130ea0145 in __gnu_cxx::__verbose_terminate_handler() () at /usr/lib64/libstdc++.so.6 #8 0x7f9130e9e2e6 in () at /usr/lib64/libstdc++.so.6 #9 0x7f9130e9e313 in () at /usr/lib64/libstdc++.so.6 #10 0x7f9130e9e586 in __cxa_rethrow () at /usr/lib64/libstdc++.so.6 #11 0x7f9131f86356 in QEventLoop::exec(QFlags) (this=this@entry=0x7ffd1d8c0e90, flags=...) at kernel/qeventloop.cpp:218 #12 0x7f9131f8b5b9 in QCoreApplication::exec() () at
[plasmashell] [Bug 359109] ibus terminated when switching back from virtual terminal
https://bugs.kde.org/show_bug.cgi?id=359109 --- Comment #10 from Evgeny Brazgin <k...@xapienz.ru> --- > The current advice is to remove ibus-qt Unfortunately, this is not a solution when ibus is necessary, because KDE itself doesn't provide input engines available in ibus. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372937] New: kdevelop crashes when removing breakpoint
https://bugs.kde.org/show_bug.cgi?id=372937 Bug ID: 372937 Summary: kdevelop crashes when removing breakpoint Product: kdevelop Version: 4.7.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: xeng...@mail.ru Target Milestone: --- Application: kdevelop (4.7.3) KDE Platform Version: 4.14.22 Qt Version: 4.8.7 Operating System: Linux 4.8.0-28-generic x86_64 Distribution: Ubuntu 16.10 -- Information about the crash: - What I was doing when the application crashed: After several debugging sessions removing a breakpoint causes crash. GDB: GNU gdb (Ubuntu 7.11.90.20161005-0ubuntu1) 7.11.90.20161005-git GCC: gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) binutils: 2.27-8ubuntu2 The crash can be reproduced every time. -- Backtrace: Application: KDevelop (kdevelop), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f252db0d900 (LWP 15304))] Thread 21 (Thread 0x7f241f7fe700 (LWP 17521)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f252a8e23a6 in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x203afb0) at thread/qwaitcondition_unix.cpp:86 #2 QWaitCondition::wait (this=this@entry=0x1f9d768, mutex=0x5cfb3a0, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158 #3 0x7f252066c180 in ThreadWeaver::WeaverImpl::blockThreadUntilJobsAreBeingAssigned (this=0x1f9d740, th=0x90c4e20) at ./threadweaver/Weaver/WeaverImpl.cpp:370 #4 0x7f252066e9e3 in ThreadWeaver::WorkingHardState::applyForWork (this=0x1fe7d00, th=0x90c4e20, previous=0x0) at ./threadweaver/Weaver/WorkingHardState.cpp:68 #5 0x7f252066d4dd in ThreadWeaver::Thread::run (this=0x90c4e20) at ./threadweaver/Weaver/Thread.cpp:98 #6 0x7f252a8e1e3c in QThreadPrivate::start (arg=0x90c4e20) at thread/qthread_unix.cpp:352 #7 0x7f25267076ca in start_thread (arg=0x7f241f7fe700) at pthread_create.c:333 #8 0x7f252a2200af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 20 (Thread 0x7f241700 (LWP 17520)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f252a8e23a6 in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x203afb0) at thread/qwaitcondition_unix.cpp:86 #2 QWaitCondition::wait (this=this@entry=0x1f9d768, mutex=0x5cfb3a0, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158 #3 0x7f252066c180 in ThreadWeaver::WeaverImpl::blockThreadUntilJobsAreBeingAssigned (this=0x1f9d740, th=0x8a78670) at ./threadweaver/Weaver/WeaverImpl.cpp:370 #4 0x7f252066e9e3 in ThreadWeaver::WorkingHardState::applyForWork (this=0x1fe7d00, th=0x8a78670, previous=0x0) at ./threadweaver/Weaver/WorkingHardState.cpp:68 #5 0x7f252066d4dd in ThreadWeaver::Thread::run (this=0x8a78670) at ./threadweaver/Weaver/Thread.cpp:98 #6 0x7f252a8e1e3c in QThreadPrivate::start (arg=0x8a78670) at thread/qthread_unix.cpp:352 #7 0x7f25267076ca in start_thread (arg=0x7f241700) at pthread_create.c:333 #8 0x7f252a2200af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 19 (Thread 0x7f2424d75700 (LWP 15950)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f252a8e23a6 in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x203afb0) at thread/qwaitcondition_unix.cpp:86 #2 QWaitCondition::wait (this=this@entry=0x1f9d768, mutex=0x5cfb3a0, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158 #3 0x7f252066c180 in ThreadWeaver::WeaverImpl::blockThreadUntilJobsAreBeingAssigned (this=0x1f9d740, th=0x1ed5940) at ./threadweaver/Weaver/WeaverImpl.cpp:370 #4 0x7f252066e9e3 in ThreadWeaver::WorkingHardState::applyForWork (this=0x1fe7d00, th=0x1ed5940, previous=0x0) at ./threadweaver/Weaver/WorkingHardState.cpp:68 #5 0x7f252066e9fc in ThreadWeaver::WorkingHardState::applyForWork (this=0x1fe7d00, th=0x1ed5940, previous=0x0) at ./threadweaver/Weaver/WorkingHardState.cpp:71 #6 0x7f252066e9fc in ThreadWeaver::WorkingHardState::applyForWork (this=0x1fe7d00, th=0x1ed5940, previous=0x0) at ./threadweaver/Weaver/WorkingHardState.cpp:71 #7 0x7f252066d4dd in ThreadWeaver::Thread::run (this=0x1ed5940) at ./threadweaver/Weaver/Thread.cpp:98 #8 0x7f252a8e1e3c in QThreadPrivate::start (arg=0x1ed5940) at thread/qthread_unix.cpp:352 #9 0x7f25267076ca in start_thread (arg=0x7f2424d75700) at pthread_create.c:333 #10 0x7f252a2200af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 18 (Thread 0x7f2456768700 (LWP 15949)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at
[plasmashell] [Bug 365570] Systray icons are big and pixelated after update to 5.7.1
https://bugs.kde.org/show_bug.cgi?id=365570 --- Comment #18 from Evgeny Brazgin <k...@xapienz.ru> --- Still not fixed in 5.7.5 :( Looking into git, I see that the fix is only merged to 5.7.95/5.8. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 344027] Synchronise news with feedly
https://bugs.kde.org/show_bug.cgi?id=344027 Evgeny Brazgin <k...@xapienz.ru> changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #4 from Evgeny Brazgin <k...@xapienz.ru> --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359109] ibus terminated when switching back from virtual terminal
https://bugs.kde.org/show_bug.cgi?id=359109 Evgeny Brazgin <k...@xapienz.ru> changed: What|Removed |Added CC||k...@xapienz.ru --- Comment #3 from Evgeny Brazgin <k...@xapienz.ru> --- I also have this problem in 5.6.2, it is very annoying. Also after ibus dies, it is impossible to input any text in KDE apps (though Qt5 and GTK apps receive input fine, only KDE apps stop responding to keyboard): konsole, yakuake, kate, krunner become useless until I restart ibus-daemon manually. I found that setting "QT_IM_MODULE=" helps to workaround this, but will disable ibus in KDE apps. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365570] Systray icons are big and pixelated after update to 5.7.1
https://bugs.kde.org/show_bug.cgi?id=365570 --- Comment #13 from Evgeny Brazgin <k...@xapienz.ru> --- The bug still appears in Plasma 5.7.2. BTW, Bob Wya's patch works well. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365570] Systray icons are big and pixelated after update to 5.7.1
https://bugs.kde.org/show_bug.cgi?id=365570 --- Comment #17 from Evgeny Brazgin <k...@xapienz.ru> --- @cher...@aip.de You have no problem, because OpenSuse has already included the patch into their build: https://build.opensuse.org/package/view_file/KDE:Frameworks5/plasma5-workspace/Configuration-option-for-System-Tray-icon-size.patch?expand=1 So, waiting for this patch to be released in 5.7.3 (it is in master branch in git, but didn't come to 5.7.2). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 350994] Crash in KScreen::Output::isEnabled
https://bugs.kde.org/show_bug.cgi?id=350994 --- Comment #11 from Evgeny Brazgin <k...@xapienz.ru> --- I can confirm that after updating to Plasma 5.7 this bug no longer appears on my system. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365570] Systray icons are big and pixelated after update to 5.7.1
https://bugs.kde.org/show_bug.cgi?id=365570 Evgeny Brazgin <k...@xapienz.ru> changed: What|Removed |Added CC||k...@xapienz.ru -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 106574] quote indicator should be color line like in thunderbird
https://bugs.kde.org/show_bug.cgi?id=106574 --- Comment #8 from Evgeny <alarmf...@yandex.ru> --- Unfortunately, I can't confirm that this issue has been resolved. I've just checked. Yes, htlm messages with html quotes are displayed correctly (with color lines), but when I try to answer on this message all these color quotes disappear because editor doesn't support this functionality. It just leaves indents instead of quotes. I can provide a screenshots if it necessary. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 350994] Opened trash folder
https://bugs.kde.org/show_bug.cgi?id=350994 --- Comment #6 from Evgeny Brazgin <k...@xapienz.ru> --- Created attachment 98256 --> https://bugs.kde.org/attachment.cgi?id=98256=edit Qt sends "screenRemoved" and "screenAdded" when renaming QScreen I modified Qt sources so it sends "screenRemoved" when the screen is converted to "fake" and sends "screenAdded" when the screen is converted to normal. My crash disappeared. Also I made Ubuntu ppa with patched package for Ubuntu-xenial: https://launchpad.net/~xapienz/+archive/ubuntu/ppa. If anyone can confirm the fix, you are welcome :) Meanwhile, I will try to notify Qt team and propose them the solution. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 350994] Opened trash folder
https://bugs.kde.org/show_bug.cgi?id=350994 --- Comment #5 from Evgeny Brazgin <k...@xapienz.ru> --- Here is part of backtrace when the screen is renamed inside Qt: #2 0x77f03c83 in QXcbScreen::setOutput (this=0x645290, outputId=outputId@entry=0, outputInfo=outputInfo@entry=0x0) at qxcbscreen.cpp:405 #3 0x77ef2c27 in QXcbConnection::destroyScreen (this=this@entry=0x636e40, screen=screen@entry=0x645290) at qxcbconnection.cpp:336 #4 0x77ef3d68 in QXcbConnection::updateScreens (this=this@entry=0x636e40, event=event@entry=0x7fffe4004300) at qxcbconnection.cpp:210 #5 0x77ef48b3 in QXcbConnection::handleXcbEvent (this=this@entry=0x636e40, event=event@entry=0x7fffe4004300) at qxcbconnection.cpp:1160 The screen is converted into "fake screen" and then later reused for another output. In my case firstly "HDMI1" is renamed to ":0.0" (fake) and then after short time to "eDP1" (real). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 350994] Opened trash folder
https://bugs.kde.org/show_bug.cgi?id=350994
--- Comment #4 from Evgeny Brazgin <k...@xapienz.ru> ---
Also I made a small proof-of-concept app which prints all available screens
with the code:
qDebug() << "screens";
foreach (QScreen* screen, QGuiApplication::screens()) {
qDebug() << "" << screen << " with name=" << screen->name() << "
and platform screen=" << screen->handle();
}
When I detach and external monitor and attach it again, I have the output
(before detaching monitor, detached monitor, after attaching it back):
screens:
QScreen(0x23fcff0) with name= "HDMI1" and platform screen= 0x2401850
screens:
QScreen(0x23fcff0) with name= "eDP1" and platform screen= 0x2401850
screens:
QScreen(0x23fcff0) with name= "HDMI1" and platform screen= 0x2401850
It is evident from the output, that the pointer to QScreen object remains the
same, but the name changes.
If necessary, I will upload this app here, just let me know.
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 356393] valgrind (vex) crashes because isZeroU happened
https://bugs.kde.org/show_bug.cgi?id=356393 Evgeny Kravchenko <cravc...@yandex.ru> changed: What|Removed |Added CC||cravc...@yandex.ru -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 343099] Linux setns syscall wrapper missing, unhandled syscall: 308
https://bugs.kde.org/show_bug.cgi?id=343099 Evgeny Vereshchagin <evv...@ya.ru> changed: What|Removed |Added CC||evv...@ya.ru --- Comment #3 from Evgeny Vereshchagin <evv...@ya.ru> --- Hi! What is the status of this issue? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 347524] Qt Creator Options crashed in Breeze theme
https://bugs.kde.org/show_bug.cgi?id=347524 --- Comment #35 from Evgeny Markov <evgenymar...@protonmail.com> --- Sorry, i forgot say info about my system: Arch Linux, plasma 5.5.2, kf 15.17, breeze 5.5.2, qtcreator 3.6.0-1 from Arch repo. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 347524] Qt Creator Options crashed in Breeze theme
https://bugs.kde.org/show_bug.cgi?id=347524 Evgeny Markov <evgenymar...@protonmail.com> changed: What|Removed |Added CC||evgenymar...@protonmail.com --- Comment #34 from Evgeny Markov <evgenymar...@protonmail.com> --- The bug still occurs! I catch it when i press "Apply" in Tools -> Options.. -> Environment -> Interface. I think the crash caused by applying a theme or color for user interface. Log attached (you can read it here https://paste.kde.org/pfdbroceb): *** Error in `qtcreator-bin': double free or corruption (out): 0x02cee290 *** === Backtrace: = /usr/lib/libc.so.6(+0x72055)[0x7f0b085c8055] /usr/lib/libc.so.6(+0x779a6)[0x7f0b085cd9a6] /usr/lib/libc.so.6(+0x7818e)[0x7f0b085ce18e] /usr/lib/qt/plugins/styles/breeze.so(+0x30344)[0x7f0af14d9344] /usr/lib/qt/plugins/styles/breeze.so(+0x2fdfc)[0x7f0af14d8dfc] /usr/lib/libQt5Widgets.so.5(_ZN7QWidget5eventEP6QEvent+0x668)[0x7f0b097229c8] /usr/lib/libQt5Widgets.so.5(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0x8c)[0x7f0b096df9ac] /usr/lib/libQt5Widgets.so.5(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x256)[0x7f0b096e4e86] /usr/lib/libQt5Core.so.5(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0xdb)[0x7f0b09335bab] /usr/lib/libQt5Widgets.so.5(_ZN14QWidgetPrivate14sendPaintEventERK7QRegion+0x49)[0x7f0b0971b4a9] /usr/lib/libQt5Widgets.so.5(_ZN14QWidgetPrivate10drawWidgetEP12QPaintDeviceRK7QRegionRK6QPointiP8QPainterP19QWidgetBackingStore+0x5f1)[0x7f0b0971baf1] /usr/lib/libQt5Widgets.so.5(_ZN14QWidgetPrivate22paintSiblingsRecursiveEP12QPaintDeviceRK5QListIP7QObjectEiRK7QRegionRK6QPointiP8QPainterP19QWidgetBackingStore+0x44c)[0x7f0b0971c79c] /usr/lib/libQt5Widgets.so.5(_ZN14QWidgetPrivate22paintSiblingsRecursiveEP12QPaintDeviceRK5QListIP7QObjectEiRK7QRegionRK6QPointiP8QPainterP19QWidgetBackingStore+0x339)[0x7f0b0971c689] /usr/lib/libQt5Widgets.so.5(_ZN14QWidgetPrivate10drawWidgetEP12QPaintDeviceRK7QRegionRK6QPointiP8QPainterP19QWidgetBackingStore+0x161)[0x7f0b0971b661] /usr/lib/libQt5Widgets.so.5(_ZN14QWidgetPrivate22paintSiblingsRecursiveEP12QPaintDeviceRK5QListIP7QObjectEiRK7QRegionRK6QPointiP8QPainterP19QWidgetBackingStore+0x44c)[0x7f0b0971c79c] /usr/lib/libQt5Widgets.so.5(_ZN14QWidgetPrivate22paintSiblingsRecursiveEP12QPaintDeviceRK5QListIP7QObjectEiRK7QRegionRK6QPointiP8QPainterP19QWidgetBackingStore+0x339)[0x7f0b0971c689] /usr/lib/libQt5Widgets.so.5(_ZN14QWidgetPrivate22paintSiblingsRecursiveEP12QPaintDeviceRK5QListIP7QObjectEiRK7QRegionRK6QPointiP8QPainterP19QWidgetBackingStore+0x339)[0x7f0b0971c689] /usr/lib/libQt5Widgets.so.5(_ZN14QWidgetPrivate10drawWidgetEP12QPaintDeviceRK7QRegionRK6QPointiP8QPainterP19QWidgetBackingStore+0x161)[0x7f0b0971b661] /usr/lib/libQt5Widgets.so.5(+0x169206)[0x7f0b096ed206] /usr/lib/libQt5Widgets.so.5(+0x16943c)[0x7f0b096ed43c] /usr/lib/libQt5Widgets.so.5(_ZN14QWidgetPrivate16syncBackingStoreEv+0x4f)[0x7f0b0970b5ef] /usr/lib/libQt5Widgets.so.5(_ZN7QWidget5eventEP6QEvent+0x468)[0x7f0b097227c8] /usr/lib/libQt5Widgets.so.5(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0x8c)[0x7f0b096df9ac] /usr/lib/libQt5Widgets.so.5(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x256)[0x7f0b096e4e86] /usr/lib/libQt5Core.so.5(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0xdb)[0x7f0b09335bab] /usr/lib/libQt5Core.so.5(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x2c6)[0x7f0b09337fa6] /usr/lib/libQt5Core.so.5(+0x2dd143)[0x7f0b0938c143] /usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x2a7)[0x7f0b073c9dc7] /usr/lib/libglib-2.0.so.0(+0x4a020)[0x7f0b073ca020] /usr/lib/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7f0b073ca0cc] /usr/lib/libQt5Core.so.5(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x5f)[0x7f0b0938c54f] /usr/lib/libQt5Core.so.5(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x10a)[0x7f0b0933357a] /usr/lib/libQt5Widgets.so.5(_ZN7QDialog4execEv+0x20d)[0x7f0b098daacd] /usr/lib/qtcreator/plugins/libCore.so(+0xff379)[0x7f0af0ef6379] /usr/lib/qtcreator/plugins/libCore.so(+0x1e9d61)[0x7f0af0fe0d61] /usr/lib/libQt5Core.so.5(_ZN11QMetaObject8activateEP7QObjectiiPPv+0x7ba)[0x7f0b0936431a] /usr/lib/libQt5Widgets.so.5(_ZN7QAction9triggeredEb+0x42)[0x7f0b096d5d92] /usr/lib/libQt5Core.so.5(_ZN11QMetaObject8activateEP7QObjectiiPPv+0x647)[0x7f0b093641a7] /usr/lib/libQt5Widgets.so.5(_ZN7QAction9triggeredEb+0x42)[0x7f0b096d5d92] /usr/lib/libQt5Widgets.so.5(_ZN7QAction8activateENS_11ActionEventE+0xf8)[0x7f0b096d8218] /usr/lib/libQt5Widgets.so.5(+0x2d6b72)[0x7f0b0985ab72] /usr/lib/libQt5Widgets.so.5(+0x2dce2c)[0x7f0b09860e2c] /usr/lib/libQt5Widgets.so.5(_ZN5QMenu17mouseReleaseEventEP11QMouseEvent+0x1d0)[0x7f0b09864d70] /usr/lib/libQt5Widgets.so.5(_ZN7QWidget5eventEP6QEvent+0x668)[0x7f0b097229c8] /usr/lib/libQt5Widgets.so.5
