[KBibTeX] [Bug 459911] Opening local PDF attached to Bibtex entry doesn't work
https://bugs.kde.org/show_bug.cgi?id=459911 Florian Edelmann changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 459911] Opening local PDF attached to Bibtex entry doesn't work
https://bugs.kde.org/show_bug.cgi?id=459911 --- Comment #11 from Florian Edelmann --- Thanks for investigating! I've executed the script like you requested: > bash run-kbibtex.sh 'https://invent.kde.org/thomasfischer/kbibtex.git' > 'bugs/kde459911' Its output includes the following line on startup: > [info] kbibtex > (/tmp/flo-kbibtex-git-a3da32a0acdc0a4ba86f7b93436ea11c/src/program/program.cpp:63) > - Starting KBibTeX version "58c75501 (bugs/kde459911)" When pressing Ctrl+D for one of the entries, Okular opens correctly. But there is no special output, just the same Okular warning as before: > [warning] okular (unknown:0) - Unable to open QuickAnnotatingTools XML > definition When clicking the button in the edit dialog's "External" tab, Okular opens correctly and there is this console output: > [info] kbibtex > (/tmp/flo-kbibtex-git-a3da32a0acdc0a4ba86f7b93436ea11c/src/gui/field/fieldlineedit.cpp:356) > - About to open URL > "file:///home/flo/www/master-thesis/master-thesis/papers/wu2019compression.pdf" > with MIME type "application/pdf" > [info] kbibtex > (/tmp/flo-kbibtex-git-a3da32a0acdc0a4ba86f7b93436ea11c/src/gui/field/fieldlineedit.cpp:363) > - KRun::runURL returned true > [warning] okular (unknown:0) - Unable to open QuickAnnotatingTools XML > definition When trying to open the PDF via the context menu, nothing happens at all. No Okular opening, no console output. For reference: Clicking an "external" URL via the context menu opens Firefox with that URL correctly. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 459911] Opening local PDF attached to Bibtex entry doesn't work
https://bugs.kde.org/show_bug.cgi?id=459911 --- Comment #9 from Florian Edelmann --- (In reply to Thomas Fischer from comment #8) > xdg-open wu2019compression.pdf > kde-open wu2019compression.pdf > kde-open5 wu2019compression.pdf All three commands successfully open the PDF in Okular. There is a warning in the terminal "Unable to open QuickAnnotatingTools XML definition" but that seems to come from Okular itself and doesn't have a negative consequence. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 459911] Opening local PDF attached to Bibtex entry doesn't work
https://bugs.kde.org/show_bug.cgi?id=459911
--- Comment #7 from Florian Edelmann ---
Created attachment 152794
--> https://bugs.kde.org/attachment.cgi?id=152794=edit
Minimal reproduction
I am using curly braces, not quotes. But the file path is relative like in your
example:
> localfile = {wu2019compression.pdf}
--
You are receiving this mail because:
You are watching all bug changes.
[KBibTeX] [Bug 459911] Opening local PDF attached to Bibtex entry doesn't work
https://bugs.kde.org/show_bug.cgi?id=459911 --- Comment #5 from Florian Edelmann --- To clarify: "I did" from my previous comment refers to your last sentence "Please use the run-kbibtex.sh script". -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 459911] Opening local PDF attached to Bibtex entry doesn't work
https://bugs.kde.org/show_bug.cgi?id=459911 --- Comment #4 from Florian Edelmann --- (In reply to Thomas Fischer from comment #3) > You cannot simply compile the code and run the resoluting kbibtex binary. I did. The last line of the output from "bash run-kbibtex.sh 'https://invent.kde.org/thomasfischer/kbibtex.git' 'kbibtex/0.10'" is exactly the mentioned error. > Please try this here: > bash run-kbibtex.sh 'https://invent.kde.org/thomasfischer/kbibtex.git' > 'bugs/kde459911' Clicking the button in the "External" tab next to a PDF entry now opens Okular like expected. So one bug fixed :) In the list, Ctrl+D still works as expected, but "View document" in the context menu still does only work for online entries, not for local PDF files. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 459911] Opening local PDF attached to Bibtex entry doesn't work
https://bugs.kde.org/show_bug.cgi?id=459911 --- Comment #2 from Florian Edelmann --- A workaround I just discovered: Opening the PDF with the keyboard shortcut (Ctrl+D) works fine. Using your instructions in the linked issue, I could verify that it does still not work in the 0.9 git version. When trying to run the 0.10 git version, I got this build error: -- The following OPTIONAL packages have not been found: * Qt5NetworkAuth * Qt5WebEngineWidgets * Qt5WebKitWidgets * Qt5 (required version >= 5.9.0) -- Configuring done CMake Error at src/networking/CMakeLists.txt:59 (add_library): Target "kbibtexnetworking" links to target "Qt5::NetworkAuth" but the target was not found. Perhaps a find_package() call is missing for an IMPORTED target, or an ALIAS target is missing? Installing libqt5networkauth5-dev fixed the issue, so it seems to be a misclassification as "optional dependency". Compiling the 0.10 git version works, but it fails to start due to the following error: /tmp/flo-kbibtex-usr/bin/kbibtex: error while loading shared libraries: libkbibtexprocessing.so.0: cannot open shared object file: No such file or directory -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 459911] New: Opening local PDF attached to Bibtex entry doesn't work
https://bugs.kde.org/show_bug.cgi?id=459911
Bug ID: 459911
Summary: Opening local PDF attached to Bibtex entry doesn't
work
Classification: Applications
Product: KBibTeX
Version: 0.9.2
Platform: Neon
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Loading/saving files
Assignee: fisc...@unix-ag.uni-kl.de
Reporter: florian-edelm...@online.de
Target Milestone: ---
SUMMARY
When a local PDF is attached to a Bibtex entry (via "localfile"), I can't open
it in KBibTex's UI.
STEPS TO REPRODUCE
1. Create a new Bibtex file with an arbitrary entry, go to the entry's
"External" tab ("Extern" in German).
2. Attach a local PDF and a website link there.
OBSERVED RESULT
When clicking the "Open" button in that "External" tab for each entry, the
webpage opens in the default browser, but the PDF button does nothing.
When saving the entry, right-clicking it and selecting "View document"
("Dokument betrachten" in German), clicking the webpage entry opens it in the
default browser, while clicking the PDF entry does nothing.
There is no output in the console when starting KBibTeX there.
EXPECTED RESULT
The PDF should open in the default PDF viewer in both cases.
SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.25
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6
Kernel Version: 5.15.0-41-generic (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 630
Manufacturer: Dell Inc.
Product Name: XPS 15 9560
ADDITIONAL INFORMATION
Default browser: Firefox
Default PDF viewer: Okular
--
You are receiving this mail because:
You are watching all bug changes.
[Breeze] [Bug 432576] Add system tray icon for Microsoft Teams (Preview)
https://bugs.kde.org/show_bug.cgi?id=432576 Florian Edelmann changed: What|Removed |Added CC||florian-edelm...@online.de -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 452848] "Kalendar Reminders" crashes when opening Kalendar
https://bugs.kde.org/show_bug.cgi?id=452848 Florian Edelmann changed: What|Removed |Added CC||florian-edelm...@online.de -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 453398] Unchecking "whole day" resets date
https://bugs.kde.org/show_bug.cgi?id=453398 Florian Edelmann changed: What|Removed |Added CC||florian-edelm...@online.de -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 453398] New: Unchecking "whole day" resets date
https://bugs.kde.org/show_bug.cgi?id=453398 Bug ID: 453398 Summary: Unchecking "whole day" resets date Product: kalendar Version: 22.04.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: claudio.cam...@gmail.com Reporter: florian-edelm...@online.de CC: c...@carlschwan.eu Target Milestone: --- SUMMARY When creating a new event on some day in the future, that day is preselected. However, checking and unchecking "whole day" (in German: "Ganztägig") resets that date to the current day. STEPS TO REPRODUCE 1. Double-click on any date in the future to create a new event. 2. Check and uncheck "whole day" checkbox. OBSERVED RESULT Start and end date is reset to today. EXPECTED RESULT Start and end date should stay as they are. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.24 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 452848] "Kalendar Reminders" crashes when opening Kalendar
https://bugs.kde.org/show_bug.cgi?id=452848 Florian Edelmann changed: What|Removed |Added Summary|kalendarac crashes when |"Kalendar Reminders" |opening Kalendar|crashes when opening ||Kalendar -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 452848] kalendarac crashes when opening Kalendar
https://bugs.kde.org/show_bug.cgi?id=452848 Florian Edelmann changed: What|Removed |Added Assignee|unassigned-b...@kde.org |claudio.cam...@gmail.com CC||c...@carlschwan.eu Component|general |general Version|unspecified |1.0.0 Product|kde |kalendar -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 452848] New: kalendarac crashes when opening Kalendar
https://bugs.kde.org/show_bug.cgi?id=452848 Bug ID: 452848 Summary: kalendarac crashes when opening Kalendar Product: kde Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: florian-edelm...@online.de Target Milestone: --- Application: kalendarac (1.0.0) Qt Version: 5.15.3 Frameworks Version: 5.93.0 Operating System: Linux 5.13.0-39-generic x86_64 Windowing System: X11 Distribution: KDE neon User - 5.24 DrKonqi: 5.24.4 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I opened the Kalendar application. The crash notification appears every time when Kalendar is opened. The crash can be reproduced every time. -- Backtrace: Application: Kalendar Reminders (kalendarac), signal: Segmentation fault [New LWP 232862] [New LWP 232863] [New LWP 232864] [New LWP 232865] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f9672c709cf in __GI___poll (fds=0x7ffc5d3fa538, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7f966c628ec0 (LWP 232861))] Thread 5 (Thread 0x7f96698ea700 (LWP 232865)): #0 0x7f9670b924dd in g_mutex_lock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f9670b4548e in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f967325c65b in QEventDispatcherGlib::processEvents (this=0x7f9654000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #3 0x7f967320087b in QEventLoop::exec (this=this@entry=0x7f96698e9be0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #4 0x7f967301a442 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #5 0x7f967301b623 in QThreadPrivate::start (arg=0x556e38dabc50) at thread/qthread_unix.cpp:331 #6 0x7f9671692609 in start_thread (arg=) at pthread_create.c:477 #7 0x7f9672c7d163 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f966a0eb700 (LWP 232864)): #0 0x7f9672c709cf in __GI___poll (fds=0x7f9660004a60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f9670b4536e in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9670b454a3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f967325c65b in QEventDispatcherGlib::processEvents (this=0x7f966b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f967320087b in QEventLoop::exec (this=this@entry=0x7f966a0eabe0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f967301a442 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f967301b623 in QThreadPrivate::start (arg=0x556e38da46d0) at thread/qthread_unix.cpp:331 #7 0x7f9671692609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f9672c7d163 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f966a8ec700 (LWP 232863)): #0 0x7f9672c709cf in __GI___poll (fds=0x7f965c004e60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f9670b4536e in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9670b454a3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f967325c65b in QEventDispatcherGlib::processEvents (this=0x7f965c000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f967320087b in QEventLoop::exec (this=this@entry=0x7f966a8ebbb0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f967301a442 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f9673b8ff4b in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f967301b623 in QThreadPrivate::start (arg=0x7f9673c13d80) at thread/qthread_unix.cpp:331 #8 0x7f9671692609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f9672c7d163 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f966b7d5700 (LWP 232862)): #0 0x7f9672c709cf in __GI___poll (fds=0x7f966b7d4ae8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f967003bc1a in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f967003d90a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f966bf051a8 in QXcbEventQueue::run (this=0x556e38cb88c0) at qxcbeventqueue.cpp:228 #4 0x7f967301b623 in QThreadPrivate::start (arg=0x556e38cb88c0) at thread/qthread_unix.cpp:331 #5 0x7f9671692609 in start_thread (arg=) at
[kalendar] [Bug 450661] Kalendar crashes when trying to enter new event's title
https://bugs.kde.org/show_bug.cgi?id=450661 --- Comment #2 from Florian Edelmann --- (In reply to Claudio Cambra from comment #1) > Have you enabled maps in Kalendar's settings? Yes, I have. -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 450661] New: Kalendar crashes when trying to enter new event's title
https://bugs.kde.org/show_bug.cgi?id=450661 Bug ID: 450661 Summary: Kalendar crashes when trying to enter new event's title Product: kalendar Version: 1.0.0 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: claudio.cam...@gmail.com Reporter: florian-edelm...@online.de CC: c...@carlschwan.eu Target Milestone: --- Application: kalendar (1.0.0) Qt Version: 5.15.3 Frameworks Version: 5.91.0 Operating System: Linux 5.13.0-28-generic x86_64 Windowing System: X11 Distribution: KDE neon User - 5.24 DrKonqi: 5.24.1 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I created a new event, filled in its time, and clicked on the summary/title input field. That moment, the whole application crashed. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Kalendar (kalendar), signal: Segmentation fault [New LWP 195987] [New LWP 195988] [New LWP 195989] [New LWP 195990] [New LWP 195994] [New LWP 195995] [New LWP 196003] [New LWP 196011] [New LWP 196012] [New LWP 196018] [New LWP 196043] [New LWP 196044] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f796d130aff in __GI___poll (fds=0x7ffcbb04a4f8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7f7967ee09c0 (LWP 195985))] Thread 13 (Thread 0x7f7915825700 (LWP 196044)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x563abd2b7124) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x563abd2b70d0, cond=0x563abd2b70f8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x563abd2b70f8, mutex=0x563abd2b70d0) at pthread_cond_wait.c:638 #3 0x7f796d4de6db in QWaitConditionPrivate::wait (deadline=..., this=0x563abd2b70d0) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=this@entry=0x563abd2b70b8, mutex=mutex@entry=0x563abd2b70b0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f796fb46c44 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x563abd2b70a8) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qdeadlinetimer.h:68 #6 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x563abd2b7010) at scenegraph/qsgthreadedrenderloop.cpp:936 #7 0x7f796fb470b9 in QSGRenderThread::run (this=0x563abd2b7010) at scenegraph/qsgthreadedrenderloop.cpp:1053 #8 0x7f796d4d8543 in QThreadPrivate::start (arg=0x563abd2b7010) at thread/qthread_unix.cpp:331 #9 0x7f796b859609 in start_thread (arg=) at pthread_create.c:477 #10 0x7f796d13d293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7f7916026700 (LWP 196043)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x563abc14c6c0) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x563abc14c670, cond=0x563abc14c698) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x563abc14c698, mutex=0x563abc14c670) at pthread_cond_wait.c:638 #3 0x7f794663a5eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7f794663a1eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7f796b859609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f796d13d293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7f791dacf700 (LWP 196018)): #0 0x7f796ae208ed in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f796ae22345 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f796ae23cbf in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f796ae24312 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f796ae244a3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f796d719a0b in QEventDispatcherGlib::processEvents (this=0x7f7918000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f796d6bdc9b in QEventLoop::exec (this=this@entry=0x7f791dacebe0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #7 0x7f796d4d7362 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #8 0x7f796d4d8543 in QThreadPrivate::start (arg=0x563abb6c1bf0) at thread/qthread_unix.cpp:331 #9 0x7f796b859609 in start_thread (arg=) at pthread_create.c:477 #10 0x7f796d13d293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7f7939c61700 (LWP 196012)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x563ab76efc94) at ../sysdeps/nptl/futex-internal.h:183 #1
[kalendar] [Bug 450640] Kalendar event notification crashes
https://bugs.kde.org/show_bug.cgi?id=450640 Florian Edelmann changed: What|Removed |Added Product|kde |kalendar CC||c...@carlschwan.eu, ||florian-edelm...@online.de Assignee|unassigned-b...@kde.org |claudio.cam...@gmail.com Version|unspecified |1.0.0 Component|general |general -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 450640] New: Kalendar event notification crashes
https://bugs.kde.org/show_bug.cgi?id=450640 Bug ID: 450640 Summary: Kalendar event notification crashes Product: kde Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: florian-edelm...@online.de Target Milestone: --- Application: kalendarac (1.0.0) Qt Version: 5.15.3 Frameworks Version: 5.91.0 Operating System: Linux 5.13.0-28-generic x86_64 Windowing System: X11 Distribution: KDE neon User - 5.24 DrKonqi: 5.24.1 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Nothing special, just browsing the web in Firefox. I woke up the laptop from standby a few minutes earlier. The KAlarmNotifier (or similar) window appeared with two event notifications that should have appeared while the laptop was in standby. Kalendar did not notify me about these two events. Instead, a notification about its crash appeared after a few minutes. Note: this is likely the same bug as https://bugs.kde.org/show_bug.cgi?id=447836, but now in version 1.0.0 The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Kalendar Reminders (kalendarac), signal: Segmentation fault [New LWP 2426] [New LWP 2429] [New LWP 2431] [New LWP 2436] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f3103745aff in __GI___poll (fds=0x7ffdcf5f58b8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7f30fd1f89c0 (LWP 2409))] Thread 5 (Thread 0x7f30fa4c3700 (LWP 2436)): #0 0x7f3101629907 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f310162a29b in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f310162a4a3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3103d2ea0b in QEventDispatcherGlib::processEvents (this=0x7f30e4000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f3103cd2c9b in QEventLoop::exec (this=this@entry=0x7f30fa4c2be0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f3103aec362 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f3103aed543 in QThreadPrivate::start (arg=0x55e2b7963400) at thread/qthread_unix.cpp:331 #7 0x7f3102178609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f3103752293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f30facc4700 (LWP 2431)): #0 0x7f3103745aff in __GI___poll (fds=0x7f30f0004a60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f310162a36e in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f310162a4a3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3103d2ea0b in QEventDispatcherGlib::processEvents (this=0x7f30fb60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f3103cd2c9b in QEventLoop::exec (this=this@entry=0x7f30facc3be0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f3103aec362 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f3103aed543 in QThreadPrivate::start (arg=0x55e2b79649c0) at thread/qthread_unix.cpp:331 #7 0x7f3102178609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f3103752293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f30fb4c5700 (LWP 2429)): #0 0x7f3103745aff in __GI___poll (fds=0x7f30ec004e60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f310162a36e in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f310162a4a3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3103d2ea0b in QEventDispatcherGlib::processEvents (this=0x7f30ec000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f3103cd2c9b in QEventLoop::exec (this=this@entry=0x7f30fb4c4bb0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f3103aec362 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f310465cf4b in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f3103aed543 in QThreadPrivate::start (arg=0x7f31046e0d80) at thread/qthread_unix.cpp:331 #8 0x7f3102178609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f3103752293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f30fc3a6700 (LWP 2426)): #0 0x7f3103745aff in __GI___poll (fds=0x7f30fc3a5ae8, nfds=1, timeout=-1)
[kalendar] [Bug 447836] Kalendar event notification crashes
https://bugs.kde.org/show_bug.cgi?id=447836 --- Comment #1 from Florian Edelmann --- Another instance of this crash report, but a different stacktrace this time: Application: Kalendar Reminders (kalendarac), signal: Segmentation fault [New LWP 35094] [New LWP 35095] [New LWP 35096] [New LWP 35097] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f0e3d346aff in __GI___poll (fds=0x7ffc92a672f8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7f0e373bb9c0 (LWP 35093))] Thread 5 (Thread 0x7f0e2eebc700 (LWP 35097)): #0 0x7f0e3d346aff in __GI___poll (fds=0x7f0e1c004e60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f0e3b43036e in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0e3b4304a3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0e3d92f61b in QEventDispatcherGlib::processEvents (this=0x7f0e1c000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f0e3d8d38ab in QEventLoop::exec (this=this@entry=0x7f0e2eebbbe0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f0e3d6ed2c2 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f0e3d6ee45c in QThreadPrivate::start (arg=0x55e871105480) at thread/qthread_unix.cpp:329 #7 0x7f0e3be35609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f0e3d353293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f0e2700 (LWP 35096)): #0 0x7f0e3b47d4dd in g_mutex_lock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f0e3b42fdac in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0e3b430312 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0e3b4304a3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f0e3d92f61b in QEventDispatcherGlib::processEvents (this=0x7f0e24000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f0e3d8d38ab in QEventLoop::exec (this=this@entry=0x7f0e2fffebe0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #6 0x7f0e3d6ed2c2 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #7 0x7f0e3d6ee45c in QThreadPrivate::start (arg=0x55e8710b03c0) at thread/qthread_unix.cpp:329 #8 0x7f0e3be35609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f0e3d353293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f0e355ac700 (LWP 35095)): #0 0x7f0e3d346aff in __GI___poll (fds=0x7f0e2801bc30, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f0e3b43036e in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0e3b4304a3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0e3d92f61b in QEventDispatcherGlib::processEvents (this=0x7f0e28000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f0e3d8d38ab in QEventLoop::exec (this=this@entry=0x7f0e355abbb0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f0e3d6ed2c2 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f0e3e90af4b in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f0e3d6ee45c in QThreadPrivate::start (arg=0x7f0e3e98ed80) at thread/qthread_unix.cpp:329 #8 0x7f0e3be35609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f0e3d353293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f0e3656a700 (LWP 35094)): #0 0x7f0e3d346aff in __GI___poll (fds=0x7f0e36569ae8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f0e3aa0ec1a in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f0e3aa1090a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f0e36c99e88 in QXcbEventQueue::run (this=0x55e870f89520) at qxcbeventqueue.cpp:228 #4 0x7f0e3d6ee45c in QThreadPrivate::start (arg=0x55e870f89520) at thread/qthread_unix.cpp:329 #5 0x7f0e3be35609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f0e3d353293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f0e373bb9c0 (LWP 35093)): [KCrash Handler] #4 0x7f0e3f11f16c in KNotification::sendEvent (this=0x55e87147c0e0) at ./src/knotification.cpp:517 #5 0x55e86efdedad in AlarmNotification::send (this=) at ./kalendarac/alarmnotification.cpp:37 #6 0x55e86efdf6ae in NotificationHandler::sendActiveNotifications (this=) at ./kalendarac/notificationhandler.cpp:59 #7 0x55e86efe0c7d in NotificationHandler::sendNotifications (this=0x55e871096500) at ./kalendarac/notificationhandler
[kalendar] [Bug 447836] Kalendar event notification crashes
https://bugs.kde.org/show_bug.cgi?id=447836 Florian Edelmann changed: What|Removed |Added Version|unspecified |0.3.1 Component|general |general CC||c...@carlschwan.eu Product|kde |kalendar Assignee|unassigned-b...@kde.org |claudio.cam...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 447836] New: Kalendar event notification crashes
https://bugs.kde.org/show_bug.cgi?id=447836 Bug ID: 447836 Summary: Kalendar event notification crashes Product: kde Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: florian-edelm...@online.de Target Milestone: --- Application: kalendarac () Qt Version: 5.15.3 Frameworks Version: 5.89.0 Operating System: Linux 5.11.0-43-generic x86_64 Windowing System: X11 Distribution: KDE neon User - Plasma 25th Anniversary Edition DrKonqi: 5.23.4 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Nothing special, just browsing the web in Firefox. I woke up the laptop from standby a few minutes earlier. The KAlarmNotifier (or similar) window appeared with two event notifications that should have appeared while the laptop was in standby. Kalendar did not notify me about these two events. Instead, a notification about its crash appeared after a few minutes. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Kalendar Reminders (kalendarac), signal: Segmentation fault [New LWP 1818] [New LWP 1833] [New LWP 1853] [New LWP 1860] [New LWP 3065] [New LWP 3066] [New LWP 3067] [New LWP 3068] [New LWP 3071] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f372fa93aff in __GI___poll (fds=0x7ffec05e9af8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7f3729b089c0 (LWP 1764))] Thread 10 (Thread 0x7f37067fc700 (LWP 3071)): #0 __GI___libc_read (nbytes=10, buf=0x7f37067fba1e, fd=24) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=24, buf=0x7f37067fba1e, nbytes=10) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f3720304975 in pa_read () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #3 0x7f3720388416 in pa_mainloop_prepare () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f3720388eb4 in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f3720388f70 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f372039711d in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #7 0x7f372033372c in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #8 0x7f372e582609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f372faa0293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f3706ffd700 (LWP 3068)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5576979a8778) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5576979a8728, cond=0x5576979a8750) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5576979a8750, mutex=0x5576979a8728) at pthread_cond_wait.c:638 #3 0x7f3712834e7b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7f3712834a7b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7f372e582609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f372faa0293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f37077fe700 (LWP 3067)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5576979a8778) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5576979a8728, cond=0x5576979a8750) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5576979a8750, mutex=0x5576979a8728) at pthread_cond_wait.c:638 #3 0x7f3712834e7b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7f3712834a7b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7f372e582609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f372faa0293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f3707fff700 (LWP 3066)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5576979a8778) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5576979a8728, cond=0x5576979a8750) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5576979a8750, mutex=0x5576979a8728) at pthread_cond_wait.c:638 #3 0x7f3712834e7b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7f3712834a7b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7f372e582609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f372faa0293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f370cf36700 (LWP 3065)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5576979a8778) at ../sysdeps/nptl/futex-internal.h:183 #1
[systemsettings] [Bug 446285] Show KCM in search results if English title matches query, even when the system is using another language
https://bugs.kde.org/show_bug.cgi?id=446285 Florian Edelmann changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #5 from Florian Edelmann --- MR https://invent.kde.org/plasma/systemsettings/-/merge_requests/102 was merged, so this is fixed now :) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 446285] Show KCM in search results if English title matches query, even when the system is using another language
https://bugs.kde.org/show_bug.cgi?id=446285 Florian Edelmann changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #3 from Florian Edelmann --- Reopening due to https://invent.kde.org/plasma/systemsettings/-/merge_requests/101#note_350997 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 446288] Clearing system settings search loses focus when in sub-menu
https://bugs.kde.org/show_bug.cgi?id=446288 Florian Edelmann changed: What|Removed |Added CC||florian-edelm...@online.de -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 446288] New: Clearing system settings search loses focus when in sub-menu
https://bugs.kde.org/show_bug.cgi?id=446288 Bug ID: 446288 Summary: Clearing system settings search loses focus when in sub-menu Product: systemsettings Version: 5.23.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: sidebarview Assignee: notm...@gmail.com Reporter: florian-edelm...@online.de CC: plasma-b...@kde.org Target Milestone: --- STEPS TO REPRODUCE * open system settings * navigate to "Appearance → App theme" (German: "Erscheinungsbild → Anwendungs-Stil") * resize window so that sidebar is collapsed to one column and search field is hidden behind the "back" button * type something in the search box * click the "clear" button or clear the search field manually WHAT ACTUALLY HAPPENS The search field loses focus and the sidebar shows the sub-menu again. WHAT I EXPECTED TO HAPPEN The search field should have stayed focused to initiate another search. The main menu should be displayed below, with the "Appearance" item highlighted. When I click on the highlighted item, the sub-menu should show again. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 446285] Show KCM in search results if English title matches query
https://bugs.kde.org/show_bug.cgi?id=446285 Florian Edelmann changed: What|Removed |Added CC||florian-edelm...@online.de -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 446285] New: Show KCM in search results if English title matches query
https://bugs.kde.org/show_bug.cgi?id=446285 Bug ID: 446285 Summary: Show KCM in search results if English title matches query Product: systemsettings Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: sidebarview Assignee: notm...@gmail.com Reporter: florian-edelm...@online.de CC: plasma-b...@kde.org Target Milestone: --- In System Settings, searching for "Update" currently yields no results if the locale is set to German. I would have expected the "Softwareaktualisierung" KCM (kcm_updates) to show up, because the English title "Software update" matches my search query. Currently, the kcm_updates.desktop file has no search keywords. (I changed that in https://invent.kde.org/plasma/discover/-/merge_requests/214.) I think that search queries are also be matched against search keywords of the default locale, additional to the currently selected locale. (e.g. when I search for "screen", many KCMs are showing up in the results) I suggest doing the same with the title (Name attribute in the desktop file). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 433993] Dolphin Crash when creating a folder in remote folder (kio-Gdrive, FTP)
https://bugs.kde.org/show_bug.cgi?id=433993 Florian Edelmann changed: What|Removed |Added CC||florian-edelm...@online.de -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 432576] Add system tray icon for Microsoft Teams (Preview)
https://bugs.kde.org/show_bug.cgi?id=432576 --- Comment #2 from Florian Edelmann --- Created attachment 135472 --> https://bugs.kde.org/attachment.cgi?id=135472=edit Current icon (with unread notifications) in Breeze Dark -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 432576] Add system tray icon for Microsoft Teams (Preview)
https://bugs.kde.org/show_bug.cgi?id=432576 --- Comment #1 from Florian Edelmann --- Created attachment 135471 --> https://bugs.kde.org/attachment.cgi?id=135471=edit Current icon in Breeze Dark -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 432576] New: Add system tray icon for Microsoft Teams (Preview)
https://bugs.kde.org/show_bug.cgi?id=432576 Bug ID: 432576 Summary: Add system tray icon for Microsoft Teams (Preview) Product: Breeze Version: unspecified Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: florian-edelm...@online.de CC: kain...@gmail.com Target Milestone: --- Microsoft Teams is available on Ubuntu / KDE Neon as an Electron app: https://teams.microsoft.com/ Unfortunately, the system tray icons don't look nice in the Breeze / Breeze Dark theme (see e.g. https://blog.microlinux.fr/wp-content/uploads/2020/05/ms-teams-statut.png) A good starting point could be those two SVGs: - https://www.svgrepo.com/svg/306419/microsoftteams - https://www.svgrepo.com/svg/303180/microsoft-teams-logo Note that there should be at least two variants: "Normal" (like in the screenshot) and "With unread notification" (with a red bell icon in the bottom right of the Teams icon). -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 350140] KSysGuard crashed on close
https://bugs.kde.org/show_bug.cgi?id=350140 --- Comment #54 from Florian Edelmann --- Created attachment 132296 --> https://bugs.kde.org/attachment.cgi?id=132296=edit New crash information added by DrKonqi ksysguard (5.19.4) using Qt 5.14.2 - What I was doing when the application crashed: Closed the system monitor by clicking on the close icon in the window title. No search query was entered before. -- Backtrace (Reduced): #4 0x7ff501969434 in QWidget::sizePolicy() const (this=this@entry=0x55e40a2efae0) at kernel/qwidget.cpp:10072 #5 0x7ff501a7263b in QLabelPrivate::updateLabel() (this=this@entry=0x55e40a2ef400) at widgets/qlabel.cpp:1132 #6 0x7ff501a735fb in QLabel::setText(QString const&) (this=0x55e40a450d90, text=...) at widgets/qlabel.cpp:326 #7 0x7ff504e23170 in TopLevel::answerReceived(int, QList const&) (this=0x55e40a2a48e0, id=, answerList=...) at ./gui/ksysguard.cpp:466 #8 0x7ff504558b8a in KSGRD::SensorAgent::processAnswer(char const*, int) () at /usr/lib/x86_64-linux-gnu/libksgrd.so.9 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 350140] KSysGuard crashed on close
https://bugs.kde.org/show_bug.cgi?id=350140 Florian Edelmann changed: What|Removed |Added CC||florian-edelm...@online.de -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 417415] New: Systemsettings crashes when clicking close
https://bugs.kde.org/show_bug.cgi?id=417415 Bug ID: 417415 Summary: Systemsettings crashes when clicking close Product: systemsettings Version: 5.17.5 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: florian-edelm...@online.de Target Milestone: --- Application: systemsettings5 (5.17.5) Qt Version: 5.13.2 Frameworks Version: 5.67.0 Operating System: Linux 5.3.0-28-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: - What I was doing when the application crashed: I have opened the Web Shortcuts systemsettings page via search for "Web", then cleared the search field, then deleted "Ecosia-Suchmaschine" and added a custom "Ecosia" shortcut with the correct URL. After leaving the window open for a while (and using the new shortcut), I closed the systemsettings window again. In this moment, the crash reporter appeared. The crash does not seem to be reproducible. -- Backtrace: Application: Systemeinstellungen (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f31cef68800 (LWP 11888))] Thread 6 (Thread 0x7f3198c41700 (LWP 11900)): #0 0x7f31ca4c4bf9 in __GI___poll (fds=0x7f3194003ce0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f31c3b735c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f31c3b736dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f31cae17acb in QEventDispatcherGlib::processEvents (this=0x7f3194000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f31cadb7f9a in QEventLoop::exec (this=this@entry=0x7f3198c40d80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f31cabd33aa in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7f31c8758815 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f31cabd4b52 in QThreadPrivate::start (arg=0x55766af29b10) at thread/qthread_unix.cpp:360 #8 0x7f31c5f326db in start_thread (arg=0x7f3198c41700) at pthread_create.c:463 #9 0x7f31ca4d188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f31a178b700 (LWP 11896)): #0 0x7f31ca4c00b4 in __GI___libc_read (fd=13, buf=0x7f31a178ab70, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f31c3bb82d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f31c3b730b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f31c3b73570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f31c3b736dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f31cae17acb in QEventDispatcherGlib::processEvents (this=0x7f319c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f31cadb7f9a in QEventLoop::exec (this=this@entry=0x7f31a178ad80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7f31cabd33aa in QThread::exec (this=) at thread/qthread.cpp:531 #8 0x7f31c8758815 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7f31cabd4b52 in QThreadPrivate::start (arg=0x55766acb8e70) at thread/qthread_unix.cpp:360 #10 0x7f31c5f326db in start_thread (arg=0x7f31a178b700) at pthread_create.c:463 #11 0x7f31ca4d188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f31ab05f700 (LWP 11892)): #0 0x7f31c5f389f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55766a8f448c) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55766a8f4438, cond=0x55766a8f4460) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55766a8f4460, mutex=0x55766a8f4438) at pthread_cond_wait.c:655 #3 0x7f31b0789ebb in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f31b0789ab7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f31c5f326db in start_thread (arg=0x7f31ab05f700) at pthread_create.c:463 #6 0x7f31ca4d188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f31b3df6700 (LWP 11891)): #0 0x7f31ca4c00b4 in __GI___libc_read (fd=7, buf=0x7f31b3df5b60, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f31c3bb82d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f31c3b730b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f31c3b73570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f31c3b736dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f31cae17acb in QEventDispatcherGlib::processEvents (this=0x7f31ac000b20, flags=...) at
[kdeconnect] [Bug 403551] Crash in kdeinit5 every time a notification from phone is received
https://bugs.kde.org/show_bug.cgi?id=403551 Florian Edelmann changed: What|Removed |Added CC||florian-edelm...@online.de --- Comment #3 from Florian Edelmann --- Created attachment 120127 --> https://bugs.kde.org/attachment.cgi?id=120127=edit Crash report collected by kcrash I can confirm this issue. I've attached my crash report, which looks slightly different than Adrian's. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.15 User Edition KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.0 I've never experienced this bug before with any older software versions. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 395933] Zoom when touchpad is disabled while typing
https://bugs.kde.org/show_bug.cgi?id=395933 --- Comment #1 from Florian Edelmann --- Actually, I just noticed that this problem is only present in certain applications, others behave correctly. Zooming not possible while touchpad is disabled: * Okular * Dolphin Zooming possible while while touchpad is otherwise disabled: * Firefox * Konsole * LibreOffice * KWrite * Visual Studio Code * Chromium -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 395933] Zoom when touchpad is disabled while typing
https://bugs.kde.org/show_bug.cgi?id=395933 Florian Edelmann changed: What|Removed |Added CC||florian-edelm...@online.de -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 395933] New: Zoom when touchpad is disabled while typing
https://bugs.kde.org/show_bug.cgi?id=395933 Bug ID: 395933 Summary: Zoom when touchpad is disabled while typing Product: Touchpad-KCM Version: unspecified Platform: unspecified OS: unspecified Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: daemon Assignee: rajeeshknamb...@gmail.com Reporter: florian-edelm...@online.de Target Milestone: --- The option "disable touchpad while typing" is pretty useful. However, zooming through holding the Control key down and zooming with a two finger swipe is not possible, since the touchpad is disabled as soon as I press the Ctrl key. There should be an option to set the Ctrl key as an exception to the "disable touchpad while typing" thing (or even make it the default). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 384860] New: Baloo crashes after login
https://bugs.kde.org/show_bug.cgi?id=384860 Bug ID: 384860 Summary: Baloo crashes after login Product: frameworks-baloo Version: 5.38.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: pinak.ah...@gmail.com Reporter: florian-edelm...@online.de Target Milestone: --- Application: baloo_file (5.38.0) Qt Version: 5.9.1 Frameworks Version: 5.38.0 Operating System: Linux 4.8.0-46-generic x86_64 Distribution: KDE neon User Edition 5.10 -- Information about the crash: - What I was doing when the application crashed: Just logged into my account and entered my KeePass2 credentials; afterwards, Baloo crashes. I already had that multiple times, but not every time I restart. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8e0c6e18c0 (LWP 1896))] Thread 2 (Thread 0x7f8e01bbb700 (LWP 1902)): #0 0x7f8e079aa490 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f8e079ac998 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8e079ad2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8e079ad49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f8e0b39394b in QEventDispatcherGlib::processEvents (this=0x7f8dfc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f8e0b33c7ca in QEventLoop::exec (this=this@entry=0x7f8e01bbacd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f8e0b165cd4 in QThread::exec (this=) at thread/qthread.cpp:515 #7 0x7f8e0c7f8b75 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7f8e0b16a989 in QThreadPrivate::start (arg=0x7f8e0c86eda0) at thread/qthread_unix.cpp:368 #9 0x7f8e09df46ba in start_thread (arg=0x7f8e01bbb700) at pthread_create.c:333 #10 0x7f8e0a76e3dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f8e0c6e18c0 (LWP 1896)): [KCrash Handler] #6 0x7f8e0a69c428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7f8e0a69e02a in __GI_abort () at abort.c:89 #8 0x7f8e0a6de7ea in __libc_message (do_abort=2, fmt=fmt@entry=0x7f8e0a7f7e98 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 #9 0x7f8e0a6e7dfb in malloc_printerr (ar_ptr=0x7f8e0aa2bb20 , ptr=0x23154b20, str=0x7f8e0a7f4c35 "corrupted size vs. prev_size", action=3) at malloc.c:5006 #10 _int_free (av=0x7f8e0aa2bb20 , p=, have_lock=0) at malloc.c:4014 #11 0x7f8e0a6eb53c in __GI___libc_free (mem=) at malloc.c:2968 #12 0x00421f00 in ?? () #13 0x0041fc16 in ?? () #14 0x7f8e0b36af46 in QtPrivate::QSlotObjectBase::call (a=0x7ffcf5d383e0, r=0x7ffcf5d389a0, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:101 #15 QMetaObject::activate (sender=0x1398740, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3749 #16 0x00426a04 in ?? () #17 0x7f8e0b36af46 in QtPrivate::QSlotObjectBase::call (a=0x7ffcf5d38560, r=0x1398740, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:101 #18 QMetaObject::activate (sender=sender@entry=0x13abe90, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffcf5d38560) at kernel/qobject.cpp:3749 #19 0x7f8e0b36b527 in QMetaObject::activate (sender=sender@entry=0x13abe90, m=m@entry=0x7f8e0b5f5cc0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffcf5d38560) at kernel/qobject.cpp:3628 #20 0x7f8e0b376ec8 in QSocketNotifier::activated (this=this@entry=0x13abe90, _t1=14, _t2=...) at .moc/moc_qsocketnotifier.cpp:137 #21 0x7f8e0b37728b in QSocketNotifier::event (this=0x13abe90, e=) at kernel/qsocketnotifier.cpp:266 #22 0x7f8e0b33e78b in doNotify (event=0x7ffcf5d38620, receiver=0x13abe90) at kernel/qcoreapplication.cpp:1093 #23 QCoreApplication::notify (event=, receiver=, this=) at kernel/qcoreapplication.cpp:1079 #24 QCoreApplication::notifyInternal2 (receiver=0x13abe90, event=event@entry=0x7ffcf5d38620) at kernel/qcoreapplication.cpp:1018 #25 0x7f8e0b3945ad in QCoreApplication::sendEvent (event=0x7ffcf5d38620, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:233 #26 socketNotifierSourceDispatch (source=0x135c6f0) at kernel/qeventdispatcher_glib.cpp:106 #27 0x7f8e079ad197 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x7f8e079ad3f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x7f8e079ad49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #30 0x7f8e0b39392f in QEventDispatcherGlib::processEvents (this=0x135c7c0,
[plasmashell] [Bug 380385] New: Plasma crashes soon after login
https://bugs.kde.org/show_bug.cgi?id=380385 Bug ID: 380385 Summary: Plasma crashes soon after login Product: plasmashell Version: 5.10.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: florian-edelm...@online.de CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.0) Qt Version: 5.7.1 Frameworks Version: 5.34.0 Operating System: Linux 4.8.0-46-generic x86_64 Distribution: KDE neon User Edition 5.10 -- Information about the crash: - What I was doing when the application crashed: Just started my session and waited a few seconds. - Unusual behavior I noticed: Sometimes Plasma comes back, sometimes not. Autostarted applications or applications I started before the crash were still usable, window management also does still work. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1a4d2f08c0 (LWP 1372))] Thread 8 (Thread 0x7f1970541700 (LWP 1747)): #0 0x7f1a47c40b5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f1a433d638c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f1a433d649c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f1a4856075b in QEventDispatcherGlib::processEvents (this=0x7f19680008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f1a4850b0ba in QEventLoop::exec (this=this@entry=0x7f1970540d00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f1a4833af64 in QThread::exec (this=) at thread/qthread.cpp:507 #6 0x7f1a4833fb48 in QThreadPrivate::start (arg=0x2e877b0) at thread/qthread_unix.cpp:368 #7 0x7f1a471e56ba in start_thread (arg=0x7f1970541700) at pthread_create.c:333 #8 0x7f1a47c4c82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f19989c3700 (LWP 1581)): #0 0x7f1a4341aa79 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f1a433d6372 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f1a433d649c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f1a4856075b in QEventDispatcherGlib::processEvents (this=0x7f19940008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f1a4850b0ba in QEventLoop::exec (this=this@entry=0x7f19989c2c90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f1a4833af64 in QThread::exec (this=) at thread/qthread.cpp:507 #6 0x7f1a4b2f2fc6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f1a4833fb48 in QThreadPrivate::start (arg=0xfe4470) at thread/qthread_unix.cpp:368 #8 0x7f1a471e56ba in start_thread (arg=0x7f19989c3700) at pthread_create.c:333 #9 0x7f1a47c4c82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f1a25746700 (LWP 1489)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f1a4cd576f4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f1a4cd57739 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f1a471e56ba in start_thread (arg=0x7f1a25746700) at pthread_create.c:333 #4 0x7f1a47c4c82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f1a27598700 (LWP 1433)): #0 0x7f1a47c40b5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f1a433d638c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f1a433d649c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f1a4856075b in QEventDispatcherGlib::processEvents (this=0x7f1a28c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f1a4850b0ba in QEventLoop::exec (this=this@entry=0x7f1a27597ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f1a4833af64 in QThread::exec (this=this@entry=0x9682c0) at thread/qthread.cpp:507 #6 0x7f1a4a96bbf5 in QQmlThreadPrivate::run (this=0x9682c0) at qml/ftw/qqmlthread.cpp:147 #7 0x7f1a4833fb48 in QThreadPrivate::start (arg=0x9682c0) at thread/qthread_unix.cpp:368 #8 0x7f1a471e56ba in start_thread (arg=0x7f1a27598700) at pthread_create.c:333 #9 0x7f1a47c4c82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f1a35351700 (LWP 1420)): #0 0x7f1a4341aa79 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f1a433d5c3e in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f1a433d6330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3
[plasmashell] [Bug 379259] Add option to activate last window in grouped icon task
https://bugs.kde.org/show_bug.cgi?id=379259 --- Comment #1 from Florian Edelmann <florian-edelm...@online.de> --- Also, tell me if I can help with implementing this in some way (I'd like to!), although I am new to KDE development and would probably need a little introduction. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379259] Add option to activate last window in grouped icon task
https://bugs.kde.org/show_bug.cgi?id=379259 Florian Edelmann <florian-edelm...@online.de> changed: What|Removed |Added CC||florian-edelm...@online.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379259] New: Add option to activate last window in grouped icon task
https://bugs.kde.org/show_bug.cgi?id=379259 Bug ID: 379259 Summary: Add option to activate last window in grouped icon task Product: plasmashell Version: master Platform: unspecified OS: All Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: florian-edelm...@online.de CC: plasma-b...@kde.org Target Milestone: 1.0 When I have multiple windows of the same application opened, they are grouped in the icon-only task manager. A click on the group presents all windows on the screen to select the one to be activated. In Unity (from where I switched from recently), a click activates the most recently used window of this application and only the second click presents the windows on the screen. As not all people will like this workflow, an option to allow this feature would be very useful. I guess it's a relatively small change, but would allow users switching from Unity to keep their habits (and I have seen in a recent OMG Ubuntu comment that I am not alone: http://www.omgubuntu.co.uk/2017/04/best-unity-desktop-features#comment-3274480565). Addition will be likely to be made here, if that helps: https://github.com/KDE/plasma-desktop/blob/master/applets/taskmanager/package/contents/code/tools.js#L100 -- You are receiving this mail because: You are watching all bug changes.
