[plasmashell] [Bug 373180] plasmashell freezes when a panel is resized.
https://bugs.kde.org/show_bug.cgi?id=373180 Benedikt Geißler <bened...@g5r.eu> changed: What|Removed |Added CC||bened...@g5r.eu --- Comment #4 from Benedikt Geißler <bened...@g5r.eu> --- Is this maybe similar to https://bugs.kde.org/show_bug.cgi?id=374393 ? -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 330472] ownCloud News App support
https://bugs.kde.org/show_bug.cgi?id=330472 Benedikt Geißler <bened...@g5r.eu> changed: What|Removed |Added CC||bened...@g5r.eu -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 346175] KDE PIM 15.08 release tracking bug
https://bugs.kde.org/show_bug.cgi?id=346175 Benedikt Geißler <bened...@g5r.eu> changed: What|Removed |Added CC||bened...@g5r.eu --- Comment #1 from Benedikt Geißler <bened...@g5r.eu> --- Isn't this outdated now? ;) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367541] High memory usage when adding PIM Events in Digital Clock Widget
https://bugs.kde.org/show_bug.cgi?id=367541 --- Comment #16 from Benedikt Geißler <bened...@g5r.eu> --- Created attachment 102285 --> https://bugs.kde.org/attachment.cgi?id=102285=edit Output of plasmashell running in valgrind after clicking on the clock applet -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370255] Calendar View crashes in certain months
https://bugs.kde.org/show_bug.cgi?id=370255 Benedikt Geißler <bened...@g5r.eu> changed: What|Removed |Added CC||bened...@g5r.eu --- Comment #5 from Benedikt Geißler <bened...@g5r.eu> --- In https://bugs.kde.org/show_bug.cgi?id=367541 I have posted a backtrace [1] that i had obtained – maybe someone can make use of it. [1] https://bugsfiles.kde.org/attachment.cgi?id=102060 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367541] High memory usage when adding PIM Events in Digital Clock Widget
https://bugs.kde.org/show_bug.cgi?id=367541 --- Comment #14 from Benedikt Geißler <bened...@g5r.eu> --- Created attachment 102060 --> https://bugs.kde.org/attachment.cgi?id=102060=edit Backtrace when I clicked on "next month" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367541] High memory usage when adding PIM Events in Digital Clock Widget
https://bugs.kde.org/show_bug.cgi?id=367541 --- Comment #13 from Benedikt Geißler <bened...@g5r.eu> --- I just noticed that the same things happen when I click on the "next month" button in the digital clock applet. Here is a backtrace: -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 367827] Desktop session crash caused by kdeconnect
https://bugs.kde.org/show_bug.cgi?id=367827 --- Comment #4 from Benedikt Geißler <bened...@g5r.eu> --- Since summer I am using openSUSE Tumbleweed (currently with kdeconnect 1.0.1, 'kdeconnect-cli' says 1.0) now and did not experience this issue during the last weeks, too. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 367827] Desktop session crash caused by kdeconnect
https://bugs.kde.org/show_bug.cgi?id=367827 Benedikt Geißler <bened...@g5r.eu> changed: What|Removed |Added CC||bened...@g5r.eu -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367541] High memory usage when adding PIM Events in Digital Clock Widget
https://bugs.kde.org/show_bug.cgi?id=367541 --- Comment #12 from Benedikt Geißler <bened...@g5r.eu> --- Created attachment 102052 --> https://bugs.kde.org/attachment.cgi?id=102052=edit Very quick rise of memory and CPU usage -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367541] High memory usage when adding PIM Events in Digital Clock Widget
https://bugs.kde.org/show_bug.cgi?id=367541 Benedikt Geißler <bened...@g5r.eu> changed: What|Removed |Added CC||bened...@g5r.eu --- Comment #11 from Benedikt Geißler <bened...@g5r.eu> --- Same here. openSUSE Tumbleweed, Plasma 5.8.2, Frameworks 5.27.0, Qt 5.7.0, Kontact/KOrganizer 5.3.0. I select some calendars in the PIM Events Plugin, click on "apply" and the CPU load as well as the memory usage rise quickly. The whole screen freezes so that I can not even switch to another terminal (Ctrl+Alt+F1) or stop the desktop environment with Ctrl+Alt+Del or Ctrl+Alt+Backspace. After a certain time plasmashell crashes (perhaps because of the OOM killer?) and when I restart plasmashell (e.g. via krunner which still works) the settings in the PIM Events Plugin are reset (i.e. no calendars are selected anymore). In addition to that the font in the PIM Events Plugin tab is kind of blurred in comparison to the other tabs… -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 343061] Yakuake creates task list entry when being opened
https://bugs.kde.org/show_bug.cgi?id=343061 Benedikt Geißler <bened...@g5r.eu> changed: What|Removed |Added CC||bened...@g5r.eu --- Comment #6 from Benedikt Geißler <bened...@g5r.eu> --- I also experience this issue on openSUSE Tumbleweed with Yakuake 3.0.2, Plasma 5.8.2, Frameworks 5.27.0 and Qt 5.7.0. It's the same symptom here as Antonio Orefice has reported. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 368143] Sometimes yakuake still appear in taskmanager
https://bugs.kde.org/show_bug.cgi?id=368143 Benedikt Geißler <bened...@g5r.eu> changed: What|Removed |Added CC||bened...@g5r.eu --- Comment #2 from Benedikt Geißler <bened...@g5r.eu> --- Probably a duplicate of bug https://bugs.kde.org/show_bug.cgi?id=343061, I also experience this issue on openSUSE Tumbleweed with Yakuake 3.0.2, Plasma 5.8.2, Frameworks 5.27.0 and Qt 5.7.0. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 362017] Yakuake icon is sometimes shown in task manager
https://bugs.kde.org/show_bug.cgi?id=362017 Benedikt Geißler <bened...@g5r.eu> changed: What|Removed |Added CC||bened...@g5r.eu --- Comment #5 from Benedikt Geißler <bened...@g5r.eu> --- Probably a duplicate of bug https://bugs.kde.org/show_bug.cgi?id=343061, I also experience this issue on openSUSE Tumbleweed with Yakuake 3.0.2, Plasma 5.8.2, Frameworks 5.27.0 and Qt 5.7.0. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 361725] Yakuake task appears in the task manager some times, when opening Yakuake with hotkey
https://bugs.kde.org/show_bug.cgi?id=361725 Benedikt Geißler <bened...@g5r.eu> changed: What|Removed |Added CC||bened...@g5r.eu --- Comment #3 from Benedikt Geißler <bened...@g5r.eu> --- Probably a duplicate of bug https://bugs.kde.org/show_bug.cgi?id=343061, I also experience this issue on openSUSE Tumbleweed with Yakuake 3.0.2, Plasma 5.8.2, Frameworks 5.27.0 and Qt 5.7.0. -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 359620] no accounts configured Cloud
https://bugs.kde.org/show_bug.cgi?id=359620 Benedikt Geißler <bened...@g5r.eu> changed: What|Removed |Added CC||bened...@g5r.eu --- Comment #1 from Benedikt Geißler <bened...@g5r.eu> --- Do you have installed the package "ktp-accounts-kcm"? -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 357663] Owncloud missing (Fedora), empty list with OpenSuse
https://bugs.kde.org/show_bug.cgi?id=357663 Benedikt Geißler <bened...@g5r.eu> changed: What|Removed |Added CC||bened...@g5r.eu -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 362095] Kdevelop crashed when I autocompleted "global" (python3 plugin)
https://bugs.kde.org/show_bug.cgi?id=362095 --- Comment #1 from Benedikt Geißler <benedi...@openaliasbox.org> --- Created attachment 98519 --> https://bugs.kde.org/attachment.cgi?id=98519=edit the autocompletion popup -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 362095] New: Kdevelop crashed when I autocompleted "global" (python3 plugin)
https://bugs.kde.org/show_bug.cgi?id=362095 Bug ID: 362095 Summary: Kdevelop crashed when I autocompleted "global" (python3 plugin) Product: kdevelop Version: 4.7.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: benedi...@openaliasbox.org Application: kdevelop (4.7.3) KDE Platform Version: 4.14.18 Qt Version: 4.8.6 Operating System: Linux 4.1.15-8-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I did some python3 code with Kdevelop (v4.7.3) and wanted to use a global variable. As I began to type the key word "global" a popup window (screenshot provided below) with a completion proposal appeared. Every* time when I press enter to use this completion kdevelop crashes. Thankfully Kdevelop saves all the data so that I did not notice data loss because of the crash. * now after some minutes this bug seems to have disappeared curiously but Dr Konqui said that the backtrace is useful. Steps to reproduce: - open Kdevelop with the python(3) plugin - edit a python source code file (e.g. by using the python file template) - begin to type "global" and autocomplete it The crash can be reproduced sometimes. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f91aa687800 (LWP 15530))] Thread 20 (Thread 0x7f918df61700 (LWP 15531)): #0 0x7f91a4b0703f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f91a47db86b in () at /usr/lib64/libQtScript.so.4 #2 0x7f91a47db8a9 in () at /usr/lib64/libQtScript.so.4 #3 0x7f91a4b030a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f91a6da5fed in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7f910cddf700 (LWP 15532)): #0 0x7f91a4b073e8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f91a746f084 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQtCore.so.4 #2 0x7f91a5d98c82 in () at /usr/lib64/libkdevplatformlanguage.so.8 #3 0x7f91a746ebbf in () at /usr/lib64/libQtCore.so.4 #4 0x7f91a4b030a4 in start_thread () at /lib64/libpthread.so.0 #5 0x7f91a6da5fed in clone () at /lib64/libc.so.6 Thread 18 (Thread 0x7f9101aba700 (LWP 15533)): #0 0x7f91a111e458 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #1 0x7f91a111ed80 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f91a111ef7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f91a759cfde in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #4 0x7f91a756ed4f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #5 0x7f91a756f045 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7f91a746c4df in QThread::exec() () at /usr/lib64/libQtCore.so.4 #7 0x7f91a746ebbf in () at /usr/lib64/libQtCore.so.4 #8 0x7f91a4b030a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f91a6da5fed in clone () at /lib64/libc.so.6 Thread 17 (Thread 0x7f90f3b14700 (LWP 15540)): #0 0x7f91a6d99c8d in read () at /lib64/libc.so.6 #1 0x7f91a115fb60 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f91a111e999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f91a111edf8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f91a111ef7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f91a759cfde in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7f91a756ed4f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #7 0x7f91a756f045 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #8 0x7f91a746c4df in QThread::exec() () at /usr/lib64/libQtCore.so.4 #9 0x7f91a746ebbf in () at /usr/lib64/libQtCore.so.4 #10 0x7f91a4b030a4 in start_thread () at /lib64/libpthread.so.0 #11 0x7f91a6da5fed in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7f90deb34700 (LWP 15577)): #0 0x7f91a6d99c8d in read () at /lib64/libc.so.6 #1 0x7f91a115fb60 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f91a111e999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f91a111edf8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f91a111ef7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f91a759cfde in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7f91a756ed4f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #7 0x7f91a756f045 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #8 0x7f91a746c4df in
[umbrello] [Bug 331655] auto-generated getters and settersto atributes are private in generated java classes
https://bugs.kde.org/show_bug.cgi?id=331655 Benedikt Geißler <benedi...@openaliasbox.org> changed: What|Removed |Added CC||benedi...@openaliasbox.org --- Comment #2 from Benedikt Geißler <benedi...@openaliasbox.org> --- Unfortunately I do not see any further options for the export of Java code. I'm using Umbrello 2.18.3 from OpenSUSE Leap 42.1 and there setting further options is only possible at the C++ code export. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 359074] New: Crash notification when restarting Akonadi
https://bugs.kde.org/show_bug.cgi?id=359074 Bug ID: 359074 Summary: Crash notification when restarting Akonadi Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: benedi...@openaliasbox.org Application: akonadi_baloo_indexer (4.14) KDE Platform Version: 4.14.16 Qt Version: 4.8.6 Operating System: Linux 4.1.15-8-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: After having restarted Akonadi several times either by typing "akonadictl restart" or by clicking "Restart Server" in akonadiconsole I got this backtrace every time. Maybe it is useful for you, at least drkonqui says that. I'm using openSUSE Leap 42.1 with the akonadi5 package. According to "aconadictl --version" it is v5.1.51 to be exact. The crash can be reproduced every time. -- Backtrace: Application: (akonadi_baloo_indexer), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #6 0x7f87c0681187 in raise () at /lib64/libc.so.6 #7 0x7f87c0682538 in abort () at /lib64/libc.so.6 #8 0x7f87c43ab6d4 in qt_message_output(QtMsgType, char const*) () at /usr/lib64/libQtCore.so.4 #9 0x7f87c2d050ee in () at /usr/lib64/libakonadi-kde.so.4 #10 0x7f87c2d03e72 in () at /usr/lib64/libakonadi-kde.so.4 #11 0x7f87c44cf49e in QObject::event(QEvent*) () at /usr/lib64/libQtCore.so.4 #12 0x7f87c18ab79c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #13 0x7f87c18b1cdd in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #14 0x7f87c25c2e1a in KApplication::notify(QObject*, QEvent*) () at /usr/lib64/libkdeui.so.5 #15 0x7f87c44b718d in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQtCore.so.4 #16 0x7f87c44ba45d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQtCore.so.4 #17 0x7f87c44e47fe in () at /usr/lib64/libQtCore.so.4 #18 0x7f87bff6ec84 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #19 0x7f87bff6eed8 in () at /usr/lib64/libglib-2.0.so.0 #20 0x7f87bff6ef7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #21 0x7f87c44e3fbe in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #22 0x7f87c19486a6 in () at /usr/lib64/libQtGui.so.4 #23 0x7f87c44b5d4f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #24 0x7f87c44b6045 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #25 0x7f87c44bb499 in QCoreApplication::exec() () at /usr/lib64/libQtCore.so.4 #26 0x7f87c2d016f3 in Akonadi::AgentBase::init(Akonadi::AgentBase*) () at /usr/lib64/libakonadi-kde.so.4 #27 0x00410993 in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 358607] New: KMail crashed after the notebook was in supend-to-RAM
https://bugs.kde.org/show_bug.cgi?id=358607 Bug ID: 358607 Summary: KMail crashed after the notebook was in supend-to-RAM Product: kmail2 Version: 5.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: benedi...@openaliasbox.org Application: kmail (5.1) Qt Version: 5.5.1 Operating System: Linux 4.1.13-5-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Unfortunately I do not know exactly what I have done so that KMail crashed, but DrKonqui said that the backtrace is useful. I just had a mail writing window opened and closed the lid of the notebook sometimes to let it sleep in suspend-to-RAM. You may close this issue if you cannot make any use of the backtrace because I did not lose any data nor would I have noticed it if DrKonqui wouldn't have come up with the backtrace. ;-) -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd1b82d4800 (LWP 5814))] Thread 22 (Thread 0x7fd193a6e700 (LWP 5817)): #0 0x7fd1b5306c1d in poll () at /lib64/libc.so.6 #1 0x7fd1a87e0422 in () at /usr/lib64/libxcb.so.1 #2 0x7fd1a87e200f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7fd1957993c9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fd1b5c1532f in () at /usr/lib64/libQt5Core.so.5 #5 0x7fd1abab70a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7fd1b530f04d in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7fd191985700 (LWP 5829)): #0 0x7fd1b531b61f in __libc_enable_asynccancel () at /lib64/libc.so.6 #1 0x7fd1b5306c12 in poll () at /lib64/libc.so.6 #2 0x7fd1ab59ae64 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fd1ab59af7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7fd1b5e47d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fd1b5deed53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fd1b5c1061a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7fd1b5c1532f in () at /usr/lib64/libQt5Core.so.5 #8 0x7fd1abab70a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fd1b530f04d in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7fd190ae3700 (LWP 5835)): #0 0x7fd1ab5dccf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fd1ab59a8fc in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #2 0x7fd1ab59adf8 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fd1ab59af7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7fd1b5e47d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fd1b5deed53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fd1b5c1061a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7fd1b5c1532f in () at /usr/lib64/libQt5Core.so.5 #8 0x7fd1abab70a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fd1b530f04d in clone () at /lib64/libc.so.6 Thread 19 (Thread 0x7fd18bfff700 (LWP 5836)): #0 0x7fd1ab5dccf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fd1ab59aa46 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #2 0x7fd1ab59aed8 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fd1ab59af7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7fd1b5e47d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fd1b5deed53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fd1b5c1061a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7fd1b5c1532f in () at /usr/lib64/libQt5Core.so.5 #8 0x7fd1abab70a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fd1b530f04d in clone () at /lib64/libc.so.6 Thread 18 (Thread 0x7fd17f6cb700 (LWP 5893)): #0 0x7fd1ababb05f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fd1a6637733 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fd1a6637759 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fd1abab70a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fd1b530f04d in clone () at /lib64/libc.so.6 Thread 17 (Thread 0x7fd13698a700 (LWP 6061)): #0 0x7fd1ababb05f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fd1a634375d in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fd1a031 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fd1abab70a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fd1b530f04d in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7fd136189700 (LWP 6062)): #0 0x7fd1ababb05f in
[kdeconnect] [Bug 357885] QXcbClipboard: SelectionRequest too old
https://bugs.kde.org/show_bug.cgi?id=357885 Benedikt Geißler <benedi...@openaliasbox.org> changed: What|Removed |Added CC||benedi...@openaliasbox.org --- Comment #1 from Benedikt Geißler <benedi...@openaliasbox.org> --- Same here with openSUSE Leap. I have a desktop PC, notebook and smartphone connected with each other via kdeconnect. Besides the journal getting flooded by "QXcbClipboard: SelectionRequest too old" I notice a significant load on the notebook so that the fan begins to spin quite fast. Furthermore the panel with the KMenu, task bar and system tray gets unresponsive – I can neither open new applications nor switch between them when this error occurs. My "workaround" for the time being is to terminate all kdeconect processes in htop and restart kwin with "kwin_x11 --replace" (don't know if the latter thing does help with this problem at all). Then the spam in the journal stops and after a while the panel gets responsive again. "Fun fact": every time when this problem occured it was between 22:00 and 23:00 CET and both my notebook and desktop PC were running at the same time. -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 353245] Support of OMEMO in Kopete
https://bugs.kde.org/show_bug.cgi?id=353245 Benedikt Geißler <benedi...@openaliasbox.org> changed: What|Removed |Added CC||benedi...@openaliasbox.org -- You are receiving this mail because: You are watching all bug changes.
