[kontact] [Bug 383885] CLI start: 0xca83b8 deleted without having been removed from the factory first.
https://bugs.kde.org/show_bug.cgi?id=383885 Don Curtis changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #4 from Don Curtis --- Two year on, no longer an issue. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 383885] CLI start: 0xca83b8 deleted without having been removed from the factory first.
https://bugs.kde.org/show_bug.cgi?id=383885 Don Curtis changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #5 from Don Curtis --- No longer an issue, therefore closed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409661] Brush properties widget (on the right) in Popup Palette becomes smaller and smaller
https://bugs.kde.org/show_bug.cgi?id=409661 Boudewijn Rempt changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409284] kwin does not allow for disabling optional libhybris
https://bugs.kde.org/show_bug.cgi?id=409284 Antonio Rojas changed: What|Removed |Added CC||aro...@archlinux.org --- Comment #6 from Antonio Rojas --- Here is your actual error, it has nothing to do with libhybris CMake Error at /usr/lib/qt5/cmake/Qt5UiTools/Qt5UiToolsConfig.cmake:48 (string): string sub-command REGEX, mode REPLACE needs at least 6 arguments total to command. What is the actual version of Qt you're using? This was a bug in one of the 5.13 betas and is fixed in the final 5.13 release. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 409665] kdesrc-build should be able to clone repos from invent.kde.org
https://bugs.kde.org/show_bug.cgi?id=409665 David Faure changed: What|Removed |Added CC||bcooks...@kde.org, ||j...@kdenlive.org -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 409665] New: kdesrc-build should be able to clone repos from invent.kde.org
https://bugs.kde.org/show_bug.cgi?id=409665 Bug ID: 409665 Summary: kdesrc-build should be able to clone repos from invent.kde.org Product: kdesrc-build Version: Git Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mp...@kde.org Reporter: fa...@kde.org Target Milestone: --- SUMMARY kde git is migrating incrementally to gitlab on invent.kde.org. kdenlive has already migrated, so in order to contribute to kdenlive I was told I had to clone g...@invent.kde.org:kde/kdenlive.git kdesrc-build however doesn't know and still clones from g...@git.kde.org:kdenlive (which still exists, must be a readonly mirror). Can kdesrc-build gain support for gitlab (without having to override git urls for repos manually)? STEPS TO REPRODUCE 1. kdesrc-build kdenlive 2. git remote -v OBSERVED RESULT g...@git.kde.org:kdenlive EXPECTED RESULT g...@invent.kde.org:kde/kdenlive.git (at least for contributors; no idea about the public URL) Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 409664] New: Folder Passwords: content inspection triggers "Save changes" despite no changes
https://bugs.kde.org/show_bug.cgi?id=409664 Bug ID: 409664 Summary: Folder Passwords: content inspection triggers "Save changes" despite no changes Product: kwalletmanager Version: 18.12 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: va...@kde.org Reporter: bugrprt21...@online.de Target Milestone: --- SUMMARY After inspection of Password text content, "Save changes" is triggered when text is marked by the mouse and then copied. "Pairs" (Key and content) doesn't exhibit this behaviour. STEPS TO REPRODUCE 1. Open the KWallet Manager. 2. Select the Folder "Passwords" and then the sub-folder "Passwords" (text). 3. Select a Password and then display the content. 4. Select some text and then copy it to the KDE Paste Buffer. 5. Select another Password. OBSERVED RESULT The "Save changes" window appears. EXPECTED RESULT There were no changes made (only content was copied) and therefore there's no need to save any changes which were not made. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Leap 15.1 KDE Plasma Version: 5.12.8 KDE Frameworks Version: 5.55.0 Qt Version: 5.9.7 ADDITIONAL INFORMATION A rather surprising, unexpected, definitely not needed, application behaviour. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 409663] Faster Metadata editing interface
https://bugs.kde.org/show_bug.cgi?id=409663 --- Comment #2 from Peter Jessup --- Hi Maik, I see those options but what I'm looking for is slightly different. The current metadata editor requires each individual image to be opened in a dialog, navigating in and out of each image file. Think of it this way, say the current "Table" view had the ability to add editable controls linked to the EXIF, IPTCX, XMP metadata fields which the user could update and tab copy/paste between. The user could then hit an save/update button to apply the metadata changes from the grid for many images and very efficiently much like updating a spreadsheet. The paradigm is where the exact metadata is not commonly shared between images, but is likely closely correlational - like date taken, location, caption, etc. The ability to edit the metadata for many correlated images in a single grid becomes quite powerful. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404595] copy/pasting animated frames from clipboard doesnt work accross Krita files.
https://bugs.kde.org/show_bug.cgi?id=404595 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/5b8660d22fbec0 |krita/commit/aa1b086860c77b |e838f03b853cdcf6e3cf2988a7 |498af8aea3914a2c1d21ddea34 --- Comment #6 from Boudewijn Rempt --- Git commit aa1b086860c77b498af8aea3914a2c1d21ddea34 by Boudewijn Rempt, on behalf of Ivan Yossi. Committed on 10/07/2019 at 07:49. Pushed by rempt into branch 'krita/4.2'. Fix copy/paste frames to clipboard This does not work if source was closed inbetween operations or source is in another krita instance. Related: bug 408421 M +34 -1plugins/dockers/animation/timeline_frames_model.cpp https://invent.kde.org/kde/krita/commit/aa1b086860c77b498af8aea3914a2c1d21ddea34 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408421] Safe Assert when copy/pasting animated frames between different open file timelines
https://bugs.kde.org/show_bug.cgi?id=408421 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/5b8660d22fbec0 |krita/commit/aa1b086860c77b |e838f03b853cdcf6e3cf2988a7 |498af8aea3914a2c1d21ddea34 --- Comment #8 from Boudewijn Rempt --- Git commit aa1b086860c77b498af8aea3914a2c1d21ddea34 by Boudewijn Rempt, on behalf of Ivan Yossi. Committed on 10/07/2019 at 07:49. Pushed by rempt into branch 'krita/4.2'. Fix copy/paste frames to clipboard This does not work if source was closed inbetween operations or source is in another krita instance. Related: bug 404595 M +34 -1plugins/dockers/animation/timeline_frames_model.cpp https://invent.kde.org/kde/krita/commit/aa1b086860c77b498af8aea3914a2c1d21ddea34 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 376007] CTRL and outline selection dont work with add and substract to the selection
https://bugs.kde.org/show_bug.cgi?id=376007 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/2aaa21f8142687 |krita/commit/bbdd9583898f15 |44a64ab7b6a9dbebbc29faa105 |006395f5852ccc4711a1f7552d --- Comment #3 from Boudewijn Rempt --- Git commit bbdd9583898f15006395f5852ccc4711a1f7552d by Boudewijn Rempt, on behalf of Ivan Yossi. Committed on 10/07/2019 at 07:49. Pushed by rempt into branch 'krita/4.2'. Avoid resetting selection mode when pressing control in outline This makes the polygon tool behave as the manual states, if a modifier is pressed it will be retained even it is let go mid selection. M +2-7plugins/tools/selectiontools/kis_tool_select_outline.cc https://invent.kde.org/kde/krita/commit/bbdd9583898f15006395f5852ccc4711a1f7552d -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408019] Crash after a drag'n'drop of a group of layers from one subwindows to another
https://bugs.kde.org/show_bug.cgi?id=408019 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/df5a97efdac6cd |krita/commit/50168c41f698d9 |08bf4c6d60576c2750c8b4de51 |735a5cf57501ed7383591e4ef6 --- Comment #5 from Boudewijn Rempt --- Git commit 50168c41f698d9735a5cf57501ed7383591e4ef6 by Boudewijn Rempt, on behalf of Agata Cacko. Committed on 10/07/2019 at 07:49. Pushed by rempt into branch 'krita/4.2'. Fix drag'n'drop of Fill layers between opened files Before this commit, that would result in crash if you drop the layer or the group with the layer on the canvas of another file (in the subwindows mode). This commit contains a fix so now it works as expected. M +1-0libs/image/kis_selection_based_layer.cpp https://invent.kde.org/kde/krita/commit/50168c41f698d9735a5cf57501ed7383591e4ef6 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 409665] kdesrc-build should be able to clone repos from invent.kde.org
https://bugs.kde.org/show_bug.cgi?id=409665 --- Comment #1 from Ben Cooksley --- I can confirm that the repositories still exist on git.kde.org - however they are indeed read-only (Gitlab propagates changes to git.kde.org, which are then picked up by the rest of our infrastructure) In terms of public cloning for Gitlab repositories, that is done over HTTPS from invent.kde.org (we'll likely remove git:// protocol support from the anongit network when we do the full switchover to Gitlab). -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 409666] New: e-Mail archive doesn't if KMail2 (Kontact) isn't running
https://bugs.kde.org/show_bug.cgi?id=409666 Bug ID: 409666 Summary: e-Mail archive doesn't if KMail2 (Kontact) isn't running Product: Akonadi Version: 5.10.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Archive Mail Agent Assignee: kdepim-b...@kde.org Reporter: bugrprt21...@online.de Target Milestone: --- SUMMARY After logging in the the KDE Plasma session, if Akonadi begins to automatically archive e-Mails before the KMail2 client is started, in my case by means of Kontact and, I also didn't start Kontact, then, the automatic e-Mail archive fails with "Can't open Mail Folder". Manually triggering the planned e-Mail Archive via KMail2 results in the planned Archive being successfully executed. STEPS TO REPRODUCE 1. Login to a KDE Plasma session where Akonadi is automatically started. 2. Don't start Kontact. 3. Wait. OBSERVED RESULT The automatic, planned, e-Mail Archive errors and, the bzip2 Archive file contains only a few bytes of rubbish. The expected Archive size is several hundred MBytes. EXPECTED RESULT The planned automatic e-Mail Archive should be executed by Akonadi without having to rely on the KDE Plasma session user starting either the KMail2 or Kontact application. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Leap 15.1 KDE Plasma Version: 5.12.8 KDE Frameworks Version: 5.55.0 Qt Version: 5.9.7 ADDITIONAL INFORMATION An unexpected, from an archiving view, more than fatal, Akonadi behaviour. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 409667] New: kdenlive crashes on startup with ASSERT failure in QCoreApplication::sendEvent: "Cannot send events to objects owned by a different thread"
https://bugs.kde.org/show_bug.cgi?id=409667 Bug ID: 409667 Summary: kdenlive crashes on startup with ASSERT failure in QCoreApplication::sendEvent: "Cannot send events to objects owned by a different thread" Product: kdenlive Version: 19.04.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Installation Assignee: vpi...@kde.org Reporter: fa...@kde.org Target Milestone: --- SUMMARY I build kdenlive from git branch Applications/19.04 (build type RelWithDebInfo), on top of a self-compiled Qt 5.13 from git, in debug mode. kdenlive asserts on startup, because setProperty() is called on GLWidget (a QQuickView) from the QtQuick render thread. setProperty calls sendEvent (with a QDynamicPropertyChangeEvent), which leads to the assert. (gdb) bt #0 0x7fffed807160 in raise () at /lib64/libc.so.6 #1 0x7fffed808741 in abort () at /lib64/libc.so.6 #2 0x7fffee722044 in qt_message_fatal(QtMsgType, QMessageLogContext const&, QString const&) (context=..., message="ASSERT failure in QCoreApplication::sendEvent: \"Cannot send events to objects owned by a different thread. Current thread 0x0x5446c90. Receiver '' (of type 'GLWidget') was created in thread 0x0xe57a80\", file /d/qt/5/kde/qtbase/src/corelib/kernel/qcoreapplication.cpp, line 578") at /d/qt/5/kde/qtbase/src/corelib/global/qlogging.cpp:1904 #3 0x7fffee722b30 in QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x7fff8dc033b0, msg=msg@entry=0x7fffee9d9858 "ASSERT failure in %s: \"%s\", file %s, line %d") at /d/qt/5/kde/qtbase/src/corelib/global/qlogging.cpp:888 #4 0x7fffee71cb69 in qt_assert_x(char const*, char const*, char const*, int) (where=where@entry=0x7fffeeab30cb "QCoreApplication::sendEvent", what=, file=file@entry=0x7fffeeab2968 "/d/qt/5/kde/qtbase/src/corelib/kernel/qcoreapplication.cpp", line=line@entry=578) at /d/qt/5/kde/qtbase/src/corelib/global/qglobal.cpp:3262 #5 0x7fffee8f4d9d in QCoreApplicationPrivate::checkReceiverThread(QObject*) (receiver=receiver@entry=0x25ecff0) at /d/qt/5/kde/qtbase/src/corelib/kernel/qcoreapplication.cpp:572 #6 0x704a0c0a in QApplication::notify(QObject*, QEvent*) (this=0x7fffcce0, receiver=0x25ecff0, e=0x7fff8dc036b0) at /d/qt/5/kde/qtbase/src/widgets/kernel/qapplication.cpp:2942 #7 0x7fffee8f5378 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x25ecff0, event=0x7fff8dc036b0) at /d/qt/5/kde/qtbase/src/corelib/kernel/qcoreapplication.cpp:1086 #8 0x7fffee8f55a0 in QCoreApplication::sendEvent(QObject*, QEvent*) (receiver=, event=) at /d/qt/5/kde/qtbase/src/corelib/kernel/qcoreapplication.cpp:1481 #9 0x7fffee92e13b in QObject::setProperty(char const*, QVariant const&) (this=this@entry=0x25ecff0, name=name@entry=0xade4de "mlt_service", value=...) at /d/qt/5/kde/qtbase/src/corelib/kernel/qobject.cpp:3946 #10 0x00785058 in GLWidget::reconfigure(bool) (this=this@entry=0x25ecff0, reload=reload@entry=false) at /d/kde/src/5/kde/kdemultimedia/kdenlive/src/monitor/glwidget.cpp:1222 #11 0x00785c9c in GLWidget::initializeGL() (this=0x25ecff0) at /d/kde/src/5/kde/kdemultimedia/kdenlive/src/monitor/glwidget.cpp:227 #12 0x7fffee926fd3 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7fff8dc039c8, r=0x25ecff0, this=) at ../../include/QtCore/../../../../qtbase/src/corelib/kernel/qobjectdefs_impl.h:394 #13 0x7fffee926fd3 in QMetaObject::activate(QObject*, int, int, void**) (sender=sender@entry=0x25ecff0, signalOffset=, local_signal_index=local_signal_index@entry=2, argv=0x7fff8dc039c8, argv@entry=0x0) at /d/qt/5/kde/qtbase/src/corelib/kernel/qobject.cpp:3787 #14 0x7fffee927429 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=0x25ecff0, m=m@entry=0x72cc3b00 , local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x0) at /d/qt/5/kde/qtbase/src/corelib/kernel/qobject.cpp:3658 #15 0x72806098 in QQuickWindow::sceneGraphInitialized() (this=) at .moc/moc_qquickwindow.cpp:503 #16 0x7280a466 in QQuickWindow::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=_o@entry=0x25ecff0, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=2, _a=_a@entry=0x7fff8dc03b18) at .moc/moc_qquickwindow.cpp:263 #17 0x7fffee92715d in QMetaObject::activate(QObject*, int, int, void**) (sender=sender@entry=0x263fae0, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=0x7fff8dc03b18, argv@entry=0x0) at /d/qt/5/kde/qtbase/src/corelib/kernel/qobject.cpp:3807 #18 0x7fffee927429 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x263fae0, m=m@entry=0x72cbebc0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at /d/qt/5/kde/qtbase/src/corelib/kernel/qobject.cpp:3658 #19 0x7277d26e
[KScreen] [Bug 409668] New: Screen switcher key stopped working in version 5.16
https://bugs.kde.org/show_bug.cgi?id=409668 Bug ID: 409668 Summary: Screen switcher key stopped working in version 5.16 Product: KScreen Version: 5.16.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: libkscreen Assignee: se...@kde.org Reporter: nicolam...@aol.com Target Milestone: --- SUMMARY After the upgrade to Plasma 5.16 the screen switch key on my Dell XPS 15 9570 stopped working. In previous versions it opened a dialog window where one could choose the output (on laptop screen, on external screen etc.). Now pressing it has no effect. It still emits Meta+P but it seems it is no longer bound to anything (I have not set up any custom shortcut but it used to work anyway with Plasma 5.15). SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux (available in About System) KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.59.0 Qt Version: 5.13.0 Kernel: 5.1.16 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394119] Panel should not stop auto-hiding even when a window wants attention
https://bugs.kde.org/show_bug.cgi?id=394119 lucian303 changed: What|Removed |Added CC||lucian...@gmail.com --- Comment #12 from lucian303 --- So let me get this straight. The *intended* behavior is that I click on every single window that demands attention each time it does so that autohide works? So every Whatsapp, Slack, Signal, Keybase message that comes in I have to switch to it to hide the panel> Every time FF or other app starts up I need to stop what I'm doing and click through these things? The whole point of having autohide is to remove distractions. This creates distractions. Look at the OSX toolbar. It autohides and doesn't pop up for a millisecond when u have notices. Same thing with Windows. You can see what notices you have when you unhide it with the mouse. That's the whole reason for autohiding. At the very least there should be an option to not show it when apps demand attention. It should be up to the user not the apps to show the panel. Sometimes apps like FF and PHPStorm demand attention for no reason just because they're starting up. I just get the dots and the panel is visible and I have to click on it and get distracted, and then try to get back to work. It took me two weeks simply to understand what was happening. At first I thought it was just random (also because the dots indicating an app wants attention are almost invisible). No desktop environment I have ever used does what this panel does. It's neither intuitive nor expected. This UX is beyond bizarre and frankly, unusable. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 409668] Screen switcher key stopped working in version 5.16
https://bugs.kde.org/show_bug.cgi?id=409668 Nicola Mori changed: What|Removed |Added CC||nicolam...@aol.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 409663] Faster Metadata editing interface
https://bugs.kde.org/show_bug.cgi?id=409663 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #3 from caulier.gil...@gmail.com --- Hi Peter, There is already a file about this whish. The goal is to apply the same changes on a set of files at the same time. The editor must take a care about the chnage to apply for each items, depending of values already assigned in metadata. If you play with CLementine audio player, there is a MP3 tags editor which work exactly like this with a 3 states editor for each metadata tags to changes. We need exactly this king of rules in digiKam metadata editor. See bug #372158 for details, where i explain also this plan for the future... Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[colord-kde] [Bug 409670] New: Color space information {primaries:INVALID, transfer:INVALID, matrix:INVALID, range:INVALID}
https://bugs.kde.org/show_bug.cgi?id=409670
Bug ID: 409670
Summary: Color space information {primaries:INVALID,
transfer:INVALID, matrix:INVALID, range:INVALID}
Product: colord-kde
Version: 0.3.0
Platform: Neon Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Systems Settings Module (KCM)
Assignee: dantt...@gmail.com
Reporter: prote...@hotmail.it
Target Milestone: ---
Created attachment 121437
--> https://bugs.kde.org/attachment.cgi?id=121437&action=edit
screenshot
SUMMARY
chrome/chromium on ubuntu base system reports this issue:
Color space information {primaries:INVALID, transfer:INVALID, matrix:INVALID,
range:INVALID}
STEPS TO REPRODUCE
1. install chromium
2. enter chrome:gpu as URL
3. look at the log result.
OBSERVED RESULT
Color space information {primaries:INVALID, transfer:INVALID, matrix:INVALID,
range:INVALID}
EXPECTED RESULT
right color space information.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: 5.16
(available in About System)
KDE Plasma Version: 5.16.2
KDE Frameworks Version: 5.59
Qt Version: 5.12.3
ADDITIONAL INFORMATION
https://github.com/agalakhov/xiccd/issues/22
--
You are receiving this mail because:
You are watching all bug changes.
[lightdm] [Bug 409669] New: Color space information {primaries:INVALID, transfer:INVALID, matrix:INVALID, range:INVALID}
https://bugs.kde.org/show_bug.cgi?id=409669
Bug ID: 409669
Summary: Color space information {primaries:INVALID,
transfer:INVALID, matrix:INVALID, range:INVALID}
Product: lightdm
Version: 0.3.2
Platform: Neon Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: k...@davidedmundson.co.uk
Reporter: prote...@hotmail.it
Target Milestone: ---
Created attachment 121436
--> https://bugs.kde.org/attachment.cgi?id=121436&action=edit
screenshot
SUMMARY
chrome/chromium on ubuntu base system reports this issue:
Color space information {primaries:INVALID, transfer:INVALID, matrix:INVALID,
range:INVALID}
STEPS TO REPRODUCE
1. install chromium
2. enter chrome:gpu as URL
3. look at the log result.
OBSERVED RESULT
Color space information {primaries:INVALID, transfer:INVALID, matrix:INVALID,
range:INVALID}
EXPECTED RESULT
right color space information.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: 5.16
(available in About System)
KDE Plasma Version: 5.16.2
KDE Frameworks Version: 5.59
Qt Version: 5.12.3
ADDITIONAL INFORMATION
https://github.com/agalakhov/xiccd/issues/22
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 409512] it doesn't let me draw. the presser point don't work and it only let me draw on the top left side of krita even though i am drawing on the bottom right of my wacom tabet
https://bugs.kde.org/show_bug.cgi?id=409512 Christoph Feck changed: What|Removed |Added Component|general |General Product|abakus |krita Assignee|k.h...@gmx.de |krita-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409512] it doesn't let me draw. the presser point don't work and it only let me draw on the top left side of krita even though i am drawing on the bottom right of my wacom tabet
https://bugs.kde.org/show_bug.cgi?id=409512 Christoph Feck changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Christoph Feck --- Please add the version information of the OS, the Wacom drivers, and for Krita. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 409667] kdenlive crashes on startup with ASSERT failure in QCoreApplication::sendEvent: "Cannot send events to objects owned by a different thread"
https://bugs.kde.org/show_bug.cgi?id=409667 Christoph Feck changed: What|Removed |Added CC||cf...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[lightdm] [Bug 409669] Color space information {primaries:INVALID, transfer:INVALID, matrix:INVALID, range:INVALID}
https://bugs.kde.org/show_bug.cgi?id=409669 David Edmundson changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 409671] New: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1".
https://bugs.kde.org/show_bug.cgi?id=409671 Bug ID: 409671 Summary: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". Product: kdevelop Version: 5.3.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: ghita.v.mar...@gmail.com Target Milestone: --- Created attachment 121438 --> https://bugs.kde.org/attachment.cgi?id=121438&action=edit backtrace SOFTWARE/OS VERSIONS OS: Fedora 30 KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.4 -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 409672] New: Crash when sorting
https://bugs.kde.org/show_bug.cgi?id=409672 Bug ID: 409672 Summary: Crash when sorting Product: trojita Version: 0.7 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Desktop GUI Assignee: trojita-b...@kde.org Reporter: johannes.kin...@gmail.com Target Milestone: --- SDescription of problem: Sort emails by data by clicking on the titel Version-Release number of selected component: trojita-0.7-14.fc30 Additional info: reporter: libreport-2.10.0 backtrace_rating: 4 cmdline:trojita crash_function: QSortFilterProxyModelPrivate::proxy_to_source executable: /usr/bin/trojita journald_cursor: s=8bf6ddad9d054d6a8450d20d9e266798;i=71a7;b=93c0cb19eb3b4ed5a8f2faddc4207f7f;m=17bc10e1;t=58d3b68ace9b5;x=70adca1c92536280 kernel: 5.1.12-300.fc30.x86_64 rootdir:/ runlevel: N 5 type: CCpp uid:1000 Truncated backtrace: Thread no. 1 (10 frames) #0 QSortFilterProxyModelPrivate::proxy_to_source at itemmodels/qsortfilterproxymodel.cpp:552 #1 QSortFilterProxyModel::mapToSource at itemmodels/qsortfilterproxymodel.cpp:3061 #2 QSortFilterProxyModel::flags at itemmodels/qsortfilterproxymodel.cpp:2487 #3 QModelIndex::flags at ../../include/QtCore/../../src/corelib/itemmodels/qabstractitemmodel.h:461 #4 QTreeViewPrivate::isIndexExpanded at ../../include/QtWidgets/5.12.1/QtWidgets/private/../../../../../src/widgets/itemviews/qtreeview_p.h:216 #5 QTreeView::isExpanded at itemviews/qtreeview.cpp:833 #6 QTreeView::verticalScrollbarValueChanged at itemviews/qtreeview.cpp:4018 #7 QAbstractItemView::qt_static_metacall at .moc/moc_qabstractitemview.cpp:423 #8 QMetaObject::activate at kernel/qobject.cpp:3789 #9 QAbstractSlider::valueChanged at .moc/moc_qabstractslider.cpp:308 Find attachment at https://bugzilla.redhat.com/show_bug.cgi?id=1728177 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 409225] Dependency problem to download libkf5networkmanagerqt-dev package
https://bugs.kde.org/show_bug.cgi?id=409225 Jonathan Riddell changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Jonathan Riddell --- This seems to work fine today on neon user edition, let me know if it's still a problem for you -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409673] For 10.15, we'll have to notarize our builds
https://bugs.kde.org/show_bug.cgi?id=409673 Boudewijn Rempt changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |ghe...@gmail.com Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #1 from Boudewijn Rempt --- Ivan, you're getting the short straw... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409673] New: For 10.15, we'll have to notarize our builds
https://bugs.kde.org/show_bug.cgi?id=409673 Bug ID: 409673 Summary: For 10.15, we'll have to notarize our builds Product: krita Version: unspecified Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: b...@valdyas.org Target Milestone: --- See https://bugreports.qt.io/browse/QTBUG-73398?focusedCommentId=468111&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-468111 for lots of information. We probably should start updating our macOS build scripts now. One problem is that we cannot notarize (or sign) our jenkins builds. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 385726] Add Support For Apple Live Photos
https://bugs.kde.org/show_bug.cgi?id=385726 Ritesh Raj Sarraf changed: What|Removed |Added CC||kde-b...@researchut.com --- Comment #13 from Ritesh Raj Sarraf --- Google has a similar feature in the form of motion images. Should I file a separate but report? Our can we track it on this report? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408402] "Extract Zone" not working
https://bugs.kde.org/show_bug.cgi?id=408402 --- Comment #4 from Jean-Baptiste Mardelle --- Git commit ff1fa2fdcaaa0727061e3dae42bfb9a4623ea328 by Jean-Baptiste Mardelle. Committed on 10/07/2019 at 09:54. Pushed by mardelle into branch 'master'. Reintroduce extract clip zone to cut a clip whithout re-encoding Fixes #237 M +1-1src/jobs/CMakeLists.txt M +150 -422 src/jobs/cutclipjob.cpp M +24 -30 src/jobs/cutclipjob.h M +1-1src/jobs/speedjob.cpp M +0-3src/mainwindow.cpp M +5-1src/monitor/monitor.cpp M +0-2src/monitor/monitor.h M +30 -5src/ui/cutjobdialog_ui.ui https://invent.kde.org/kde/kdenlive/commit/ff1fa2fdcaaa0727061e3dae42bfb9a4623ea328 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 409323] Revoke "Network Disconnected" notification once the network is re-connected
https://bugs.kde.org/show_bug.cgi?id=409323 Jan Grulich changed: What|Removed |Added CC||jgrul...@redhat.com --- Comment #2 from Jan Grulich --- I experience a similar issue with notifications from Konversation or from KMail. Notificatons in plasma-nm have KNotification::CloseOnTimeout set, they should be automatically closed, which is not happening from some reason. @Kai, do you have idea what could be wrong? I'm running Plasma on Wayland if that is relevant. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409674] New: Sudden plasma crash (v5.16.3)
https://bugs.kde.org/show_bug.cgi?id=409674 Bug ID: 409674 Summary: Sudden plasma crash (v5.16.3) Product: plasmashell Version: 5.16.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: zawer...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.16.3) Qt Version: 5.12.4 Frameworks Version: 5.59.0 Operating System: Linux 5.1.12-300.fc30.x86_64 x86_64 Distribution: "Fedora release 30 (Thirty)" -- Information about the crash: I see this crash right after updating to plasma 5.16.3. I have no third party plasma widgets installed. The crash does not seem to be reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 29return SYSCALL_CANCEL (poll, fds, nfds, timeout); [Current thread is 1 (Thread 0x7f3275c1ad00 (LWP 28087))] Thread 19 (Thread 0x7f31fa8b7700 (LWP 2457)): #0 0x7f327bd204d5 in futex_wait_cancelable (private=0, expected=0, futex_word=0x55f5e99cbd04) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f327bd204d5 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55f5e99cbcb0, cond=0x55f5e99cbcd8) at pthread_cond_wait.c:502 #2 0x7f327bd204d5 in __pthread_cond_wait (cond=0x55f5e99cbcd8, mutex=0x55f5e99cbcb0) at pthread_cond_wait.c:655 #3 0x7f327c87f283 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib64/libQt5Core.so.5 #4 0x7f327c87f311 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #5 0x7f327e61ff59 in () at /lib64/libQt5Quick.so.5 #6 0x7f327e6201fd in () at /lib64/libQt5Quick.so.5 #7 0x7f327c879786 in () at /lib64/libQt5Core.so.5 #8 0x7f327bd1a5a2 in start_thread (arg=) at pthread_create.c:486 #9 0x7f327c4f8303 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7f321666a700 (LWP 2413)): #0 0x7f327bd204d5 in futex_wait_cancelable (private=0, expected=0, futex_word=0x55f5e7e8bcc0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f327bd204d5 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55f5e7e8bc70, cond=0x55f5e7e8bc98) at pthread_cond_wait.c:502 #2 0x7f327bd204d5 in __pthread_cond_wait (cond=0x55f5e7e8bc98, mutex=0x55f5e7e8bc70) at pthread_cond_wait.c:655 #3 0x7f327c87f283 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib64/libQt5Core.so.5 #4 0x7f327c87f311 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #5 0x7f327e61ff59 in () at /lib64/libQt5Quick.so.5 #6 0x7f327e6201fd in () at /lib64/libQt5Quick.so.5 #7 0x7f327c879786 in () at /lib64/libQt5Core.so.5 #8 0x7f327bd1a5a2 in start_thread (arg=) at pthread_create.c:486 #9 0x7f327c4f8303 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7f3216ffd700 (LWP 2363)): #0 0x7f327bd204d5 in futex_wait_cancelable (private=0, expected=0, futex_word=0x55f5e8170e14) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f327bd204d5 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55f5e8170dc0, cond=0x55f5e8170de8) at pthread_cond_wait.c:502 #2 0x7f327bd204d5 in __pthread_cond_wait (cond=0x55f5e8170de8, mutex=0x55f5e8170dc0) at pthread_cond_wait.c:655 #3 0x7f327c87f283 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib64/libQt5Core.so.5 #4 0x7f327c87f311 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #5 0x7f3258ee3ba0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5 #6 0x7f3258ee781e in () at /lib64/libKF5ThreadWeaver.so.5 #7 0x7f3258ee2d72 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #8 0x7f3258ee7879 in () at /lib64/libKF5ThreadWeaver.so.5 #9 0x7f3258ee2d72 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /lib64/libKF5ThreadWeaver.so.5 #10 0x7f3258ee57d3 in ThreadWeaver::Thread::run() () at /lib64/libKF5ThreadWeaver.so.5 #11 0x7f327c879786 in () at /lib64/libQt5Core.so.5 #12 0x7f327bd1a5a2 in start_thread (arg=) at pthread_create.c:486 #13 0x7f327c4f8303 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 16 (Thread 0x7f32177fe700 (LWP 2362)): #0 0x7f327bd204d5 in futex_wait_cancelable (private=0, expected=0, futex_word=0x55f5e8170e14) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f327bd204d5 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55f5e8170dc0, cond=0x55f5e8170de8) at pthread_cond_wait.c:502 #2 0x7f327bd204d5 in __pthread_cond_wait (cond=0x55f5e8170de8, mutex=0x55f5e81
[trojita] [Bug 409672] Crash when sorting
https://bugs.kde.org/show_bug.cgi?id=409672 Jan Kundrát changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |UPSTREAM --- Comment #1 from Jan Kundrát --- This backtrace looks like a crash somewhere deep in the Qt stack. Yes, we're banging the QAbstractProxyModel quite intensively, but we've got test coverage for this. Unless you can reproduce this with the latest git of Trojita and with assertions enabled, I'm closing this as a "possible bug in Qt". -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 409675] New: Main window does not remember its position.
https://bugs.kde.org/show_bug.cgi?id=409675 Bug ID: 409675 Summary: Main window does not remember its position. Product: kate Version: 19.04.2 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: critical Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: michal.m...@mitec.cz Target Milestone: --- SUMMARY Main window does not remember its position. STEPS TO REPRODUCE 1. Change windows size and position 2. Close app 3. Run app OBSERVED RESULT Size is restored but window position not. It seems that top-left corner is set to the same position regardless of position set by user. EXPECTED RESULT Window position should be restored to last set. SOFTWARE/OS VERSIONS Windows: 10 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.
[frameworks-knotifications] [Bug 409676] New: all notifications no more stored in kde notifier history
https://bugs.kde.org/show_bug.cgi?id=409676 Bug ID: 409676 Summary: all notifications no more stored in kde notifier history Product: frameworks-knotifications Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: philippe.roub...@free.fr CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY All notifications no more stored in kde notifier history. Only a window pops up for every notification then disappears Only kdeconnect notifications are stored in kde notifier history. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.59.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION openSuse 15.1 kde apps 19.04.2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 409676] all notifications no more stored in kde notifier history
https://bugs.kde.org/show_bug.cgi?id=409676 Philippe ROUBACH changed: What|Removed |Added Version|unspecified |5.59.0 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 409677] New: Main window is not brought to front when file is opened from outside (e.g. via association click)
https://bugs.kde.org/show_bug.cgi?id=409677 Bug ID: 409677 Summary: Main window is not brought to front when file is opened from outside (e.g. via association click) Product: kate Version: 19.04.2 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: critical Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: michal.m...@mitec.cz Target Milestone: --- SUMMARY Main window is not brought to front when file is opened from outside (e.g. via association click). STEPS TO REPRODUCE 1. Associate Kate with txt files 2. Open Kate 3. Go to explorer, find any txt file and double-click OBSERVED RESULT File is opened in Kate but Kate is not brought to front (only its icon in taskbat blinks) EXPECTED RESULT Kate should get focus and become front window SOFTWARE/OS VERSIONS Windows: 10 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.
[valgrind] [Bug 409678] New: improvement suggestion for dhat
https://bugs.kde.org/show_bug.cgi?id=409678 Bug ID: 409678 Summary: improvement suggestion for dhat Product: valgrind Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: dhat Assignee: jsew...@acm.org Reporter: plasm...@gmx.net Target Milestone: --- Created attachment 121439 --> https://bugs.kde.org/attachment.cgi?id=121439&action=edit patch against git VALGRIND_3_14_0-225-g514f89938 In my work dhat is almost useful, since the most important thing isn't which byte of a struct is accessed, but in which way (read/write), to avoid things like false sharing. Therefore we have always been using a modification of exp-dhat, and now that we have upgraded to the overhauled version of valgrind/dhat we had to adapt to the new kind of output and I would like to share our patch (we also made the output a little bit nicer formatted, but didn't really bother to integrate it into the drop down filter). Hopefully you can integrate some or all of this into dhat to make it even more useful. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394119] Panel should not stop auto-hiding even when a window wants attention
https://bugs.kde.org/show_bug.cgi?id=394119 --- Comment #13 from Michael Zanetti --- (In reply to lucian303 from comment #12) > So let me get this straight. The *intended* behavior is that I click on > every single window that demands attention each time it does so that > autohide works? So every Whatsapp, Slack, Signal, Keybase message that comes > in I have to switch to it to hide the panel> Every time FF or other app > starts up I need to stop what I'm doing and click through these things? The > whole point of having autohide is to remove distractions. This creates > distractions. Look at the OSX toolbar. It autohides and doesn't pop up for a > millisecond when u have notices. Same thing with Windows. You can see what > notices you have when you unhide it with the mouse. That's the whole reason > for autohiding. At the very least there should be an option to not show it > when apps demand attention. It should be up to the user not the apps to show > the panel. Sometimes apps like FF and PHPStorm demand attention for no > reason just because they're starting up. I just get the dots and the panel > is visible and I have to click on it and get distracted, and then try to > get back to work. It took me two weeks simply to understand what was > happening. At first I thought it was just random (also because the dots > indicating an app wants attention are almost invisible). No desktop > environment I have ever used does what this panel does. It's neither > intuitive nor expected. This UX is beyond bizarre and frankly, unusable. Now, I agree with pretty much you are saying here. I'd still like to remind you that we're all supposed to be friends here and be nice to each other :). I also understand that's hard at times, because, I also agree this bug can be so annoying that it makes one angry when it's interrupting a focus demanding workflow. @triffid.hunger, after reading the review comments from David on your patch, I understand your patch will prevent all plasmoids from popping up, not just the panel. I can understand that this is not a solution that will be accepted upstream. Do you think you could try and fix this in a way that could be accepted upstream? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408908] File Transfer notification are gone since update to Plasma 5.16.0
https://bugs.kde.org/show_bug.cgi?id=408908 --- Comment #6 from JORGETECH --- In another computer where I have KDE configured with the "icon only" taskbar I still don't have file transfer notifications, instead I get a file transfer window. Any ideas on why I get a window on this particular setup? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 409585] QMYSQL driver not loaded
https://bugs.kde.org/show_bug.cgi?id=409585 --- Comment #6 from Maik Qualmann --- I'm a little further. It is not the binary in itself, because your panorama plugin copied into my Windows installation is loaded without problems by the Qt plugin loader. The number of files is different, in your installation missing 14 DLL files. I list tonight which ones are it. I suspect that the workaround with "LANG=C" is not working correctly. Maik -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409284] kwin does not allow for disabling optional libhybris
https://bugs.kde.org/show_bug.cgi?id=409284 --- Comment #7 from Dennis veatch --- Hmm. Well using https://mirrors.dotsrc.org/qtproject/official_releases/qt/5.13/5.13.0/single/ so assuming that's the official release. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394119] Panel should not stop auto-hiding even when a window wants attention
https://bugs.kde.org/show_bug.cgi?id=394119 --- Comment #14 from triffid.hun...@gmail.com --- I haven't experienced the issue since adding my comment #1 patch into my local patchset, and I'm not even slightly familiar with KDE/QT programming.. Care to offer any pointers for more suitable places to put it? Since it alters a file called 'panelview.cpp' and specifically ignores 'NeedsAttentionStatus', I haven't currently any better ideas. I guess for best results, a user setting would need to be added to panel config that controls whether or not 'NeedsAttentionStatus' is ignored wrt panel hiding? That's a little beyond my skill currently but perhaps I can have a dig when I've some time and try to work it out - unless one of these other infuriated folk beat me to it ;) I'm not really sure what the point about 'other plasmoids' is, the panel is basically the only thing I have with widgets and I don't use it that often, so I'm not sure if I'd even notice if I inadvertently break these 'other plasmoids'.. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 409679] New: Kmail crash when open through a mailto link
https://bugs.kde.org/show_bug.cgi?id=409679 Bug ID: 409679 Summary: Kmail crash when open through a mailto link Product: kmail2 Version: 5.11.2 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: sylv...@sbx.pm Target Milestone: --- Application: kmail (5.11.2) Qt Version: 5.12.3 Frameworks Version: 5.59.0 Operating System: Linux 4.15.0-54-generic x86_64 Distribution: KDE neon Plasma LTS Edition 5.12 -- Information about the crash: - What I was doing when the application crashed: I clicked on a link like mailto:x...@yyy.com, in Firefox. Kmail never opened but the error reporting tool was shown. I tried twice and the error was thrown each times. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f898767bbc0 (LWP 26688))] Thread 20 (Thread 0x7f88cbfff700 (LWP 27595)): #0 0x7f8979e31ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f88cbffe710, expected=0, futex_word=0x7f88cbffe8f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7f88cbffe7b0, mutex=0x7f88cbffe8a8, cond=0x7f88cbffe8d0) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x7f88cbffe8d0, mutex=0x7f88cbffe8a8, abstime=0x7f88cbffe7b0) at pthread_cond_wait.c:667 #3 0x7f896ef0cb17 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f896ef0d46a in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f896ef0d552 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f896eecdfb1 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f896eed04c7 in base::internal::SchedulerWorker::RunWorker() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f896eed0ab4 in base::internal::SchedulerWorker::RunPooledWorker() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f896ef0f561 in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f8979e2b6db in start_thread (arg=0x7f88cbfff700) at pthread_create.c:463 #11 0x7f89846b688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7f88f8ff9700 (LWP 27552)): #0 0x7f8979e319f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f88f8ff8908) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7f88f8ff88b8, cond=0x7f88f8ff88e0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7f88f8ff88e0, mutex=0x7f88f8ff88b8) at pthread_cond_wait.c:655 #3 0x7f896ef0ca49 in base::ConditionVariable::Wait() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f896ef0d478 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f896ef0d50f in base::WaitableEvent::Wait() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f896eecdfc8 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f896eed07f6 in base::internal::SchedulerWorker::RunWorker() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f896eed0b34 in base::internal::SchedulerWorker::RunDedicatedWorker() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f896ef0f561 in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f8979e2b6db in start_thread (arg=0x7f88f8ff9700) at pthread_create.c:463 #11 0x7f89846b688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7f88f97fa700 (LWP 27549)): #0 __lll_lock_wait_private () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95 #1 0x7f89846c7474 in ___fprintf_chk (fp=0x7f89849828b0 <_IO_stdfile_2_lock>, flag=1, format=0x7f89645d06a8 "[%s] %s\n") at fprintf_chk.c:30 #2 0x7f89645b89ad in event_logv_ () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #3 0x7f89645b8b44 in event_warn () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #4 0x7f89645ba46c in ?? () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #5 0x7f89645b0114 in event_base_loop () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #6 0x7f896ef12db4 in base::MessagePumpLibevent::Run(base::Messag
[plasmashell] [Bug 409680] New: [Wayland] Neon unstable edition - After you dismiss Notes widget placed in plasma panel, you can not minimize an app by clicking its entry in task manager
https://bugs.kde.org/show_bug.cgi?id=409680 Bug ID: 409680 Summary: [Wayland] Neon unstable edition - After you dismiss Notes widget placed in plasma panel, you can not minimize an app by clicking its entry in task manager Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: 1.0 STEPS TO REPRODUCE 1. start Wayland session 2. add Notes widget to plasma panel 3. open Dolṕhin 4. click on Notes widget placed on your panel 5. click on Dolphin window to dismiss Notes widget 6. click on Dolphin entry in task manager to minimize it OBSERVED RESULT nothing hapeens, Dolphin is not minimized EXPECTED RESULT Dolphin is minimized SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.16.80 KDE Frameworks Version: 5.60.0 Qt Version: 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 345979] kmail stucks reegualary when syncing a gmail-imap-akonadi-ressource
https://bugs.kde.org/show_bug.cgi?id=345979 Tom Kijas changed: What|Removed |Added CC||t.ki...@gmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED Version|5.6.0 |5.11.2 --- Comment #5 from Tom Kijas --- I have same experience for months and THANK YOU for workaround - akonadictl restart in konsole. I use latest KDE NEON (Ubuntu based) User edition KMail 5.11.2 KDE Frameworks 5.59.0 Qt 5.12.3 regularly the akonadi dies and emails stays in Outgoing folder forever. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 407181] [RFE] Display WiFi access point connection information as QR code for consumption of mobile devices
https://bugs.kde.org/show_bug.cgi?id=407181 Jan Grulich changed: What|Removed |Added Summary|Display WiFi access point |[RFE] Display WiFi access |connection information as |point connection |QR code for consumption of |information as QR code for |mobile devices |consumption of mobile ||devices CC||jgrul...@redhat.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 403547] plasma-nm Wireguard: redundant options offered in the Advanced configuration
https://bugs.kde.org/show_bug.cgi?id=403547 Jan Grulich changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Jan Grulich --- Shouldn't be a problem with Plasma 5.16. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 377029] Crash in connection editor when importing openvpn connection
https://bugs.kde.org/show_bug.cgi?id=377029 Jan Grulich changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #4 from Jan Grulich --- I believe this is no longer a problem. Please re-open if you still can reproduce this issue. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 409656] Unable to get feeds
https://bugs.kde.org/show_bug.cgi?id=409656 --- Comment #4 from Manuel Alcaraz --- Hello. I don't use a proxy server and I don't have the ad blocker plugin enabled. After some tests, I think that the error is caused after resuming from hibernation. I installed kdebugsettings and I get this error: kf5.syndication: Retriever error: 114 This time a could fetch my feeds after manually clicking on the "Fetch All Feeds" button, but auto update didn't work. Note: > This happened since Akregator updated to 5.11.2 I'm not sure -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 385370] Crash System Settings Module
https://bugs.kde.org/show_bug.cgi?id=385370 Jan Grulich changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #8 from Jan Grulich --- I believe this is no longer a problem. Please re-open if you still can reproduce this issue. -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 409681] New: Lokalize silently fails to show project tree on KIO error
https://bugs.kde.org/show_bug.cgi?id=409681 Bug ID: 409681 Summary: Lokalize silently fails to show project tree on KIO error Product: lokalize Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: project management Assignee: sdepi...@gmail.com Reporter: aspotas...@gmail.com CC: sha...@ukr.net Target Milestone: --- SUMMARY Lokalize silently fails to show project tree on KIO error. STEPS TO REPRODUCE 1. Have a problem with KIO's file.so. 2. Open a project in Lokalize. OBSERVED RESULT Project tree is empty. On the command line: kf5.kio.core: couldn't create slave: "Ответ от klauncher: Ошибка загрузки «/usr/lib64/qt5/plugins/kf5/kio/file.so»." kf5.kio.core: "Ошибка создания вспомогательного процесса ввода/вывода. Ответ от klauncher: Ошибка загрузки «/usr/lib64/qt5/plugins/kf5/kio/file.so»." EXPECTED RESULT Lokalize should report this error in its GUI. SOFTWARE/OS VERSIONS Operating System: Fedora 30 KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.4 Kernel Version: 5.1.8-300.fc30.x86_64 OS Type: 64-bit Processors: 2 × Intel® Celeron® CPU B800 @ 1.50GHz Memory: 3,8 ГиБ ADDITIONAL INFORMATION Lokalize 19.07.70 (built from Git master some months ago). -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 398332] Plasma (plasmashell), signal: Segmentation fault: QQmlDelegateModel::_q_layoutChanged(QList const&, QAbstractItemModel::LayoutChangeHint)
https://bugs.kde.org/show_bug.cgi?id=398332 Jan Grulich changed: What|Removed |Added Resolution|--- |FIXED CC||jgrul...@redhat.com Status|REPORTED|RESOLVED --- Comment #1 from Jan Grulich --- This was a bug in Qt some time ago, fixed in newer versions. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 398280] [RFE] Enhancement of plasma-nm for include proxy settings
https://bugs.kde.org/show_bug.cgi?id=398280 Jan Grulich changed: What|Removed |Added CC||jgrul...@redhat.com Summary|Enhancement of plasma-nm|[RFE] Enhancement of |for include proxy settings |plasma-nm for include proxy ||settings -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 409323] Revoke "Network Disconnected" notification once the network is re-connected
https://bugs.kde.org/show_bug.cgi?id=409323 --- Comment #3 from Kai Uwe Broulik --- Once in history, there's nothing you can do. We could add a "don't preserve in history flag" maybe or at least revoke the notification when its popup is still shown. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394119] Panel should not stop auto-hiding even when a window wants attention
https://bugs.kde.org/show_bug.cgi?id=394119 --- Comment #15 from Ville Aakko --- So, to recap: I believe there are actually two parts to the problem here; 1) An application wanting attention, causing *task manager* to want attention, and 2) the way any auto-hide enabled panels behave when *any plasmoid* in them wants attention (see the discussion in phabricator; this comments makes more sense as a whole after reading that, too). I believe most people are experiencing this bug because of task manager - the chain of autohide misbehaving in this case is something like this: * Application wants attention -> * Task Manager notices the application and wants attention -> * Panel not autohiding since a plasmoid (Task Manager in this case) wants attention. However, IMHO the panel should autohide no matter what plasmoid wants attention - just that no other plasmoid seems to cause this, or does it only very rarely, should not be a reason to have this prevention of autohide in the first place. That's just weird design - can't think of any reason / situation I'd want to be notified this way! I also firmly believe the behavior user experiences is not something even the developer of a application wanted. Many applications might not even be aware / had nothing to do with KDE/Plasma when they made their application. I'm speculating here: perhaps the whole feature is poorly documented, and/or even misunderstood by developers? In any case, the current situation is a mess, as there is no way for the end user to disable it, and bad assumptions have been made when designing the whole thing. However, it is difficult to say for sure - in case someone knows of some pointers to documentation, which any programmer making an application should adhere to, would be a nice addition to this discussion. It would still be a mess to fix each and every application! I have problems regularly with Steam client, Firefox, and FAHControl (these are just most annoying and often re-occuring examples - there are others). None of these were probably dessigned this way with the intention to clutter user desktop interface! FWIW, I think I've had a few cases of some system tray icon preventing autohide, which I would not have rather had. They have happened only rarely, and I don't remember the details. I don't believe there are any other plasmoids which could seek attention - and if they did, they would certainly be promptly removed from the task bar. Sadly, the task manager is a major point of having the panel in the first place, and there is no good replacement. In summary: I believe this should be fixed at the panel level (not per-plasmoid, as proposed in Fabricator). However, a task-manager specific option would be welcome, too, to at least alleviate the problem. Also, some pointers to documentation would be welcome - is this really something application makers are and/or should be aware of, when making their applications? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409682] New: Krita crashes when using flood-fill
https://bugs.kde.org/show_bug.cgi?id=409682 Bug ID: 409682 Summary: Krita crashes when using flood-fill Product: krita Version: 4.2.2 Platform: Other OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: ramskulls...@gmail.com Target Milestone: --- Created attachment 121440 --> https://bugs.kde.org/attachment.cgi?id=121440&action=edit Krita crash log SUMMARY Krita has been crashing when I try to use flood-fill multiple times STEPS TO REPRODUCE 1. Create a canvas around 2000x2000 2. Draw on a layer and duplicate it 3. Lock the duplicate layer and try to fill multiple times OBSERVED RESULT Krita stops responding and crashes EXPECTED RESULT Krita flood fills layer with selected color SOFTWARE/OS VERSIONS Windows 10 ADDITIONAL INFORMATION Krita Version: 4.2.2 Languages: en_US Hidpi: false Qt Version (compiled): 5.12.4 Version (loaded): 5.12.4 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.17763 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 Hardware Information GPU Acceleration: desktop Memory: 16065 Mb Number of Cores: 8 Swap Location: C:/Users/Ramskulls/AppData/Local/Temp -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 345979] kmail stucks reegualary when syncing a gmail-imap-akonadi-ressource
https://bugs.kde.org/show_bug.cgi?id=345979 --- Comment #6 from avlas --- This happens to me (in KDE neon) most of the times after "Accepting a Google Calendar Invitation Request" in my gmail account. The email that is sent (not always but very frequently, I would say 80% of the times or more) gets stuck and then no more emails can be sent from any account (gmail and others). Saying because if you could reproduce this behavior, it may help to debug and fix the issue. [Note: I have the feeling that this happens more frequently if the akonadi process has been running for a while] -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409017] It is not possible to view/remove the packages installed via Add-On installer
https://bugs.kde.org/show_bug.cgi?id=409017 Ivan changed: What|Removed |Added Version|5.16.2 |5.16.3 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409683] New: SystemSettings crash on installing local gtk theme tar.gz
https://bugs.kde.org/show_bug.cgi?id=409683 Bug ID: 409683 Summary: SystemSettings crash on installing local gtk theme tar.gz Product: systemsettings Version: 5.16.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: rahil.rules@gmail.com Target Milestone: --- Application: systemsettings5 (5.16.3) Qt Version: 5.13.0 Frameworks Version: 5.59.0 Operating System: Linux 5.1.16-arch1-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: I downloaded https://store.kde.org/p/1275087 tar.gz file and tried to import it to systemsettings install local theme dialog. Since it doesn't support tar.xz, I converted it to tar.gz by extracting and compressing into a tar.gz again. After selecting the file, the systemsettings application crashed The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f92a82f4840 (LWP 19380))] Thread 8 (Thread 0x7f927dfa5700 (LWP 19591)): #0 0x7f92ad1bd18c in read () at /usr/lib/libc.so.6 #1 0x7f92aad4e961 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f92aad9ef70 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f92aada0766 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f92aada08ae in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f92ad7629bc in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f92ad7095ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f92ad53c2f5 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f92ad53d520 in () at /usr/lib/libQt5Core.so.5 #9 0x7f92abb7a57f in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f92ad1cc0e3 in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f927700 (LWP 19589)): #0 0x7f92ad1c1667 in poll () at /usr/lib/libc.so.6 #1 0x7f92aada07c0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f92aada08ae in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f92ad7629bc in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f92ad7095ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f92ad53c2f5 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f92ad53d520 in () at /usr/lib/libQt5Core.so.5 #7 0x7f92abb7a57f in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f92ad1cc0e3 in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f9285138700 (LWP 19588)): #0 0x7f92aad4e3a9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7f92aada0899 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #2 0x7f92ad7629bc in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f92ad7095ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f92ad53c2f5 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f92ad53d520 in () at /usr/lib/libQt5Core.so.5 #6 0x7f92abb7a57f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f92ad1cc0e3 in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f9292c56700 (LWP 19386)): #0 0x7f92ad53d99c in QMutex::lock() () at /usr/lib/libQt5Core.so.5 #1 0x7f92ad7628b0 in () at /usr/lib/libQt5Core.so.5 #2 0x7f92aada008a in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #3 0x7f92aada06e6 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f92aada08ae in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f92ad7629bc in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f92ad7095ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f92ad53c2f5 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f92ac84a8f9 in () at /usr/lib/libQt5Qml.so.5 #9 0x7f92ad53d520 in () at /usr/lib/libQt5Core.so.5 #10 0x7f92abb7a57f in start_thread () at /usr/lib/libpthread.so.0 #11 0x7f92ad1cc0e3 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f929cd6b700 (LWP 19385)): #0 0x7f92aad4e3a9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7f92aada0899 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #2 0x7f92ad7629bc in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f92ad7095ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f92ad53c2f5 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f92ac84a8f9 in () at /usr/lib/libQt5Qml.so.5 #6 0x7f92ad53d520 in () at /usr/lib/libQt5Core.so.5 #7 0x7f92abb7a57f in start_threa
[krita] [Bug 409682] Krita crashes when using flood-fill
https://bugs.kde.org/show_bug.cgi?id=409682 --- Comment #1 from ramskulls...@gmail.com --- The file is too big to upload so I try a link: https://drive.google.com/file/d/1R2toaGfXvRv5VQBL8hMGe2x9qYSRZaQq/view?usp=sharing -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409682] Krita crashes when using flood-fill
https://bugs.kde.org/show_bug.cgi?id=409682 --- Comment #2 from Boudewijn Rempt --- I see there are basically two different crashes in this log, one occurs only once, the other at least nine times: The one that occurs only once: krita.exe caused an Access Violation at location 7FFF53E85C32 in module libkritapigment.dll Reading from location 0038. AddrPC Params 7FFF53E85C32 7FFF46F92310 5374F620 5374F620 libkritapigment.dll!0x55c32 KoResource::md5+0x42 7FFF487629BB 7FFF51CA3F30 5374 254209B0 libkritalibpaintop.dll!0x529bb operator==+0x5b 7FFF48763A0B 5374F6E8 7FFF969F9D0C 25420A20 libkritalibpaintop.dll!0x53a0b KisTextureMaskInfoCache::fetchCachedTextureInfo+0x3b 7FFF48760F89 0030 0480 libkritalibpaintop.dll!0x50f89 KisTextureProperties::fillProperties+0x179 7FFF4871AEB4 0002 00184380 00180D20 libkritalibpaintop.dll!0xaeb4 KisBrushBasedPaintOp::KisBrushBasedPaintOp+0x1a4 7FFF46F776FB F5155857 7FFF516F907C 7FFF51CA3F30 kritadefaultpaintops.dll!0x76fb KisBrushOp::KisBrushOp+0x4b 7FFF46F94C4B 7FFF51CA3F30 5374F9D8 5374F9E0 kritadefaultpaintops.dll!0x24c4b KisSimplePaintOpFactory::createOp+0x7b 7FFF51CC1D79 1BA9A000 0002 006326F0 libkritaimage.dll!0x41d79 KisPaintOpRegistry::paintOp+0xd9 7FFF51CC23FB 1757FAA0 0006 0006 libkritaimage.dll!0x423fb KisPaintOpRegistry::paintOp+0xab 7FFF51CA3C64 5374FC18 5374FD00 5374FC18 libkritaimage.dll!0x23c64 KisPainter::setPaintOpPreset+0xb4 7FFF4CE24585 5374FD08 0001 1BF0BD10 libkritaui.dll!0x1d4585 KisResourcesSnapshot::setupPainter+0x1d5 7FFF4CE2E988 0100 5374FD08 libkritaui.dll!0x1de988 KisPainterBasedStrokeStrategy::initPainters+0x178 7FFF4CE2F326 7FFF969F9DB0 libkritaui.dll!0x1df326 KisPainterBasedStrokeStrategy::initStrokeCallback+0x466 7FFF4CE2A5CD 1BF0BA10 000351848D8D 00F8 libkritaui.dll!0x1da5cd FreehandStrokeStrategy::initStrokeCallback+0xd 7FFF51F4BFC4 0010 1BF0BA10 1C7B4770 libkritaimage.dll!0x2cbfc4 KisUpdateJobItem::run+0x84 7FFF51678620 2593D0B0 1C7B4700 Qt5Core.dll!0x28620 QThreadPool::tryStart+0x520 7FFF5167169B Qt5Core.dll!0x2169b QThread::qt_metacall+0x68b 7FFF96EC7974 KERNEL32.DLL!0x17974 BaseThreadInitThunk+0x14 7FFF9706A271 ntdll.dll!0x6a271 RtlUserThreadStart+0x21 And the one that occurs many times: krita.exe caused an Access Violation at location 7FFF5EE29C47 in module libkritaimage.dll Reading from location 0029. AddrPC Params 7FFF5EE29C47 libkritaimage.dll!0x2d9c47 KisTileDataSwapper::pass+0xa7 7FFF5EB68CC0 157F0AE0 libkritaimage.dll!0x18cc0 KisTileDataSwapper::doJob+0x80 7FFF5EB68D3F 7FFF5EFFF0E0 157F0A00 libkritaimage.dll!0x18d3f KisTileDataSwapper::run+0x2f 7FFF4CB8169B Qt5Core.dll!0x2169b QThread::qt_metacall+0x68b 7FFF96EC7974 KERNEL32.DLL!0x17974 BaseThreadInitThunk+0x14 7FFF9706A271 ntdll.dll!0x6a271 RtlUserThreadStart+0x21 Two questions: -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409682] Krita crashes when using flood-fill
https://bugs.kde.org/show_bug.cgi?id=409682 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #3 from Boudewijn Rempt --- Note: "locked" is "alpha-locked" -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 409684] New: okular crashes when opening a pdf file I got from government website
https://bugs.kde.org/show_bug.cgi?id=409684 Bug ID: 409684 Summary: okular crashes when opening a pdf file I got from government website Product: okular Version: 1.7.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: a...@mizerski.pl Target Milestone: --- Application: okular (1.7.2) Qt Version: 5.12.3 Frameworks Version: 5.59.0 Operating System: Linux 5.1.10-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I tried openin a pdf file, I'll attach to this report in a minute. The crash can be reproduced every time. -- Backtrace: Application: Okular (okular), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 29return SYSCALL_CANCEL (poll, fds, nfds, timeout); [Current thread is 1 (Thread 0x7f2d398de900 (LWP 16562))] Thread 4 (Thread 0x7f2d2e050700 (LWP 16567)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x56552ae58768) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x56552ae58718, cond=0x56552ae58740) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x56552ae58740, mutex=0x56552ae58718) at pthread_cond_wait.c:655 #3 0x7f2d2e34733b in ?? () from /usr/lib64/dri/i965_dri.so #4 0x7f2d2e346f57 in ?? () from /usr/lib64/dri/i965_dri.so #5 0x7f2d3ad65faa in start_thread (arg=) at pthread_create.c:486 #6 0x7f2d3b63571f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f2d35f1b700 (LWP 16566)): #0 __GI___libc_read (nbytes=16, buf=0x7f2d35f1aa60, fd=7) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=7, buf=0x7f2d35f1aa60, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f2d3a2c43bf in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f2d3a27d85e in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #4 0x7f2d3a27dcd2 in ?? () from /usr/lib64/libglib-2.0.so.0 #5 0x7f2d3a27de4f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #6 0x7f2d3bbbce1b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #7 0x7f2d3bb65bdb in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #8 0x7f2d3b9a7751 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #9 0x7f2d3be3a4e6 in ?? () from /usr/lib64/libQt5DBus.so.5 #10 0x7f2d3b9a88d2 in ?? () from /usr/lib64/libQt5Core.so.5 #11 0x7f2d3ad65faa in start_thread (arg=) at pthread_create.c:486 #12 0x7f2d3b63571f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f2d37873700 (LWP 16565)): #0 0x7f2d3b62ac9f in __GI___poll (fds=0x7f2d37872ba8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f2d3adeacc2 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f2d3adec8ba in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f2d37a8ee28 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f2d3b9a88d2 in ?? () from /usr/lib64/libQt5Core.so.5 #5 0x7f2d3ad65faa in start_thread (arg=) at pthread_create.c:486 #6 0x7f2d3b63571f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f2d398de900 (LWP 16562)): [KCrash Handler] #6 HASH_End (context=0x0, result=0x56552b35ca10 "0/6+UV", result_len=0x768339fc, max_result_len=0) at sechash.c:462 #7 0x7f2d2d6d0cdb in SignatureHandler::validateSignature (this=this@entry=0x76833a80) at /usr/src/debug/poppler-0.72.0-1.5.x86_64/poppler/SignatureHandler.cc:258 #8 0x7f2d2d5c5e71 in FormFieldSignature::validateSignature (forceRevalidation=, validationTime=4294967295, doVerifyCert=true, this=0x56552b29e7a0) at /usr/src/debug/poppler-0.72.0-1.5.x86_64/poppler/Form.cc:1747 #9 FormFieldSignature::validateSignature (this=0x56552b29e7a0, doVerifyCert=, forceRevalidation=, validationTime=4294967295) at /usr/src/debug/poppler-0.72.0-1.5.x86_64/poppler/Form.cc:1690 #10 0x7f2d2d7e73e4 in Poppler::FormFieldSignature::validate (this=this@entry=0x56552b29e570, opt=opt@entry=1, validationTime=...) at /usr/src/debug/poppler-qt5-0.72.0-1.5.x86_64/qt5/src/poppler-form.cc:681 #11 0x7f2d2d7e7940 in Poppler::FormFieldSignature::validate (this=0x56552b29e570, opt=opt@entry=Poppler::FormFieldSignature::ValidateVerifyCertificate) at /usr/src/debug/poppler-qt5-0.72.0-1.5.x86_64/qt5/src/poppler-form.cc:674 #12 0x7f2d2d840e53 in PopplerFormFieldSignature::PopplerFormFieldSignature (this=0x56552b29eb90, field=0x56552b29e570) at /usr/src/debug/okular-19.04.2-1.1.x86_64/generators/poppler/formfields.cpp:387 #13 0x7f2d2d8399bd in PDFGenerator::addFormFields (this=, popplerPage=, page=) at /usr/src/debug/okular-19.0
[okular] [Bug 409684] okular crashes when opening a pdf file I got from government website
https://bugs.kde.org/show_bug.cgi?id=409684 --- Comment #1 from Adam Mizerski --- Created attachment 121441 --> https://bugs.kde.org/attachment.cgi?id=121441&action=edit file that causes okular to crash -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 407338] Okular segfaults when opening a file digitally signed with portablesigner and Acrobat Reader
https://bugs.kde.org/show_bug.cgi?id=407338 Yuri Chornoivan changed: What|Removed |Added CC||a...@mizerski.pl --- Comment #9 from Yuri Chornoivan --- *** Bug 409684 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 409684] okular crashes when opening a pdf file I got from government website
https://bugs.kde.org/show_bug.cgi?id=409684 Yuri Chornoivan changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||yurc...@ukr.net --- Comment #2 from Yuri Chornoivan --- *** This bug has been marked as a duplicate of bug 407338 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409682] Krita crashes when using flood-fill
https://bugs.kde.org/show_bug.cgi?id=409682 --- Comment #4 from Boudewijn Rempt --- Lets keep this open for a week or so to see if the reporter experiences more crashes with the nightly builds. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 409685] New: ImageEditor can only be invoked once
https://bugs.kde.org/show_bug.cgi?id=409685 Bug ID: 409685 Summary: ImageEditor can only be invoked once Product: digikam Version: 5.9.0 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: ImageEditor Assignee: digikam-bugs-n...@kde.org Reporter: k...@kde.lka.org.lu Target Milestone: --- SUMMARY Image editor can only be invoked once from digikam's main window STEPS TO REPRODUCE 1. In an album, select a picture 2. Click Image Editor button 3. Image editor opens (albeit, without its menu) 4. Close image editor 5. In main window, click Image Editor button again OBSERVED RESULT After Step 5, an image editor window with a white background (and nothing else) appears. At the same time, the following message is printed to STDERR: digikam.geoiface: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 48058, resource id: 96469350, major code: 19 (DeleteProperty), minor code: 0 ... and after closing the useless image editor: digikam.geoiface: EXPECTED RESULT Image editor should appear normally (i.e. with selected photo), even when opening it the second time. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Linux 4.19.0-5-amd64, Debian 10, KDE 5.54.0-1 (available in About System) KDE Plasma Version: 4:5.14.5.1-1 KDE Frameworks Version: Qt Version: 5.11.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 409323] Revoke "Network Disconnected" notification once the network is re-connected
https://bugs.kde.org/show_bug.cgi?id=409323 --- Comment #4 from Nate Graham --- (In reply to Kai Uwe Broulik from comment #3) > Once in history, there's nothing you can do. > We could add a "don't preserve in history flag" maybe or at least revoke the > notification when its popup is still shown. Hmm, I must have misunderstood some of our recent conversations then. I was left with the impression that it was possible for an app to revoke its notification and for that notification to disappear from the history. If this isn't currently possible, what's blocking it from being possible? -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 409323] Revoke "Network Disconnected" notification once the network is re-connected
https://bugs.kde.org/show_bug.cgi?id=409323 --- Comment #5 from Kai Uwe Broulik --- > If this isn't currently possible, what's blocking it from being possible? A redesign of KNotification class to have its lifetime not bound to the expiration of the popup and an extension to the freedesktop Notification spec to allow applications to revoke notifications after the fact. And then persuading 3rd party apps to also use that. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 409685] ImageEditor can only be invoked once
https://bugs.kde.org/show_bug.cgi?id=409685 --- Comment #1 from Alain Knaff --- I just noticed: the problem only occurs when closing the Image Editor window using the "cross" icon on its title bar (top-right corner). It doesn't occur when using the "Close Editor" from the Image Editor's own "Main toolbar" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408594] color saturation in blurred regions is higher than expected
https://bugs.kde.org/show_bug.cgi?id=408594 David de Cos changed: What|Removed |Added CC||david.de...@ehu.eus --- Comment #33 from David de Cos --- Created attachment 121442 --> https://bugs.kde.org/attachment.cgi?id=121442&action=edit Grainy panel after update to 5.16.3 I just updated to 5.16.3, and my panel has gotten kind of grainy. That wasn't there before, so I went through the changelog and found this bug report. Since my card is an Intel, I thought it might be related. In case it helps, I'm using Breeze Transparent Dark, but I switched to other transparent themes and the "grains" are there too, even in the non-dark ones. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409660] App's in-progress progress bar persists when app is closed
https://bugs.kde.org/show_bug.cgi?id=409660 --- Comment #2 from Nate Graham --- So I guess I should complain to Elisa that showing song progress isn't an appropriate use of the progress indicator API, or ask to have it removed prior to quitting the app? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409660] App's in-progress progress bar persists when app is closed
https://bugs.kde.org/show_bug.cgi?id=409660 --- Comment #3 from Kai Uwe Broulik --- Yes. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 409686] New: Digikam hits database deadlock on start with gelocation query
https://bugs.kde.org/show_bug.cgi?id=409686 Bug ID: 409686 Summary: Digikam hits database deadlock on start with gelocation query Product: digikam Version: 5.9.0 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: ImageEditor Assignee: digikam-bugs-n...@kde.org Reporter: k...@kde.lka.org.lu Target Milestone: --- SUMMARY When digikam is started, it freezes for 10 seconds, and then says that it could not execute a database query about geolocation STEPS TO REPRODUCE 1. Start digikam OBSERVED RESULT The following is printed to STDERR, all the while the UI is unresponsive for 10 seconds: digikam.geoiface: digikam.general: Cancel Main Thread digikam.general: Cancel Main Thread digikam.geoiface: "setting backend marble" QFSFileEngine::open: No file name specified digikam.geoiface: "ROADMAP" digikam.geoiface: "setting backend marble" digikam.facesengine: Face database ready for use digikam.general: Face PipeLine: add database writer digikam.general: Face PipeLine: add faces trainer digikam.facesengine: Face database ready for use digikam.general: Face PipeLine: add database writer digikam.general: Face PipeLine: add faces trainer digikam.geoiface: "setting backend marble" QFSFileEngine::open: No file name specified digikam.geoiface: "ROADMAP" digikam.geoiface: "ROADMAP" digikam.general: scan mode: ScanDeferredFiles digikam.general: total scan value : 373261 digikam.dbengine: Database is locked. Waited 0 digikam.dbengine: Database is locked. Waited 250 digikam.dbengine: Database is locked. Waited 500 digikam.dbengine: Database is locked. Waited 750 digikam.dbengine: Database is locked. Waited 1000 digikam.dbengine: Database is locked. Waited 1250 digikam.dbengine: Database is locked. Waited 1500 digikam.dbengine: Database is locked. Waited 1750 digikam.dbengine: Database is locked. Waited 2000 digikam.dbengine: Database is locked. Waited 2250 digikam.dbengine: Database is locked. Waited 2500 digikam.dbengine: Database is locked. Waited 2750 digikam.dbengine: Database is locked. Waited 3000 digikam.dbengine: Database is locked. Waited 3250 digikam.dbengine: Database is locked. Waited 3500 digikam.dbengine: Database is locked. Waited 3750 digikam.dbengine: Database is locked. Waited 4000 digikam.dbengine: Database is locked. Waited 4250 digikam.dbengine: Database is locked. Waited 4500 digikam.dbengine: Database is locked. Waited 4750 digikam.dbengine: Database is locked. Waited 5000 digikam.dbengine: Database is locked. Waited 5250 digikam.dbengine: Database is locked. Waited 5500 digikam.dbengine: Database is locked. Waited 5750 digikam.dbengine: Database is locked. Waited 6000 digikam.dbengine: Database is locked. Waited 6250 digikam.dbengine: Database is locked. Waited 6500 digikam.dbengine: Database is locked. Waited 6750 digikam.dbengine: Database is locked. Waited 7000 digikam.dbengine: Database is locked. Waited 7250 digikam.dbengine: Database is locked. Waited 7500 digikam.dbengine: Database is locked. Waited 7750 digikam.dbengine: Database is locked. Waited 8000 digikam.dbengine: Database is locked. Waited 8250 digikam.dbengine: Database is locked. Waited 8500 digikam.dbengine: Database is locked. Waited 8750 digikam.dbengine: Database is locked. Waited 9000 digikam.dbengine: Database is locked. Waited 9250 digikam.dbengine: Database is locked. Waited 9500 digikam.dbengine: Database is locked. Waited 9750 digikam.dbengine: Database is locked. Waited 1 digikam.dbengine: Detected locked database file. There is an active transaction. Waited but giving up now. digikam.dbengine: Failure executing query: "SELECT latitude, latitudeNumber, longitude, longitudeNumber, altitude, orientation, tilt, roll, accuracy, description FROM ImagePositions WHERE imageid=:a;" Error messages: "Unable to fetch row" "database table is locked: ImagePositions" 6 1 Bound values: (QVariant(qlonglong, 275510)) EXPECTED RESULT Digikam should not freeze. A database query should not take that long, especially for a feature which is only of interest to a minority of users. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I do not have any need for geolocation. How can I switch it off easily? -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 409687] New: Unset progress indicator on task manager button when quitting
https://bugs.kde.org/show_bug.cgi?id=409687 Bug ID: 409687 Summary: Unset progress indicator on task manager button when quitting Product: elisa Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: n...@kde.org Target Milestone: --- Created attachment 121443 --> https://bugs.kde.org/attachment.cgi?id=121443&action=edit Progress bar visible when app isn't running When an app is pinned to an Icons-Only Task Manager, Plasmashell retains progress state shown for that app when the app is not running (See Bug 409660). This manifests in Elisa's launcher icon showing a progress bar background corresponding to the playback position of the last-running song (see attached screenshot), even when the app isn't running. This information is not useful or relevant when Elisa isn't running, so Elisa should un-set the progress information before it quits. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 409687] Unset progress indicator on task manager button when quitting
https://bugs.kde.org/show_bug.cgi?id=409687 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=409660, ||https://bugs.kde.org/show_b ||ug.cgi?id=406454 -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 406454] Make the progress indicator on the Task Manager button optional
https://bugs.kde.org/show_bug.cgi?id=406454 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=409687 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409660] App's in-progress progress bar persists when app is closed
https://bugs.kde.org/show_bug.cgi?id=409660 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=409687 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409660] App's in-progress progress bar persists when app is closed
https://bugs.kde.org/show_bug.cgi?id=409660 --- Comment #4 from Nate Graham --- Thanks, filed Bug 409687. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 409686] Digikam hits database deadlock on start with gelocation query
https://bugs.kde.org/show_bug.cgi?id=409686 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Component|ImageEditor |Database-Scan -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409688] New: kwin_wayland aborted when shutting down involving invalid reads and writes, use of uninitialized variables etc.
https://bugs.kde.org/show_bug.cgi?id=409688 Bug ID: 409688 Summary: kwin_wayland aborted when shutting down involving invalid reads and writes, use of uninitialized variables etc. Product: kwin Version: 5.15.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: matthew.fagn...@utoronto.ca Target Milestone: --- Created attachment 121444 --> https://bugs.kde.org/attachment.cgi?id=121444&action=edit valgrind log file when run on kwin_wayland after shutting down SUMMARY I've seen audit messages in my journal indicating that kwin_wayland aborted when shutting down the system in Plasma 5.15.5 on Wayland in Fedora 30 such as the following. Jul 09 21:01:21 audit[1399]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=1399 comm="QDBusConnection" exe="/usr/bin/kwin_wayland" sig=6 res=1 Jul 09 21:01:21 systemd[1]: Requested transaction contradicts existing jobs: Transaction for systemd-coredump@0-1970-0.service/start is destructive (systemd-poweroff.service has 'start' job queued, but 'stop' is included in transaction). Jul 09 21:01:21 systemd[1]: systemd-coredump.socket: Failed to queue service startup job (Maybe the service file is missing or not a non-template unit?): Transaction for systemd-coredump@0-1970-0.service/start is destructive (systemd-poweroff.service has 'start' job queued, but 'stop' is included in transaction). Jul 09 21:01:21 systemd[1]: systemd-coredump.socket: Failed with result 'resources'. Jul 09 21:01:21 systemd-coredump[1970]: Failed to send coredump datagram: Connection reset by peer There are 149 such messages indicating kwin_wayland aborted when I shut down or rebooted. The crashes were not in coredumpctl or abrt. I edited /usr/bin/startplasmacompositor at line 239 to run kwin_wayland under valgrind like valgrind --log-file=/programs/kde/kwin/valgrind-kwin_wayland-3.txt --track-origins=yes /usr/bin/kwin_wayland --xwayland --libinput --exit-with-session=/usr/libexec/startplasma I rebooted then logged into Plasma on wayland from sddm 0.18.1 under valgrind. I shut down the system. The valgrind log showed 20 invalid reads and 2 invalid writes overall. An invalid read in wl_proxy_unref (wayland-client.c:229) in libwayland-client and invalid write in wl_proxy_unref (wayland-client.c:230) happened before I started the shutdown. Those appear to be use-after-free errors since they contained lines like "Address 0x1c2e4ffc is 44 bytes inside a block of size 72 free'd". ==2115== Thread 3 QThread: ==2115== Invalid read of size 4 ==2115==at 0x8844BB4: wl_proxy_unref (wayland-client.c:229) ==2115==by 0x8844CB3: destroy_queued_closure (wayland-client.c:291) ==2115==by 0x8844EC7: dispatch_event.isra.0 (wayland-client.c:1436) ==2115==by 0x884646B: dispatch_queue (wayland-client.c:1576) ==2115==by 0x884646B: wl_display_dispatch_queue_pending (wayland-client.c:1818) ==2115==by 0x6605F16: operator() (connection_thread.cpp:129) ==2115==by 0x6605F16: call (qobjectdefs_impl.h:146) ==2115==by 0x6605F16: call, void> (qobjectdefs_impl.h:256) ==2115==by 0x6605F16: QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (qobjectdefs_impl.h:439) ==2115==by 0x5883EBF: call (qobjectdefs_impl.h:394) ==2115==by 0x5883EBF: QMetaObject::activate(QObject*, int, int, void**) (qobject.cpp:3781) ==2115==by 0x588FFCB: QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) (moc_qsocketnotifier.cpp:140) ==2115==by 0x5890330: QSocketNotifier::event(QEvent*) (qsocketnotifier.cpp:266) ==2115==by 0x50C4AF5: QApplicationPrivate::notify_helper(QObject*, QEvent*) (qapplication.cpp:3737) ==2115==by 0x50CDE7F: QApplication::notify(QObject*, QEvent*) (qapplication.cpp:3483) ==2115==by 0x5859AE7: QCoreApplication::notifyInternal2(QObject*, QEvent*) (qcoreapplication.cpp:1084) ==2115==by 0x58AF586: socketNotifierSourceDispatch(_GSource*, int (*)(void*), void*) (qeventdispatcher_glib.cpp:106) ==2115== Address 0x1c2e4ffc is 44 bytes inside a block of size 72 free'd ==2115==at 0x4839A0C: free (vg_replace_malloc.c:540) ==2115==by 0x661DC14: destroy (wayland_pointer_p.h:63) ==2115==by 0x661DC14: KWayland::Client::Registry::Private::globalSync(void*, wl_callback*, unsigned int) (registry.cpp:539) ==2115==by 0x8856B27: ffi_call_unix64 (unix64.S:76) ==2115==by 0x8856338: ffi_call (ffi64.c:525) ==2115==by 0x8848606: wl_closure_invoke (connection.c:1014) ==2115==by 0x8844F17: dispatch_event.isra.0 (wayland-client.c:1430) ==2115==by 0x884646B: dispatch_queue (wayland-client.c:1576) ==2115==by 0x884646B: wl_display_dispatch_queue_pending (wayland-client.c:1818
[digikam] [Bug 409686] Digikam hits database deadlock on start with gelocation query
https://bugs.kde.org/show_bug.cgi?id=409686 --- Comment #1 from caulier.gil...@gmail.com --- 5.9.0 is an older version. This problem have been already seen in the past. Please test with last stable release 6.1.0 using Linux AppImage bundle that we provide in project download area. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408504] Krita 4.2.0 window does not tile to left or right side of screen
https://bugs.kde.org/show_bug.cgi?id=408504 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/kde/ ||krita/commit/b1cdd068348243 ||337a96e30d615f363ac4419d5e --- Comment #8 from Boudewijn Rempt --- Git commit b1cdd068348243337a96e30d615f363ac4419d5e by Boudewijn Rempt. Committed on 10/07/2019 at 14:07. Pushed by rempt into branch 'master'. Put the hello widget in a scroller So it doesn't affect the minimum width of the main window. M +9-1libs/ui/KisMainWindow.cpp https://invent.kde.org/kde/krita/commit/b1cdd068348243337a96e30d615f363ac4419d5e -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 385726] Add Support For Apple Live Photos
https://bugs.kde.org/show_bug.cgi?id=385726 caulier.gil...@gmail.com changed: What|Removed |Added Version|unspecified |5.9.0 --- Comment #14 from caulier.gil...@gmail.com --- Yes please, fill a new file, as this one is already closed. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 409689] New: KDevelop crashes when you're building a project
https://bugs.kde.org/show_bug.cgi?id=409689 Bug ID: 409689 Summary: KDevelop crashes when you're building a project Product: kdevelop Version: 5.3.2 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: li...@inboxen.co.uk Target Milestone: --- Application: kdevelop (5.3.2) Qt Version: 5.12.2 Frameworks Version: 5.59.0 Operating System: Linux 5.0.0-20-generic x86_64 Distribution: Ubuntu 19.04 -- Information about the crash: - What I was doing when the application crashed: I'm using a custom build method which calls out to Ninja. I find it crashes a lot when interacting with the build process either initiating a build or stopping a build (this occasion I used the "Stop All" button). I'm not sure if it's relevent but it's also indexing the project at the same time, I haven't tested it when it's not indexing as it takes a long time due to the project size so it's usually indexing. It's not always consistant that sometimes I am able to stop it and sometimes I am able to initiate a build but it's not a rare crash, it occurs quite often. Many times during the course of a day. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc4d5a7fe80 (LWP 6788))] Thread 24 (Thread 0x7fc4477fe700 (LWP 10732)): #0 0x7fc4e0e77729 in __GI___poll (fds=0x7fc4300f3dc0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fc4ddad8bf6 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc4ddad8d1c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc4e13fb063 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fc4e13a65bb in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fc4e11f12c6 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fc4dfe9845c in () at /usr/lib/x86_64-linux-gnu/libKDevPlatformLanguage.so.53 #7 0x7fc4e11f2612 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fc4de34c182 in start_thread (arg=) at pthread_create.c:486 #9 0x7fc4e0e83b1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 23 (Thread 0x7fc462ffd700 (LWP 9337)): #0 0x7fc4de3523bb in futex_wait_cancelable (private=, expected=0, futex_word=0x55dd30abc7c0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fc4de3523bb in __pthread_cond_wait_common (abstime=0x0, mutex=0x55dd30abc770, cond=0x55dd30abc798) at pthread_cond_wait.c:502 #2 0x7fc4de3523bb in __pthread_cond_wait (cond=0x55dd30abc798, mutex=0x55dd30abc770) at pthread_cond_wait.c:655 #3 0x7fc4e11f8733 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fc4e11f8819 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fc4dda6e680 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7fc4dda721f8 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7fc4dda6d90d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7fc4dda72252 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7fc4dda6d90d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7fc4dda72252 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #11 0x7fc4dda6d90d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #12 0x7fc4dda702c9 in ThreadWeaver::Thread::run() () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #13 0x7fc4e11f2612 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7fc4de34c182 in start_thread (arg=) at pthread_create.c:486 #15 0x7fc4e0e83b1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 22 (Thread 0x7fc4637fe700 (LWP 9336)): #0 0x7fc4de3523bb in futex_wait_cancelable (private=, expected=0, futex_word=0x55dd30abc7c0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fc4de3523bb in __pthread_cond_wait_common (abstime=0x0, mutex=0x55dd30abc770, cond=0x55dd30abc798) at pthread_cond_wait.c:502 #2 0x7fc4de3523bb in __pthread_cond_wait (cond=0x55dd30abc798, mutex=0x55dd30abc770) at pthread_cond_wait.c:655 #3 0x7fc4e11f8733 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x
[krita] [Bug 408053] [Brush-Presets-Docker] Long Brush Presets tag name causes brushes to disappear if the tag name is ellipsized due to docker resizing
https://bugs.kde.org/show_bug.cgi?id=408053 Boudewijn Rempt changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/kde/ ||krita/commit/dc224f4773d5d0 ||4ce7484047e6210dca77ef5882 Resolution|--- |FIXED --- Comment #1 from Boudewijn Rempt --- Git commit dc224f4773d5d04ce7484047e6210dca77ef5882 by Boudewijn Rempt. Committed on 10/07/2019 at 14:19. Pushed by rempt into branch 'master'. Fix KoTagChooserWidget not selecting items for tags that don't fit M +1-1libs/ui/dialogs/kis_dlg_png_import.cpp M +1-1libs/ui/dialogs/kis_dlg_preferences.cc M +2-2libs/ui/widgets/kis_color_space_selector.cc M +8-5libs/widgets/KoTagChooserWidget.cpp M +1-0libs/widgets/KoTagChooserWidget.h M +1-1libs/widgetutils/KisSqueezedComboBox.cpp M +1-1libs/widgetutils/KisSqueezedComboBox.h M +4-4plugins/dockers/lut/lutdocker_dock.cpp M +1-1plugins/impex/raw/3rdparty/libkdcraw/src/squeezedcombobox.cpp M +1-1plugins/impex/raw/3rdparty/libkdcraw/src/squeezedcombobox.h https://invent.kde.org/kde/krita/commit/dc224f4773d5d04ce7484047e6210dca77ef5882 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408053] [Brush-Presets-Docker] Long Brush Presets tag name causes brushes to disappear if the tag name is ellipsized due to docker resizing
https://bugs.kde.org/show_bug.cgi?id=408053 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/dc224f4773d5d0 |krita/commit/296519d7beed93 |4ce7484047e6210dca77ef5882 |fb07970810fc56f6a57712999e --- Comment #2 from Boudewijn Rempt --- Git commit 296519d7beed93fb07970810fc56f6a57712999e by Boudewijn Rempt. Committed on 10/07/2019 at 14:26. Pushed by rempt into branch 'krita/4.2'. Fix KoTagChooserWidget not selecting items for tags that don't fit M +1-1libs/ui/dialogs/kis_dlg_png_import.cpp M +1-1libs/ui/dialogs/kis_dlg_preferences.cc M +2-2libs/ui/widgets/kis_color_space_selector.cc M +8-5libs/widgets/KoTagChooserWidget.cpp M +1-0libs/widgets/KoTagChooserWidget.h M +1-1libs/widgetutils/KisSqueezedComboBox.cpp M +1-1libs/widgetutils/KisSqueezedComboBox.h M +4-4plugins/dockers/lut/lutdocker_dock.cpp M +1-1plugins/impex/raw/3rdparty/libkdcraw/src/squeezedcombobox.cpp M +1-1plugins/impex/raw/3rdparty/libkdcraw/src/squeezedcombobox.h https://invent.kde.org/kde/krita/commit/296519d7beed93fb07970810fc56f6a57712999e -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408504] Krita 4.2.0 window does not tile to left or right side of screen
https://bugs.kde.org/show_bug.cgi?id=408504 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/b1cdd068348243 |krita/commit/7dc3527003b9c8 |337a96e30d615f363ac4419d5e |1533bca8399da257eebda07759 --- Comment #9 from Boudewijn Rempt --- Git commit 7dc3527003b9c81533bca8399da257eebda07759 by Boudewijn Rempt. Committed on 10/07/2019 at 14:26. Pushed by rempt into branch 'krita/4.2'. Put the hello widget in a scroller So it doesn't affect the minimum width of the main window. M +9-1libs/ui/KisMainWindow.cpp https://invent.kde.org/kde/krita/commit/7dc3527003b9c81533bca8399da257eebda07759 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407693] Transparent Interface using OpenGL on Windows
https://bugs.kde.org/show_bug.cgi?id=407693 Boudewijn Rempt changed: What|Removed |Added Summary|Transparent Interface |Transparent Interface using ||OpenGL on Windows -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 409690] Add option to auto copy screenshot to clipboard
https://bugs.kde.org/show_bug.cgi?id=409690 Vladimir changed: What|Removed |Added CC||vladimiro...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 409690] New: Add option to auto copy screenshot to clipboard
https://bugs.kde.org/show_bug.cgi?id=409690 Bug ID: 409690 Summary: Add option to auto copy screenshot to clipboard Product: Spectacle Version: 19.04.2 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: vladimiro...@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY Please add option to auto copy screenshot to clipboard SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 19.04.4 KDE Plasma Version: 5.16.2 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION Kernel 5.0.0-20-generic 64 bit -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409374] You can not enable font anti-aliasing with sub-pixel rendering because system settings will automatically put a check mark in the box to block anti-aliasing and make font
https://bugs.kde.org/show_bug.cgi?id=409374 Michael changed: What|Removed |Added CC||finod...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 409257] Baloo index gets corrupted, no results
https://bugs.kde.org/show_bug.cgi?id=409257 --- Comment #27 from S --- (In reply to S from comment #26) > (In reply to S from comment #25) > > (In reply to Igor Poboiko from comment #24) > > > > > This patch might help: https://phabricator.kde.org/D21427. > > > Can anyone confirm? > > > > Nice work Igor! I'm building baloo5 with that patch now and I'll test it > > throughout my workday today. > > This is tentatively looking good! It survived a long day of work yesterday, > including quite a few reboots (because I was diagnosing a different > unrelated bug... :-/ ) I'd say push this change to master. I can confidently say that the patch fixes this bug. Is there anything preventing the integration of the patch into the official code? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407658] Foreground and background color chooser dialogs have different titles
https://bugs.kde.org/show_bug.cgi?id=407658 Boudewijn Rempt changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 CC||b...@valdyas.org Assignee|krita-bugs-n...@kde.org |b...@valdyas.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409474] ctrl(meta) + click on macOS blocks mouse events on canvas.
https://bugs.kde.org/show_bug.cgi?id=409474 grzegorzpedr...@o2.pl changed: What|Removed |Added CC||grzegorzpedr...@o2.pl --- Comment #2 from grzegorzpedr...@o2.pl --- Freezing cursor over canvas issue appear on Windows as well ( with 4.2.2 Version ) I working on the workflow to reproduce that bug, Maybe you are aware if it already ? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407658] Foreground and background color chooser dialogs have different titles
https://bugs.kde.org/show_bug.cgi?id=407658 Boudewijn Rempt changed: What|Removed |Added Latest Commit||https://invent.kde.org/kde/ ||krita/commit/20357195392011 ||9784efb09c7457cbe769198cf5 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Boudewijn Rempt --- Git commit 203571953920119784efb09c7457cbe769198cf5 by Boudewijn Rempt. Committed on 10/07/2019 at 14:43. Pushed by rempt into branch 'master'. Fix the caption of the BG color selector M +81 -93 libs/ui/widgets/KoDualColorButton.cpp M +0-7libs/ui/widgets/KoDualColorButton.h https://invent.kde.org/kde/krita/commit/203571953920119784efb09c7457cbe769198cf5 -- You are receiving this mail because: You are watching all bug changes.
