[okular] [Bug 450519] New: uninstall
https://bugs.kde.org/show_bug.cgi?id=450519 Bug ID: 450519 Summary: uninstall Product: okular Version: unspecified Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: rodrigoj...@hotmail.com Target Milestone: --- Created attachment 146911 --> https://bugs.kde.org/attachment.cgi?id=146911&action=edit image bug Usability When the okular update (Development-stable version) is available. okular cannot uninstall previous files. OS: Windows 7 (Professional). Below is the image of the problem: -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 466305] New: monitor fecha sozinho
https://bugs.kde.org/show_bug.cgi?id=466305 Bug ID: 466305 Summary: monitor fecha sozinho Classification: Plasma Product: plasma-systemmonitor Version: 5.27.1 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: offspring_...@hotmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Application: plasma-systemmonitor (5.27.1) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.2.0-4-cachyos-pds x86_64 Windowing System: X11 Distribution: "Arch Linux" DrKonqi: 5.27.1 [KCrashBackend] -- Information about the crash: o monitor do sistema fecha sozinho ao clicar em alguns dos itens laterais esquerdo, exemplo processos, historicos etc. The crash can be reproduced every time. -- Backtrace: Application: Monitor do sistema (plasma-systemmonitor), signal: Segmentation fault [KCrash Handler] #4 0x7f53b0628277 in QQuickTransform::~QQuickTransform() () from /usr/lib/libQt5Quick.so.5 #5 0x7f53b07b1a33 in ?? () from /usr/lib/libQt5Quick.so.5 #6 0x7f53b0794c22 in QAccessibleQuickItem::role() const () from /usr/lib/libQt5Quick.so.5 #7 0x7f53b2441919 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #8 0x7f53b242dd7e in ?? () from /usr/lib/libQt5XcbQpa.so.5 #9 0x7f53b242ea36 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #10 0x7f53b0631a7c in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /usr/lib/libQt5Quick.so.5 #11 0x7f53b0635303 in QQuickItem::setParentItem(QQuickItem*) () from /usr/lib/libQt5Quick.so.5 #12 0x7f53b0629802 in QQuickItem::~QQuickItem() () from /usr/lib/libQt5Quick.so.5 #13 0x7f5394dba00b in ?? () from /usr/lib/qt/qml/QtQuick/Templates.2/libqtquicktemplates2plugin.so #14 0x7f53abd17e3f in QQmlTableInstanceModel::destroyModelItem(QQmlDelegateModelItem*, QQmlTableInstanceModel::DestructionMode) () from /usr/lib/libQt5QmlModels.so.5 #15 0x7f53abd40cd2 in ?? () from /usr/lib/libQt5QmlModels.so.5 #16 0x7f53abd17199 in QQmlTableInstanceModel::drainReusableItemsPool(int) () from /usr/lib/libQt5QmlModels.so.5 #17 0x7f53b071cfc1 in QQuickTableView::geometryChanged(QRectF const&, QRectF const&) () from /usr/lib/libQt5Quick.so.5 #18 0x7f53b063b99d in QQuickItem::setSize(QSizeF const&) () from /usr/lib/libQt5Quick.so.5 #19 0x7f53abe1c65f in QQuickControlPrivate::resizeContent() () from /usr/lib/libQt5QuickTemplates2.so.5 #20 0x7f53abe1efb5 in QQuickControl::paddingChange(QMarginsF const&, QMarginsF const&) () from /usr/lib/libQt5QuickTemplates2.so.5 #21 0x7f53abe18ae1 in QQuickControlPrivate::setRightPadding(double, bool) () from /usr/lib/libQt5QuickTemplates2.so.5 #22 0x7f53b7a3c85e in ?? () from /usr/lib/libQt5Qml.so.5 #23 0x7f53b7a9101b in ?? () from /usr/lib/libQt5Qml.so.5 #24 0x7f53b7a978fe in ?? () from /usr/lib/libQt5Qml.so.5 #25 0x7f53b7a98f73 in QQmlBinding::update(QFlags) () from /usr/lib/libQt5Qml.so.5 #26 0x7f53b7a7647f in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /usr/lib/libQt5Qml.so.5 #27 0x7f53b62be740 in ?? () from /usr/lib/libQt5Core.so.5 #28 0x7f53b7a31fcb in QQmlVMEMetaObject::metaCall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQt5Qml.so.5 #29 0x7f53b7a3c823 in ?? () from /usr/lib/libQt5Qml.so.5 #30 0x7f53b7a9101b in ?? () from /usr/lib/libQt5Qml.so.5 #31 0x7f53b7a978fe in ?? () from /usr/lib/libQt5Qml.so.5 #32 0x7f53b7a98f73 in QQmlBinding::update(QFlags) () from /usr/lib/libQt5Qml.so.5 #33 0x7f53b7a7647f in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /usr/lib/libQt5Qml.so.5 #34 0x7f53b62be740 in ?? () from /usr/lib/libQt5Core.so.5 #35 0x7f53b0631ad9 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /usr/lib/libQt5Quick.so.5 #36 0x7f53b06319f8 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /usr/lib/libQt5Quick.so.5 #37 0x7f53b06319f8 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /usr/lib/libQt5Quick.so.5 #38 0x7f53b06319f8 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /usr/lib/libQt5Quick.so.5 #39 0x7f53b06319f8 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /usr/lib/libQt5Quick.so.5 #40 0x7f53b06319f8 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /usr/lib/libQt5Quick.so.5 #41 0x7f53b06319f8 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /usr/lib/libQt5Quick.so.5 #42 0x7f53b06319f8 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /usr/lib/libQt5Quick.so.5 #43 0x7f53b06319f8 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /usr/lib/libQt5Quick.so.5 #44 0x7f53b06319f8 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /usr/lib/libQt5Quic
[kwin] [Bug 430160] New: Kwin Crash after return from Suspend
https://bugs.kde.org/show_bug.cgi?id=430160 Bug ID: 430160 Summary: Kwin Crash after return from Suspend Product: kwin Version: 5.20.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: rodrigo.ch...@gmail.com Target Milestone: --- Application: kwin_x11 (5.20.3) Qt Version: 5.15.2 Frameworks Version: 5.75.0 Operating System: Linux 5.9.11-200.fc33.x86_64 x86_64 Windowing system: X11 Distribution: Fedora 33 (KDE Plasma) -- Information about the crash: I woke up the Laptop from suspend in ram like 40 minutes in that condition. I guess can be a Nvidia problem, I don't have a motive or how to reproduce the error, but in my opinion I have the same problem in Fedora and Archlinux(Manjaro Included), if the PC has a Nvidia GPU with the proprietary drivers is most possible to reproduce. Right now the config of my X11 is vainilla Nvidia config without Full composition and Pipeline composition. Why the Nvidia link to this? Kwin have others bugs if Nvidia is present, GTK artifacts, in QT apps same in specific occasions . The artifacts are like TV noise? The Kwin Fails are only happen in my experiece with Nvidia's Dedicated GPU, my other Laptop with ony Intel iGPU not happen this problems The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault [KCrash Handler] #4 0x7f67a9ddf538 in KWin::WindowQuadList::makeInterleavedArrays(unsigned int, KWin::GLVertex2D*, QMatrix4x4 const&) const () at /lib64/libkwineffects.so.12 #5 0x7f6786d24c88 in KWin::OpenGLWindow::performPaint(int, QRegion const&, KWin::WindowPaintData const&) () at /usr/lib64/qt5/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so #6 0x7f67ac02e6b5 in KWin::EffectsHandlerImpl::drawWindow(KWin::EffectWindow*, int, QRegion const&, KWin::WindowPaintData&) () at /lib64/libkwin.so.5 #7 0x7f67aa60e69d in KWin::ContrastEffect::drawWindow(KWin::EffectWindow*, int, QRegion const&, KWin::WindowPaintData&) () at /lib64/libkwin4_effect_builtins.so.1 #8 0x7f67ac02e6b5 in KWin::EffectsHandlerImpl::drawWindow(KWin::EffectWindow*, int, QRegion const&, KWin::WindowPaintData&) () at /lib64/libkwin.so.5 #9 0x7f67aa5895fd in KWin::BlurEffect::drawWindow(KWin::EffectWindow*, int, QRegion const&, KWin::WindowPaintData&) () at /lib64/libkwin4_effect_builtins.so.1 #10 0x7f67ac02e6b5 in KWin::EffectsHandlerImpl::drawWindow(KWin::EffectWindow*, int, QRegion const&, KWin::WindowPaintData&) () at /lib64/libkwin.so.5 #11 0x7f67ac033d07 in KWin::EffectsHandlerImpl::paintWindow(KWin::EffectWindow*, int, QRegion const&, KWin::WindowPaintData&) () at /lib64/libkwin.so.5 #12 0x7f67ac033d07 in KWin::EffectsHandlerImpl::paintWindow(KWin::EffectWindow*, int, QRegion const&, KWin::WindowPaintData&) () at /lib64/libkwin.so.5 #13 0x7f67ac033d07 in KWin::EffectsHandlerImpl::paintWindow(KWin::EffectWindow*, int, QRegion const&, KWin::WindowPaintData&) () at /lib64/libkwin.so.5 #14 0x7f67ac0a12c6 in KWin::Scene::paintWindow(KWin::Scene::Window*, int, QRegion const&, KWin::WindowQuadList const&) () at /lib64/libkwin.so.5 #15 0x7f67ac0a2e31 in KWin::Scene::paintSimpleScreen(int, QRegion const&) () at /lib64/libkwin.so.5 #16 0x7f67ac09cf96 in KWin::Scene::finalPaintScreen(int, QRegion const&, KWin::ScreenPaintData&) () at /lib64/libkwin.so.5 #17 0x7f67ac033c5e in KWin::EffectsHandlerImpl::paintScreen(int, QRegion const&, KWin::ScreenPaintData&) () at /lib64/libkwin.so.5 #18 0x7f67ac033c5e in KWin::EffectsHandlerImpl::paintScreen(int, QRegion const&, KWin::ScreenPaintData&) () at /lib64/libkwin.so.5 #19 0x7f67ac033c5e in KWin::EffectsHandlerImpl::paintScreen(int, QRegion const&, KWin::ScreenPaintData&) () at /lib64/libkwin.so.5 #20 0x7f67ac0a0030 in KWin::Scene::paintScreen(int*, QRegion const&, QRegion const&, QRegion*, QRegion*, QMatrix4x4 const&, QRect const&, double) () at /lib64/libkwin.so.5 #21 0x7f6786d1cc03 in KWin::SceneOpenGL::paint(QRegion const&, QList const&) () at /usr/lib64/qt5/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so #22 0x7f67ac008de7 in KWin::Compositor::performCompositing() () at /lib64/libkwin.so.5 #23 0x7f67aacdec7f in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #24 0x7f67ab74bec3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #25 0x7f67aacb6bd8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #26 0x7f67aad02a03 in QTimerInfoList::activateTimers() () at /lib64/libQt5Core.so.5 #27 0x7f67aad00e6f in QEventDispatcherUNIX::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #28 0x7f67978eb852 in QXcbUnixEventDispatcher::processEvents(QFlags) () at /lib64/libQt5XcbQpa.so.5 #29 0x7f67aacb55
[kwin] [Bug 491467] night color does not start automatically on system startup using X11
https://bugs.kde.org/show_bug.cgi?id=491467 --- Comment #8 from Rodrigo --- Created attachment 172677 --> https://bugs.kde.org/attachment.cgi?id=172677&action=edit Profiles from Color Management hello everyone! I have some profiles in color management, but they are all standard profiles, I've never touched this section before xD -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 491467] night color does not start automatically on system startup using X11
https://bugs.kde.org/show_bug.cgi?id=491467 --- Comment #9 from Rodrigo --- (In reply to Rodrigo from comment #8) > Created attachment 172677 [details] > Profiles from Color Management > > hello everyone! > I have some profiles in color management, but they are all standard > profiles, I've never touched this section before xD I left a screenshot attached, but this session was started in wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 491467] New: night color does not start automatically on system startup using X11
https://bugs.kde.org/show_bug.cgi?id=491467 Bug ID: 491467 Summary: night color does not start automatically on system startup using X11 Classification: Plasma Product: kwin Version: 6.1.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: night color Assignee: kwin-bugs-n...@kde.org Reporter: rodrigo.el...@engenharia.ufjf.br Target Milestone: --- When I restart the system or put the computer to sleep the night light function is disabled, I need to manually enable it to work again. This is happening while I am using X11, the night color is set to "always on night light" Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.9.12-200.fc40.x86_64 (64-bit) Graphics Platform: X11 Processors: 4 × AMD Ryzen 3 3200G with Radeon Vega Graphics Memory: 15.3 GiB of RAM Graphics Processor: AMD Radeon RX 550 Series -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 491467] night color does not start automatically on system startup using X11
https://bugs.kde.org/show_bug.cgi?id=491467 Rodrigo changed: What|Removed |Added Alias||Night, Light, buggy, X11 Keywords||accessibility, usability -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 491467] night color does not start automatically on system startup using X11
https://bugs.kde.org/show_bug.cgi?id=491467 --- Comment #2 from Rodrigo --- (In reply to Nate Graham from comment #1) > Does it work on Wayland? It works on Wayland, I would like to know if it will continue to work on X11 because I still need X11 for some features that I need. Regards -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 491467] night color does not start automatically on system startup using X11
https://bugs.kde.org/show_bug.cgi?id=491467 --- Comment #4 from Rodrigo --- I understand, the Wayland is now a priority, I will try to migrate to it then, thanks for the answer! Regards -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433802] New: Feature Request: Make volume UP scroll UP, even in INVERTER SCROLL DIRECTION
https://bugs.kde.org/show_bug.cgi?id=433802 Bug ID: 433802 Summary: Feature Request: Make volume UP scroll UP, even in INVERTER SCROLL DIRECTION Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Media Player Assignee: k...@privat.broulik.de Reporter: rodrigodon...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY STEPS TO REPRODUCE 1. Select Inverter Scroll Directionn 2. Try to increase the volume OBSERVED RESULT When you scroll up, the volume goes down. Which in this case is counter intuitive, although it makes sense when scrolling a web or text. EXPECTED RESULT I think it could be good to make the volume go up, if you scroll up, even if the Inverter Scroll Direction is selected SOFTWARE/OS VERSIONS KDE Plasma Version: 5.21.1 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 280343] Copying file from obex session with bluetooth, dolphin uses full path as filename
https://bugs.kde.org/show_bug.cgi?id=280343 Rodrigo changed: What|Removed |Added CC||fera...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412531] New: Reload quando abrindo o menu do sistema
https://bugs.kde.org/show_bug.cgi?id=412531 Bug ID: 412531 Summary: Reload quando abrindo o menu do sistema Product: plasmashell Version: 5.16.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: frango...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.16.4) Qt Version: 5.13.0 Frameworks Version: 5.61.0 Operating System: Linux 5.2.11-1-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: Quando abri o menu do sistema, o KDE travou de forma inesperada -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa65aa6b880 (LWP 1336))] Thread 14 (Thread 0x7fa5f37fe700 (LWP 27863)): #0 0x7fa65ea4b415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa65f57c5a0 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fa65f57c692 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fa6613607bd in () at /usr/lib/libQt5Quick.so.5 #4 0x7fa661360a6e in () at /usr/lib/libQt5Quick.so.5 #5 0x7fa65f576520 in () at /usr/lib/libQt5Core.so.5 #6 0x7fa65ea4557f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fa65f2050e3 in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7fa6229ee700 (LWP 8736)): #0 0x7fa65ea4b415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa65f57c5a0 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fa65f57c692 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fa6613607bd in () at /usr/lib/libQt5Quick.so.5 #4 0x7fa661360a6e in () at /usr/lib/libQt5Quick.so.5 #5 0x7fa65f576520 in () at /usr/lib/libQt5Core.so.5 #6 0x7fa65ea4557f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fa65f2050e3 in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7fa6220ed700 (LWP 8735)): #0 0x7fa65f1f618c in read () at /usr/lib/libc.so.6 #1 0x7fa6451cd782 in pa_read () at /usr/lib/pulseaudio/libpulsecommon-12.2.so #2 0x7fa64585955f in pa_mainloop_prepare () at /usr/lib/libpulse.so.0 #3 0x7fa645859fd1 in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #4 0x7fa64585a091 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #5 0x7fa6458685ae in () at /usr/lib/libpulse.so.0 #6 0x7fa6451fd9fc in () at /usr/lib/pulseaudio/libpulsecommon-12.2.so #7 0x7fa65ea4557f in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fa65f2050e3 in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7fa630b9d700 (LWP 8313)): #0 0x7fa65ea4b415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa65f57c5a0 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fa65f57c692 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fa6613607bd in () at /usr/lib/libQt5Quick.so.5 #4 0x7fa661360a6e in () at /usr/lib/libQt5Quick.so.5 #5 0x7fa65f576520 in () at /usr/lib/libQt5Core.so.5 #6 0x7fa65ea4557f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fa65f2050e3 in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7fa6217e2700 (LWP 2578)): #0 0x7fa65ea4b415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa65f57c5a0 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fa65f57c692 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fa6613607bd in () at /usr/lib/libQt5Quick.so.5 #4 0x7fa661360a6e in () at /usr/lib/libQt5Quick.so.5 #5 0x7fa65f576520 in () at /usr/lib/libQt5Core.so.5 #6 0x7fa65ea4557f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fa65f2050e3 in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7fa623fff700 (LWP 1748)): #0 0x7fa65ea4b415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa65f57c5a0 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fa65f57c692 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fa6613607bd in () at /usr/lib/libQt5Quick.so.5 #4 0x7fa661360a6e in () at /usr/lib/libQt5Quick.so.5 #5 0x7fa65f576520 in () at /usr/lib/libQt5Core.so.5 #6 0x7fa65ea4557f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fa65f2050e3 in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7fa631e36700 (LWP 1738)): #0 0x7fa65d9d2470 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x0
[rkward] [Bug 386899] New: KDE -- RKWard
https://bugs.kde.org/show_bug.cgi?id=386899 Bug ID: 386899 Summary: KDE -- RKWard Product: rkward Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: rkward-de...@kde.org Reporter: rodrigooliveira...@gmail.com Target Milestone: --- ---Descrição do problema--- Por favor, preencha as informações ausentes *em inglês*. Encontrei a mensagem de erro citada abaixo. Além disso, vi os seguintes sintomas: ###Por favor, preencha (se aplicável)### O que fez - em detalhes - diretamente antes de encontrar este problema? ###Por favor, preencha### Quando tentou repetir os passos acima, o problema voltou a ocorrer (não, às vezes, sempre)? ###Por favor, preencha### Se aplicável: Ao fazer a mesma coisa em uma sessão de R fora do RKWard, ocorreu o mesmo problema? ###Por favor, preencha### Você tem alguma informação adicional que possa nos ajudar a localizar este problema? Em particular, se aplicável, pode fornecer dados e código em R como exemplo para reproduzir este problema? ###Por favor, preencha### O RKWard está disponível em muitas distribuições e, às vezes, os problemas são específicos para um determinado método de instalação. Como você instalou o RKWard (quais arquivos você baixou)? ###Por favor, preencha### ---Error Message--- Código da mensagem: r_engine_has_died Connection closed unexpectedly. Last error was: QLocalSocket: Remote closed A infraestrutura do R será encerrada imediatamente. Isso significa que você não poderá usar mais funções que dependam dele, ou seja, provavelmente não poderá fazer mais nada, nem mesmo salvar o espaço de trabalho (mas, se tiver sorte, o R já o fez antes). O que poderá fazer, todavia, é salvar os arquivos de comandos que estiverem abertos, o resultado ou copiar os dados das janelas de editores de dados abertas. Saia do RKWard depois disso. Pedimos desculpas! ---Session Info--- RKWard version: 0.6.4 KDE version (runtime): 4.14.16 KDE version (compile time): 4.14.13 Qt build key: x86_64 linux g++-4 full-config Local KDE directory: /home/rodrigo/.kde/ RKWard storage directory: /home/rodrigo/.rkward/ Backend version (as known to the frontend): 3.4.1 Debug message file (this may contain relevant diagnostic output in case of trouble): /tmp/rkward.frontend.kn4902 - backend not available or rk.sessionInfo() canceled - -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 386913] New: RKWard
https://bugs.kde.org/show_bug.cgi?id=386913 Bug ID: 386913 Summary: RKWard Product: rkward Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: rkward-de...@kde.org Reporter: rodrigooliveira...@gmail.com Target Milestone: --- ---Descrição do problema--- Por favor, preencha as informações ausentes *em inglês*. Encontrei a mensagem de erro citada abaixo. Além disso, vi os seguintes sintomas: ###Por favor, preencha (se aplicável)### O que fez - em detalhes - diretamente antes de encontrar este problema? ###Por favor, preencha### Quando tentou repetir os passos acima, o problema voltou a ocorrer (não, às vezes, sempre)? ###Por favor, preencha### Se aplicável: Ao fazer a mesma coisa em uma sessão de R fora do RKWard, ocorreu o mesmo problema? ###Por favor, preencha### Você tem alguma informação adicional que possa nos ajudar a localizar este problema? Em particular, se aplicável, pode fornecer dados e código em R como exemplo para reproduzir este problema? ###Por favor, preencha### O RKWard está disponível em muitas distribuições e, às vezes, os problemas são específicos para um determinado método de instalação. Como você instalou o RKWard (quais arquivos você baixou)? ###Por favor, preencha### ---Error Message--- Código da mensagem: r_engine_has_died Connection closed unexpectedly. Last error was: QLocalSocket: Remote closed A infraestrutura do R será encerrada imediatamente. Isso significa que você não poderá usar mais funções que dependam dele, ou seja, provavelmente não poderá fazer mais nada, nem mesmo salvar o espaço de trabalho (mas, se tiver sorte, o R já o fez antes). O que poderá fazer, todavia, é salvar os arquivos de comandos que estiverem abertos, o resultado ou copiar os dados das janelas de editores de dados abertas. Saia do RKWard depois disso. Pedimos desculpas! ---Session Info--- RKWard version: 0.6.4 KDE version (runtime): 4.14.16 KDE version (compile time): 4.14.13 Qt build key: x86_64 linux g++-4 full-config Local KDE directory: /home/rodrigo/.kde/ RKWard storage directory: /home/rodrigo/.rkward/ Backend version (as known to the frontend): 3.4.1 Debug message file (this may contain relevant diagnostic output in case of trouble): /tmp/rkward.frontend.n49722 - backend not available or rk.sessionInfo() canceled - -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 386981] New: RKWard
https://bugs.kde.org/show_bug.cgi?id=386981 Bug ID: 386981 Summary: RKWard Product: rkward Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: rkward-de...@kde.org Reporter: rodrigooliveira...@gmail.com Target Milestone: --- ---Descrição do problema--- Por favor, preencha as informações ausentes *em inglês*. Encontrei a mensagem de erro citada abaixo. Além disso, vi os seguintes sintomas: ###Por favor, preencha (se aplicável)### O que fez - em detalhes - diretamente antes de encontrar este problema? ###Por favor, preencha### Quando tentou repetir os passos acima, o problema voltou a ocorrer (não, às vezes, sempre)? ###Por favor, preencha### Se aplicável: Ao fazer a mesma coisa em uma sessão de R fora do RKWard, ocorreu o mesmo problema? ###Por favor, preencha### Você tem alguma informação adicional que possa nos ajudar a localizar este problema? Em particular, se aplicável, pode fornecer dados e código em R como exemplo para reproduzir este problema? ###Por favor, preencha### O RKWard está disponível em muitas distribuições e, às vezes, os problemas são específicos para um determinado método de instalação. Como você instalou o RKWard (quais arquivos você baixou)? ###Por favor, preencha### ---Error Message--- Código da mensagem: r_engine_has_died Connection closed unexpectedly. Last error was: QLocalSocket: Remote closed A infraestrutura do R será encerrada imediatamente. Isso significa que você não poderá usar mais funções que dependam dele, ou seja, provavelmente não poderá fazer mais nada, nem mesmo salvar o espaço de trabalho (mas, se tiver sorte, o R já o fez antes). O que poderá fazer, todavia, é salvar os arquivos de comandos que estiverem abertos, o resultado ou copiar os dados das janelas de editores de dados abertas. Saia do RKWard depois disso. Pedimos desculpas! ---Session Info--- RKWard version: 0.6.4 KDE version (runtime): 4.14.16 KDE version (compile time): 4.14.13 Qt build key: x86_64 linux g++-4 full-config Local KDE directory: /home/rodrigo/.kde/ RKWard storage directory: /home/rodrigo/.rkward/ Backend version (as known to the frontend): 3.4.1 Debug message file (this may contain relevant diagnostic output in case of trouble): /tmp/rkward.frontend.n13094 - backend not available or rk.sessionInfo() canceled - -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 386474] New: Software update crash
https://bugs.kde.org/show_bug.cgi?id=386474 Bug ID: 386474 Summary: Software update crash Product: Discover Version: 5.10.5 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: rodrigo...@yahoo.com.br Target Milestone: --- Application: plasma-discover (5.10.5) (Compiled from sources) Qt Version: 5.7.1 Frameworks Version: 5.38.0 Operating System: Linux 4.13.9-200.fc26.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: I was trying to install TOR web browser. When I try to install libre writer, the same crash happen, but I try sometimes and the libre writer was installed. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5f71f518c0 (LWP 1699))] Thread 8 (Thread 0x7f5f235fb700 (LWP 1712)): #0 0x7f5f6d12842d in read () from /lib64/libc.so.6 #1 0x7f5f6648c170 in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0 #2 0x7f5f66448078 in g_main_context_check () from /lib64/libglib-2.0.so.0 #3 0x7f5f66448510 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #4 0x7f5f6644867c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7f5f6df48e6b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f5f6def960a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #7 0x7f5f6dd5199a in QThread::exec() () from /lib64/libQt5Core.so.5 #8 0x7f5f6dd55c9e in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #9 0x7f5f6bc9e36d in start_thread () from /lib64/libpthread.so.0 #10 0x7f5f6d138e1f in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7f5f33fff700 (LWP 1707)): #0 0x7f5f6bca490b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f5f6dd563fb in QWaitCondition::wait(QMutex*, unsigned long) () from /lib64/libQt5Core.so.5 #2 0x7f5f6dd5056b in QSemaphore::acquire(int) () from /lib64/libQt5Core.so.5 #3 0x7f5f6df218eb in QMetaObject::activate(QObject*, int, int, void**) () from /lib64/libQt5Core.so.5 #4 0x7f5f6e46076b in QHttpThreadDelegate::encryptedSlot() () from /lib64/libQt5Network.so.5 #5 0x7f5f6e4de71d in QHttpThreadDelegate::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /lib64/libQt5Network.so.5 #6 0x7f5f6df21a73 in QMetaObject::activate(QObject*, int, int, void**) () from /lib64/libQt5Core.so.5 #7 0x7f5f6e423e2e in QHttpNetworkConnectionChannel::_q_encrypted() () from /lib64/libQt5Network.so.5 #8 0x7f5f6e424345 in QHttpNetworkConnectionChannel::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /lib64/libQt5Network.so.5 #9 0x7f5f6df21a73 in QMetaObject::activate(QObject*, int, int, void**) () from /lib64/libQt5Core.so.5 #10 0x7f5f6e4d3c1e in QSslSocketBackendPrivate::continueHandshake() () from /lib64/libQt5Network.so.5 #11 0x7f5f6e4d7f90 in QSslSocketBackendPrivate::startHandshake() () from /lib64/libQt5Network.so.5 #12 0x7f5f6e4d833a in QSslSocketBackendPrivate::transmit() () from /lib64/libQt5Network.so.5 #13 0x7f5f6e4c42f1 in QSslSocket::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /lib64/libQt5Network.so.5 #14 0x7f5f6df21a73 in QMetaObject::activate(QObject*, int, int, void**) () from /lib64/libQt5Core.so.5 #15 0x7f5f6e4994d5 in QAbstractSocketPrivate::emitReadyRead() () from /lib64/libQt5Network.so.5 #16 0x7f5f6e499588 in QAbstractSocketPrivate::canReadNotification() () from /lib64/libQt5Network.so.5 #17 0x7f5f6e4a42d1 in QReadNotifier::event(QEvent*) () from /lib64/libQt5Network.so.5 #18 0x7f5f6ef2a5dc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #19 0x7f5f6ef31c74 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #20 0x7f5f6defa627 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #21 0x7f5f6df4977f in socketNotifierSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #22 0x7f5f66448247 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #23 0x7f5f664485e8 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #24 0x7f5f6644867c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #25 0x7f5f6df48e6b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #26 0x7f5f6def960a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #27 0x7f5f6dd5199a in QThread::exec() () from /lib64/libQt5Cor
[kwin] [Bug 378486] New: KWin crashes after unlocking locked session
https://bugs.kde.org/show_bug.cgi?id=378486 Bug ID: 378486 Summary: KWin crashes after unlocking locked session Product: kwin Version: 5.8.6 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: rmsi...@cmicro.com.br Target Milestone: --- Application: kwin_x11 (5.8.6) Qt Version: 5.7.1 Frameworks Version: 5.32.0 Operating System: Linux 4.10.8-200.fc25.x86_64 x86_64 Distribution: "Fedora release 25 (Twenty Five)" -- Information about the crash: - What I was doing when the application crashed: Desktop is set to lock after 5 min, require password after 35secs. Sometimes unlocking works as expected; sometimes KWin crashes (and restarts) after unlocking. Other times the desktop is completely messed up with with ever changing shapes (squares, triangles) containing distorted (zoomed, shifted) application windows contents. In this scenario, unlocking does not work by entering the password. It is necessary to log into another tty and issue an "loginctl unlock-sessions" in order for the session to be usable again. After manual unlock as root, I can return to X and session is correctly restored. - Unusual behavior I noticed: - Custom settings of the application: System running NVIDIA proprietary drivers (378.13). Fedora 25 with linux 4.10.8-200. 4K display using DP connector. This behavior (especially the messed up lock screen) seems to occur more often after a fresh boot. If the machine is suspended one or more times, unlocking problems occur less frequently (but will eventually happen again). Every week or so, even unlocking from the console fails and an X restart is needed to be able to log into KDE again. The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f290c06d940 (LWP 32438))] Thread 6 (Thread 0x7f28d0dfe700 (LWP 32473)): #0 0x7f291e29d460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2923b642f4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /lib64/libQt5Script.so.5 #2 0x7f2923b64339 in () at /lib64/libQt5Script.so.5 #3 0x7f291e2976ca in start_thread () at /lib64/libpthread.so.0 #4 0x7f291b486f7f in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f28e9208700 (LWP 32471)): #0 0x7f291e29d809 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f28f051be44 in () at /lib64/libGLX_nvidia.so.0 #2 0x7f28e9fd4394 in () at /lib64/libnvidia-glcore.so.378.13 #3 0x7f28f051b12c in () at /lib64/libGLX_nvidia.so.0 #4 0x7f291e2976ca in start_thread () at /lib64/libpthread.so.0 #5 0x7f291b486f7f in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f28f0ffd700 (LWP 32468)): #0 0x7f291b47b0e1 in ppoll () at /lib64/libc.so.6 #1 0x7f291c27d971 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /lib64/libQt5Core.so.5 #2 0x7f291c27ee86 in QEventDispatcherUNIX::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #3 0x7f291c23268a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f291c08f5e3 in QThread::exec() () at /lib64/libQt5Core.so.5 #5 0x7f2922db94e5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #6 0x7f291c0939ca in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7f291e2976ca in start_thread () at /lib64/libpthread.so.0 #8 0x7f291b486f7f in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f2902e18700 (LWP 32464)): #0 0x7f291b47b0e1 in ppoll () at /lib64/libc.so.6 #1 0x7f291c27d971 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /lib64/libQt5Core.so.5 #2 0x7f291c27ee86 in QEventDispatcherUNIX::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #3 0x7f291c23268a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f291c08f5e3 in QThread::exec() () at /lib64/libQt5Core.so.5 #5 0x7f291ddb2739 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #6 0x7f291c0939ca in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7f291e2976ca in start_thread () at /lib64/libpthread.so.0 #8 0x7f291b486f7f in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f29044da700 (LWP 32463)): #0 0x7f291b47b01d in poll () at /lib64/libc.so.6 #1 0x7f291db80d10 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x7f291db82aa9 in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7f29053b4d69 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x7f291c0939ca in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7f291e2976ca in start_thread () at /lib64/libpthread.so.0 #6 0x7f291b486f7f in clone () at /lib64/libc.so.6
[kwin] [Bug 378486] KWin crashes after unlocking locked session
https://bugs.kde.org/show_bug.cgi?id=378486 --- Comment #2 from Rodrigo --- Created attachment 104906 --> https://bugs.kde.org/attachment.cgi?id=104906&action=edit KWin support information Output of "qdbus org.kde.KWin /KWin supportInformation" attached. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 378486] KWin crashes after unlocking locked session
https://bugs.kde.org/show_bug.cgi?id=378486 --- Comment #4 from Rodrigo --- Yes, I had already seen that bug report and the SIMPTOMS are very similar. The difference is that when I suspend the machine, it usually (almost always) resumes fine (i.e. functions as expected). For me the problem happens most often after a screen lock/display sleep. Everytime I leave my desk for over 5 min, when I come back there's a big chance (~60%) that the issue will happen (garbled screen, unlock from tty, kwin crash). The machine is only suspended at night, never during the day when the issue happens very often. Moreover if I disable screen locking due to inactivity, the problem disappears. That is, screen locking seems to cause the issue. In that other report, they are talking about a similar issue but only when the computer is suspended and resumed. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 495614] New: Discover crash
https://bugs.kde.org/show_bug.cgi?id=495614 Bug ID: 495614 Summary: Discover crash Classification: Applications Product: Discover Version: 5.27.11 Platform: Kubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: rodho...@gmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.27.11) Qt Version: 5.15.13 Frameworks Version: 5.115.0 Operating System: Linux 6.8.0-47-generic x86_64 Windowing System: X11 Distribution: Ubuntu 24.04.1 LTS DrKonqi: 5.27.11 [KCrashBackend] -- Information about the crash: Discover randomly and constantly crashes after opening or after looking for updates or searching for apps. The crash can be reproduced sometimes. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault [KCrash Handler] #4 0x7b39905a2d4c in QSGNode::~QSGNode() () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7b39906f42b6 in ??? () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7b39905a2d19 in QSGNode::destroy() () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7b39905a2d43 in QSGNode::~QSGNode() () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7b39905a2f25 in QSGTransformNode::~QSGTransformNode() () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7b399067b57e in QQuickWindowPrivate::cleanupNodes() () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x7b399067ea73 in QQuickWindowPrivate::updateDirtyNodes() () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #11 0x7b3990680674 in QQuickWindowPrivate::syncSceneGraph() () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #12 0x7b399061931f in ??? () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #13 0x7b399061afec in ??? () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #14 0x7b399061c007 in ??? () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #15 0x7b398eedb674 in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7b398e69ca94 in start_thread (arg=) at ./nptl/pthread_create.c:447 #17 0x7b398e729c3c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 Thread 7 (Thread 0x7b3927e006c0 (LWP 31211) "QNetworkAccessM"): #1 0x7b398e6ec96d in __GI___clock_gettime (clock_id=, tp=) at ../sysdeps/unix/sysv/linux/clock_gettime.c:42 #2 0x7b398f134b79 in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7b398f1332b5 in QTimerInfoList::updateCurrentTime() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7b398f1338fa in QTimerInfoList::timerWait(timespec&) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7b398f13501d in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7b398d91489a in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7b398d9735ab in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7b398d913a53 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7b398f135296 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7b398f0d6a7b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7b398eeda36b in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7b398eedb674 in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7b398e69ca94 in start_thread (arg=) at ./nptl/pthread_create.c:447 #14 0x7b398e729c3c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 Thread 6 (Thread 0x7b3958c006c0 (LWP 31259) "QNetworkAccessM"): #1 0x7b398d97366e in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7b398d913a53 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7b398f135296 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7b398f0d6a7b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7b398eeda36b in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7b398eedb674 in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7b398e69ca94 in start_thread (arg=) at ./nptl/pthread_create.c:447 #8 0x7b398e729c3c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 Thread 5 (Thread 0x7b39258006c0 (LWP 31773) "QNetworkAccessM"): #1 0x7b398e6ec96d in __GI___clock_gettime (clock_id=, tp=) at ../sysdeps/unix/sysv/linux/clock_gettime.c:42 #2 0x7b398f134b79 in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7b398f1332b5 in QTimerInfoList::updateCurrentTime() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7b398f1338fa in QTimerInfoList::timerWait(timespec&) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7b398f13501d in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7b398d91489a in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7b398d9735ab in
[kolourpaint] [Bug 502039] New: app crashes after trying to copy hexadecimal color code
https://bugs.kde.org/show_bug.cgi?id=502039 Bug ID: 502039 Summary: app crashes after trying to copy hexadecimal color code Classification: Applications Product: kolourpaint Version: 24.12.3 Platform: Ubuntu OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kolourpaint-supp...@lists.sourceforge.net Reporter: rodrigo.lust...@usp.br Target Milestone: --- SUMMARY app crashes after trying to copy hexadecimal color code, or after double click on the color (after installation). STEPS TO REPRODUCE 1. Double click on a color 2. right click on the color 3. click in Customize 4. select the hexadecimal color code 5. copy it after reinstalling, the app is crashing in the first step OBSERVED RESULT The app crashes EXPECTED RESULT I should be able to copy the text SOFTWARE/OS VERSIONS (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: Ubuntu 22.04.5 LTS ADDITIONAL INFORMATION The app was installed via snap, and I wasn't able to generate Backtraces -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 502039] app crashes after trying to copy hexadecimal color code
https://bugs.kde.org/show_bug.cgi?id=502039 --- Comment #3 from Rodrigo --- (In reply to Martin Koller from comment #1) > can you add a screenshot of the dialog which opens after double-click, > please. > I have the feeling that this is a non-KDE dialog which might make the > problem... I see, thanks for your reply. There wasn't a dialog after double-click, the app just closes. But I opened the app through the terminal and made the double-click. I attached the screenshot of the terminal, does it help? -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 502039] app crashes after trying to copy hexadecimal color code
https://bugs.kde.org/show_bug.cgi?id=502039 --- Comment #2 from Rodrigo --- Created attachment 179913 --> https://bugs.kde.org/attachment.cgi?id=179913&action=edit terminal mesages after runing the app and the error mesage after crashing -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 451263] New: Ampache plugin doesn't work with ampache API 5 responses which renders it useless unless api version forced in ampache server
https://bugs.kde.org/show_bug.cgi?id=451263 Bug ID: 451263 Summary: Ampache plugin doesn't work with ampache API 5 responses which renders it useless unless api version forced in ampache server Product: amarok Version: 2.9.71 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: usability Severity: major Priority: NOR Component: Services/Ampache Assignee: amarok-bugs-d...@kde.org Reporter: rodrigoesbor...@gmail.com Target Milestone: kf5 SUMMARY *** Until very recently, and for about 1-2 years, I haven't been able to use amarok with ampache's collection plugin and my ampache server. It errored and Ampache collection returned empty on the UI. *** STEPS TO REPRODUCE 1. Open amarok -> Configure Amarok -> Plugins -> Ampache Collection Plugin 2. Add ampache server nick,URL , user and password 3. Restart ampache OBSERVED RESULT I get "reference error Qprocess not defined" as an error warning, and "handshakeaccount Invalid handshake received " wether using password or API key for any user of that ampache server. Empty collection EXPECTED RESULT Browsable collection and no error to login. OBSERVATION In some not very old update, AMPACHE allows to "force API version". Trying API v3 or API v4 still brings the Qprocess not defined error, but ampache's collection is retrieved and becomes usable and playable. SOFTWARE/OS VERSIONS Linux/KDE Plasma: customized openSuse Tumbleweed (available in About System) KDE Plasma Version: 5.22.90 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Amarok version: 2.9.71 (compiled 2022-02-24) ADDITIONAL INFORMATION Maybe related with https://bugs.kde.org/show_bug.cgi?id=396590 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440665] New: Plasma crashes when adding webslice plasmoid
https://bugs.kde.org/show_bug.cgi?id=440665 Bug ID: 440665 Summary: Plasma crashes when adding webslice plasmoid Product: plasmashell Version: 5.22.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: rodrigoesbor...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.22.4) Qt Version: 5.15.2 Frameworks Version: 5.84.0 Operating System: Linux 4.4.180-1.g7cfa20a-default x86_64 Windowing System: X11 Drkonqi Version: 5.22.4 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Added a webslice plasmoid to an activity - Unusual behavior I noticed: plasmashell crashes repeatedly closing and crashing on restarting again - Custom settings of the application: Webslice plasmoid installed; opensuse factory qt5/kf5/plasma packages The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7f185e8fe49e in QProcessPrivate::startProcess() (this=0x7f17e80046c0) at io/qprocess_unix.cpp:461 #5 0x7f185e8f9893 in QProcess::start(QString const&, QFlags) (this=0x7f17e80046a0, command=, mode=...) at io/qprocess.cpp:2352 #6 0x7f183e9e425e in WebKit::ProcessLauncher::launchProcess() () at ../Source/WebKit2/UIProcess/Launcher/qt/ProcessLauncherQt.cpp:202 #7 0x7f183d4c88f8 in std::function::operator()() const () at /usr/include/c++/10/bits/std_function.h:622 #8 WTF::WorkQueue::WorkItemQt::execute() () at ../Source/WTF/wtf/qt/WorkQueueQt.cpp:63 #9 WTF::WorkQueue::WorkItemQt::executeAndDelete() () at ../Source/WTF/wtf/qt/WorkQueueQt.cpp:68 #10 WTF::WorkQueue::WorkItemQt::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () at Source/WTF/wtf/WorkQueueQt.moc:76 #11 0x7f185e9b3f5e in QObject::event(QEvent*) (this=0x560960ab4f80, e=0x560960abd800) at kernel/qobject.cpp:1314 #12 0x7f185f713a7f in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x560960ab4f80, e=0x560960abd800) at kernel/qapplication.cpp:3632 #13 0x7f185e98796a in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x560960ab4f80, event=0x560960abd800) at kernel/qcoreapplication.cpp:1064 #14 0x7f185e98a9b7 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=0x0, event_type=0, data=0x560960ab8cf0) at kernel/qcoreapplication.cpp:1821 #15 0x7f185e9df7d3 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=s@entry=0x7f17e8004150) at kernel/qeventdispatcher_glib.cpp:277 #16 0x7f185ccab80f in g_main_dispatch (context=0x7f17e8000c20) at ../glib/gmain.c:3337 #17 g_main_context_dispatch (context=0x7f17e8000c20) at ../glib/gmain.c:4055 #18 0x7f185ccabb98 in g_main_context_iterate (context=context@entry=0x7f17e8000c20, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4131 #19 0x7f185ccabc4f in g_main_context_iteration (context=0x7f17e8000c20, may_block=1) at ../glib/gmain.c:4196 #20 0x7f185e9dee54 in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f17e8000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #21 0x7f185e98636b in QEventLoop::exec(QFlags) (this=this@entry=0x7f17f59fcb80, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #22 0x7f185e7a1c9e in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #23 0x7f185e7a2dd1 in QThreadPrivate::start(void*) (arg=0x560960a8e120) at thread/qthread_unix.cpp:329 #24 0x7f185d764259 in start_thread (arg=0x7f17f59fd640) at pthread_create.c:481 #25 0x7f185e3c32b3 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f17f61fe640 (LWP 9134) "plasmashell"): #1 0x7f185d770a3f in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x7f18373cb058, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ../sysdeps/nptl/futex-internal.c:123 #2 0x7f185d76a280 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f18373cb008, cond=0x7f18373cb030) at pthread_cond_wait.c:504 #3 __pthread_cond_wait (cond=0x7f18373cb030, mutex=0x7f18373cb008) at pthread_cond_wait.c:619 #4 0x7f185e56e0d0 in __gthread_cond_wait (__mutex=, __cond=) at /usr/src/debug/gcc11-11.1.1+git536-1.1.x86_64/obj-x86_64-suse-linux/x86_64-suse-linux/libstdc++-v3/include/x86_64-suse-linux/bits/gthr-default.h:865 #5 std::__condvar::wait(std::mutex&) (__m=, this=) at /usr/src/debug/gcc11-11.1.1+git536-1.1.x86_64/obj-x86_64-suse-linux/x86_64-suse-linux/libstdc++-v3/include/bits/std_mutex.h:155 #6 std::condition_variable::wait(std::unique_lock&) (t
[kdeconnect] [Bug 423683] remote input from laptop not working on Xubuntu
https://bugs.kde.org/show_bug.cgi?id=423683 Rodrigo Cacilhas changed: What|Removed |Added CC||batal...@cacilhas.info --- Comment #6 from Rodrigo Cacilhas --- I’m using Ubuntu 20.04, running i3, and I’m getting the a similar problem with KDE Connect: fish-3.1> kdeconnect-app QApplication: invalid style override passed, ignoring it. Available styles: Windows, Fusion QQmlApplicationEngine failed to load component qrc:/qml/main.qml:93 Cannot assign object of type "DevicesModel" to property of type "QAbstractItemModel*" as the former is neither the same as the latter nor a sub-class of it. Any chance of this bug being fixed someday? -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 362607] KTorrent default folder locations are changed to an incorrect path therefore ignored when opening .torrent files or magnet links
https://bugs.kde.org/show_bug.cgi?id=362607 --- Comment #3 from Rodrigo Orihuela --- Hello, I cannot provide further information since I no longer use KDE. Thank you for your time. On Thu, 20 Oct 2022 at 21:17, Justin Zobel wrote: > https://bugs.kde.org/show_bug.cgi?id=362607 > > Justin Zobel changed: > >What|Removed |Added > > > Resolution|--- |WAITINGFORINFO > Status|REPORTED|NEEDSINFO > > --- Comment #2 from Justin Zobel --- > Thank you for reporting this bug 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 "CONFIRMED" > when > replying. Thank you! > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 434415] New: Crash at update firewall policy from System Settings
https://bugs.kde.org/show_bug.cgi?id=434415 Bug ID: 434415 Summary: Crash at update firewall policy from System Settings Product: systemsettings Version: 5.21.2 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tecinfo.helpd...@yahoo.com Target Milestone: --- Application: systemsettings5 (5.21.2) Qt Version: 5.15.2 Frameworks Version: 5.80.0 Operating System: Linux 5.4.0-66-generic x86_64 Windowing System: X11 Drkonqi Version: 5.21.2 Distribution: KDE neon Testing Edition -- Information about the crash: - What I was doing when the application crashed: I was updating the firewall default policy (IN) from Ignore to reject. - Unusual behavior I noticed: The application (System Settings) closed unexpectedly. - Custom settings of the application: N/A The crash does not seem to be reproducible. -- Backtrace: Application: Configurações do sistema (systemsettings5), signal: Segmentation fault [New LWP 61680] [New LWP 61681] [New LWP 61686] [New LWP 61695] [New LWP 61706] [New LWP 61707] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f6ae99d3aff in __GI___poll (fds=0x7ffc088abae8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f6ae5790500 (LWP 61678))] Thread 7 (Thread 0x7f6ab5264700 (LWP 61707)): #0 0x7f6ae7ba1c63 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f6ae7ba2312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6ae7ba26f3 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6ab5b84f8a in ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7f6ae7bcbad1 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f6ae8561609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f6ae99e0293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f6ab5a65700 (LWP 61706)): #0 __GI___libc_read (nbytes=16, buf=0x7f6ab5a64c20, fd=34) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=34, buf=0x7f6ab5a64c20, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f6ae7beab2f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6ae7ba1ebe in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f6ae7ba2312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f6ae7ba24a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f6ae7ba24f1 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f6ae7bcbad1 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f6ae8561609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f6ae99e0293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f6abec87700 (LWP 61695)): #0 __GI___libc_read (nbytes=16, buf=0x7f6abec86ab0, fd=26) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=26, buf=0x7f6abec86ab0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f6ae7beab2f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6ae7ba1ebe in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f6ae7ba2312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f6ae7ba24a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f6aea0edffb in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f6aea0921eb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f6ae9eaca52 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f6ae91a1fa9 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #10 0x7f6ae9eadbec in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f6ae8561609 in start_thread (arg=) at pthread_create.c:477 #12 0x7f6ae99e0293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f6ad4eaa700 (LWP 61686)): #0 0x7f6ae7bef4dd in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f6ae7ba18fa in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6ae7ba229b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6ae7ba24a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f6aea0edffb in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6aea0921eb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f6ae9eaca52 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f6ae91a1fa9 in ?? () from /lib/x8
[frameworks-kwallet] [Bug 434480] New: API to query if password exists without triggering Wallet creation and its GUI
https://bugs.kde.org/show_bug.cgi?id=434480
Bug ID: 434480
Summary: API to query if password exists without triggering
Wallet creation and its GUI
Product: frameworks-kwallet
Version: unspecified
Platform: Ubuntu Packages
OS: All
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: va...@kde.org
Reporter: k...@rodrigosilva.com
CC: kdelibs-b...@kde.org
Target Milestone: ---
This is an API request that could solve an issue in
[Keyring](https://github.com/jaraco/keyring), the most widely used python
keyring library, and perhaps other similar libraries/clients.
Consider the following scenario, as described in this [bug
report](https://github.com/jaraco/keyring/issues/496):
- Gnome Shell user, KWallet was pulled as dependency of some installed KDE
utility but never actually used.
- Keyring, when asked for a (non-existing) password, looks for it in every
registered backend, including KWallet.
- Some DBus calls are made to _query_ if a password exists in KWallet:
- opening `org.kde.kwalletd5/modules/kwalletd5.networkWallet()` DBus
interface
- `.hasEntry()` to check if password exists (in this example, it doesn't)
- if hasEntry succeeds, `.readPassword()` to finally get the data.
Since no Wallet exists, KWalled pops up its Wallet Creation GUI! A very
undesirable side-effect when merely querying for password existence. After all,
if there is no Wallet then `.hasEntry()` could (should?) have short-circuited
to say **no**.
Either approach could solve that problem:
- `.networkWallet()`/`.hasEntry()` could _not_ trigger Wallet creation, either
by default (preferable) or by a `create=False` flag parameter, that could
default to `True` to preserve backward-compatibility with current behavior.
- A method/interface that allow clients to probe if Wallet infrastructure
exists prior to issuing `.networkWallet()`/`.hasEntry()`. Is there any such
method already?
Relevant (python) code that trigger the undesirable wallet creation GUI, if
that helps:
https://github.com/jaraco/keyring/blob/02f341401df8063e0a962ddc4fe73c06e59068a3/keyring/backends/kwallet.py#L89-L116
```python
def connected(self, service):
if self.handle >= 0:
if self.iface.isOpen(self.handle):
return True
bus = dbus.SessionBus(mainloop=DBusGMainLoop())
wId = 0
try:
remote_obj = bus.get_object(self.bus_name, self.object_path)
self.iface = dbus.Interface(remote_obj, 'org.kde.KWallet')
self.handle = self.iface.open(self.iface.networkWallet(), wId,
self.appid)
except dbus.DBusException as e:
raise InitError('Failed to open keyring: %s.' % e)
if self.handle < 0:
return False
self._migrate(service)
return True
def get_password(self, service, username):
"""Get password of the username for the service"""
if not self.connected(service):
# the user pressed "cancel" when prompted to unlock their keyring.
raise KeyringLocked("Failed to unlock the keyring!")
if not self.iface.hasEntry(self.handle, service, username, self.appid):
return None
password = self.iface.readPassword(self.handle, service, username,
self.appid)
return str(password)
```
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 434415] Crash at update firewall policy from System Settings
https://bugs.kde.org/show_bug.cgi?id=434415 Rodrigo Paiva changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|DUPLICATE |--- --- Comment #3 from Rodrigo Paiva --- Thanks everyone. I applied updates on my system and now the KDE Frameworks version is 5.81.0 - Operating System: KDE neon Testing Edition KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 Kernel Version: 5.4.0-67-generic OS Type: 64-bit - How can I compile and test if master crashes? Help-me about it, please. :) Tnx -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 398277] kubuntu 18.04.1 dolphin pdf thumbnail viewer bug
https://bugs.kde.org/show_bug.cgi?id=398277 --- Comment #5 from rodrigo tyrone --- (In reply to Alex Cherepanov from comment #4) > Perhaps, "Advanced Backend Code Optimization" file includes 2 pages per > frame. Little can be done about this bug without your sample file. no "Advanced Backend Code Optimization" is single paged i checked. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 420973] New: Crash while browsing django-bower based site just after authenticating
https://bugs.kde.org/show_bug.cgi?id=420973 Bug ID: 420973 Summary: Crash while browsing django-bower based site just after authenticating Product: Falkon Version: 3.1.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: now...@gmail.com Reporter: rodrigoesbor...@gmail.com Target Milestone: --- Application: falkon (3.1.0) Qt Version: 5.14.1 Frameworks Version: 5.69.0 Operating System: Linux 4.12.14-318.g9869ead-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: Had several tabs opened, two of them with the same site, one auth as normal user/part ; the other one just auth with admin user in admi section Recently downgraded kernel in order to use GPU HW acceleration features, not sure if it might be related (don't remember seeing same falkon version crash before downgrading) -- Backtrace: Application: Falkon (falkon), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f705be46f00 (LWP 8371))] Thread 30 (Thread 0x7f6fd237d700 (LWP 10580)): #0 0x7f706285baaa in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f7065ee1a86 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x0594 in () #3 0x186c99b5 in () #4 0x0573 in () #5 0x186c9d9d in () #6 0x in () Thread 29 (Thread 0x7f7031ffb700 (LWP 9006)): #0 0x7f706285baaa in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f7065ee1a86 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x05ad in () #3 0x142c9d3b in () #4 0x058c in () #5 0x142ca50b in () #6 0x in () Thread 28 (Thread 0x7f7033fff700 (LWP 8461)): #0 0x7f706af60f59 in syscall () at /lib64/libc.so.6 #1 0x7f706b2da841 in QSemaphore::acquire(int) () at /usr/lib64/libQt5Core.so.5 #2 0x7f706316a9a4 in () at /usr/lib64/libQt5Network.so.5 #3 0x7f706b2d8698 in () at /usr/lib64/libQt5Core.so.5 #4 0x7f7062854efa in start_thread () at /lib64/libpthread.so.0 #5 0x7f706af663bf in clone () at /lib64/libc.so.6 Thread 27 (Thread 0x7f6fd0b7a700 (LWP 8460)): #0 0x7f706af5bacf in poll () at /lib64/libc.so.6 #1 0x7f706206a9de in g_main_context_poll (priority=, n_fds=1, fds=0x7f6fb4000b60, timeout=, context=0x7f6fb4030a60) at ../glib/gmain.c:4346 #2 0x7f706206a9de in g_main_context_iterate (context=context@entry=0x7f6fb4030a60, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4042 #3 0x7f706206aaff in g_main_context_iteration (context=0x7f6fb4030a60, may_block=1) at ../glib/gmain.c:4108 #4 0x7f706b504beb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f706b4acb7b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f706b2d75ce in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f706b2d8698 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f7062854efa in start_thread () at /lib64/libpthread.so.0 #9 0x7f706af663bf in clone () at /lib64/libc.so.6 Thread 26 (Thread 0x7f6fd37fe700 (LWP 8433)): #0 0x7f706285b795 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f7065ee198c in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x in () Thread 25 (Thread 0x7f6fd3fff700 (LWP 8432)): #0 0x7f706285baaa in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f70530ed3a4 in () at /usr/lib64/libnvidia-glcore.so.440.33.01 #2 0x7f7052ee03d0 in () at /usr/lib64/libnvidia-glcore.so.440.33.01 #3 0x7f7052ee0e22 in () at /usr/lib64/libnvidia-glcore.so.440.33.01 #4 0x7f70530ec57c in () at /usr/lib64/libnvidia-glcore.so.440.33.01 #5 0x7f7062854efa in start_thread () at /lib64/libpthread.so.0 #6 0x7f706af663bf in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7f6ff4ff9700 (LWP 8431)): #0 0x7f706285baaa in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f70530ed3a4 in () at /usr/lib64/libnvidia-glcore.so.440.33.01 #2 0x7f705315efcc in () at /usr/lib64/libnvidia-glcore.so.440.33.01 #3 0x7f7052ee0ecd in () at /usr/lib64/libnvidia-glcore.so.440.33.01 #4 0x7f70530ec57c in () at /usr/lib64/libnvidia-glcore.so.440.33.01 #5 0x7f7062854efa in start_thread () at /lib64/libpthread.so.0 #6 0x7f706af663bf in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7f6ff57fa700 (LWP 8430)): #0 0x7f706285baaa in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f70530ed3a4 in () at /usr/lib64/libnvidia-glcore.so.440.33.01 #2 0x7f705315efcc in () at /usr/lib64/lib
[kdevelop] [Bug 397045] Kdevelop crashes when parsing starts [clang::Decl::setInvalidDecl]
https://bugs.kde.org/show_bug.cgi?id=397045 --- Comment #3 from Rodrigo Fernandes --- Created attachment 114505 --> https://bugs.kde.org/attachment.cgi?id=114505&action=edit New crash information added by DrKonqi kdevelop (5.2.3) using Qt 5.11.1 - What I was doing when the application crashed: Importing a CMakeLists clone of https://gitlab.com/swirlycloud/swirly-cpp -- Backtrace (Reduced): #6 0x7f50881d2450 in clang::Decl::setInvalidDecl(bool) () at /usr/lib/../lib/libclangAST.so.6 #7 0x7f50881d249c in clang::Decl::setInvalidDecl(bool) () at /usr/lib/../lib/libclangAST.so.6 #8 0x7f5081284bc8 in clang::ASTDeclReader::VisitDecl(clang::Decl*) () at /usr/lib/../lib/../lib/libclangSerialization.so.6 #9 0x7f5081285482 in clang::ASTDeclReader::VisitNamedDecl(clang::NamedDecl*) () at /usr/lib/../lib/../lib/libclangSerialization.so.6 #10 0x7f5081285982 in clang::ASTDeclReader::VisitValueDecl(clang::ValueDecl*) () at /usr/lib/../lib/../lib/libclangSerialization.so.6 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 397045] Kdevelop crashes when parsing starts [clang::Decl::setInvalidDecl]
https://bugs.kde.org/show_bug.cgi?id=397045 Rodrigo Fernandes changed: What|Removed |Added CC||rfernan...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 403472] New: Amarok random crashing on Plasma 5
https://bugs.kde.org/show_bug.cgi?id=403472 Bug ID: 403472 Summary: Amarok random crashing on Plasma 5 Product: amarok Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: rodrigoesbor...@gmail.com Target Milestone: kf5 Application: amarok (2.9.70) Qt Version: 5.12.0 Frameworks Version: 5.53.0 Operating System: Linux 4.19.11-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Amarok is crashing randomly, this time the crash ocurred while dragging filtered songs to add/replace a playlist The crash can be reproduced sometimes. -- Backtrace: Application: Amarok (amarok), signal: Bus error Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff6d53c3980 (LWP 8041))] Thread 23 (Thread 0x7ff666006700 (LWP 8080)): #0 0x7ff6dbfeb2c9 in poll () at /lib64/libc.so.6 #1 0x7ff6d85f6f46 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7ff6d85f706c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7ff6dc71b88b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7ff6dc6c602b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7ff6dc5103b6 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7ff6dc511702 in () at /usr/lib64/libQt5Core.so.5 #7 0x7ff6da381554 in start_thread () at /lib64/libpthread.so.0 #8 0x7ff6dbff5ccf in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7ff6676ba700 (LWP 8076)): #0 0x7ff6dbfe6d34 in read () at /lib64/libc.so.6 #1 0x7ff6d863ca00 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7ff6d85f6a4b in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7ff6d85f6ef0 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7ff6d85f706c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7ff6dc71b88b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7ff6dc6c602b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7ff6dc5103b6 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7ff6dabe4f25 in () at /usr/lib64/libQt5Qml.so.5 #9 0x7ff6dc511702 in () at /usr/lib64/libQt5Core.so.5 #10 0x7ff6da381554 in start_thread () at /lib64/libpthread.so.0 #11 0x7ff6dbff5ccf in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7ff667fff700 (LWP 8075)): #0 0x7ff6dbfe6d34 in read () at /lib64/libc.so.6 #1 0x7ff6d863ca00 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7ff6d85f6a4b in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7ff6d85f6ef0 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7ff6d85f706c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7ff6dc71b88b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7ff6dc6c602b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7ff6dc5103b6 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7ff6dc511702 in () at /usr/lib64/libQt5Core.so.5 #9 0x7ff6da381554 in start_thread () at /lib64/libpthread.so.0 #10 0x7ff6dbff5ccf in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7ff688ff9700 (LWP 8066)): #0 0x7ff6da3874dc in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff6dc517633 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7ff6dc517719 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #3 0x7ff6da5ae800 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7ff6da5b2538 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7ff6da5ad90d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7ff6da5b2592 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7ff6da5ad90d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7ff6da5b2592 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #9 0x7ff6da5ad90d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #10 0x7ff6da5b2592 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #11 0x7ff6da5ad90d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #12 0x7ff6da5b2592 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #13 0x7ff6da5ad90d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #14
[amarok] [Bug 403473] New: Amarok crashes when clicking on diagnostics
https://bugs.kde.org/show_bug.cgi?id=403473 Bug ID: 403473 Summary: Amarok crashes when clicking on diagnostics Product: amarok Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: rodrigoesbor...@gmail.com Target Milestone: kf5 Application: amarok (2.9.70) Qt Version: 5.12.0 Frameworks Version: 5.53.0 Operating System: Linux 4.19.11-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: Tried to use diagnostics in Amarok , clicking on that option produced the crash. I needed to diagnose why amarok couldn't play anything. The crash can be reproduced sometimes. -- Backtrace: Application: Amarok (amarok), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3fb1df1980 (LWP 9135))] Thread 25 (Thread 0x7f3f2e3fc700 (LWP 9517)): #0 0x7f3fb8a192c9 in poll () at /lib64/libc.so.6 #1 0x7f3fb5024f46 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f3fb50252d2 in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0 #3 0x7f3fa70e5b16 in () at /usr/lib64/libgio-2.0.so.0 #4 0x7f3fb504d476 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7f3fb6daf554 in start_thread () at /lib64/libpthread.so.0 #6 0x7f3fb8a23ccf in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7f3f2ebfd700 (LWP 9516)): #0 0x7f3fb8a14d34 in read () at /lib64/libc.so.6 #1 0x7f3fb506aa00 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f3fb5024a4b in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f3fb5024ef0 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f3fb502506c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f3f361a902d in () at /usr/lib64/gio/modules/libdconfsettings.so #6 0x7f3fb504d476 in () at /usr/lib64/libglib-2.0.so.0 #7 0x7f3fb6daf554 in start_thread () at /lib64/libpthread.so.0 #8 0x7f3fb8a23ccf in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7f3f2f3fe700 (LWP 9515)): #0 0x7f3fb506bd89 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f3fb5024681 in g_main_context_query () at /usr/lib64/libglib-2.0.so.0 #2 0x7f3fb5024ec7 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f3fb502506c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f3fb50250b1 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7f3fb504d476 in () at /usr/lib64/libglib-2.0.so.0 #6 0x7f3fb6daf554 in start_thread () at /lib64/libpthread.so.0 #7 0x7f3fb8a23ccf in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7f3f42a34700 (LWP 9196)): #0 0x7f3fb8a14d34 in read () at /lib64/libc.so.6 #1 0x7f3fb506aa00 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f3fb5024a4b in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f3fb5024ef0 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f3fb502506c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f3fb914988b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f3fb90f402b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f3fb8f3e3b6 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f3fb8f3f702 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f3fb6daf554 in start_thread () at /lib64/libpthread.so.0 #10 0x7f3fb8a23ccf in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7f3f43fff700 (LWP 9193)): #0 0x7f3fb8a192c9 in poll () at /lib64/libc.so.6 #1 0x7f3fb5024f46 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f3fb502506c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f3fb914988b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f3fb90f402b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f3fb8f3e3b6 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f3fb7612f25 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f3fb8f3f702 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f3fb6daf554 in start_thread () at /lib64/libpthread.so.0 #9 0x7f3fb8a23ccf in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7f3f58b6b700 (LWP 9192)): #0 0x7f3fb8a3189a in clock_gettime () at /lib64/libc.so.6 #1 0x7f3fb91491a1 in () at /usr/lib64/libQt5Core.so.5 #2 0x7f3fb91479e9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #3 0x7f3fb9147fe5 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #4 0x7f3fb91495fe in () at /usr/lib64/libQt5Core.so.5 #5 0x7f3fb5024499 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #6 0x7f3fb5024e7b in () at /usr/lib64/libglib-2.0.so.0 #7 0x7f3fb502506c in g_main_context_iteration () at /us
[dolphin] [Bug 398277] New: kubuntu 18.04.1 dolphin pdf thumbnail viewer bug
https://bugs.kde.org/show_bug.cgi?id=398277 Bug ID: 398277 Summary: kubuntu 18.04.1 dolphin pdf thumbnail viewer bug Product: dolphin Version: 18.04.1 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: rodrigotyrone1...@gmail.com Target Milestone: --- Created attachment 114787 --> https://bugs.kde.org/attachment.cgi?id=114787&action=edit dolphin pdf thumnail bug Ever since i migrated to kde (kubuntu) i been experiencing a letdown in dolphin.Some of my pdf documents appear double paned on the saved thumbnail.As you can see in my attached photo, look very closely at the file manager and see dolphins faults(the pdf document named "Advanced Backend Code Optimization").I checked google and nobody has been experiencing this so i guess im the only person.The daunting reality is that i went to the kubuntu irc support channel and to my knowledge nobody to their humanity had experience with another dolphin thumbnail viewer, so as a beginner to kde can anybody help fix this bug so no other person go through hardship like i have been facing? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 385768] segfault on parsing project: in clang::Decl::setInvalidDecl(bool) () from /usr/lib64/llvm/5/lib64/../lib64/libclangAST.so.5
https://bugs.kde.org/show_bug.cgi?id=385768 Rodrigo Fernandes changed: What|Removed |Added CC||rfernan...@gmx.com --- Comment #8 from Rodrigo Fernandes --- This bug renders KDevelop unusable for me, as most projects I deal with now a days are C++17, and it would be unfeasable to manually add each of the offending files to the filter. Is there any way to set the parser to c++17 mode so the nullptr deref doesn't happen? Happy to dig submit patches to either Kdevelop / Clang to help remediate this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385886] New: Right clicking on a menu item and immediately right clicking somewhere else will show the menu item's contextual menu and not the contextual menu of the clicked element
https://bugs.kde.org/show_bug.cgi?id=385886 Bug ID: 385886 Summary: Right clicking on a menu item and immediately right clicking somewhere else will show the menu item's contextual menu and not the contextual menu of the clicked element Product: plasmashell Version: 5.11.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: rodrigo.peloro...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 I could reproduce this in Gwenview and Dolphin. To reproduce in Dolphin: - Left click on the File menu - Right click anywhere but the top menu bar (an file or the white space between files) Result: The contextual menu for the File menu item will appear. I have recorded a video of such behavior here: https://youtu.be/DbEDLj2ptPo -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 385892] New: Sound not working
https://bugs.kde.org/show_bug.cgi?id=385892 Bug ID: 385892 Summary: Sound not working Product: kalarm Version: 2.11 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: djar...@kde.org Reporter: rodrigo.alons...@gmail.com Target Milestone: --- Created attachment 108421 --> https://bugs.kde.org/attachment.cgi?id=108421&action=edit Console output When setting an audio alarm, there is no sound, even though the interface reacts as if there was. Audio works otherwise normally in KDE, in fact I can listen an audio file from the preview button in the file dialog window but not when clicking on the Try button nor when triggering the actual alarm. How to reproduce: I had previously set a command alarm. I opened KAlarm from the console, clicked on create audio alarm, manually wrote the path to an existing OGG file, then clicked on "Try" (to the left of OK/Accept) and nothing happened (other than the `QObject::connect: Cannot...` logs onwards) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 373872] New: error kde virtualbox
https://bugs.kde.org/show_bug.cgi?id=373872 Bug ID: 373872 Summary: error kde virtualbox Product: kwin Version: 5.8.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: rodlinux...@gmail.com Target Milestone: --- Application: kwin_x11 (5.8.4) Qt Version: 5.7.0 Frameworks Version: 5.28.0 Operating System: Linux 4.4.38-1-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: - What I was doing when the application crashed: Estaba usando virtualbox cuando mando un error, de hecho estaba configurando una maquina virtual Esperemos que la informacion les sirva -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd4efbc2840 (LWP 977))] Thread 5 (Thread 0x7fd4bf7ff700 (LWP 1628)): #0 0x7fd4eccb0345 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #1 0x7fd4ecc5d24a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #2 0x7fd4eca800f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #3 0x7fd4e75f62d5 in () at /usr/lib/libQt5Qml.so.5 #4 0x7fd4eca84d78 in () at /usr/lib/libQt5Core.so.5 #5 0x7fd4e8898454 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fd4ef60a7df in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7fd4b7fff700 (LWP 1128)): #0 0x7fd4e889e10f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fd4ebbf4ac4 in () at /usr/lib/libQt5Script.so.5 #2 0x7fd4ebbf4b09 in () at /usr/lib/libQt5Script.so.5 #3 0x7fd4e8898454 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fd4ef60a7df in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7fd4cca73700 (LWP 1123)): #0 0x7fd4ef601551 in ppoll () at /usr/lib/libc.so.6 #1 0x7fd4eccaead9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fd4eccb03c8 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fd4ecc5d24a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fd4eca800f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fd4e75f62d5 in () at /usr/lib/libQt5Qml.so.5 #6 0x7fd4eca84d78 in () at /usr/lib/libQt5Core.so.5 #7 0x7fd4e8898454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fd4ef60a7df in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7fd4cf19b700 (LWP 1041)): #0 0x7fd4ef601551 in ppoll () at /usr/lib/libc.so.6 #1 0x7fd4eccaead9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fd4eccb03c8 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fd4ecc5d24a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fd4eca800f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fd4e67c0e55 in () at /usr/lib/libQt5DBus.so.5 #6 0x7fd4eca84d78 in () at /usr/lib/libQt5Core.so.5 #7 0x7fd4e8898454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fd4ef60a7df in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7fd4efbc2840 (LWP 977)): [KCrash Handler] #6 0x8028 in () #7 0x7fd4ecc90d00 in QObject::connect(QObject const*, char const*, QObject const*, char const*, Qt::ConnectionType) () at /usr/lib/libQt5Core.so.5 #8 0x7fd4ebc36f6f in () at /usr/lib/libQt5Script.so.5 #9 0x7fd4ebc37034 in () at /usr/lib/libQt5Script.so.5 #10 0x7fd4ebc372b2 in QScriptEngine::newQObject(QObject*, QScriptEngine::ValueOwnership, QFlags const&) () at /usr/lib/libQt5Script.so.5 #11 0x7fd4ef20b97c in () at /usr/lib/libkwin.so.5 #12 0x7fd4ebc37565 in () at /usr/lib/libQt5Script.so.5 #13 0x7fd4ebc5ffb6 in () at /usr/lib/libQt5Script.so.5 #14 0x7fd4ebc68281 in () at /usr/lib/libQt5Script.so.5 #15 0x7fd4ecc8a804 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #16 0x7fd4ec43ffc8 in KWin::EffectsHandler::desktopPresenceChanged(KWin::EffectWindow*, int, int) () at /usr/lib/libkwineffects.so.9 #17 0x7fd4ec441981 in () at /usr/lib/libkwineffects.so.9 #18 0x7fd4ecc8b4c9 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #19 0x7fd4ed93ee0c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #20 0x7fd4ed946581 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #21 0x7fd4ecc5edf0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #22 0x7fd4ecc6157d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #23 0x7fd4eccb020a in QEve
[amarok] [Bug 384748] New: Amarok crash on opening
https://bugs.kde.org/show_bug.cgi?id=384748 Bug ID: 384748 Summary: Amarok crash on opening Product: amarok Version: 2.8.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: rodrigoesbor...@gmail.com Target Milestone: 2.9 Application: amarok (2.8.0) KDE Platform Version: 4.14.35 Qt Version: 4.8.7 Operating System: Linux 4.12.9-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: Whenever trying to open Amarok from KDE or Gnome, amarok crashes and doesn't start The crash can be reproduced every time. -- Backtrace: Application: Amarok (amarok), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4d29858380 (LWP 25850))] Thread 4 (Thread 0x7f4cfb221700 (LWP 25929)): #0 0x7f4d2502659d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4cfcb94b6b in blas_thread_server () at /usr/lib64/libopenblas_pthreads.so.0 #2 0x7f4d250202f8 in start_thread () at /lib64/libpthread.so.0 #3 0x7f4d2649a5ef in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f4cfba22700 (LWP 25928)): #0 0x7f4d2502659d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4cfcb94b6b in blas_thread_server () at /usr/lib64/libopenblas_pthreads.so.0 #2 0x7f4d250202f8 in start_thread () at /lib64/libpthread.so.0 #3 0x7f4d2649a5ef in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f4cfc223700 (LWP 25927)): #0 0x7f4d2502659d in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4cfcb94b6b in blas_thread_server () at /usr/lib64/libopenblas_pthreads.so.0 #2 0x7f4d250202f8 in start_thread () at /lib64/libpthread.so.0 #3 0x7f4d2649a5ef in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f4d29858380 (LWP 25850)): [KCrash Handler] #6 0x7f4cf1e09867 in QMetaObject::className() const () at /usr/lib64/libQt5Core.so.5 #7 0x7f4cf2f8b207 in () at /usr/lib64/libQt5Widgets.so.5 #8 0x7f4cf2f2f3b7 in () at /usr/lib64/libQt5Widgets.so.5 #9 0x7f4d296dd4ea in call_init.part () at /lib64/ld-linux-x86-64.so.2 #10 0x7f4d296dd5f6 in _dl_init () at /lib64/ld-linux-x86-64.so.2 #11 0x7f4d296e1a7e in dl_open_worker () at /lib64/ld-linux-x86-64.so.2 #12 0x7f4d264d60d4 in _dl_catch_error () at /lib64/libc.so.6 #13 0x7f4d296e1299 in _dl_open () at /lib64/ld-linux-x86-64.so.2 #14 0x7f4d206def26 in dlopen_doit () at /lib64/libdl.so.2 #15 0x7f4d264d60d4 in _dl_catch_error () at /lib64/libc.so.6 #16 0x7f4d206df5f5 in _dlerror_run () at /lib64/libdl.so.2 #17 0x7f4d206defb1 in dlopen@@GLIBC_2.2.5 () at /lib64/libdl.so.2 #18 0x7f4d052545f0 in () at /usr/lib64/libvlccore.so.8 #19 0x7f4d051cd074 in () at /usr/lib64/libvlccore.so.8 #20 0x7f4d051ccf22 in () at /usr/lib64/libvlccore.so.8 #21 0x7f4d051cd371 in () at /usr/lib64/libvlccore.so.8 #22 0x7f4d051cd8f3 in () at /usr/lib64/libvlccore.so.8 #23 0x7f4d051b4b44 in libvlc_InternalInit () at /usr/lib64/libvlccore.so.8 #24 0x7f4d04f7b94e in libvlc_new () at /usr/lib64/libvlc.so.5 #25 0x7f4d054ddca9 in () at /usr/lib64/kde4/plugins/phonon_backend/phonon_vlc.so #26 0x7f4d054c3228 in () at /usr/lib64/kde4/plugins/phonon_backend/phonon_vlc.so #27 0x7f4d054c3dab in qt_plugin_instance () at /usr/lib64/kde4/plugins/phonon_backend/phonon_vlc.so #28 0x7f4d26c5577d in QPluginLoader::instance() () at /usr/lib64/libQtCore.so.4 #29 0x7f4d06579c88 in () at /usr/lib64/kde4/plugins/phonon_platform/kde.so #30 0x7f4d0657a56b in () at /usr/lib64/kde4/plugins/phonon_platform/kde.so #31 0x7f4d25eb2df9 in Phonon::FactoryPrivate::createBackend() () at /usr/lib64/libphonon.so.4 #32 0x7f4d25eb3600 in Phonon::Factory::backend(bool) () at /usr/lib64/libphonon.so.4 #33 0x7f4d25eb3b62 in Phonon::Factory::createAudioOutput(QObject*) () at /usr/lib64/libphonon.so.4 #34 0x7f4d25eab12f in Phonon::AudioOutputPrivate::createBackendObject() () at /usr/lib64/libphonon.so.4 #35 0x7f4d25ea89ee in Phonon::AudioOutputPrivate::init(Phonon::Category) () at /usr/lib64/libphonon.so.4 #36 0x7f4d2925fb5f in EngineController::initializePhonon() () at /usr/lib64/libamaroklib.so.1 #37 0x7f4d292672b5 in () at /usr/lib64/libamaroklib.so.1 #38 0x7f4d26c7b8cb in QMetaMethod::invoke(QObject*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) const () at /usr/lib64/libQtCore.so.4 #39 0x7f4d26c7ceba in QMetaObject::invokeMethod(QObject*, char const*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgumen
[plasmashell] [Bug 424485] GDbus-DBusMenu-Proxy does not work for GTK Wayland apps
https://bugs.kde.org/show_bug.cgi?id=424485 Rodrigo Gonçalves changed: What|Removed |Added CC||keitar...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 506977] Color schemes and month/day translations in Xubuntu
https://bugs.kde.org/show_bug.cgi?id=506977 --- Comment #3 from Rodrigo Farías --- Thanks for your answer. I know that version 5.4 is old. Excuse me to make the following consultation, but I have not found a Korganizer forum where to ask and I am an end user with few knowledge. Is there any way to obtain the most recent versions? (.deb, Snap, Appimage, Flathub). The only way I have been able to install is through APT, and there the version is 5.4. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 506977] New: Color schemes and month/day translations in Xubuntu
https://bugs.kde.org/show_bug.cgi?id=506977 Bug ID: 506977 Summary: Color schemes and month/day translations in Xubuntu Classification: Applications Product: korganizer Version First 5.24.5 Reported In: Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: rodr...@ffr.cl Target Milestone: --- Created attachment 183193 --> https://bugs.kde.org/attachment.cgi?id=183193&action=edit image of color scheme submenu I had previously installed Korganizer on another PC (unfortunately I don't remember what distribution or version). Now I installed it in my Xubuntu 24.04 through "sudo apt install korganizer". There are two differences that I can't solve. 1. There is no list of color schemes. It only has in "default" scheme. I would like to select the dark theme, as I had before. 2. The entire application interface is correctly in Spanish. However, the names of the months and days remain in English. Thanks -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 506977] Color schemes and month/day translations in Xubuntu
https://bugs.kde.org/show_bug.cgi?id=506977 --- Comment #1 from Rodrigo Farías --- Created attachment 183194 --> https://bugs.kde.org/attachment.cgi?id=183194&action=edit image of non translated month -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 462931] No metadata URIs for vendor directory
https://bugs.kde.org/show_bug.cgi?id=462931 Rodrigo Pedra Brum changed: What|Removed |Added Status|RESOLVED|REOPENED CC||rodrigo.pe...@gmail.com Resolution|WORKSFORME |--- Ever confirmed|0 |1 --- Comment #6 from Rodrigo Pedra Brum --- I also have the exact same issue on OpenSUSE Tumbleweed. Updating from terminal using zypper works without any messages. When searching to solve this I found the Stack Overflow answer below asking the user to change some configuration on Discover. Unfortunately, this configuration is not available to me. https://askubuntu.com/questions/1444178/kubuntu-update-yeilds-no-metadata-uris-for-vendor-directory For reference easiness, I will paste the steps given in the answer here, I don't have the "Advanced button" on my Discover installation, nor any option similar to those on the answer neither in Discover nor on the Settings app. > You can try the following steps if you want to use "Discover" to install > updates. > > - Open Discover and go to the Updates tab. > - In the Updates tab, click on the Settings button in the top right corner of > the window. > - In the Settings window, go to the "Updates" section and click on the > "Advanced" button. > - In the Advanced settings window, go to the "Metadata" section and check the > "Use vendor-provided metadata" option. > - Click on the "Apply" button to save your changes and close the Settings > window. In one of the comments on the answer above, a user said they also don't have this configuration option but managed to fix it by reinstalling WINE, after comparing its apt source files to another installation where the message was absent. I don't have WINE installed, and I can't tell how I could verify the repos about this on OpenSUSE -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 462931] No metadata URIs for vendor directory
https://bugs.kde.org/show_bug.cgi?id=462931 --- Comment #7 from Rodrigo Pedra Brum --- Created attachment 156337 --> https://bugs.kde.org/attachment.cgi?id=156337&action=edit Screencast showcasing the unexpected error message Screencast showcasing the unexpected "no metadata URIs for vendor-directory" error message -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 462931] "No metadata URIs for vendor directory" error seen in Discover
https://bugs.kde.org/show_bug.cgi?id=462931 --- Comment #11 from Rodrigo Pedra Brum --- (In reply to Nate Graham from comment #10) > Sure, we can move the bug report to Neon. But anyone else who had this issue > on another distro needs to submit a bug for their distro. Hey Nathan, thanks for the reply! Regarding the screen mentioned on SO here > - In the Settings window, go to the "Updates" section and click on the > "Advanced" button. > - In the Advanced settings window, go to the "Metadata" section and check the > "Use vendor-provided metadata" option. Do you happen to know if these screens were added by a particular distro, or if they should be available on every Discover install? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 462931] "No metadata URIs for vendor directory" error seen in Discover
https://bugs.kde.org/show_bug.cgi?id=462931 --- Comment #13 from Rodrigo Pedra Brum --- (In reply to Nate Graham from comment #12) > Yes, that UI is distro-specific. Discover includes a button to open it if > it's present; not all distros ship a config UI to tweak packaging stuff. OK, thanks for the reply =) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 462931] "No metadata URIs for vendor directory" error seen in Discover
https://bugs.kde.org/show_bug.cgi?id=462931 --- Comment #14 from Rodrigo Pedra Brum --- Created attachment 156408 --> https://bugs.kde.org/attachment.cgi?id=156408&action=edit discover settings page highlighting vendor directory checkbox I thought it was weird two different distros, from different Linux "lineage" (sorry, couldn't find a better word), to have the exact same error message. After some more research, I found a bug report on Arch bug tracker where the user ran `plasma-dsicover-update` from their terminal. I ran in mine and had the following output ```bash $ plasma-discover-update fetch ratings! false adding empty sources model QStandardItemModel(0x55d272279b60) QCommandLineParser: option not defined: "feedback" Fwupd Error 10 no metadata URIs for vendor-directory no component found for "org.opensuse.opensuse-tumbleweed" ready 0 steady 0 No updates available, exiting ``` Which hinted the problem to be with `fwupd`. I ended up disabling the "vendor directory" checkbox on Discover's settings page, under the "Firmware Updates" section, and the message is gone. (see attached image) Of course this is not an optimal solution, but could give someone else a hint. I know `fwupd` is about hardware firmware updates from LVFS. The "vendor directory" checkbox is what is not yet clear to me, but I'll keep looking around. I'd appreciate if someone knows better about how `fwupd` works, and what this "vendor directory" could be. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 462931] "No metadata URIs for vendor directory" error seen in Discover
https://bugs.kde.org/show_bug.cgi?id=462931 --- Comment #15 from Rodrigo Pedra Brum --- Looking into `/etc/fwupd/remotes.d` I have two files called `vendor.conf` and `vendor-directory.conf`. In both files, I have a key-pair `Enabled=false` (they were already like this). They also have these key-pair for their MetadataURI property: - vendor.conf MetadataURI=file:///usr/share/fwupd/remotes.d/vendor/vendor.xml.gz - vendor-directory.conf MetadataURI=file:///usr/share/fwupd/remotes.d/vendor/firmware The directory exists, but the `vendor.xml.gz` file referenced above is missing. As I don't have any relevant files on the `/usr/share/fwupd/remotes.d/vendor/` directory, I'll call it a day, and leave the Discover's Settings Page vendor-directory checkbox unchecked. My doubt is if Discover, or PackageKit, or fwupd (somehow), should be respecting the `Enabled=false`. Or if this still is something to be reported on the distro level. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 460985] portal-based open-with implementation lacks choosing custom binary
https://bugs.kde.org/show_bug.cgi?id=460985 Rodrigo Pedra Brum changed: What|Removed |Added CC||rodrigo.pe...@gmail.com --- Comment #23 from Rodrigo Pedra Brum --- As Plasma 5.27 is the last release of the Plasma 5 series, can't we revert to the old application selector? As others already have said, I often used this feature to test custom binaries, and I don't think adding a custom `.desktop` file for each binary is a feasible solution. Sometimes I just want to process a CSV, or TSV, with a custom binary, and doing it from the interface, with its embed history, specially when I am doing some repeated work is very handy. I truly believe all advancements are proposed and coded with the best intentions and having a regular user in mind. But I can't recall any complaint of how this specific feature works. Never saw any mentions in KDE's reddit or anywhere else. But of course, you as maintainers know better. If I could choose, I'd say to keep both for a while and do some A/B testing, or asking for user feedback. But I know resources and time is limited. Just please consider not limiting it to `.desktop` file. This would be very limiting to mine, and -- as it seems from some comments -- others workflow. Having this as a hard requirement for replacing this component is very frustrating. Is this a feature that could be maintained by volunteers and be replaced desktop-wise for those who prefer the older component? Thanks in advance. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 460985] portal-based open-with implementation lacks choosing custom binary
https://bugs.kde.org/show_bug.cgi?id=460985 --- Comment #24 from Rodrigo Pedra Brum --- Created attachment 156816 --> https://bugs.kde.org/attachment.cgi?id=156816&action=edit mockup of additional option on open with menu I made a mockup of what could be an additional option on open with menu (not a pro, not even an amateur with Krita) Could that be an option? Having an additional option to open with path that would open a file picker directly? That way, the current portal selector wouldn't need to be changed, and users who rely on the old behavior could keep their workflow. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 460985] portal-based open-with implementation lacks choosing custom binary
https://bugs.kde.org/show_bug.cgi?id=460985 --- Comment #33 from Rodrigo Pedra Brum --- Thank you all =) Maybe for Plasma 6 the mockup I made could be taken into consideration. Not necessarily the mockup, but the idea. I think it would be a clear way to separate both concepts, whilst reducing the clutter and confusion on the portal component. And as a bonus, it would allow to those of us who like the ability to quick use a binary path to have a way to do so with fewer steps. Thanks again, and have a nice day =) -- You are receiving this mail because: You are watching all bug changes.
[kcron] [Bug 467708] New: KCron does not load System Cron
https://bugs.kde.org/show_bug.cgi?id=467708 Bug ID: 467708 Summary: KCron does not load System Cron Classification: Applications Product: kcron Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: g...@meyer.net Reporter: rodrigo.pe...@gmail.com Target Milestone: --- Created attachment 157525 --> https://bugs.kde.org/attachment.cgi?id=157525&action=edit Screencast showcasing the unexpected behavior SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** When opening, or reopening KCron, the tasks for System Cron are not loaded. If one adds tasks, it shows it fine, but upon closing and reopening it misses all tasks again. Personal Cron works fine. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kcron] [Bug 467708] KCron does not load System Cron
https://bugs.kde.org/show_bug.cgi?id=467708 --- Comment #1 from Rodrigo Pedra Brum --- Sorry I forgot to fill the template STEPS TO REPRODUCE 1. Open KCron 2. Add a task to System Cron 3. Close KCron 4. Reopen KCron 5. Switch to System Cron OBSERVED RESULT System Cron task list is empty after reopening EXPECTED RESULT System Cron should load the tasks from the previous created crontab file SOFTWARE/OS VERSIONS Windows: Not tested macOS: Not tested Linux/KDE Plasma: openSUSE Tumbleweed / Plasma 5.27.3 (available in About System) KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Kernel version: 6.2.6-1-default (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 448179] Network global download limit ignored
https://bugs.kde.org/show_bug.cgi?id=448179 Rodrigo Pedra Brum changed: What|Removed |Added CC||rodrigo.pe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450327] Night Color doesn't work at all on Plasma Wayland with NVIDIA
https://bugs.kde.org/show_bug.cgi?id=450327 Rodrigo López Dato changed: What|Removed |Added CC||rolod...@rolodato.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 460066] New: Discover crashed when closing just after an update
https://bugs.kde.org/show_bug.cgi?id=460066 Bug ID: 460066 Summary: Discover crashed when closing just after an update Classification: Applications Product: Discover Version: 5.25.5 Platform: OpenSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: rodrigo.pe...@gmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.25.5) Qt Version: 5.15.6 Frameworks Version: 5.98.0 Operating System: Linux 5.19.12-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.25.5 [KCrashBackend] -- Information about the crash: In a fresh boot I saw Discover's update icon, I opened Discover and ran the update with just a flatpak app. Just when the update finished, I closed the window and the application crahsed. I noticed Discover had just started to search for updates again. The crash does not seem to be reproducible. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault [KCrash Handler] #4 0x7f050bf424ab in g_cancellable_is_cancelled () at /lib64/libgio-2.0.so.0 #5 0x7f050bf424ce in g_cancellable_set_error_if_cancelled () at /lib64/libgio-2.0.so.0 #6 0x7f050bf53c21 in g_file_query_info () at /lib64/libgio-2.0.so.0 #7 0x7f050bf53db9 in g_file_query_exists () at /lib64/libgio-2.0.so.0 #8 0x7f04d443ade9 in () at /lib64/libflatpak.so.0 #9 0x7f04d44498cf in () at /lib64/libflatpak.so.0 #10 0x7f04d444d61e in () at /lib64/libflatpak.so.0 #11 0x7f04d446c60a in () at /lib64/libflatpak.so.0 #12 0x7f04d4458a58 in flatpak_installation_list_installed_refs_for_update () at /lib64/libflatpak.so.0 #13 0x7f04d44e872d in () at /usr/lib64/qt5/plugins/discover/flatpak-backend.so #14 0x7f04d44f058f in () at /usr/lib64/qt5/plugins/discover/flatpak-backend.so #15 0x7f050d8023f1 in () at /lib64/libQt5Core.so.5 #16 0x7f050d7fee4d in () at /lib64/libQt5Core.so.5 #17 0x7f050d3739ad in start_thread () at /lib64/libc.so.6 #18 0x7f050d3fa0f0 in clone3 () at /lib64/libc.so.6 Thread 18 (Thread 0x7f04c67fc6c0 (LWP 6250) "QNetworkAccessM"): #1 0x7f050da3c72a in () at /lib64/libQt5Core.so.5 #2 0x7f050c21e245 in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #3 0x7f050c21ecb3 in () at /lib64/libglib-2.0.so.0 #4 0x7f050c21ee9c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7f050da3c81e in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f050d9e3beb in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7f050d7fdc47 in QThread::exec() () at /lib64/libQt5Core.so.5 #8 0x7f050d7fee4d in () at /lib64/libQt5Core.so.5 #9 0x7f050d3739ad in start_thread () at /lib64/libc.so.6 #10 0x7f050d3fa0f0 in clone3 () at /lib64/libc.so.6 Thread 17 (Thread 0x7f04c4b876c0 (LWP 6245) "dconf worker"): #1 0x7f050c21ed7e in () at /lib64/libglib-2.0.so.0 #2 0x7f050c21ee9c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f04a7ecd84d in () at /usr/lib64/gio/modules/libdconfsettings.so #4 0x7f050c2492a5 in () at /lib64/libglib-2.0.so.0 #5 0x7f050d3739ad in start_thread () at /lib64/libc.so.6 #6 0x7f050d3fa0f0 in clone3 () at /lib64/libc.so.6 Thread 16 (Thread 0x7f0496ffd6c0 (LWP 6207) "QNetworkAccessM"): #1 0x7f050c21ed7e in () at /lib64/libglib-2.0.so.0 #2 0x7f050c21ee9c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f050da3c81e in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f050d9e3beb in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f050d7fdc47 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f050d7fee4d in () at /lib64/libQt5Core.so.5 #7 0x7f050d3739ad in start_thread () at /lib64/libc.so.6 #8 0x7f050d3fa0f0 in clone3 () at /lib64/libc.so.6 Thread 15 (Thread 0x7f0494ffd6c0 (LWP 6091) "QLibProxyWrappe"): #1 0x7f050d800e7b in QSemaphore::acquire(int) () at /lib64/libQt5Core.so.5 #2 0x7f050d19c1c4 in () at /lib64/libQt5Network.so.5 #3 0x7f050d7fee4d in () at /lib64/libQt5Core.so.5 #4 0x7f050d3739ad in start_thread () at /lib64/libc.so.6 #5 0x7f050d3fa0f0 in clone3 () at /lib64/libc.so.6 Thread 14 (Thread 0x7f0497fff6c0 (LWP 6090) "QNetworkAccessM"): #1 0x7f050c21cad0 in () at /lib64/libglib-2.0.so.0 #2 0x7f050c21e15b in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #3 0x7f050c21ecb3 in () at /lib64/libglib-2.0.so.0 #4 0x7f050c21ee9c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7f050da3c81e in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f050d9e3beb in QEventLoop::exec(QFlags) () at /lib64/li
[frameworks-ktexteditor] [Bug 475378] Selected text background does not scroll with text
https://bugs.kde.org/show_bug.cgi?id=475378 --- Comment #5 from Rodrigo Pedra Brum --- Created attachment 165711 --> https://bugs.kde.org/attachment.cgi?id=165711&action=edit screencast of kate odd text selection behavior on increased line height So, I booted a live neon session on a VM, and to my surprise, stock Kate worked as expected. So I decided to change settings, one by one, to match my local settings and find if some setting was the culprit. Lucky me, I found it on the first settings screen: line height. If one increases the line height setting, then the bug occurs. I made another screencast from a new VM using a neon live session. For instance, in the video, I just increased it by one tick to 1.1. Locally, I use 1.2. But just by changing it, the odd behavior starts happening. Please let me know if I can provide any further info. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 475378] Selected text background does not scroll with text
https://bugs.kde.org/show_bug.cgi?id=475378 --- Comment #6 from Rodrigo Pedra Brum --- For completeness, setting the line-height back to 1 gets rid of the odd behavior, and text selection behaves as expected. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 475378] Selected text background does not scroll with text
https://bugs.kde.org/show_bug.cgi?id=475378 --- Comment #8 from Rodrigo Pedra Brum --- Can you check if some other setting triggers the behavior? It would help the developers to track the root cause. In my case, I planned to have the neon live instance and keep comparing settings one by one until I could reproduce. To my luck, what triggered the bug on my install, was on the first settings page. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 415330] Songs aren't shown if id3v1 is used
https://bugs.kde.org/show_bug.cgi?id=415330 Rodrigo Pedra Brum changed: What|Removed |Added CC||rodrigo.pe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 482293] Elisa fails to detect/display music tags and thus, Albums and Artists categories are empty
https://bugs.kde.org/show_bug.cgi?id=482293 Rodrigo Pedra Brum changed: What|Removed |Added CC||rodrigo.pe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 482293] Elisa fails to detect/display music tags and thus, Albums and Artists categories are empty
https://bugs.kde.org/show_bug.cgi?id=482293 --- Comment #1 from Rodrigo Pedra Brum --- I have the same issue. Even compiled Elisa from source to see if I had a missing dependency of some sort. ``` ~ $ kinfo Operating System: openSUSE Leap 15.5 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.7.0 Kernel Version: 5.14.21-150500.55.52-default (64-bit) Graphics Platform: X11 ``` -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484473] Symbolic icons have wrong color when using Twilight theme
https://bugs.kde.org/show_bug.cgi?id=484473 Rodrigo Pedra Brum changed: What|Removed |Added CC||rodrigo.pe...@gmail.com --- Comment #1 from Rodrigo Pedra Brum --- Created attachment 167864 --> https://bugs.kde.org/attachment.cgi?id=167864&action=edit System tray with some icons off-color when using Breeze Twilight on Plasma 6.0.3 Same here, but also some of the icons are off color on the system tray Operating System: openSUSE Leap 15.5 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 Kernel Version: 5.14.21-150500.55.52-default (64-bit) Graphics Platform: X11 Note: I've added the KDE repos (Argon like) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482645] System tray icons are colored wrong when using dark Plasma and light application theme
https://bugs.kde.org/show_bug.cgi?id=482645 Rodrigo Pedra Brum changed: What|Removed |Added CC||rodrigo.pe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445430] kinfocenter crash after app start
https://bugs.kde.org/show_bug.cgi?id=445430 Rodrigo Pedra Brum changed: What|Removed |Added CC||rodrigo.pe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445430] kinfocenter crash after app start
https://bugs.kde.org/show_bug.cgi?id=445430 --- Comment #2 from Rodrigo Pedra Brum --- Created attachment 144273 --> https://bugs.kde.org/attachment.cgi?id=144273&action=edit New crash information added by DrKonqi systemsettings5 (5.23.4) using Qt 5.15.3 - What I was doing when the application crashed: Just updated KDE Neon to latest updates, I guess 5.23.4 (as I cannot open KInfoCenter I cannot tell), and tried to open KInfoCenter from the launcher after restart. I tried three times, all crashed, before reporting -- Backtrace (Reduced): #4 0x7f8ac358dd22 in QV4::QQmlTypeWrapper::virtualInstanceOf (typeObject=0x7fffc2689db0, var=...) at qml/qqmltypewrapper.cpp:423 #5 0x7f8ac3455248 in QV4::Object::instanceOf (var=..., this=0x7fffc2689db0) at ../../include/QtQml/5.15.3/QtQml/private/../../../../../src/qml/memory/qv4heap_p.h:73 #6 QV4::Runtime::Instanceof::call (engine=0x55ce8b566be0, lval=..., rval=...) at jsruntime/qv4runtime.cpp:387 #7 0x7f8ac34429e0 in QV4::Moth::VME::interpret (frame=0x7fffc2689e90, engine=0x55ce8b566be0, code=0x7f8a4c001819 "pL;/\231") at jsruntime/qv4vme_moth.cpp:351 #8 0x7f8ac344611f in QV4::Moth::VME::exec (frame=frame@entry=0x7fffc2689e90, engine=engine@entry=0x55ce8b566be0) at jsruntime/qv4vme_moth.cpp:463 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 446562] After latest update (2021-12-07), System Settings and Info Center keep crashing every time.
https://bugs.kde.org/show_bug.cgi?id=446562 Rodrigo Pedra Brum changed: What|Removed |Added CC||rodrigo.pe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 446562] After latest update (2021-12-07), System Settings and Info Center keep crashing every time.
https://bugs.kde.org/show_bug.cgi?id=446562 --- Comment #1 from Rodrigo Pedra Brum --- Created attachment 144276 --> https://bugs.kde.org/attachment.cgi?id=144276&action=edit New crash information added by DrKonqi systemsettings5 (5.23.4) using Qt 5.15.3 - What I was doing when the application crashed: I updated KDE Neon and tried opening System Settings after restart from the launcher. I already submitted a crash reporter earlier for the same issue with KInfoCenter, but attached to another bug. -- Backtrace (Reduced): #4 0x7f4f404c1d22 in QV4::QQmlTypeWrapper::virtualInstanceOf (typeObject=0x7fff23de94a0, var=...) at qml/qqmltypewrapper.cpp:423 #5 0x7f4f40389248 in QV4::Object::instanceOf (var=..., this=0x7fff23de94a0) at ../../include/QtQml/5.15.3/QtQml/private/../../../../../src/qml/memory/qv4heap_p.h:73 #6 QV4::Runtime::Instanceof::call (engine=0x56302d2e40a0, lval=..., rval=...) at jsruntime/qv4runtime.cpp:387 #7 0x7f4f403769e0 in QV4::Moth::VME::interpret (frame=0x7fff23de9580, engine=0x56302d2e40a0, code=0x7f4ec0200a1b "L\020/\276") at jsruntime/qv4vme_moth.cpp:351 #8 0x7f4f4037a11f in QV4::Moth::VME::exec (frame=frame@entry=0x7fff23de9580, engine=engine@entry=0x56302d2e40a0) at jsruntime/qv4vme_moth.cpp:463 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 438711] Discover notifies about new update on startup but there is no update at all.
https://bugs.kde.org/show_bug.cgi?id=438711 Rodrigo Pedra Brum changed: What|Removed |Added CC||rodrigo.pe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 438711] Discover notifies about new update on startup but there is no update at all.
https://bugs.kde.org/show_bug.cgi?id=438711 --- Comment #1 from Rodrigo Pedra Brum --- Created attachment 139375 --> https://bugs.kde.org/attachment.cgi?id=139375&action=edit Discover system tray showing up with no updates Image shows: - Discover system tray showing up (system tray is in upper left) - Info center screen with installation info - Discover screen with no updates available -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 438711] Discover notifies about new update on startup but there is no update at all.
https://bugs.kde.org/show_bug.cgi?id=438711 --- Comment #2 from Rodrigo Pedra Brum --- Sorry for posting twice in a row, new to bug tracker, thought comment box on attachments page would add a alt text to the attachment. Can confirm this started to happen after running updates for Plasma 5.22.1 I am running KDE Neon with every other dependency up to date. I reboot several times to see if it would disappear, with no success. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 438711] Discover notifies about new update on startup but there is no update at all.
https://bugs.kde.org/show_bug.cgi?id=438711 Rodrigo Pedra Brum changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #3 from Rodrigo Pedra Brum --- Reading the docs I realized I should have changed the status to CONFIRMED so it gets triaged. Sorry again, new to this. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 475378] Selected text background does not scroll with text
https://bugs.kde.org/show_bug.cgi?id=475378 Rodrigo Pedra Brum changed: What|Removed |Added CC||rodrigo.pe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 476979] Display of dragged text wrong when word-wrap is enabled
https://bugs.kde.org/show_bug.cgi?id=476979 Rodrigo Pedra Brum changed: What|Removed |Added CC||rodrigo.pe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 392926] KTextEditor scrollbar preview and mini map do not respect word wrapping
https://bugs.kde.org/show_bug.cgi?id=392926 Rodrigo Pedra Brum changed: What|Removed |Added CC||rodrigo.pe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 475378] Selected text background does not scroll with text
https://bugs.kde.org/show_bug.cgi?id=475378 --- Comment #2 from Rodrigo Pedra Brum --- Created attachment 164906 --> https://bugs.kde.org/attachment.cgi?id=164906&action=edit Screen recording demonstrating the odd behavior I have this odd behavior in Kate for a long time, but I haven't had the opportunity to search for an existing bug, or to properly report it. When working with a file with long lines, text selection is very odd, and doesn't work as expected. I added subtitles commenting out the behavior to the video, I will paste it here, for easier discoverability: ``` - Selection "scrolls" with horizontal scroll - If cutting what seems to be selected, the original selection is actually cut - (note, the expectation is the selection not be scrolled) - Selecting when horizontal scroll is full at scroll start, works as expected - Double-clicking a word, when horizontal scroll is full at scroll start, also works as expected - But when moving the horizontal scroll, neither selecting text with a keyboard, or with a mouse, work as expected, as well cutting a text is odd - When scrolling past the window width, even a displaced selection does not appear anymore - (actually we can notice on all cases the "expected" selection gets is font color faded) ``` Apart from using the solarized light built-in theme, I don't have any other relevant customizations, or plugins added to Kate. My installation info: ``` Operating System: openSUSE Tumbleweed 20240112 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.114.0 Qt Version: 5.15.12 Kernel Version: 6.6.11-1-default (64-bit) Graphics Platform: X11 ``` -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 460874] New: KDE Partition Manager crashes when removing USB mount
https://bugs.kde.org/show_bug.cgi?id=460874 Bug ID: 460874 Summary: KDE Partition Manager crashes when removing USB mount Classification: Applications Product: partitionmanager Version: 22.08.2 Platform: OpenSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: rodrigo.pe...@gmail.com Target Milestone: --- Application: partitionmanager (22.08.2) Qt Version: 5.15.6 Frameworks Version: 5.99.0 Operating System: Linux 6.0.2-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.26.1 [KCrashBackend] -- Information about the crash: It chrashes when removing a USB partition mounted on a directory The crash can be reproduced every time. -- Backtrace: Application: KDE Partition Manager (partitionmanager), signal: Segmentation fault [KCrash Handler] #4 0x7f94af3ba030 in FstabEntry::fsSpec() const () at /lib64/libkpmcore.so.12 #5 0x55a6421f5580 in () #6 0x7f94adbf005d in () at /lib64/libQt5Core.so.5 #7 0x7f94ae859092 in QAbstractButton::clicked(bool) () at /lib64/libQt5Widgets.so.5 #8 0x7f94ae8592fa in () at /lib64/libQt5Widgets.so.5 #9 0x7f94ae85ab98 in () at /lib64/libQt5Widgets.so.5 #10 0x7f94ae85adb7 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () at /lib64/libQt5Widgets.so.5 #11 0x7f94ae7a8c48 in QWidget::event(QEvent*) () at /lib64/libQt5Widgets.so.5 #12 0x7f94ae7673fe in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #13 0x7f94ae76f922 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #14 0x7f94adbb9178 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #15 0x7f94ae76da9e in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () at /lib64/libQt5Widgets.so.5 #16 0x7f94ae7c1a68 in () at /lib64/libQt5Widgets.so.5 #17 0x7f94ae7c4fc0 in () at /lib64/libQt5Widgets.so.5 #18 0x7f94ae7673fe in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #19 0x7f94adbb9178 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #20 0x7f94ae019a3d in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /lib64/libQt5Gui.so.5 #21 0x7f94adfed38c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /lib64/libQt5Gui.so.5 #22 0x7f94a92fd0ea in () at /lib64/libQt5XcbQpa.so.5 #23 0x7f94acc4ba50 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #24 0x7f94acc4be08 in () at /lib64/libglib-2.0.so.0 #25 0x7f94acc4be9c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #26 0x7f94adc10806 in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #27 0x7f94adbb7beb in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #28 0x7f94ae96f487 in QDialog::exec() () at /lib64/libQt5Widgets.so.5 #29 0x55a64220f25f in () #30 0x7f94adbf005d in () at /lib64/libQt5Core.so.5 #31 0x7f94ae760bb2 in QAction::triggered(bool) () at /lib64/libQt5Widgets.so.5 #32 0x7f94ae7636fb in QAction::activate(QAction::ActionEvent) () at /lib64/libQt5Widgets.so.5 #33 0x7f94ae8e8222 in () at /lib64/libQt5Widgets.so.5 #34 0x7f94ae8f0084 in () at /lib64/libQt5Widgets.so.5 #35 0x7f94ae7a8c48 in QWidget::event(QEvent*) () at /lib64/libQt5Widgets.so.5 #36 0x7f94ae7673fe in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #37 0x7f94ae76f922 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #38 0x7f94adbb9178 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #39 0x7f94ae76da9e in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () at /lib64/libQt5Widgets.so.5 #40 0x7f94ae7c1eb5 in () at /lib64/libQt5Widgets.so.5 #41 0x7f94ae7c4fc0 in () at /lib64/libQt5Widgets.so.5 #42 0x7f94ae7673fe in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #43 0x7f94adbb9178 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #44 0x7f94ae019a3d in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /lib64/libQt5Gui.so.5 #45 0x7f94adfed38c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /lib64/libQt5Gui.so.5 #46 0x7f94a92fd0ea in () at /lib64/libQt5XcbQpa.so.5 #47 0x7f94acc4ba50 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #48 0x7f94acc4be08 in () at /lib64/libglib-2.0.so.0 #49 0x7f94acc4be9c in g_main_context_iteration () at /lib64/libg
[kde-cli-tools] [Bug 429408] kde-open5 changes case of argument
https://bugs.kde.org/show_bug.cgi?id=429408 Rodrigo Garcia Martin changed: What|Removed |Added CC||rodrigogarci...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 460066] Discover crashed when closing just after an update
https://bugs.kde.org/show_bug.cgi?id=460066 --- Comment #3 from Rodrigo Pedra Brum --- Hey Nate, Sorry for not responding earlier, somehow the e-mails for this but report got sent to a different tag in my GMail. I often update through CLI and seldom through Discover, but I will try to replicate the bug as soon as I get a flatpak update. Thanks for looking into it. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 460066] Discover crashed when closing just after an update
https://bugs.kde.org/show_bug.cgi?id=460066 Rodrigo Pedra Brum changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Rodrigo Pedra Brum --- Nate, I tried twice this week and I can't replicate it anymore. I will close the bug for now, and if I can replicate it I will reopen it again. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 448417] neon-settings needs updating to 50-kcoreaddons to reflect frameworks update
https://bugs.kde.org/show_bug.cgi?id=448417 Rodrigo Pedra Brum changed: What|Removed |Added CC||rodrigo.pe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 438194] New: Kdenlive crashes on exit
https://bugs.kde.org/show_bug.cgi?id=438194 Bug ID: 438194 Summary: Kdenlive crashes on exit Product: kdenlive Version: 21.04.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: rodrigo.pe...@gmail.com Target Milestone: --- Created attachment 139064 --> https://bugs.kde.org/attachment.cgi?id=139064&action=edit Crash Report SUMMARY Kdenlive crashes on exit. I tried sending a Crash Report, but the wizard kept failing, so I am sending it here. STEPS TO REPRODUCE 1. Open kdenlive 2. Open a project 3. Quit the app, either by clicking the window's close button or File > Quit OBSERVED RESULT App crashes on exit. Notifications about sending a Bug report is shown. EXPECTED RESULT App gracefully quits. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.21 (available in About System) KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Please see the attached kcrash file. I added some more info there when writing it on the wizard. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 438194] Kdenlive crashes on exit
https://bugs.kde.org/show_bug.cgi?id=438194 Rodrigo Pedra Brum changed: What|Removed |Added CC||rodrigo.pe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 400366] New: ktouch does not leave the welcome screen
https://bugs.kde.org/show_bug.cgi?id=400366 Bug ID: 400366 Summary: ktouch does not leave the welcome screen Product: ktouch Version: unspecified Platform: Mint (Debian based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: sebastian.gottfr...@posteo.de Reporter: rfrodrigofcam...@gmail.com Target Milestone: --- ktouch does not leave the welcome screen in linux mint 19 x64 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 381142] New: Kwin crashed g when I clicked on "Print" buttom
https://bugs.kde.org/show_bug.cgi?id=381142 Bug ID: 381142 Summary: Kwin crashed g when I clicked on "Print" buttom Product: kwin Version: 5.9.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: rodrigodeara...@fedoraproject.org Target Milestone: --- Application: kwin_x11 (5.9.5) Qt Version: 5.7.1 Frameworks Version: 5.34.0 Operating System: Linux 4.11.3-202.fc25.x86_64 x86_64 Distribution: "Fedora release 25 (Twenty Five)" -- Information about the crash: - What I was doing when the application crashed: I was sending a file to be printed by Brother HL1102. Printer received the documented just fine, but Kwin got crashed. - Unusual behavior I noticed: Kwin crashed in the moment that I cliked on the "Print" buttom (I was using WPS Writer). The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0dca14e940 (LWP 1955))] Thread 6 (Thread 0x7f0da56cc700 (LWP 7651)): #0 0x7f0dd9551001 in ppoll () at /lib64/libc.so.6 #1 0x7f0dda355971 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /lib64/libQt5Core.so.5 #2 0x7f0dda356e86 in QEventDispatcherUNIX::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #3 0x7f0dda30a68a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f0dda1675e3 in QThread::exec() () at /lib64/libQt5Core.so.5 #5 0x7f0de0c6f4e5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #6 0x7f0dda16b9ca in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7f0ddc0f373a in start_thread () at /lib64/libpthread.so.0 #8 0x7f0dd955ce7f in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f0db5718700 (LWP 2723)): #0 0x7f0dd9551001 in ppoll () at /lib64/libc.so.6 #1 0x7f0dda355971 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /lib64/libQt5Core.so.5 #2 0x7f0dda356e86 in QEventDispatcherUNIX::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #3 0x7f0dda30a68a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f0dda1675e3 in QThread::exec() () at /lib64/libQt5Core.so.5 #5 0x7f0de0c6f4e5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #6 0x7f0dda16b9ca in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7f0ddc0f373a in start_thread () at /lib64/libpthread.so.0 #8 0x7f0dd955ce7f in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f0da4ecb700 (LWP 2192)): #0 0x7f0ddc0f9460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f0de1a1a2f4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /lib64/libQt5Script.so.5 #2 0x7f0de1a1a339 in () at /lib64/libQt5Script.so.5 #3 0x7f0ddc0f373a in start_thread () at /lib64/libpthread.so.0 #4 0x7f0dd955ce7f in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f0db6719700 (LWP 2142)): #0 0x7f0dd9551001 in ppoll () at /lib64/libc.so.6 #1 0x7f0dda355971 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /lib64/libQt5Core.so.5 #2 0x7f0dda356e86 in QEventDispatcherUNIX::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #3 0x7f0dda30a68a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f0dda1675e3 in QThread::exec() () at /lib64/libQt5Core.so.5 #5 0x7f0de0c6f4e5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #6 0x7f0dda16b9ca in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7f0ddc0f373a in start_thread () at /lib64/libpthread.so.0 #8 0x7f0dd955ce7f in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f0dca14a700 (LWP 2011)): #0 0x7f0dd9550f3d in poll () at /lib64/libc.so.6 #1 0x7f0dd0a8a166 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f0dd0a8a27c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f0dda3596eb in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f0dda30a68a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f0dda1675e3 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f0dde8a1fb9 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #7 0x7f0dda16b9ca in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f0ddc0f373a in start_thread () at /lib64/libpthread.so.0 #9 0x7f0dd955ce7f in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f0dca14e940 (LWP 1955)): [KCrash Handler] #6 0x in () #7 0x7f0dda338878 in QObject::connect(QObject const*, char const*, QObject const*, char const*, Qt::ConnectionType) () at /lib64/libQt5Core.so.5 #8 0x7f0de1a5cd2f in QScriptEnginePrivate::qobjectD
[plasmashell] [Bug 501865] Windows can cover are missing
https://bugs.kde.org/show_bug.cgi?id=501865 Rodrigo Pedra Brum changed: What|Removed |Added CC||rodrigo.pe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377162] Window shading not supported for Wayland windows
https://bugs.kde.org/show_bug.cgi?id=377162 Rodrigo Pedra Brum changed: What|Removed |Added CC||rodrigo.pe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 128434] Preview tooltip for hyperlinks to other pages
https://bugs.kde.org/show_bug.cgi?id=128434 Rodrigo Pedra Brum changed: What|Removed |Added CC||rodrigo.pe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 494125] Double-clicking a file *deselects* it after opening
https://bugs.kde.org/show_bug.cgi?id=494125 Rodrigo Pedra Brum changed: What|Removed |Added CC||rodrigo.pe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 469113] KDE doesn't remember display resolution
https://bugs.kde.org/show_bug.cgi?id=469113 Rodrigo Pedra Brum changed: What|Removed |Added CC||rodrigo.pe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363956] No pen sensitivity with Freehand Path Tool
https://bugs.kde.org/show_bug.cgi?id=363956 Rodrigo changed: What|Removed |Added CC||rmart...@gmail.com --- Comment #2 from Rodrigo --- I have the same problem using MS windows 10, multi-touch screen (HP ENVY 23) and I cannot use the freehand brush Tool (B). All other tools like calligrafy, line tool, etc.. are working without problems. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363956] No pen sensitivity with Freehand Path Tool
https://bugs.kde.org/show_bug.cgi?id=363956 --- Comment #4 from Rodrigo --- Yes, I mean that and to give you more information with mouse point it works, nevertheless I paint with a pen for touchscreens not my finger. Later I'll try with my finger and I'll say you what happened. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 364386] New: The freehand tool doesn't work when I am trying to finger paint on the touch screen
https://bugs.kde.org/show_bug.cgi?id=364386 Bug ID: 364386 Summary: The freehand tool doesn't work when I am trying to finger paint on the touch screen Product: krita Version: 3.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Brush engine Assignee: krita-bugs-n...@kde.org Reporter: rmart...@gmail.com I have the same problem using MS windows 10, multi-touch screen (HP ENVY 23) and I cannot use the freehand brush Tool (B). All other tools like calligrafy, line tool, etc.. are working without problems. The freehand tool doesn't work when I am trying to finger paint on the touch screen. Driver Intel HD graphics 4600. Reproducible: Always Steps to Reproduce: 1. Open krita 2. Select freehad brush tool 3. Try to paint. Actual Results: It doesn't work. Expected Results: draw a line -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 365238] New: Calligra Sheets Crashes when adding chart
https://bugs.kde.org/show_bug.cgi?id=365238 Bug ID: 365238 Summary: Calligra Sheets Crashes when adding chart Product: calligrasheets Version: 2.9.11 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: calligra-sheets-bugs-n...@kde.org Reporter: rodrigoesbor...@gmail.com Application: calligrasheets (2.9.11) KDE Platform Version: 4.14.9 Qt Version: 4.8.6 Operating System: Linux 4.2.0-banana08-60-desktop x86_64 Distribution: "openSUSE 13.2 (Harlequin) (x86_64)" -- Information about the crash: Application crashed when trying to add a chart, after having selected first row as legend, first column as legend -- Backtrace: Application: Calligra Sheets (calligrasheets), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #5 0x7f9d1fad1616 in QPen::QPen(QPen const&) () at /usr/lib64/libQtGui.so.4 #6 0x7f9d00c5a609 in () at /usr/lib64/kde4/calligra_shape_chart.so #7 0x7f9d00c8f880 in () at /usr/lib64/kde4/calligra_shape_chart.so #8 0x7f9d00c90024 in () at /usr/lib64/kde4/calligra_shape_chart.so #9 0x7f9d00c90e93 in () at /usr/lib64/kde4/calligra_shape_chart.so #10 0x7f9d00c88ef3 in () at /usr/lib64/kde4/calligra_shape_chart.so #11 0x7f9d00c89c35 in () at /usr/lib64/kde4/calligra_shape_chart.so #12 0x7f9d207f81fa in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib64/libQtCore.so.4 #13 0x7f9d207fc59e in QObject::event(QEvent*) () at /usr/lib64/libQtCore.so.4 #14 0x7f9d1f96076c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #15 0x7f9d1f966cad in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #16 0x7f9d0bdf8e37 in KoApplication::notify(QObject*, QEvent*) () at /usr/lib64/libkomain.so.14 #17 0x7f9d207e42ad in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQtCore.so.4 #18 0x7f9d207e757d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQtCore.so.4 #19 0x7f9d208118fe in () at /usr/lib64/libQtCore.so.4 #20 0x7f9d1c2c0a04 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #21 0x7f9d1c2c0c48 in () at /usr/lib64/libglib-2.0.so.0 #22 0x7f9d1c2c0cec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #23 0x7f9d208110be in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #24 0x7f9d1f9fd676 in () at /usr/lib64/libQtGui.so.4 #25 0x7f9d207e2e6f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #26 0x7f9d207e3165 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #27 0x7f9d207e85b9 in QCoreApplication::exec() () at /usr/lib64/libQtCore.so.4 #28 0x7f9d0c0a57a5 in kdemain () at /usr/lib64/libkdeinit4_calligrasheets.so #29 0x00408815 in _start () The reporter indicates this bug may be a duplicate of or related to bug 322162, bug 311177, bug 322161, bug 360939. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 47320] [testcase] text and background uses colors from KDE color scheme if not specified in the html style
https://bugs.kde.org/show_bug.cgi?id=47320 Rodrigo Fernandes changed: What|Removed |Added CC||rfernan...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 166687] Firefox 3-like location bar in Konqueror (possibly combined with Dolphin's bar)
https://bugs.kde.org/show_bug.cgi?id=166687 Rodrigo Fernandes changed: What|Removed |Added CC||rfernan...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
