[plasmashell] [Bug 344879] memory leak in plasmashell - huge ram usage
https://bugs.kde.org/show_bug.cgi?id=344879 René Krell changed: What|Removed |Added CC|renda.kr...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 378228] KMail hangs when trying to open a MS Outlook calendar (invitation) message
https://bugs.kde.org/show_bug.cgi?id=378228 René Krell changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #12 from René Krell --- (In reply to Justin Zobel from comment #11) > Thank you for reporting this issue in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the issue with a recent software version? > > If you can reproduce the issue, please change the status to "REPORTED" when > replying. Thank you! Sorry, I can't tell you any longer, haven't used KDE for a very long time and don't have an instance for testing the fix the next time. The issue has been probably fixed by the commit mentioned above. You may close this if you want. -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 373344] Clear contact history does not clear anything instantly
https://bugs.kde.org/show_bug.cgi?id=373344 René Krell changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from René Krell --- Sorry, I can't tell you any longer, haven't used Telepathy for a very long time and don't have an instance for testing it the next time. You may close this if you want. -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 373343] Open "Previous Conversations" from chat window doesn't preselected the dedicated user in log viewer
https://bugs.kde.org/show_bug.cgi?id=373343 René Krell changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from René Krell --- Sorry, I can't tell you any longer, haven't used Telepathy for a very long time and don't have an instance for testing it the next time. You may close this if you want. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 268913] Load a default session that can be saved on application closure, so session saving is automatic like a web browser
https://bugs.kde.org/show_bug.cgi?id=268913 René Krell changed: What|Removed |Added CC|renda.kr...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373368] Spurious XCB Events causing high CPU
https://bugs.kde.org/show_bug.cgi?id=373368 --- Comment #20 from René Krell --- (In reply to Nate Graham from comment #19) > Is anyone still seeing this issue in a recent Plasma version? I haven't used KDE / KMail since 07/2017, I'm not able to update the state of the issue in current versions. From my point of view it is not interesting any longer. Maybe anybody else around? Otherwise this can be closed. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 368434] Kontact crash when filing through eMail
https://bugs.kde.org/show_bug.cgi?id=368434 René Krell changed: What|Removed |Added CC|renda.kr...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 165732] reproducible crash on blauarbeit.de (QMetaObject::activate)
https://bugs.kde.org/show_bug.cgi?id=165732 René Krell changed: What|Removed |Added CC|renda.kr...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381981] New: Plasma crash on startup
https://bugs.kde.org/show_bug.cgi?id=381981 Bug ID: 381981 Summary: Plasma crash on startup Product: plasmashell Version: 5.10.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: renda.kr...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.3) Qt Version: 5.9.0 Frameworks Version: 5.34.0 Operating System: Linux 4.11.8-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: Plasma crashes each time on start without any interaction. Using native nvidia drivers 384.47. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1e206758c0 (LWP 3354))] Thread 12 (Thread 0x7f1d33bfe700 (LWP 4081)): #0 0x7f1e1956c5ed in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1e1a39fa5b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f1e1e105748 in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f1e1e105b7a in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f1e1a39e73e in () at /usr/lib64/libQt5Core.so.5 #5 0x7f1e195664e7 in start_thread () at /lib64/libpthread.so.0 #6 0x7f1e19caca2f in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7f1d40d53700 (LWP 4080)): #0 0x7f1e1956c5ed in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1e1a39fa5b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f1e1e105748 in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f1e1e105b7a in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f1e1a39e73e in () at /usr/lib64/libQt5Core.so.5 #5 0x7f1e195664e7 in start_thread () at /lib64/libpthread.so.0 #6 0x7f1e19caca2f in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7f1d41dc8700 (LWP 4079)): [KCrash Handler] #6 0x7f1e19bf3a60 in raise () at /lib64/libc.so.6 #7 0x7f1e19bf50c6 in abort () at /lib64/libc.so.6 #8 0x7f1e19c328f1 in __libc_message () at /lib64/libc.so.6 #9 0x7f1e19c38f3b in malloc_printerr () at /lib64/libc.so.6 #10 0x7f1e19c3a671 in _int_free () at /lib64/libc.so.6 #11 0x7f1e1b11415f in () at /usr/lib64/libQt5Gui.so.5 #12 0x7f1e1b11319c in () at /usr/lib64/libQt5Gui.so.5 #13 0x7f1e1b0dfc95 in () at /usr/lib64/libQt5Gui.so.5 #14 0x7f1e1b0e05d8 in QOpenGLShaderProgram::link() () at /usr/lib64/libQt5Gui.so.5 #15 0x7f1e1e0f8d90 in QSGDefaultRenderContext::compileShader(QSGMaterialShader*, QSGMaterial*, char const*, char const*) () at /usr/lib64/libQt5Quick.so.5 #16 0x7f1e1e0c70f6 in () at /usr/lib64/libQt5Quick.so.5 #17 0x7f1e1e0c7a2a in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () at /usr/lib64/libQt5Quick.so.5 #18 0x7f1e1e0c8e15 in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib64/libQt5Quick.so.5 #19 0x7f1e1e0ce2bc in QSGBatchRenderer::Renderer::render() () at /usr/lib64/libQt5Quick.so.5 #20 0x7f1e1e0bf2ea in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib64/libQt5Quick.so.5 #21 0x7f1e1e0bf77b in QSGRenderer::renderScene(unsigned int) () at /usr/lib64/libQt5Quick.so.5 #22 0x7f1e1e0f81e0 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at /usr/lib64/libQt5Quick.so.5 #23 0x7f1e1e150f58 in QQuickWindowPrivate::renderSceneGraph(QSize const&) () at /usr/lib64/libQt5Quick.so.5 #24 0x7f1e1e100e19 in () at /usr/lib64/libQt5Quick.so.5 #25 0x7f1e1e105b38 in () at /usr/lib64/libQt5Quick.so.5 #26 0x7f1e1a39e73e in () at /usr/lib64/libQt5Core.so.5 #27 0x7f1e195664e7 in start_thread () at /lib64/libpthread.so.0 #28 0x7f1e19caca2f in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f1d4a5fc700 (LWP 4065)): #0 0x7f1e14ad120d in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #1 0x7f1e14ad1c3b in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f1e14ad1e1c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f1e1a5be75b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f1e1a567d0a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f1e1a39a05a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f1d4ce93f37 in KCupsConnection::run() () at /usr/lib64/libkcupslib.so #7 0x7f1e1a39e73e in () at /usr/lib64/libQt5Core.so.5 #8 0x7f1e195664e7 in start_thread () at /lib64/libpthread.so.0 #9 0x7f1e19caca2f in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f1d65392700 (LWP 3885)): #0 0x7f1e1956c5ed in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1
[kmail2] [Bug 378228] KMail hangs when trying to open a MS Outlook calendar (invitation) message
https://bugs.kde.org/show_bug.cgi?id=378228 --- Comment #10 from René Krell <renda.kr...@gmail.com> --- (In reply to Laurent Montel from comment #9) > akonadi-calendar: > commit 12711617070bae66679d107e270c7fb5a676c154 Aha, ok, finally found it: https://github.com/KDE/akonadi-calendar/commit/12711617070bae66679d107e270c7fb5a676c154 Thank you. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 378228] KMail hangs when trying to open a MS Outlook calendar (invitation) message
https://bugs.kde.org/show_bug.cgi?id=378228 --- Comment #8 from René Krell <renda.kr...@gmail.com> --- (In reply to Laurent Montel from comment #7) > Thanks I tested it. > David fixed a bug in 5.5.0 > We can open this eml file and see invitation without problem now. > So I think that in new version it will work. > > I will delete your testcase Great, thank you. Do you have any reference to the fix (some Git commit or another issue)? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 378228] KMail hangs when trying to open a MS Outlook calendar (invitation) message
https://bugs.kde.org/show_bug.cgi?id=378228 --- Comment #5 from René Krell <renda.kr...@gmail.com> --- Just for the record, as a hint: Thunderbird 45.8.0 does show this kind of messages (TNEF) without any trouble - in header there appears: "This message contains an invitation to an event." with the Decline | Tentative | Accept buttons. Which probably means this seems not to be an authorization or other integration problem. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 378228] KMail hangs when trying to open a MS Outlook calendar (invitation) message
https://bugs.kde.org/show_bug.cgi?id=378228 --- Comment #4 from René Krell <renda.kr...@gmail.com> --- It also depends what do you expect as testcase. Is it enough to forward you a mail causing this problem, and how (inline, as attachment). Or should I save this mail (which format *.eml, *.txt)? What is the best way for you? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 378228] KMail hangs when trying to open a MS Outlook calendar (invitation) message
https://bugs.kde.org/show_bug.cgi?id=378228 --- Comment #3 from René Krell <renda.kr...@gmail.com> --- I cannot attach these mails publically, because they are confidential. But I might choose one to forward to your mail address if you promise not to make them public, ok? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 378228] KMail hangs when trying to open a MS Outlook calendar (invitation) message
https://bugs.kde.org/show_bug.cgi?id=378228 --- Comment #1 from René Krell <renda.kr...@gmail.com> --- Special headers of the affected message look like this: --- ... X-MS-Exchange-Organization-AuthAs: Internal X-MS-Exchange-Organization-AuthMechanism: 04 X-MS-Exchange-Organization-AuthSource: mail.a.company.com X-MS-Has-Attach: X-MS-Exchange-Organization-SCL: -1 X-MS-TNEF-Correlator: acceptlanguage: de-DE Content-Type: multipart/alternative; boundary="_002_F263790328C47E4C80994544E26F19C2017786B9AB73mail_" MIME-Version: 1.0 --_002_F263790328C47E4C80994544E26F19C2017786B9AB73mail_ Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: base64 ... --- -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 378228] New: KMail hangs when trying to open a MS Outlook calendar (invitation) message
https://bugs.kde.org/show_bug.cgi?id=378228 Bug ID: 378228 Summary: KMail hangs when trying to open a MS Outlook calendar (invitation) message Product: kmail2 Version: 5.4.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list Assignee: kdepim-b...@kde.org Reporter: renda.kr...@gmail.com Target Milestone: --- Linkage info: - KDE Frameworks 5.31.0 - Qt 5.7.1 (built against 5.7.1) If I receive a calendar message (invitation) from MS Outlook via KMail/Akonadi the message window starts showing "retrieving folder contents" and hangs up infinitely. After that, even on changing to other messages in the message list the message window does not recover from that. To recover, I have to restart KMail and Akonadi (akonadictl restart), but if the first message to show after restarting KDE is the same calendar message again, the whole problem reappears of course. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373368] Spurious XCB Events causing high CPU
https://bugs.kde.org/show_bug.cgi?id=373368 --- Comment #11 from René Krell <renda.kr...@gmail.com> --- (In reply to bjoernv from comment #9) > I see this bug every day on the same Tumbleweed version You're right, right now I got the problem again with 5.8.5, just after "heavily using" the system (many Java processes and IDE in use). So this is definitely not fixed in 5.8.5. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373368] Plasmashell falls into high CPU load after a while, desktop and kmail remains almost unresponsive (initial kmail issue)
https://bugs.kde.org/show_bug.cgi?id=373368 --- Comment #8 from René Krell <renda.kr...@gmail.com> --- (In reply to David Edmundson from comment #7) > Rene, had a look > > Log shows we're receiving a ridiculous number of X events. 674603 in fact. > Assuming "several minutes" == 3 minutes, that's 3743 events per second, > which is a sign that something is going wrong. > > This matches something seen in one of the other generic high CPU threads. Edmund, thanks. I saw just this issue: Bug 356479. Is there the same cause? Most times this happened during sleep/hibernation mode, but not always. I'm now at 5.8.5 (OpenSUSE Tumbleweed RPMs), and the problem hasn't appeared a long time here since updating. Maybe just accidentally, or has it been already fixed? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374176] Plasmashell hogs CPU while network connection is setting up
https://bugs.kde.org/show_bug.cgi?id=374176 René Krell <renda.kr...@gmail.com> changed: What|Removed |Added CC||renda.kr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373368] Plasmashell falls into high CPU load after a while, desktop and kmail remains almost unresponsive (initial kmail issue)
https://bugs.kde.org/show_bug.cgi?id=373368 René Krell <renda.kr...@gmail.com> changed: What|Removed |Added Severity|normal |major -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373368] Plasmashell falls into high CPU load after a while, desktop and kmail remains almost unresponsive (initial kmail issue)
https://bugs.kde.org/show_bug.cgi?id=373368 René Krell <renda.kr...@gmail.com> changed: What|Removed |Added Summary|Opening new message very|Plasmashell falls into high |slow and freezes KMail for |CPU load after a while, |several second each |desktop and kmail remains ||almost unresponsive ||(initial kmail issue) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373368] Opening new message very slow and freezes KMail for several second each
https://bugs.kde.org/show_bug.cgi?id=373368 René Krell <renda.kr...@gmail.com> changed: What|Removed |Added Product|kmail2 |plasmashell Component|message list|general Version|Git (master)|5.8.4 CC||bhus...@gmail.com, ||plasma-b...@kde.org Target Milestone|--- |1.0 --- Comment #6 from René Krell <renda.kr...@gmail.com> --- This seems to become a plasmashell issue. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 373368] Opening new message very slow and freezes KMail for several second each
https://bugs.kde.org/show_bug.cgi?id=373368 --- Comment #5 from René Krell <renda.kr...@gmail.com> --- Created attachment 102662 --> https://bugs.kde.org/attachment.cgi?id=102662=edit Compressed output of valgrind --tool=callgrind --instr-atstart=no plasmashell for a few minutes after starting callgrind_control -i o Added the compressed output of 'valgrind --tool=callgrind --instr-atstart=no plasmashell' for a few minutes after starting 'callgrind_control -i o'. I started callgrind_control when kmail started to be unresponsive, including the rest of the plasmashell. I'm not able to interpret the output shown in kcachegrind. Can someone look at this, please? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 373368] Opening new message very slow and freezes KMail for several second each
https://bugs.kde.org/show_bug.cgi?id=373368 --- Comment #4 from René Krell <renda.kr...@gmail.com> --- I'm currently keeping plasmashell running in valgrind according to this comment: https://forum.kde.org/viewtopic.php?f=289=121533=7ab1403c4fedc79c23d4cadac1e09fd3=45#p343228 and waiting for plasmashell to fall into the high CPU load again, which is apparently the reason for the unresponsiveness of KMail. As soon as this will be the case I try to send some kcachegrind dump from it to get this issue to the right direction. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 373368] Opening new message very slow and freezes KMail for several second each
https://bugs.kde.org/show_bug.cgi?id=373368 --- Comment #3 from René Krell <renda.kr...@gmail.com> --- Sorry, that was to fast. Baloo isn't the cause. I run into this problem again with deactivated File Search, but now I have plasmashell at high load: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 3392 rkrell20 0 0,255t 471020 187628 S 115,3 1,456 33:34.98 plasmashell There is no comparable process in this situation with such a high CPU load. Now even restarting KMail doesn't help. Navigating between messages is almost unresponsive in both accounts, IMAP and Local Folders. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 373368] Opening new message very slow and freezes KMail for several second each
https://bugs.kde.org/show_bug.cgi?id=373368 --- Comment #2 from René Krell <renda.kr...@gmail.com> --- The only process I saw with a high load during reproducing the problem was the baloo_file_extractor. After that I switched off Search -> File Search -> [ ] Enable File Search. Deactivating the Baloo File Extractor might be way how to avoid the issue reported here, I'll watch this several days. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 373368] Opening new message very slow and freezes KMail for several second each
https://bugs.kde.org/show_bug.cgi?id=373368 --- Comment #1 from René Krell <renda.kr...@gmail.com> --- Important addition: This problem doesn't happen right after system start, but some time after using KMail (after several seconds, minutes or even hours). At the moment I can't see it, but when it happens the notebook's fan is running on higher speed, probably due to a high CPU load. As soon as the problem occurs, KMail doesn't recover from it, so the high load remains instant until the next system restart. I nobody can reproduce this, please give me some hints what outputs to generate and provide, and what to do else to help analyzing. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 373368] New: Opening new message very slow and freezes KMail for several second each
https://bugs.kde.org/show_bug.cgi?id=373368 Bug ID: 373368 Summary: Opening new message very slow and freezes KMail for several second each Product: kmail2 Version: Git (master) Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list Assignee: kdepim-b...@kde.org Reporter: renda.kr...@gmail.com Target Milestone: --- KMail 5.3.3 (QtWebEngine), OpenSUSE Tumbleweed, Linux (x86_64) release 4.8.12-1-default: Kmail is very slow when navigating between messages in the message list. I have two accounts - an IMAP account (Activated Download all messages for offline use) and a Local Folders account. To be sure this is no migration problem from KDE 4 I stopped KMail and Akonadi and removed the following folders and files: ~/.local/share/akonadi ~/.config/akonadi ~/.kde4/share/config/akonadi* After that I restarted Akonadi and resynchronized the account again. Thus, this should be a clean state. When having synchronized all messages after the above cleanup action the problem reoccurs again: I click on several messages in the message list, marking a new message in the message list freezes KMail for several seconds before the new message is shown in the message window. This behavior happened from my point of view since the QtWebEngine has been introduced as message viewer. Because I've read about multi-threading problems of Nouveau, I tried also the native NVidia driver, no change so far. -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 373344] New: Clear contact history does not clear anything instantly
https://bugs.kde.org/show_bug.cgi?id=373344 Bug ID: 373344 Summary: Clear contact history does not clear anything instantly Product: telepathy Version: git-latest Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: log-viewer Assignee: kde-telepathy-b...@kde.org Reporter: renda.kr...@gmail.com Target Milestone: Future In log viewer, if I select a contact history and using the contect menu on the contact name, choosing Clear contact history I get the following: - A warning message box appears: Are you sure ->Choose button Delete - Only the contact disappears in the left upper part of the log viewer, but the messages (dates and contents) are still shown below. - If restarting the log viewer also the contact name itself is available again, along with all the contact history. At the end, nothing is deleted at all. I f deleting, I'd expect the contact and its history disappera instantly from log viewer unless there is no new message in a chat from that contact. -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 373343] New: Open "Previous Conversations" from chat window doesn't preselected the dedicated user in log viewer
https://bugs.kde.org/show_bug.cgi?id=373343 Bug ID: 373343 Summary: Open "Previous Conversations" from chat window doesn't preselected the dedicated user in log viewer Product: telepathy Version: git-latest Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: log-viewer Assignee: kde-telepathy-b...@kde.org Reporter: renda.kr...@gmail.com Target Milestone: Future When chatting with a contact, opening Conversation -> Previous Conversations does never pre-select the dedicated contact in the log viewer. I must always filter or find the contact from the chat window manually in the log viewer instead, after the log viewer opened from that menu. I'd expect there are immediately displayed only conversations from the contact I'm in chat with. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 369514] KMail crash on starting (nouveau-related)
https://bugs.kde.org/show_bug.cgi?id=369514 --- Comment #2 from René Krell <renda.kr...@gmail.com> --- (In reply to BingMyBong from comment #1) > Maybe this should be logged against qtwebengine and nouveau as well Did report it to nouveau: https://bugs.freedesktop.org/show_bug.cgi?id=98039 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 369514] New: KMail crash on starting (nouveau-related)
https://bugs.kde.org/show_bug.cgi?id=369514 Bug ID: 369514 Summary: KMail crash on starting (nouveau-related) 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: renda.kr...@gmail.com Application: kmail (5.3.0 (QtWebEngine)) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.7.4-2-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I started KMail. Using OpenSUSE Tumbleweed 20160927 and the Nouveau driver (kernel 4.7.4, xf86-video-nouveau-1.0.13), KMail crashes everytime I try to start it. The KDE Plasma desktop and Chromium run without any flaw. 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 0x7ff6d0b6a940 (LWP 12021))] Thread 42 (Thread 0x7ff52effb700 (LWP 12105)): #0 0x7ff6c37af10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff6b9c95d49 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7ff6b9c96460 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7ff6b9c96630 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7ff6b9c9323d in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7ff6c37a9454 in start_thread () at /lib64/libpthread.so.0 #6 0x7ff6cd91f3ff in clone () at /lib64/libc.so.6 Thread 41 (Thread 0x7ff52f7fc700 (LWP 12103)): #0 0x7ff6c37af10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff6be711353 in JSC::GCThread::gcThreadMain() () at heap/GCThread.cpp:81 #2 0x7ff6be711353 in JSC::GCThread::gcThreadMain() () at heap/GCThread.cpp:99 #3 0x7ff6bea47971 in wtfThreadEntryPoint() () at wtf/ThreadingPthreads.cpp:195 #4 0x7ff6c37a9454 in start_thread () at /lib64/libpthread.so.0 #5 0x7ff6cd91f3ff in clone () at /lib64/libc.so.6 Thread 40 (Thread 0x7ff52fffd700 (LWP 12102)): #0 0x7ff6c37af10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff6be711353 in JSC::GCThread::gcThreadMain() () at heap/GCThread.cpp:81 #2 0x7ff6be711353 in JSC::GCThread::gcThreadMain() () at heap/GCThread.cpp:99 #3 0x7ff6bea47971 in wtfThreadEntryPoint() () at wtf/ThreadingPthreads.cpp:195 #4 0x7ff6c37a9454 in start_thread () at /lib64/libpthread.so.0 #5 0x7ff6cd91f3ff in clone () at /lib64/libc.so.6 Thread 39 (Thread 0x7ff5f4fca700 (LWP 12101)): #0 0x7ff6c37af10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff6be711353 in JSC::GCThread::gcThreadMain() () at heap/GCThread.cpp:81 #2 0x7ff6be711353 in JSC::GCThread::gcThreadMain() () at heap/GCThread.cpp:99 #3 0x7ff6bea47971 in wtfThreadEntryPoint() () at wtf/ThreadingPthreads.cpp:195 #4 0x7ff6c37a9454 in start_thread () at /lib64/libpthread.so.0 #5 0x7ff6cd91f3ff in clone () at /lib64/libc.so.6 Thread 38 (Thread 0x7ff5f57cb700 (LWP 12100)): #0 0x7ff6c37af10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff6be711353 in JSC::GCThread::gcThreadMain() () at heap/GCThread.cpp:81 #2 0x7ff6be711353 in JSC::GCThread::gcThreadMain() () at heap/GCThread.cpp:99 #3 0x7ff6bea47971 in wtfThreadEntryPoint() () at wtf/ThreadingPthreads.cpp:195 #4 0x7ff6c37a9454 in start_thread () at /lib64/libpthread.so.0 #5 0x7ff6cd91f3ff in clone () at /lib64/libc.so.6 Thread 37 (Thread 0x7ff5f5fcc700 (LWP 12099)): #0 0x7ff6c37af10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff6be711353 in JSC::GCThread::gcThreadMain() () at heap/GCThread.cpp:81 #2 0x7ff6be711353 in JSC::GCThread::gcThreadMain() () at heap/GCThread.cpp:99 #3 0x7ff6bea47971 in wtfThreadEntryPoint() () at wtf/ThreadingPthreads.cpp:195 #4 0x7ff6c37a9454 in start_thread () at /lib64/libpthread.so.0 #5 0x7ff6cd91f3ff in clone () at /lib64/libc.so.6 Thread 36 (Thread 0x7ff5f67cd700 (LWP 12098)): #0 0x7ff6c37af10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff6be711353 in JSC::GCThread::gcThreadMain() () at heap/GCThread.cpp:81 #2 0x7ff6be711353 in JSC::GCThread::gcThreadMain() () at heap/GCThread.cpp:99 #3 0x7ff6bea47971 in wtfThreadEntryPoint() () at wtf/ThreadingPthreads.cpp:195 #4 0x7ff6c37a9454 in start_thread () at /lib64/libpthread.so.0 #5 0x7ff6cd91f3ff in clone () at /lib64/libc.so.6 Thread 35 (Thread 0x7ff5f6fce700 (LWP 12097)): #0 0x7ff6c37af10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff6be710201 in JSC::BlockAllocator::blockFreeingThreadMain() () at heap/BlockAllocator.cpp:139 #2
[user-manager] [Bug 362845] sddm shows empty space instead of several "0" digits for system time in login prompt
https://bugs.kde.org/show_bug.cgi?id=362845 --- Comment #3 from René Krell <renda.kr...@gmail.com> --- Compiled and running in Qt 5.5.1 when reporting this. -- You are receiving this mail because: You are watching all bug changes.
[user-manager] [Bug 362845] sddm shows empty space instead of several "0" digits for system time in login prompt
https://bugs.kde.org/show_bug.cgi?id=362845 --- Comment #2 from René Krell <renda.kr...@gmail.com> --- This has been present already in previous versions. Using the nvidia native graphics driver, if this is important here. -- You are receiving this mail because: You are watching all bug changes.
[user-manager] [Bug 362845] sddm shows empty space instead of several "0" digits for system time in login prompt
https://bugs.kde.org/show_bug.cgi?id=362845 --- Comment #1 from René Krell <renda.kr...@gmail.com> --- Created attachment 98854 --> https://bugs.kde.org/attachment.cgi?id=98854=edit Screenshot of SDDM logon prompt -- You are receiving this mail because: You are watching all bug changes.
[user-manager] [Bug 362845] New: sddm shows empty space instead of several "0" digits for system time in login prompt
https://bugs.kde.org/show_bug.cgi?id=362845 Bug ID: 362845 Summary: sddm shows empty space instead of several "0" digits for system time in login prompt Product: user-manager Version: 5.6.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcontrol module Assignee: afies...@kde.org Reporter: renda.kr...@gmail.com Only after reboot, sddm often shows empty space instead of the digt of the system time. This happened for digits which have been set to "0", they appeared whe never switching to "1". After logout it seems to be ok from what I have seen. Reproducible: Sometimes Steps to Reproduce: 1. Reboot computer and wait for sddm login prompt Actual Results: Empty "0" digits in system time display (see screenshot) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357895] Regression: KDE Plasma with KF 5.18 crash, if mouse repeatedly hovers over panel
https://bugs.kde.org/show_bug.cgi?id=357895 --- Comment #28 from René Krell <renda.kr...@gmail.com> --- Just for the record: Workaround for me to get rid of these crashes: Right click on Task Manager: Task Manager Settings -> Tab "General" -> Uncheck "Show tooltips" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357895] Regression: KDE Plasma with KF 5.18 crash, if mouse repeatedly hovers over panel
https://bugs.kde.org/show_bug.cgi?id=357895 René Krell <renda.kr...@gmail.com> changed: What|Removed |Added CC||renda.kr...@gmail.com --- Comment #25 from René Krell <renda.kr...@gmail.com> --- I can confirm this report, the problem started after updating from Plasma 5.5.2 to 5.5.3 and KF from 5.17 to 5.18, OpenSUSE Tumbleweed 20160120: Thread 1 (Thread 0x7f00cef988c0 (LWP 13967)): [KCrash Handler] #6 0x7f00c8566cc4 in __memmove_avx_unaligned () from /lib64/libc.so.6 #7 0x7f00ae1864fd in ?? () from /usr/lib64/dri/swrast_dri.so #8 0x7f00ae184f95 in ?? () from /usr/lib64/dri/swrast_dri.so #9 0x7f00b40d5c9f in Plasma::WindowThumbnail::bindGLXTexture (this=this@entry=0x45a3220) at /usr/src/debug/plasma-framework-5.18.0/src/declarativeimports/core/windowthumbnail.cpp:447 #10 0x7f00b40d6e31 in Plasma::WindowThumbnail::windowToTextureGLX (this=this@entry=0x45a3220, textureNode=textureNode@entry=0x45279d0) at /usr/src/debug/plasma-framework-5.18.0/src/declarativeimports/core/windowthumbnail.cpp:282 #11 0x7f00b40d7783 in Plasma::WindowThumbnail::windowToTexture (this=0x45a3220, textureNode=0x45279d0) at /usr/src/debug/plasma-framework-5.18.0/src/declarativeimports/core/windowthumbnail.cpp:394 #12 0x7f00b40d7c74 in Plasma::WindowThumbnail::updatePaintNode (this=0x45a3220, oldNode=, updatePaintNodeData=) at /usr/src/debug/plasma-framework-5.18.0/src/declarativeimports/core/windowthumbnail.cpp:199 #13 0x7f00ccaf9588 in QQuickWindowPrivate::updateDirtyNode (this=this@entry=0x3928630, item=item@entry=0x45a3220) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/quick/items/qquickwindow.cpp:2984 #14 0x7f00ccaf9df8 in QQuickWindowPrivate::updateDirtyNodes (this=this@entry=0x3928630) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/quick/items/qquickwindow.cpp:2722 #15 0x7f00ccaf9f40 in QQuickWindowPrivate::syncSceneGraph (this=this@entry=0x3928630) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/quick/items/qquickwindow.cpp:341 #16 0x7f00ccacaba4 in QSGGuiThreadRenderLoop::renderWindow (this=this@entry=0x2630300, window=0x3927a40) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/quick/scenegraph/qsgrenderloop.cpp:372 #17 0x7f00ccacc44e in QSGGuiThreadRenderLoop::exposureChanged (this=0x2630300, window=0x3927a40) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/quick/scenegraph/qsgrenderloop.cpp:422 #18 0x7f00c932dc3b in QWindow::event (this=this@entry=0x3927a40, ev=ev@entry=0x7ffde64f1ba0) at kernel/qwindow.cpp:2054 #19 0x7f00ccb03621 in QQuickWindow::event (this=this@entry=0x3927a40, e=e@entry=0x7ffde64f1ba0) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/quick/items/qquickwindow.cpp:1413 #20 0x7f00ce9b42f3 in PlasmaQuick::Dialog::event (this=this@entry=0x3927a40, event=event@entry=0x7ffde64f1ba0) at /usr/src/debug/plasma-framework-5.18.0/src/plasmaquick/dialog.cpp:1168 #21 0x7f00b40d0055 in ToolTipDialog::event (this=0x3927a40, e=0x7ffde64f1ba0) at /usr/src/debug/plasma-framework-5.18.0/src/declarativeimports/core/tooltipdialog.cpp:120 #22 0x7f00ca1588cc in QApplicationPrivate::notify_helper (this=this@entry=0x21672a0, receiver=receiver@entry=0x3927a40, e=e@entry=0x7ffde64f1ba0) at kernel/qapplication.cpp:3716 #23 0x7f00ca15d9d6 in QApplication::notify (this=0x7ffde64f1f80, receiver=0x3927a40, e=0x7ffde64f1ba0) at kernel/qapplication.cpp:3499 #24 0x7f00c8de1cf3 in QCoreApplication::notifyInternal (this=0x7ffde64f1f80, receiver=receiver@entry=0x3927a40, event=event@entry=0x7ffde64f1ba0) at kernel/qcoreapplication.cpp:965 #25 0x7f00c93266e4 in sendSpontaneousEvent (event=0x7ffde64f1ba0, receiver=0x3927a40) at ../../src/corelib/kernel/qcoreapplication.h:227 #26 QGuiApplicationPrivate::processExposeEvent (e=0x338a240) at kernel/qguiapplication.cpp:2648 #27 0x7f00c932737d in QGuiApplicationPrivate::processWindowSystemEvent (e=e@entry=0x338a240) at kernel/qguiapplication.cpp:1643 #28 0x7f00c930c9f8 in QWindowSystemInterface::sendWindowSystemEvents (flags=...) at kernel/qwindowsysteminterface.cpp:625 #29 0x7f00ba6b8ed0 in userEventSourceDispatch (source=) at eventdispatchers/qeventdispatcher_glib.cpp:70 #30 0x7f00c4c13097 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #31 0x7f00c4c132c8 in ?? () from /usr/lib64/libglib-2.0.so.0 #32 0x7f00c4c1336c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #33 0x7f00c8e3550f in QEventDispatcherGlib::processEvents (this=0x21c38c0, flags=...) at kernel/qeventdispatcher_glib.cpp:418 #34 0x7f00c8ddf63a in QEventLoop::exec (this=this@entry=0x7ffde64f1e30, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #35 0x7f00c8de72fd in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1229 #36 0x7f00c931d53c in QGu
[plasma-nm] [Bug 357525] plasma-nm crash confirming credentials to openconnect VPN
https://bugs.kde.org/show_bug.cgi?id=357525 René Krell <renda.kr...@gmail.com> changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #3 from René Krell <renda.kr...@gmail.com> --- I'm already on Plasma 5.5.2 and cannot reproduce this any longer. Apparently there is nothing else to do here, marking this resolved. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 357307] kdeinit5 5.16.0 crash after login
https://bugs.kde.org/show_bug.cgi?id=357307 René Krell <renda.kr...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from René Krell <renda.kr...@gmail.com> --- Well, it really doesn't happen any longer. Probably a problem with cached data after the update. I will close this, probably nobody else cares in this case. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356670] Plasma shell memory leak let subsequent applications run out of memory
https://bugs.kde.org/show_bug.cgi?id=356670 --- Comment #11 from René Krell <renda.kr...@gmail.com> --- Created attachment 96358 --> https://bugs.kde.org/attachment.cgi?id=96358=edit Output of killall plasmashell; kstart valgrind --error-limit=no --leak-check=full --show-leak-kinds=all --log-file=/tmp/plasmashell-valgrind.log plasmashell Added the output of killall plasmashell; kstart valgrind --error-limit=no --leak-check=full --show-leak-kinds=all --log-file=/tmp/Xorg-valgrind.log plasmashell. >From my point of view doesn't still show the leak in the dimensions described. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356670] Plasma shell memory leak let subsequent applications run out of memory
https://bugs.kde.org/show_bug.cgi?id=356670 --- Comment #13 from René Krell <renda.kr...@gmail.com> --- Created attachment 96359 --> https://bugs.kde.org/attachment.cgi?id=96359=edit Output of killall baloo_file; kstart valgrind --error-limit=no --leak-check=full --show-leak-kinds=all --log-file=/tmp/baloo_file-valgrind.log baloo_file BTW: Baloo crashes all the time after a while (DrKonqui), not just over valgrind. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 357307] kdeinit5 5.16.0 crash after login
https://bugs.kde.org/show_bug.cgi?id=357307 René Krell <renda.kr...@gmail.com> changed: What|Removed |Added Platform|Other |openSUSE RPMs -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 357307] New: kdeinit5 5.16.0 crash after login
https://bugs.kde.org/show_bug.cgi?id=357307 Bug ID: 357307 Summary: kdeinit5 5.16.0 crash after login Product: frameworks-kinit Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: fa...@kde.org Reporter: renda.kr...@gmail.com CC: kdelibs-b...@kde.org After login, I get each time the following crash: Application: kdeinit5 (kdeinit5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9769012740 (LWP 19241))] Thread 4 (Thread 0x7f97488af700 (LWP 19249)): #0 0x7f97673c224d in poll () from /lib64/libc.so.6 #1 0x7f976408c264 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f976408c36c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f976408c3a9 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f97640b1ee5 in ?? () from /usr/lib64/libglib-2.0.so.0 #5 0x7f9764dde4a4 in start_thread () from /lib64/libpthread.so.0 #6 0x7f97673cabdd in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f9743fff700 (LWP 19250)): #0 0x7f97673be22d in read () from /lib64/libc.so.6 #1 0x7f97640ce210 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f976408bd94 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f976408c208 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f976408c5e2 in g_main_loop_run () from /usr/lib64/libglib-2.0.so.0 #5 0x7f97491cd9d6 in ?? () from /usr/lib64/libgio-2.0.so.0 #6 0x7f97640b1ee5 in ?? () from /usr/lib64/libglib-2.0.so.0 #7 0x7f9764dde4a4 in start_thread () from /lib64/libpthread.so.0 #8 0x7f97673cabdd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f973b7fe700 (LWP 19259)): #0 0x7f97673c224d in poll () from /lib64/libc.so.6 #1 0x7f976408c264 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f976408c36c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f976795452b in QEventDispatcherGlib::processEvents (this=0x7f97340008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f97678fe63a in QEventLoop::exec (this=this@entry=0x7f973b7fde90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f976772ab1c in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7f976772f94f in QThreadPrivate::start (arg=0x1a82110) at thread/qthread_unix.cpp:331 #7 0x7f9764dde4a4 in start_thread () from /lib64/libpthread.so.0 #8 0x7f97673cabdd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f9769012740 (LWP 19241)): [KCrash Handler] #5 detach (this=0x30) at /usr/include/qt5/QtCore/qmap.h:364 #6 begin (this=0x30) at /usr/include/qt5/QtCore/qmap.h:526 #7 KDirWatchPrivate::removeEntries (this=0x0, instance=instance@entry=0x7f97672dffe0 <(anonymous namespace)::Q_QGS_s_pKDirWatchSelf::innerFunction()::holder>) at /usr/src/debug/kcoreaddons-5.16.0/src/lib/io/kdirwatch.cpp:1114 #8 0x7f97670878ff in KDirWatch::~KDirWatch (this=0x7f97672dffe0 <(anonymous namespace)::Q_QGS_s_pKDirWatchSelf::innerFunction()::holder>, __in_chrg=) at /usr/src/debug/kcoreaddons-5.16.0/src/lib/io/kdirwatch.cpp:1895 #9 0x7f9767087919 in (anonymous namespace)::Q_QGS_s_pKDirWatchSelf::Holder::~Holder (this=, __in_chrg=) at /usr/src/debug/kcoreaddons-5.16.0/src/lib/io/kdirwatch.cpp:1857 #10 0x7f9767087919 in operator() (this=) from /usr/lib64/libKF5CoreAddons.so.5 #11 postRoutine_KDirWatch () at /usr/src/debug/kcoreaddons-5.16.0/src/lib/io/kdirwatch.cpp:1873 #12 0x7f9767318678 in __run_exit_handlers () from /lib64/libc.so.6 #13 0x7f97673186c5 in exit () from /lib64/libc.so.6 #14 0x7f9768710395 in _XDefaultIOError () from /usr/lib64/libX11.so.6 #15 0x7f9755b5d95e in ioErrorHandler (dpy=0x2361760) at qxcbconnection.cpp:140 #16 0x7f97687105be in _XIOError () from /usr/lib64/libX11.so.6 #17 0x7f976870d94b in ?? () from /usr/lib64/libX11.so.6 #18 0x7f976870e0e5 in _XFlush () from /usr/lib64/libX11.so.6 #19 0x7f9768710c25 in _XGetRequest () from /usr/lib64/libX11.so.6 #20 0x7f97686f23b7 in XFreeGC () from /usr/lib64/libX11.so.6 #21 0x7f97686ec20c in XCloseDisplay () from /usr/lib64/libX11.so.6 #22 0x7f9701314aad in cleanup (p=) at /usr/src/debug/plasma-desktop-5.4.3/kcms/touchpad/src/backends/x11/xlibbackend.cpp:60 #23 ~QScopedPointer (this=0x1ddb410, __in_chrg=) at /usr/include/qt5/QtCore/qscopedpointer.h:101 #24 XlibBackend::~XlibBackend (this=0x1ddb400, __in_chrg=) at /usr/src/debug/plasma-desktop-5.4.3/kcms/touchpad/src/backends/x11/xlibbackend.cpp:338 #25 0x7f970131b4d3 in ~XlibLibinputBackend (this=0x1ddb400, __in_chrg=) at /usr/src/debug/plasma-desktop-5.4.3/kcms/touchpad/src/backends/x11/xlibbackend.cpp:144 #26 XlibLibinputBackend::~XlibLibinputBackend (this=0x1ddb400, __in_chrg=) at
[plasmashell] [Bug 356670] Plasma shell memory leak let subsequent applications run out of memory
https://bugs.kde.org/show_bug.cgi?id=356670 --- Comment #8 from René Krell <renda.kr...@gmail.com> --- Just one more hint, running the other apps (Firefox, Chromium) in Gnome 3.18.2 on the same system initially reported works without memory failures, it depends on the KDE environment. >From what I reported there was also the big baloo index of 5 GB. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356670] Plasma shell memory leak let subsequent applications run out of memory
https://bugs.kde.org/show_bug.cgi?id=356670 --- Comment #12 from René Krell <renda.kr...@gmail.com> --- Launching chromium in valgrind using the same command line options ends in: ==16979== LEAK SUMMARY: ==16979==definitely lost: 0 bytes in 0 blocks ==16979==indirectly lost: 0 bytes in 0 blocks ==16979== possibly lost: 0 bytes in 0 blocks ==16979==still reachable: 108,483 bytes in 1,293 blocks ==16979== suppressed: 0 bytes in 0 blocks but just about 10 of 30 open tabs open, the rest of the processes crash because it gets no resources. This does not happen in Gnome 3.18.2 at all. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356670] Plasma shell memory leak let subsequent applications run out of memory
https://bugs.kde.org/show_bug.cgi?id=356670 René Krell <renda.kr...@gmail.com> changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|INVALID |--- --- Comment #14 from René Krell <renda.kr...@gmail.com> --- Please just check whether the additional information gives you any useful information. Or just send a hint. I just see the problem just existing in KDE and offer help for finding the reason. If not possible, feel free to close this again. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 344879] memory leak in plasmashell - huge ram usage
https://bugs.kde.org/show_bug.cgi?id=344879 René Krell <renda.kr...@gmail.com> changed: What|Removed |Added CC||renda.kr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356670] Plasma shell memory leak let subsequent applications run out of memory
https://bugs.kde.org/show_bug.cgi?id=356670 --- Comment #9 from René Krell <renda.kr...@gmail.com> --- >From the user comments, https://bugs.kde.org/show_bug.cgi?id=344879 looks very similar to me. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356670] Plasma shell memory leak let subsequent applications run out of memory
https://bugs.kde.org/show_bug.cgi?id=356670 --- Comment #1 from René Krell <renda.kr...@gmail.com> --- Created attachment 96058 --> https://bugs.kde.org/attachment.cgi?id=96058=edit cat /proc/`pidof plasmashell`/smaps (output) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356670] New: Plasma shell memory leak let subsequent applications run out of memory
https://bugs.kde.org/show_bug.cgi?id=356670 Bug ID: 356670 Summary: Plasma shell memory leak let subsequent applications run out of memory Product: plasmashell Version: 5.4.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: renda.kr...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org After the most recent system updates I encounter a heavy memory leak which lets applications like Chromium, Chrome, Firefox, Maven builds etc. run out of memory. It is jard for me to analyze, but I try to collect the necessary information. OS: OpenSUSE Tumbleweed 20151209 uname -a: Linux rkrell 4.3.0-2-default #1 SMP PREEMPT Sat Nov 14 16:19:19 UTC 2015 (734b32c) x86_64 x86_64 x86_64 GNU/Linux I opened the Gnome System Monitor to get an idea of a suspicious application - the most common one for all failure situations which consumes most memory is plasmashell: - Virtual Memory: 10 GB - Resident Memory: 435,2 MB - Shared Memory 204,4 MB - X-Server memory: 2,3 MB followed by baloo: - Virtual Memory: 5,3 GB - Resident Memory: 88,5 MB - Shared Memory 17,2 MB - X-Server memory: 0 kBytes Several weeks ago with previous KDE versions this didn't happen. I'll append several output I get from my system, if you're interested please tell me what else to provide, I'm not sure. Reproducible: Always Steps to Reproduce: 1. Logon to KDE 2. Open Chromium/Chrome (or whatever app usually consuming a bit more memory) Actual Results: Most of the tabs of about 20 open tabs don't open. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356670] Plasma shell memory leak let subsequent applications run out of memory
https://bugs.kde.org/show_bug.cgi?id=356670 --- Comment #3 from René Krell <renda.kr...@gmail.com> --- KDE versions: - KDE Releases Frameworks: 5.16.0 - KDE Releases Applications 15.08.3 - Plasma: 5.4.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356670] Plasma shell memory leak let subsequent applications run out of memory
https://bugs.kde.org/show_bug.cgi?id=356670 --- Comment #2 from René Krell <renda.kr...@gmail.com> --- Created attachment 96059 --> https://bugs.kde.org/attachment.cgi?id=96059=edit cat /proc/`pidof baloo_file`/smaps (output) -- You are receiving this mail because: You are watching all bug changes.
