[kscreenlocker] [Bug 360489] kscreenlocker suggests running "loginctl unlock-sessions" even though I don't use systemd
https://bugs.kde.org/show_bug.cgi?id=360489 Martin Gräßlin changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #2 from Martin Gräßlin --- There is nothing wrong there. It's a fallback for the case that something is seriously broken. We improved that experience from black screen to something which works on 99 % of our users systems. There is no Plasma developer who doesn't use logind, so it's just not possible for us to support anything else. We expect the non-logind users to add code for this (which could also be a dummy loginctl binary which just works the same way). (Similar code was contributed to support consolekit in kscreenlocker). >From our side this is a clear wontfix or more a cantfix. Please do not expect us to go an extramile to support a corner case of the corner case. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 360421] After waking from standby mouse clicks and keyboard input doesn't reach kscreenlocker or other applications, session kill necessary
https://bugs.kde.org/show_bug.cgi?id=360421 --- Comment #3 from Martin Gräßlin --- next time try to kill kglobalaccel. Maybe then xorg usage goes down. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 352869] No indicators in Shade selector
https://bugs.kde.org/show_bug.cgi?id=352869 Dmitry Kazakov changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/krit ||a/c17ed27409710a87cea1e7f74 ||015873967095baf --- Comment #4 from Dmitry Kazakov --- Git commit c17ed27409710a87cea1e7f74015873967095baf by Dmitry Kazakov, on behalf of Nataly Novak. Committed on 14/03/2016 at 07:10. Pushed by dkazakov into branch 'master'. Patch for the Bug 352869 shade selector indicator For minimal shade selector, this patch adds indications of the first color, and the one that is now selected. Differential revision: https://phabricator.kde.org/D1030 M +47 -14 plugins/extensions/dockers/advancedcolorselector/kis_shade_selector_line.cpp M +4-0 plugins/extensions/dockers/advancedcolorselector/kis_shade_selector_line.h http://commits.kde.org/krita/c17ed27409710a87cea1e7f74015873967095baf -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 Martin Mrvka changed: What|Removed |Added CC||mmr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 360499] New: yakuake too small after update and not ajustable
https://bugs.kde.org/show_bug.cgi?id=360499 Bug ID: 360499 Summary: yakuake too small after update and not ajustable Product: yakuake Version: 3.0.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: ingo.e...@ingoebel.de After updating to 3.0.2 on Plasma 5 yakuake is not really usable anymore cause I can't ajust the width or height anymore. Not with the mouse and not via context menu. So the window is too small. I'm using a 4k Screen. Reproducible: Always Steps to Reproduce: 1. Open Yakuake 2. 3. Actual Results: Tried to make it bigger with mouse. Tried to use the context menus. Expected Results: Former versions where able to fit on the whole screen and to adjusted with the mouse. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 360499] yakuake too small after update and not ajustable
https://bugs.kde.org/show_bug.cgi?id=360499 --- Comment #1 from Ingo Ebel --- Created attachment 97882 --> https://bugs.kde.org/attachment.cgi?id=97882&action=edit yakuake too small -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 359532] Burning speed can´t be reduced
https://bugs.kde.org/show_bug.cgi?id=359532 --- Comment #1 from Armin Mohring --- Work in progress. Write speed is reduced, but not displayed. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 360500] New: Unable to enter the same value in the No. field for more than 1 transaction.
https://bugs.kde.org/show_bug.cgi?id=360500 Bug ID: 360500 Summary: Unable to enter the same value in the No. field for more than 1 transaction. Product: kmymoney4 Version: 4.7.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: bo...@yahoo.com v4.7.2 now requires to enter different values in the No. field for different transactions. This is annoying when the No. check field is used for other purposes than incremental cheque numbers, e.g. method of payment or the date for a deferred debit card. Now when entering a same value KMM asks whether to increment this value. If the answer is NO, the field is automatically erased and the transaction is entered with an empty No. field. In v4.6.6 I was able to enter the same value in different transactions, thus when I answered NO the field was not blanked out. Reproducible: Always Steps to Reproduce: 1. Enter a transaction with "XXX-01" in No. field 2. Enter a new transaction with same "XXX-01" in No. field 3. Actual Results: User will not be allowed to validate the 2nd transaction with the same "XXX-01" No. field. The No. field will either be erased or set to "XXX-02". Expected Results: User should be allowed to enter whatever he likes in the No. field if he decides not to use this field as an incremental cheque number field. That was the case in older versions of KMM. Please leave the options for No. field as they were in v4.6.6. I couldn't find any workaround to enter different transactions with a same value in the No. field. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 360501] New: Broken signal/slot connections
https://bugs.kde.org/show_bug.cgi?id=360501 Bug ID: 360501 Summary: Broken signal/slot connections Product: umbrello Version: Git Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: umbrello-de...@kde.org Reporter: ralf.habac...@freenet.de While looking at review 127304 it turns out that umbrello source code contains some broken signal/slot connections (e.g. the mentioned slot method does not exist) which prevents a successful compile of the related patch. It is required to fix the broken connections. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 360499] yakuake too small after update and not ajustable
https://bugs.kde.org/show_bug.cgi?id=360499 Eike Hein changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #2 from Eike Hein --- Width/height configuration is the same as it has always been via the title bar menu or the config dialog. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 358098] Baloo fails to index plain text files unless extension is .txt
https://bugs.kde.org/show_bug.cgi?id=358098 Boudhayan Gupta changed: What|Removed |Added CC||m...@baloneygeek.com --- Comment #6 from Boudhayan Gupta --- Fixed in commit https://quickgit.kde.org/?p=baloo.git&a=commit&h=06efd6c05c15a64b53daac9e598666af584488ec. Not sure why the bug wasn't autoclosed. I'll inform someone from the bugsquad to close this manually. -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 360502] New: Menu items not readable
https://bugs.kde.org/show_bug.cgi?id=360502 Bug ID: 360502 Summary: Menu items not readable Product: ktouch Version: 2.3.0 Platform: ROSA RPMs URL: https://cloud.mail.ru/public/6BxA/YYJ5MGro5 OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: sebastiangottfr...@web.de Reporter: a...@mail.ru I install ktouch though ROSA Linux package manager. Then I lunch the program from terminal and enter an account information. Then I see that menu items are not readable. But if I move mouse on it, an item appears. Reproducible: Always Steps to Reproduce: 1.Lunch ktouch 2.Enter account information 3.Whe enter to menu you can see the bug. Actual Results: The menu item unredeable. Expected Results: Normal menu with constrast text color Error log from console: file:///usr/lib64/kde4/imports/org/kde/plasma/components/Button.qml:194:5: QML Row: ÃÂñýðÃÂÃÂöõýð òþ÷üþöýðàÃÂøúûøÃÂýðàÿÃÂøòÃÂ÷úð ýð fill file:///usr/lib64/kde4/imports/org/kde/plasma/components/Button.qml:194:5: QML Row: ÃÂñýðÃÂÃÂöõýð òþ÷üþöýðàÃÂøúûøÃÂýðàÿÃÂøòÃÂ÷úð ýð fill Could not resolve property : linearGradient5334 Could not resolve property : linearGradient5332 Could not resolve property : linearGradient5326 Could not resolve property : linearGradient5328 Could not resolve property : linearGradient5334 Could not resolve property : linearGradient5332 Could not resolve property : linearGradient5326 Could not resolve property : linearGradient5328 Could not resolve property : linearGradient5334 Could not resolve property : linearGradient5332 Could not resolve property : linearGradient5326 Could not resolve property : linearGradient5328 file:///usr/lib64/kde4/imports/org/kde/plasma/components/Button.qml:194:5: QML Row: ÃÂñýðÃÂÃÂöõýð òþ÷üþöýðàÃÂøúûøÃÂýðàÿÃÂøòÃÂ÷úð ýð fill file:///usr/lib64/kde4/imports/org/kde/plasma/components/Button.qml:194:5: QML Row: ÃÂñýðÃÂÃÂöõýð òþ÷üþöýðàÃÂøúûøÃÂýðàÿÃÂøòÃÂ÷úð ýð fill file:///usr/share/apps/ktouch/qml/LessonSelectorBase.qml:44:9: QML Column: Cannot specify top, bottom, verticalCenter, fill or centerIn anchors for items inside Column file:///usr/lib64/kde4/imports/org/kde/plasma/components/Button.qml:194:5: QML Row: ÃÂñýðÃÂÃÂöõýð òþ÷üþöýðàÃÂøúûøÃÂýðàÿÃÂøòÃÂ÷úð ýð fill file:///usr/lib64/kde4/imports/org/kde/plasma/components/Button.qml:194:5: QML Row: ÃÂñýðÃÂÃÂöõýð òþ÷üþöýðàÃÂøúûøÃÂýðàÿÃÂøòÃÂ÷úð ýð fill file:///usr/lib64/kde4/imports/org/kde/plasma/components/Button.qml:194:5: QML Row: ÃÂñýðÃÂÃÂöõýð òþ÷üþöýðàÃÂøúûøÃÂýðàÿÃÂøòÃÂ÷úð ýð fill file:///usr/lib64/kde4/imports/org/kde/plasma/components/Button.qml:194:5: QML Row: ÃÂñýðÃÂÃÂöõýð òþ÷üþöýðàÃÂøúûøÃÂýðàÿÃÂøòÃÂ÷úð ýð fill file:///usr/share/apps/ktouch/qml/LessonSelectorBase.qml:44:9: QML Column: Cannot specify top, bottom, verticalCenter, fill or centerIn anchors for items inside Column file:///usr/lib64/kde4/imports/org/kde/plasma/components/Button.qml:194:5: QML Row: ÃÂñýðÃÂÃÂöõýð òþ÷üþöýðàÃÂøúûøÃÂýðàÿÃÂøòÃÂ÷úð ýð fill file:///usr/lib64/kde4/imports/org/kde/plasma/components/Button.qml:194:5: QML Row: ÃÂñýðÃÂÃÂöõýð òþ÷üþöýðàÃÂøúûøÃÂýðàÿÃÂøòÃÂ÷úð ýð fill file:///usr/lib64/kde4/imports/org/kde/plasma/components/Button.qml:194:5: QML Row: ÃÂñýðÃÂÃÂöõýð òþ÷üþöýðàÃÂøúûøÃÂýðàÿÃÂøòÃÂ÷úð ýð fill file:///usr/lib64/kde4/imports/org/kde/plasma/components/Button.qml:194:5: QML Row: ÃÂñýðÃÂÃÂöõýð òþ÷üþöýðàÃÂøúûøÃÂýðàÿÃÂøòÃÂ÷úð ýð fill file:///usr/share/apps/ktouch/qml/ProfileSelector.qml:57:31: QML ProfileSelector: ÃÂñýðÃÂÃÂöõýþ ÷ðÃÂøúûøòðýøõ ÿÃÂøòÃÂ÷úø ôûàÃÂòþùÃÂÃÂòð ëheightû file:///usr/share/apps/ktouch/qml/ProfileSelector.qml:57:31: QML ProfileSelector: ÃÂñýðÃÂÃÂöõýþ ÷ðÃÂøúûøòðýøõ ÿÃÂøòÃÂ÷úø ôûàÃÂòþùÃÂÃÂòð ëheightû file:///usr/share/apps/ktouch/qml/ProfileSelector.qml:57:31: QML ProfileSelector: ÃÂñýðÃÂÃÂöõýþ ÷ðÃÂøúûøòðýøõ ÿÃÂøòÃÂ÷úø ôûàÃÂòþùÃÂÃÂòð ëheightû file:///usr/share/apps/ktouch/qml/ListItem.qml:41:5: QML Item: ÃÂñýðÃÂÃÂöõýð òþ÷üþö
[yakuake] [Bug 360499] yakuake too small after update and not ajustable
https://bugs.kde.org/show_bug.cgi?id=360499 --- Comment #3 from Ingo Ebel --- Did take a look at my screenshot? Width = 100% height = 100% but still its just a tiny window the only thing that works is fullscreen mode. i didn't find an other way to make the windows bigger but it was no problem with the old versions... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 352050] Moving windows between monitors is stuttering badly when side screen tiling is enabled.
https://bugs.kde.org/show_bug.cgi?id=352050 --- Comment #13 from Artur O. --- (In reply to Thomas Lübking from comment #11) > Git commit 3a1f11d21347032f7d1b8fd43d30ee7d3ce5ede0 by Thomas Lübking. > Committed on 14/09/2015 at 19:02. > Pushed by luebking into branch 'master'. > > delay QuickTiling indication on inner screenborder > > The user might just want to move the window from > one screen to another, no point in wasting time to > show the indicator > REVIEW: 125024 > FIXED-IN: 5.5 > > M +1-0client.cpp > M +1-0client.h > M +29 -8events.cpp > > http://commits.kde.org/kwin/3a1f11d21347032f7d1b8fd43d30ee7d3ce5ede0 Hm im running on Arch and it seems that Windows still stutter when its enabled. -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 360350] enhanced context menu for objects
https://bugs.kde.org/show_bug.cgi?id=360350 --- Comment #4 from Jan --- (In reply to Thomas Friedrichsmeier from comment #3) Thank you for your reply. I'm delighted about your interest. > I am slightly surprised by your choice of example actions, though: E.g. > dimensions (rows / columns) is already visible from the tool-tip, when > hovering the mouse over an object. You're right. Sometimes "nrow" and "length" return different results so a quick check via context menu would be useful (for me). Same with "names" and "colnames". > Also, the existing "View" action is meant to serve a somewhat similar purpose "View" isn't a good choice for an overview of large objects. Clicking at the tab "print(x)" shows "Fetching information. Please wait." for up to a minute. The command "head" give results much faster. > I am wondering: Would it make more sense to allow (the same / different?) > custom areas in the "View" window, in addition to / instead of your > suggestion? This is another possibility. Sometimes the first tab of the "View" window "summary(x)" also needs some time to be ready (for large objects). So the first tab should have only a limited amount of information. Example: first tab: various ncol: ... nrow: ... length: ... (Please both nrow and length) names: ... colnames: ... (Please both names and colnames) second tab: head(x) third tab: tail(x) (or head(x) and tail(x) combined in one tab) fourth tab: summary(x) fifth tab: print(x) sixth tab: str(x) Regards Jan -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 360501] Broken signal/slot connections
https://bugs.kde.org/show_bug.cgi?id=360501 --- Comment #1 from Ralf Habacker --- Git commit 6b847cd47dd970bef718383e9cd45be941bf7d83 by Ralf Habacker. Committed on 14/03/2016 at 07:58. Pushed by habacker into branch 'master'. Fix 'Broken signal/slot connections'. Remove connection to unavailable RefactoringAssistant::method(). M +1-1umbrello/refactoring/refactoringassistant.cpp http://commits.kde.org/umbrello/6b847cd47dd970bef718383e9cd45be941bf7d83 -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 360503] New: Please add ellipsis to "Create File" and "Create Folder": they open dialogs
https://bugs.kde.org/show_bug.cgi?id=360503 Bug ID: 360503 Summary: Please add ellipsis to "Create File" and "Create Folder": they open dialogs Product: kdevplatform Version: git master Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: project Assignee: kdevelop-bugs-n...@kde.org Reporter: aspotas...@gmail.com KDE HIG says: "Use an ellipsis (...) after menu items and button labels which require user’s input before completing their action." Actions in context menu "Create File" and "Create Folder" require ellipsis because each of these opens a dialog asking the user for a file/folder name. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 360504] New: Fingerprint
https://bugs.kde.org/show_bug.cgi?id=360504 Bug ID: 360504 Summary: Fingerprint Product: systemsettings Version: unspecified Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: jean.comme...@gmail.com Application: systemsettings (4.11.16) KDE Platform Version: 4.14.5 Qt Version: 4.8.6 Operating System: Linux 4.1.15-desktop-2.mga5 x86_64 Distribution: "Mageia 5" -- Information about the crash: - What I was doing when the application crashed: The window close after taking the last scan KDE4.14 sur Mageia5 à jour The crash can be reproduced every time. -- Backtrace: Application: Configuration du système (systemsettings), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #5 0x7f6df1cfed73 in EnrollStatus::setChecked(bool) () at /usr/lib64/kde4/kcm_kfingermanager.so #6 0x7f6df1cfe93f in FMEnroll::enrollStatusSlot(QString const&, bool) () at /usr/lib64/kde4/kcm_kfingermanager.so #7 0x7f6e0eff088a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /lib64/libQtCore.so.4 #8 0x7f6df1cf6ff3 in FMDbusConn::EnrollStatus(QString, bool) () at /usr/lib64/kde4/kcm_kfingermanager.so #9 0x7f6df1cfa70c in FMDbusConn::enrollStatusSlot(QString, bool) () at /usr/lib64/kde4/kcm_kfingermanager.so #10 0x7f6df1cf7031 in FMDbusConn::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () at /usr/lib64/kde4/kcm_kfingermanager.so #11 0x7f6e0eff088a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /lib64/libQtCore.so.4 #12 0x7f6e0f37a0fa in QDBusInterfacePrivate::metacall(QMetaObject::Call, int, void**) () at /lib64/libQtDBus.so.4 #13 0x7f6e0f367b06 in QDBusConnectionPrivate::deliverCall(QObject*, int, QDBusMessage const&, QList const&, int) () at /lib64/libQtDBus.so.4 #14 0x7f6e0eff4d61 in QObject::event(QEvent*) () at /lib64/libQtCore.so.4 #15 0x7f6e0fc6179c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQtGui.so.4 #16 0x7f6e0fc67e40 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQtGui.so.4 #17 0x7f6e1099425a in KApplication::notify(QObject*, QEvent*) () at /lib64/libkdeui.so.5 #18 0x7f6e0efdccad in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /lib64/libQtCore.so.4 #19 0x7f6e0efdfbe1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQtCore.so.4 #20 0x7f6e0f009cae in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQtCore.so.4 #21 0x7f6e0787dc6d in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #22 0x7f6e0787df18 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #23 0x7f6e0787dfbc in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #24 0x7f6e0f009e1e in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQtCore.so.4 #25 0x7f6e0fcff4f6 in QGuiEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQtGui.so.4 #26 0x7f6e0efdb931 in QEventLoop::processEvents(QFlags) () at /lib64/libQtCore.so.4 #27 0x7f6e0efdbc45 in QEventLoop::exec(QFlags) () at /lib64/libQtCore.so.4 #28 0x7f6e1010b0cc in QDialog::exec() () at /lib64/libQtGui.so.4 #29 0x7f6df1cf785d in FingerManagerWindow::fingerSelectedSlot(int) () at /usr/lib64/kde4/kcm_kfingermanager.so #30 0x7f6e0eff088a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /lib64/libQtCore.so.4 #31 0x7f6e102b3bb1 in QButtonGroup::buttonPressed(int) () at /lib64/libQtGui.so.4 #32 0x7f6e100158af in QAbstractButtonPrivate::emitPressed() () at /lib64/libQtGui.so.4 #33 0x7f6e100160ec in QAbstractButton::mousePressEvent(QMouseEvent*) () at /lib64/libQtGui.so.4 #34 0x7f6e0fcb1ba9 in QWidget::event(QEvent*) () at /lib64/libQtGui.so.4 #35 0x7f6e0fc6179c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQtGui.so.4 #36 0x7f6e0fc67f8e in QApplication::notify(QObject*, QEvent*) () at /lib64/libQtGui.so.4 #37 0x7f6e1099425a in KApplication::notify(QObject*, QEvent*) () at /lib64/libkdeui.so.5 #38 0x7f6e0efdccad in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /lib64/libQtCore.so.4 #39 0x7f6e0fc6766f in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () at /lib64/libQtGui.so.4 #40 0x7f6e0fcd98b2 in QETWidget::translateMouseEvent(_XEvent const*) () at /lib64/libQtGui.so.4 #41 0x7f6e0fcd82ac in QApplication::x11ProcessEvent(_XEvent*) () at /lib64/libQtGui.so.4 #42 0x7f6e0fcff442 in x11EventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQtGui.so.4 #43 0x7f6e0787dc6d in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #44
[okular] [Bug 177778] make it possible to resize resizable annotations
https://bugs.kde.org/show_bug.cgi?id=18 nono31...@gmail.com changed: What|Removed |Added CC||nono31...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 360505] New: When starting docker krunner crash
https://bugs.kde.org/show_bug.cgi?id=360505 Bug ID: 360505 Summary: When starting docker krunner crash Product: krunner Version: 5.5.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: windows Assignee: m...@vhanda.in Reporter: nils.acrim...@gmail.com Created attachment 97883 --> https://bugs.kde.org/attachment.cgi?id=97883&action=edit krunner crash following starting docker Almost every times I launch docker through "sudo systemctl start docker", krunner is crashing. I have not a lot of data available. I am sending them through attached files. -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 360503] Please add ellipsis to "Create File" and "Create Folder": they open dialogs
https://bugs.kde.org/show_bug.cgi?id=360503 --- Comment #1 from Alexander Potashev --- Same for "Rename" and "Find/Replace in This Folder". "Remove" is an exception, see https://techbase.kde.org/Projects/Usability/HIG/Labels -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 360505] When starting docker krunner crash
https://bugs.kde.org/show_bug.cgi?id=360505 --- Comment #1 from Nils --- Created attachment 97884 --> https://bugs.kde.org/attachment.cgi?id=97884&action=edit journalctl of krunner crash -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 360501] Broken signal/slot connections
https://bugs.kde.org/show_bug.cgi?id=360501 Ralf Habacker changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #2 from Ralf Habacker --- Git commit 47f5312c20b1a84fd70c860c29870ca00c5d6b0a by Ralf Habacker. Committed on 14/03/2016 at 08:02. Pushed by habacker into branch 'master'. Fix 'Broken signal/slot connections'. Remove parameters from RefactoringAssistant::objectModified() to make it connectable to signal UMLObject::modified(). M +2-4umbrello/refactoring/refactoringassistant.cpp M +1-1umbrello/refactoring/refactoringassistant.h http://commits.kde.org/umbrello/47f5312c20b1a84fd70c860c29870ca00c5d6b0a -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 360503] Please add ellipsis to "Create File" and "Create Folder": they open dialogs
https://bugs.kde.org/show_bug.cgi?id=360503 Kevin Funk changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/kdev ||platform/fae696a1756d741be8 ||32828ef3ff87a4643b6c5e Resolution|--- |FIXED Version Fixed In||5.1.0 --- Comment #2 from Kevin Funk --- Git commit fae696a1756d741be832828ef3ff87a4643b6c5e by Kevin Funk. Committed on 14/03/2016 at 08:47. Pushed by kfunk into branch 'master'. Respect KDE HIG Add ellipses (...) where necessary FIXED-IN: 5.1.0 M +3-3plugins/grepview/grepviewplugin.cpp M +3-3plugins/projectmanagerview/projectmanagerviewplugin.cpp http://commits.kde.org/kdevplatform/fae696a1756d741be832828ef3ff87a4643b6c5e -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 336043] SFTP: Should be able to browse external SD cards via SFTP too
https://bugs.kde.org/show_bug.cgi?id=336043 Conan changed: What|Removed |Added CC||conan1...@gmail.com --- Comment #40 from Conan --- Hi, Having the same issue also Desktop - Arch Linux kdeconnect 0.9.g plasma-desktop 5.5.5 plasma-desktop 5.5.5 linux 4.4.5 Android - CyanogenMod (ASOP 6) kdeconnect 0.9.g -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 355906] Please consider unification for themes' data paths.
https://bugs.kde.org/show_bug.cgi?id=355906 Simon Andric changed: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360506] New: P5 crashing when returning from suspend mode
https://bugs.kde.org/show_bug.cgi?id=360506 Bug ID: 360506 Summary: P5 crashing when returning from suspend mode Product: plasmashell Version: 5.5.4 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: flywh...@illogical.dk CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.4) Qt Version: 5.5.1 Operating System: Linux 4.1.15-8-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: I was just reentering the system/shell after the PC had been in suspend mode overnight. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7faa817f67c0 (LWP 22336))] Thread 19 (Thread 0x7faa6c73b700 (LWP 22337)): #0 0x7faa7ad06bbd in poll () at /lib64/libc.so.6 #1 0x7faa7fc4f422 in () at /usr/lib64/libxcb.so.1 #2 0x7faa7fc5100f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7faa6eebe3c9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7faa7b3ff32f in () at /usr/lib64/libQt5Core.so.5 #5 0x7faa7a5100a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7faa7ad0efed in clone () at /lib64/libc.so.6 Thread 18 (Thread 0x7faa696ec700 (LWP 22340)): #0 0x7faa773e6ec2 in g_main_context_acquire () at /usr/lib64/libglib-2.0.so.0 #1 0x7faa773e7d25 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7faa773e7f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7faa7b631d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7faa7b5d8d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7faa7b3fa61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7faa7e70cdf8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7faa7b3ff32f in () at /usr/lib64/libQt5Core.so.5 #8 0x7faa7a5100a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7faa7ad0efed in clone () at /lib64/libc.so.6 Thread 17 (Thread 0x7faa56854700 (LWP 22344)): #0 0x7faa7ace0d4d in nanosleep () at /lib64/libc.so.6 #1 0x7faa7ad08974 in usleep () at /lib64/libc.so.6 #2 0x7faa5b62a9d0 in () at /usr/X11R6/lib64/modules/dri/fglrx_dri.so #3 0x7faa5acf9512 in () at /usr/X11R6/lib64/modules/dri/fglrx_dri.so #4 0x7faa5acf9565 in () at /usr/X11R6/lib64/modules/dri/fglrx_dri.so #5 0x7faa7a5100a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7faa7ad0efed in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7faa5503a700 (LWP 22348)): #0 0x7faa773e52ab in () at /usr/lib64/libglib-2.0.so.0 #1 0x7faa773e7893 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #2 0x7faa773e7df8 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7faa773e7f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7faa7b631d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7faa7b5d8d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7faa7b3fa61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7faa7e70cdf8 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7faa7b3ff32f in () at /usr/lib64/libQt5Core.so.5 #9 0x7faa7a5100a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7faa7ad0efed in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7faa4f784700 (LWP 22349)): #0 0x7faa77429cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7faa773e78fc in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #2 0x7faa773e7df8 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7faa773e7f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7faa7b631d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7faa7b5d8d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7faa7b3fa61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7faa7e70cdf8 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7faa7b3ff32f in () at /usr/lib64/libQt5Core.so.5 #9 0x7faa7a5100a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7faa7ad0efed in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7faa4de0a700 (LWP 22356)): #0 0x7faa7a51403f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7faa80ed486b in () at /usr/lib64/libQt5Script.so.5 #2 0x7faa80ed4899 in () at /usr/lib64/libQt5Script.so.5 #3 0x7faa7a5100a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7faa7ad0efed in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7fa9c3208700 (LWP 22363)): #0 0x7faa7b631b55 in () at /usr/lib64/libQt5Core.so.5 #1 0x00
[yakuake] [Bug 360499] yakuake too small after update and not ajustable
https://bugs.kde.org/show_bug.cgi?id=360499 --- Comment #4 from Eike Hein --- Do you use hidpi app scaling? If so, could you try setting the scaling to 1.0? I'm wondering if your screenshot is a bug that happens with higher scaling. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 360229] Krita instantly closes when i use my tablet
https://bugs.kde.org/show_bug.cgi?id=360229 --- Comment #3 from Boudewijn Rempt --- Then there is nothing we can do; Trust no longer makes or sells or supports their tablets, so we cannot get test hardware. We might accidentally have fixed the crash in Krita 3.0 -- you can try a pre-alpha build and see if that works for you. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 360507] New: fingerprint
https://bugs.kde.org/show_bug.cgi?id=360507 Bug ID: 360507 Summary: fingerprint Product: systemsettings Version: unspecified Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: jean.comme...@gmail.com Application: systemsettings (4.11.16) KDE Platform Version: 4.14.5 Qt Version: 4.8.6 Operating System: Linux 4.1.15-desktop-2.mga5 x86_64 Distribution: "Mageia 5" -- Information about the crash: - What I was doing when the application crashed: enregistrement d'empreintes des doigts. le logiciel plante a la fin de l'enregistrement. Sur un Lenovo x201 The crash can be reproduced every time. -- Backtrace: Application: Configuration du système (systemsettings), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #5 0x7f820beeeda0 in EnrollStatus::clearStatus() () at /usr/lib64/kde4/kcm_kfingermanager.so #6 0x7f820beedf1c in FMEnroll::timeoutSlot() () at /usr/lib64/kde4/kcm_kfingermanager.so #7 0x7f8228b9388a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /lib64/libQtCore.so.4 #8 0x7f8228b97c2b in QObject::event(QEvent*) () at /lib64/libQtCore.so.4 #9 0x7f822980479c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQtGui.so.4 #10 0x7f822980ae40 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQtGui.so.4 #11 0x7f822a53725a in KApplication::notify(QObject*, QEvent*) () at /lib64/libkdeui.so.5 #12 0x7f8228b7fcad in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /lib64/libQtCore.so.4 #13 0x7f8228baf31b in QTimerInfoList::activateTimers() () at /lib64/libQtCore.so.4 #14 0x7f8228bac4f9 in idleTimerSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQtCore.so.4 #15 0x7f8221420c6d in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #16 0x7f8221420f18 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #17 0x7f8221420fbc in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #18 0x7f8228bace1e in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQtCore.so.4 #19 0x7f82298a24f6 in QGuiEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQtGui.so.4 #20 0x7f8228b7e931 in QEventLoop::processEvents(QFlags) () at /lib64/libQtCore.so.4 #21 0x7f8228b7ec45 in QEventLoop::exec(QFlags) () at /lib64/libQtCore.so.4 #22 0x7f8229cae0cc in QDialog::exec() () at /lib64/libQtGui.so.4 #23 0x7f820bee785d in FingerManagerWindow::fingerSelectedSlot(int) () at /usr/lib64/kde4/kcm_kfingermanager.so #24 0x7f8228b9388a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /lib64/libQtCore.so.4 #25 0x7f8229e56bb1 in QButtonGroup::buttonPressed(int) () at /lib64/libQtGui.so.4 #26 0x7f8229bb88af in QAbstractButtonPrivate::emitPressed() () at /lib64/libQtGui.so.4 #27 0x7f8229bb90ec in QAbstractButton::mousePressEvent(QMouseEvent*) () at /lib64/libQtGui.so.4 #28 0x7f8229854ba9 in QWidget::event(QEvent*) () at /lib64/libQtGui.so.4 #29 0x7f822980479c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQtGui.so.4 #30 0x7f822980af8e in QApplication::notify(QObject*, QEvent*) () at /lib64/libQtGui.so.4 #31 0x7f822a53725a in KApplication::notify(QObject*, QEvent*) () at /lib64/libkdeui.so.5 #32 0x7f8228b7fcad in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /lib64/libQtCore.so.4 #33 0x7f822980a66f in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () at /lib64/libQtGui.so.4 #34 0x7f822987c8b2 in QETWidget::translateMouseEvent(_XEvent const*) () at /lib64/libQtGui.so.4 #35 0x7f822987b2ac in QApplication::x11ProcessEvent(_XEvent*) () at /lib64/libQtGui.so.4 #36 0x7f82298a2442 in x11EventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQtGui.so.4 #37 0x7f8221420c6d in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #38 0x7f8221420f18 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #39 0x7f8221420fbc in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #40 0x7f8228bace1e in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQtCore.so.4 #41 0x7f82298a24f6 in QGuiEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQtGui.so.4 #42 0x7f8228b7e931 in QEventLoop::processEvents(QFlags) () at /lib64/libQtCore.so.4 #43 0x7f8228b7ec45 in QEventLoop::exec(QFlags) () at /lib64/libQtCore.so.4 #44 0x7f8228b83e59 in QCoreApplication::exec() () at /lib64/libQtCore.so.4 #45 0x0040aa8c in main () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 359887] Neon packages change DISTRIB_ID in /etc/lsb-release
https://bugs.kde.org/show_bug.cgi?id=359887 apache changed: What|Removed |Added CC||sabayo...@gmail.com --- Comment #6 from apache --- I have inconsistent release info http://i.imgur.com/OYnv4gA.png -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 359887] Neon packages change DISTRIB_ID in /etc/lsb-release
https://bugs.kde.org/show_bug.cgi?id=359887 --- Comment #7 from Jonathan Riddell --- If you have kubuntu-settings-desktop installed then it'll show that. remove --purge it if you don't want it to. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 360508] New: system tray doesn't show copy finished
https://bugs.kde.org/show_bug.cgi?id=360508 Bug ID: 360508 Summary: system tray doesn't show copy finished Product: neon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: n...@kde.org Reporter: sabayo...@gmail.com Created attachment 97885 --> https://bugs.kde.org/attachment.cgi?id=97885&action=edit systray entries KDE Neon 5.6.90 on Kubuntu 15.10 System tray doesn't show copy finished, nor copy pop-up dialog at all. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 360509] New: KDevelop doesn't highlight friend class members
https://bugs.kde.org/show_bug.cgi?id=360509
Bug ID: 360509
Summary: KDevelop doesn't highlight friend class members
Product: kdevelop
Version: git master
Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Language Support: CPP (Clang-based)
Assignee: kdevelop-bugs-n...@kde.org
Reporter: arkang...@gmail.com
The source was reduced by Milian to:
class LockableHolder
{
friend void swap(LockableHolder a, LockableHolder b)
{
a = b;
}
};
Execution of clang-parser yields:
clang-parser -a /tmp/test.cpp
AST tree successfully generated
ClassDecl (4) | type: "LockableHolder" (105) | display: "LockableHolder" | loc:
/tmp/test.cpp@[(1,1),(7,2)] | isDecl
UnexposedDecl (1) | loc: /tmp/test.cpp@[(3,5),(6,6)] | isDecl
no problems encountered during parsing
Reproducible: Always
This is likely an upstream issue.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 360403] plasma-desktop 5.5.95 with libunity: Chromium doesn't show minimize/maximize/close buttons for maximized windows
https://bugs.kde.org/show_bug.cgi?id=360403 --- Comment #4 from Timo Gurr --- FYI I've opened an upstream bug about this Chromium misbehaviour: https://bugs.chromium.org/p/chromium/issues/detail?id=594490 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 360510] New: oxygen5-icon-theme error processing archive
https://bugs.kde.org/show_bug.cgi?id=360510 Bug ID: 360510 Summary: oxygen5-icon-theme error processing archive Product: neon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: n...@kde.org Reporter: sabayo...@gmail.com Created attachment 97886 --> https://bugs.kde.org/attachment.cgi?id=97886&action=edit terminal output As in description. Look at attachment, please. The problem is that oxygen5-icon-theme has weird dependencies. I carelessly uninstalled it and it uninstalled Okular and I can't install Okular now because of the bug with processing oxygen5-icon-theme KDE Neon on Kubuntu 15.10 unstable, Plasma 5.6.90 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 360511] New: clang-parser utility doesn't get standard include files
https://bugs.kde.org/show_bug.cgi?id=360511 Bug ID: 360511 Summary: clang-parser utility doesn't get standard include files Product: kdevelop Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: arkang...@gmail.com When running the "clang-parser" utility in kdevelop/language/clang/tests, the include directories are not passed in. Thus, #include for example causes the parser session to stop. I hacked it by removing the "nostdinc" from parsersession.cpp, in the "empty parser session" conditional block, but this might have undesirable consequences. Reproducible: Always Steps to Reproduce: Write a simple C++ source with "#include " for example. A clang-parser execution should provide the "file not found" diagnostic. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 360512] New: Kate doesn't open text file with click.
https://bugs.kde.org/show_bug.cgi?id=360512 Bug ID: 360512 Summary: Kate doesn't open text file with click. Product: neon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: n...@kde.org Reporter: sabayo...@gmail.com Created attachment 97887 --> https://bugs.kde.org/attachment.cgi?id=97887&action=edit xsession-errors Kate doesn't open text file with click. I have to open Kate first and then open document or drug and drop. Actually it opened one file but then it couldn't open anymore. Actually Kate wasn't installed by default with the rest of Plasma 5.6.90. I installed it manually. KDE Neon on Kubuntu 15.10 unstable, Plasma 5.6.90 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 337153] kdev-qmljs crashes when parsing big projects [KDevelop::Declaration::setType, DeclarationBuilder::closeAndAssignType, QmlJS::AST::Node::accept]
https://bugs.kde.org/show_bug.cgi?id=337153 --- Comment #6 from Denis Steckelmacher --- I was never able to reproduce the bug. I have tested the file attached to this bug report, downloaded jsdom and other node.js packages, but everything always worked. A couple days later, I fixed a bug somewhere else that could have caused this one, but as I was not able to reproduce the problem, I don't know if I have fixed it. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 360512] Kate doesn't open text file with click.
https://bugs.kde.org/show_bug.cgi?id=360512 Harald Sitter changed: What|Removed |Added CC||sit...@kde.org Resolution|--- |UPSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #1 from Harald Sitter --- Kate is not part of Plasma, but Applications. We presently do not build applications, so that issue probably should be directed at Kubuntu instead. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 360511] clang-parser utility doesn't get standard include files
https://bugs.kde.org/show_bug.cgi?id=360511 Kevin Funk changed: What|Removed |Added Keywords||junior-jobs -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 360511] clang-parser utility doesn't get standard include files
https://bugs.kde.org/show_bug.cgi?id=360511 Kevin Funk changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Kevin Funk --- Note: You could work-around by doing: KDEV_CLANG_EXTRA_ARGUMENTS="-I /foo" clang-parser ... But we should indeed allow something as easy as: clang-parser -clang-parser-arg1 -clang-parser-arg2 -- -clang-arg1 -clang-arg2 myfile.cpp (Maybe even by simply setting KDEV_CLANG_EXTRA_ARGUMENTS inside clang-parser.cpp. Even better would be proper API inside kdev-clang to set the additional arguments) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360457] Thumbnail Scaling with "Accurate" filter not work
https://bugs.kde.org/show_bug.cgi?id=360457 --- Comment #3 from Thomas Lübking --- What does not magically enact your GPU to provide this feature. The environment is to check whether things in the driver may have changed and/or the GPU match is too wide (ie. a newer generation of chips is accidentally blacklisted) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 337153] kdev-qmljs crashes when parsing big projects [KDevelop::Declaration::setType, DeclarationBuilder::closeAndAssignType, QmlJS::AST::Node::accept]
https://bugs.kde.org/show_bug.cgi?id=337153 Kevin Funk changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #7 from Kevin Funk --- Alright. Assuming this was fixed in the meanwhile. -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 360513] New: Baloon crashed during git pull command execution
https://bugs.kde.org/show_bug.cgi?id=360513 Bug ID: 360513 Summary: Baloon crashed during git pull command execution Product: Baloo Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: m...@vhanda.in Reporter: pdraj...@gmail.com CC: pinak.ah...@gmail.com Application: baloo_file (5.18.0) Qt Version: 5.5.1 Operating System: Linux 4.2.0-30-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: - What I was doing when the application crashed: I was executing command git pull. When command has been finished I notced crash window. It happened second time in row once I executed this command. The crash can be reproduced sometimes. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Bus error Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [KCrash Handler] #6 __memcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:33 #7 0x7f8fbfa172d5 in memcpy (__len=23089600, __src=0x7f8f0008, __dest=) at /usr/include/x86_64-linux-gnu/bits/string3.h:53 #8 Baloo::IdTreeDB::get (this=this@entry=0x7fff3e0cdc30, docId=docId@entry=21956753285512196) at ../../../src/engine/idtreedb.cpp:90 #9 0x7f8fbfa1406d in Baloo::DocumentUrlDB::getChildren (this=this@entry=0x7fff3e0cdc80, docId=docId@entry=21956753285512196) at ../../../src/engine/documenturldb.cpp:165 #10 0x7f8fbfa2d8d7 in Baloo::WriteTransaction::removeRecursively (this=this@entry=0x1c293b0, parentId=21956753285512196) at ../../../src/engine/writetransaction.cpp:161 #11 0x7f8fbfa2d907 in Baloo::WriteTransaction::removeRecursively (this=0x1c293b0, parentId=21956448342834180) at ../../../src/engine/writetransaction.cpp:163 #12 0x7f8fbfa26139 in Baloo::Transaction::removeRecursively (this=, id=) at ../../../src/engine/transaction.cpp:244 #13 0x00428f25 in Baloo::MetadataMover::removeMetadata (this=this@entry=0x162d0c0, tr=tr@entry=0x7fff3e0cdd70, url=...) at ../../../src/file/metadatamover.cpp:84 #14 0x00428f6d in Baloo::MetadataMover::removeFileMetadata (this=0x162d0c0, file=...) at ../../../src/file/metadatamover.cpp:66 #15 0x7f8fbf556777 in QtPrivate::QSlotObjectBase::call (a=0x7fff3e0cdec0, r=0x162d0c0, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124 #16 QMetaObject::activate (sender=sender@entry=0x16b3e30, signalOffset=, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7fff3e0cdec0) at kernel/qobject.cpp:3698 #17 0x7f8fbf5570e7 in QMetaObject::activate (sender=sender@entry=0x16b3e30, m=m@entry=0x645840 , local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7fff3e0cdec0) at kernel/qobject.cpp:3578 #18 0x00432765 in Baloo::PendingFileQueue::removeFileIndex (this=this@entry=0x16b3e30, _t1=...) at moc_pendingfilequeue.cpp:217 #19 0x004270e6 in Baloo::PendingFileQueue::processCache (this=0x16b3e30) at ../../../src/file/pendingfilequeue.cpp:89 #20 0x7f8fbf556777 in QtPrivate::QSlotObjectBase::call (a=0x7fff3e0ce040, r=0x16b3e30, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124 #21 QMetaObject::activate (sender=sender@entry=0x16b3e48, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3698 #22 0x7f8fbf5570e7 in QMetaObject::activate (sender=sender@entry=0x16b3e48, m=m@entry=0x7f8fbf7717a0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3578 #23 0x7f8fbf5d63b0 in QTimer::timeout (this=this@entry=0x16b3e48) at .moc/moc_qtimer.cpp:197 #24 0x7f8fbf563198 in QTimer::timerEvent (this=0x16b3e48, e=) at kernel/qtimer.cpp:247 #25 0x7f8fbf557763 in QObject::event (this=0x16b3e48, e=) at kernel/qobject.cpp:1261 #26 0x7f8fbf527d5c in QCoreApplication::notify (event=0x7fff3e0ce1c0, receiver=0x16b3e48, this=0x7fff3e0ce4c0) at kernel/qcoreapplication.cpp:1038 #27 QCoreApplication::notifyInternal (this=0x7fff3e0ce4c0, receiver=0x16b3e48, event=event@entry=0x7fff3e0ce1c0) at kernel/qcoreapplication.cpp:965 #28 0x7f8fbf57d30d in QCoreApplication::sendEvent (event=0x7fff3e0ce1c0, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:224 #29 QTimerInfoList::activateTimers (this=0x15f3120) at kernel/qtimerinfo_unix.cpp:637 #30 0x7f8fbf57d849 in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:177 #31 idleTimerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:224 #32 0x7f8fbbb17ff7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #33 0x7f8fbbb18250 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #34 0x7f8fbbb182fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.
[kwin] [Bug 357007] kscreenlocker_greet unresponsive when using compositor
https://bugs.kde.org/show_bug.cgi?id=357007 --- Comment #34 from Jan-Marek Glogowski --- (In reply to Götz from comment #32) > Using EGL, there same issue(s) continue. > > > Can you try to kill just kscreenlocker_greet instead? (see jmux's input) > > Yes, the newly restarted kscreenlocker_greet works fine, and after unlocking > it, plasmashell is unresponsive. Is it also unresponsive for you Jan-Marek? > After killing plasmashell, the panel is still shown (there is no longer a > plasma process). Restarting kwin_x11 solves this. For me everything is responsive again, after killing the greeter and unlocking it. Otherwise I would run an other kind of session. I'm still don't know the origin of the deadlock. I thought it was related to DPMS, but locking the screen and running "sleep 10 && xset dpms force off" in the background doesn't trigger the greeter lockup. I just know it doesn't always lockup the greeter, but ever after longer inactivity. (In reply to Thomas Lübking from comment #30) > You may safely assume that this is a bug in the greeter or its foundation > (greeter dysfunctional -> killing. restarted greeter works) > Common pattern is Gallium/AMD, can you try EGL compositing? If I switch to EGL, compositing is disabled (according to to the qdbus output). Doesn't matter if I select OpenGL 2.0 or 3.1. The stripped output from es2_info (minus stripped extensions) says: 1.5 - not sure if this EGL version is related to the selected OpenGL version: EGL_VERSION: 1.5 (DRI2) EGL_VENDOR: Mesa Project EGL_CLIENT_APIS: OpenGL OpenGL_ES OpenGL_ES2 OpenGL_ES3 GL_VERSION: OpenGL ES 3.0 Mesa 11.1.2 GL_RENDERER: Gallium 0.4 on AMD RV710 (DRM 2.43.0, LLVM 3.8.0) BTW: my HW is old - a [AMD/ATI] RV710/M92 [Mobility Radeon HD 4530/4570/545v] -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357007] kscreenlocker_greet unresponsive when using compositor
https://bugs.kde.org/show_bug.cgi?id=357007 --- Comment #35 from Jan-Marek Glogowski --- Created attachment 97888 --> https://bugs.kde.org/attachment.cgi?id=97888&action=edit jmux full es2_info output -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 352050] Moving windows between monitors is stuttering badly when side screen tiling is enabled.
https://bugs.kde.org/show_bug.cgi?id=352050 --- Comment #14 from Thomas Lübking --- How fast do you move windows? You'll have 250ms to get it across the active area (20px on either side of the edge) - otherwise the indicator is still created. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 328359] Amarok crashes when using MusicBrains to update tags [@ MusicBrainzTagsItem::childCount]
https://bugs.kde.org/show_bug.cgi?id=328359 Myriam Schweingruber changed: What|Removed |Added CC||ukr...@gmail.com --- Comment #48 from Myriam Schweingruber --- *** Bug 360447 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 360447] Amarok is crashing when trying to fetch tags from MusicBrainz
https://bugs.kde.org/show_bug.cgi?id=360447 Myriam Schweingruber changed: What|Removed |Added CC||123k...@gmail.com Component|general |Metadata Editing and ||Reading Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Myriam Schweingruber --- Thankyou for the report, but unfortunately your backtrace has no debugging symbols, without those it is rather useless. When submitting crash reports, please make sure Dr. Konqi gives you at least a 2 star rating, and that you have debugging symbols installed for Amarok and its dependencies. Please see also https://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports on how to get a a better backtrace. FWIW: Dr. Konqi would then also have shown you that this is a known bug *** This bug has been marked as a duplicate of bug 328359 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 337186] LineTool - possibility to switch off stroke preview
https://bugs.kde.org/show_bug.cgi?id=337186 wolthera changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||griffinval...@gmail.com Resolution|--- |FIXED --- Comment #2 from wolthera --- fixed I guess https://phabricator.kde.org/rKRITA4abc1af37a470878363f71c8ba61a29068106519 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355190] copy current date/time into clipboard
https://bugs.kde.org/show_bug.cgi?id=355190 user_feedback_...@yahoo.com changed: What|Removed |Added CC||user_feedback_...@yahoo.com --- Comment #10 from user_feedback_...@yahoo.com --- Count me as another user who misses this functionality. I used to use it every couple of days to add dates to emails or add the date to a folder name. I found it quicker and less error prone that reading off the date and typing it in by hand. I was really frustrated when I found, for no apparent reason, this functionality had just disappeared. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcmutils] [Bug 349631] There is no possibility to configure my touchscreen
https://bugs.kde.org/show_bug.cgi?id=349631 Kiril Vladimiroff changed: What|Removed |Added CC||ki...@vladimiroff.org -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 357413] kde crash on user swap
https://bugs.kde.org/show_bug.cgi?id=357413 --- Comment #9 from Wolfgang Bauer --- Created attachment 97889 --> https://bugs.kde.org/attachment.cgi?id=97889&action=edit patch that fixes the crash The attached patch to qtdeclarative 5.5.1 prevents the crashes here. I think I'll just add this to openSUSE's Qt 5.5.1 packages. As mentioned, it seems to be fixed with Qt 5.6 anyway. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360514] Fade-out/fade-in when autohiding
https://bugs.kde.org/show_bug.cgi?id=360514 Yves Glodt changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360514] New: Fade-out/fade-in when autohiding
https://bugs.kde.org/show_bug.cgi?id=360514 Bug ID: 360514 Summary: Fade-out/fade-in when autohiding Product: plasmashell Version: 5.5.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: y...@mind.lu This is purely a nice-to-have thing. It would be nice if we could have the panel fade-out and fade-in if it's set to autohide. The current slide-from-bottom is functionally ok. But it feels old-fashioned. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 360515] New: Crash on KDE audio config
https://bugs.kde.org/show_bug.cgi?id=360515 Bug ID: 360515 Summary: Crash on KDE audio config Product: systemsettings Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ivan10...@yahoo.com.br Application: kcmshell4 (4.14.9) KDE Platform Version: 4.14.9 Qt Version: 4.8.6 Operating System: Linux 3.16.7-35-desktop x86_64 Distribution: "openSUSE 13.2 (Harlequin) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Every times when open KDE audio configuration a KDE exception handler is opened. When knotify is invoqued same error occours. The crash can be reproduced every time. -- Backtrace: Application: Módulo de controle do KDE (kcmshell4), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #5 0x7fde5f1b9fec in __strcmp_ssse3 () at /lib64/libc.so.6 #6 0x7fde4453afee in QMetaType::registerNormalizedType(QByteArray const&, void (*)(void*), void* (*)(void const*), void (*)(void*), void* (*)(void*, void const*), int, QFlags, QMetaObject const*) () at /usr/lib64/libQt5Core.so.5 #7 0x7fde44a3af57 in () at /usr/lib64/libQt5Gui.so.5 #8 0x7fde5f6598ea in call_init.part () at /lib64/ld-linux-x86-64.so.2 #9 0x7fde5f6599d3 in _dl_init_internal () at /lib64/ld-linux-x86-64.so.2 #10 0x7fde5f65db08 in dl_open_worker () at /lib64/ld-linux-x86-64.so.2 #11 0x7fde5f6597a4 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2 #12 0x7fde5f65d2fb in _dl_open () at /lib64/ld-linux-x86-64.so.2 #13 0x7fde59db102b in dlopen_doit () at /lib64/libdl.so.2 #14 0x7fde5f6597a4 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2 #15 0x7fde59db15dd in _dlerror_run () at /lib64/libdl.so.2 #16 0x7fde59db10c1 in dlopen@@GLIBC_2.2.5 () at /lib64/libdl.so.2 #17 0x7fde467e359f in () at /usr/lib64/libvlccore.so.7 #18 0x7fde467ccd5d in () at /usr/lib64/libvlccore.so.7 #19 0x7fde467cd057 in () at /usr/lib64/libvlccore.so.7 #20 0x7fde467cd2c9 in () at /usr/lib64/libvlccore.so.7 #21 0x7fde467cd534 in () at /usr/lib64/libvlccore.so.7 #22 0x7fde467cda87 in () at /usr/lib64/libvlccore.so.7 #23 0x7fde4676549d in libvlc_InternalInit () at /usr/lib64/libvlccore.so.7 #24 0x7fde46536623 in libvlc_new () at /usr/lib64/libvlc.so.5 #25 0x7fde46a67ec9 in () at /usr/lib64/kde4/plugins/phonon_backend/phonon_vlc.so #26 0x7fde46a4d728 in () at /usr/lib64/kde4/plugins/phonon_backend/phonon_vlc.so #27 0x7fde46a4e1eb in qt_plugin_instance () at /usr/lib64/kde4/plugins/phonon_backend/phonon_vlc.so #28 0x7fde5dd33641 in QPluginLoader::instance() () at /usr/lib64/libQtCore.so.4 #29 0x7fde46f96f8b in () at /usr/lib64/kde4/plugins/phonon_platform/kde.so #30 0x7fde46f97773 in () at /usr/lib64/kde4/plugins/phonon_platform/kde.so #31 0x7fde4d845c76 in () at /usr/lib64/libphonon.so.4 #32 0x7fde4d846317 in Phonon::Factory::backend(bool) () at /usr/lib64/libphonon.so.4 #33 0x7fde4d849aaa in Phonon::GlobalConfig::audioOutputDeviceListFor(Phonon::Category, int) const () at /usr/lib64/libphonon.so.4 #34 0x7fde4dacfb0a in () at /usr/lib64/kde4/kcm_phonon.so #35 0x7fde4dad04b8 in () at /usr/lib64/kde4/kcm_phonon.so #36 0x7fde4dac9564 in () at /usr/lib64/kde4/kcm_phonon.so #37 0x7fde4dac981b in () at /usr/lib64/kde4/kcm_phonon.so #38 0x7fde5e53a553 in KPluginFactory::create(char const*, QWidget*, QObject*, QList const&, QString const&) () at /usr/lib64/libkdecore.so.5 #39 0x7fde5ee72ede in KCModuleLoader::loadModule(KCModuleInfo const&, KCModuleLoader::ErrorReporting, QWidget*, QStringList const&) () at /usr/lib64/libkcmutils.so.4 #40 0x7fde5ee780e3 in () at /usr/lib64/libkcmutils.so.4 #41 0x7fde5ee787f5 in KCModuleProxy::realModule() const () at /usr/lib64/libkcmutils.so.4 #42 0x7fde5ee78b59 in KCModuleProxy::useRootOnlyMessage() const () at /usr/lib64/libkcmutils.so.4 #43 0x7fde5ee75b91 in KCMultiDialog::addModule(KCModuleInfo const&, KPageWidgetItem*, QStringList const&) () at /usr/lib64/libkcmutils.so.4 #44 0x7fde5f44625e in kdemain () at /usr/lib64/libkdeinit4_kcmshell4.so #45 0x7fde5f0b7b05 in __libc_start_main () at /lib64/libc.so.6 #46 0x0040075e in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354928] Minimized task cannot be told apart from a not running launcher
https://bugs.kde.org/show_bug.cgi?id=354928 Simon Andric changed: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 356940] kalarm crash on start up
https://bugs.kde.org/show_bug.cgi?id=356940 Hugo Pereira Da Costa changed: What|Removed |Added CC||anntzer@gmail.com --- Comment #1 from Hugo Pereira Da Costa --- *** Bug 360151 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 360151] Frequent segfault when a PyQt application exits.
https://bugs.kde.org/show_bug.cgi?id=360151 Hugo Pereira Da Costa changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #6 from Hugo Pereira Da Costa --- *** This bug has been marked as a duplicate of bug 356940 *** -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 353246] OpenLP tool bars are incorrectly styles with Breeze
https://bugs.kde.org/show_bug.cgi?id=353246 Hugo Pereira Da Costa changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 356276] Kate crashes when opened file is changed by external program
https://bugs.kde.org/show_bug.cgi?id=356276 Christoph Cullmann changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED CC||cullm...@kde.org --- Comment #1 from Christoph Cullmann --- cullmann committed rKATE3a0fe4097d3d: fix crash if any signals arrives during handleSelected (authored by cullmann). fix crash if any signals arrives during handleSelected BRANCHES master AFFECTED FILES /kate/katemwmodonhddialog.cpp /kate/katemwmodonhddialog.h USERS cullmann (Author) COMMIT https://phabricator.kde.org/rKATE3a0fe4097d3d EMAIL PREFERENCES https://phabricator.kde.org/settings/panel/emailpreferences/ To: cullmann -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 357556] During import of vCard: Message box with either-or-question provides Yes/No buttons
https://bugs.kde.org/show_bug.cgi?id=357556 Gunter Ohrner changed: What|Removed |Added CC||kdeb...@customcdrom.de --- Comment #4 from Gunter Ohrner --- Created attachment 97890 --> https://bugs.kde.org/attachment.cgi?id=97890&action=edit Correct messagebox for importing iCal/vCal, which appears if kOrganizer is already running. This screenshot shows the same dialog with correct buttons. It appears this way if the kOrganizer is already running when the iCal/vCal file is to be imported. The buttons read "Merge into existing calendar" and "Import as new calendar". If the kOrganizer GUI is not yet running while an iCal/vCal import is attempted, the same message box appears but shows just "Yes" and "No" instead, while the displayed message is an either/or question. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 360516] New: Locked transparency mask position doesn't stay locked while moving parent layer
https://bugs.kde.org/show_bug.cgi?id=360516 Bug ID: 360516 Summary: Locked transparency mask position doesn't stay locked while moving parent layer Product: krita Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: raghavendr.ra...@gmail.com If we want to move a layer but not the transparency masks, we often lock the transparency mask and hide it . but in recent 3.0 alpha git , moving the layer also moves the locked transparency mask too. Reproducible: Always Steps to Reproduce: 1.open Krita and create a new document 2.scribble something and make a selection then add a transparency mask, then lock and hide this transparency mask 3.now move the parent layer , then unhide and unlock the transparency mask Actual Results: the transparency mask gets moved even if it is locked down Expected Results: the tranparency mask should be intact in same place -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 351593] Ark extracts into subdirectory regardless of "Extract into subdirectory" checkbox
https://bugs.kde.org/show_bug.cgi?id=351593 Elvis Angelaccio changed: What|Removed |Added Severity|major |normal --- Comment #10 from Elvis Angelaccio --- (In reply to Steven Roose from comment #3) > When extracted without "Extract into subfolder", the latter type of archive > will still appear as if it was extracted into a subfolder, because the "root > folder" of the archive is the folder where all the files are in. This is the intended behavior. If the archive has a root folder and if you are preserving the paths, then the root folder will occur in the extracted path, because it's just a normal folder. > But when > "Extract into subfolder" is enabled, that root folder (which is mostly the > same as the name of the archive), will appear twice. This is also intentional, although I'd agree that it doesn't make much sense. > > Hopefully you understand what I mean. It's possible that the functions are > implemented correctly, but just behave different from how all other > extraction tools I've used before behave. I noticed that because it annoyed > me, that's the reason I filed this issue. So, what you really want is the following feature/option: "always discard the root folder if it has the same name of the archive". If you can confirm this, I will mark this report as whish instead of bug. @Hans Überacher: please open another report for your issue. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 359416] Merge Selected Layers shortcut is unreliable
https://bugs.kde.org/show_bug.cgi?id=359416 wolthera changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |RESOLVED --- Comment #5 from wolthera --- Tyson, please check if this still happens with the 3.0 pre-alpha whenever you get the chance? -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 357556] During import of vCard: Message box with either-or-question provides Yes/No buttons
https://bugs.kde.org/show_bug.cgi?id=357556 --- Comment #5 from Laurent Montel --- I confirm it it's a bug in kmessagebox + kguiitem... No idea how to fix it yet -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 352043] Regression: kOrganizer 5 systray reminder module does not open main application window on click
https://bugs.kde.org/show_bug.cgi?id=352043 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- Still valid ? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 270808] KDE should spin-down external hard disks when 'safely removed'
https://bugs.kde.org/show_bug.cgi?id=270808 Davide Olianas changed: What|Removed |Added CC||n...@davideolianas.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 353503] cursor shape offsetting to the right with intuos 5
https://bugs.kde.org/show_bug.cgi?id=353503 Boudewijn Rempt changed: What|Removed |Added OS|Windows CE |MS Windows -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 360517] New: Gwenview crashes when using image viewer and navigating to next image with arrowkey on keyboard
https://bugs.kde.org/show_bug.cgi?id=360517 Bug ID: 360517 Summary: Gwenview crashes when using image viewer and navigating to next image with arrowkey on keyboard Product: gwenview Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: pandora...@gmail.com CC: myr...@kde.org Application: gwenview (4.14.0 pre) KDE Platform Version: 4.14.17 Qt Version: 4.8.6 Operating System: Linux 4.1.15-8-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: I am rating images with Gwenview. When going to next image, sometimes Gwenview crashes. Happens a couple of times per day. I have used both OpenGL and software viewer. Crash seems to happen with both settings. I have nvidia drivers installed. OS > OpenSuse Leap 42.1 The crash can be reproduced sometimes. -- Backtrace: Application: Gwenview (gwenview), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f36b6d75880 (LWP 14119))] Thread 3 (Thread 0x7f369ee0c700 (LWP 14124)): #0 0x7f36b3796bbd in poll () at /lib64/libc.so.6 #1 0x7f36b0626e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f36b0626f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f36b6305fde in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #4 0x7f36b62d7d4f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #5 0x7f36b62d8045 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7f36b61d54df in QThread::exec() () at /usr/lib64/libQtCore.so.4 #7 0x7f36b62b9653 in () at /usr/lib64/libQtCore.so.4 #8 0x7f36b61d7bbf in () at /usr/lib64/libQtCore.so.4 #9 0x7f36b0af60a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f36b379efed in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f3696935700 (LWP 16802)): #0 0x7f36b0afa3e8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f36b61d8084 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQtCore.so.4 #2 0x7f36b61cbbda in () at /usr/lib64/libQtCore.so.4 #3 0x7f36b61d7bbf in () at /usr/lib64/libQtCore.so.4 #4 0x7f36b0af60a4 in start_thread () at /lib64/libpthread.so.0 #5 0x7f36b379efed in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f36b6d75880 (LWP 14119)): [KCrash Handler] #6 0x7f36abbef598 in Xapian::Database::get_document(unsigned int) const () at /usr/lib64/libxapian.so.22 #7 0x7f36ab99e8a4 in Baloo::XapianDatabase::document(unsigned int) () at /usr/lib64/libbalooxapian.so.4 #8 0x7f36b1db72ed in Baloo::FileModifyJob::doStart() () at /usr/lib64/libbaloofiles.so.4 #9 0x7f36b62f149e in QObject::event(QEvent*) () at /usr/lib64/libQtCore.so.4 #10 0x7f36b448679c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #11 0x7f36b448ccdd in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #12 0x7f36b519de1a in KApplication::notify(QObject*, QEvent*) () at /usr/lib64/libkdeui.so.5 #13 0x7f36b62d918d in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQtCore.so.4 #14 0x7f36b62dc45d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQtCore.so.4 #15 0x7f36b63067fe in () at /usr/lib64/libQtCore.so.4 #16 0x7f36b0626c84 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #17 0x7f36b0626ed8 in () at /usr/lib64/libglib-2.0.so.0 #18 0x7f36b0626f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #19 0x7f36b6305fbe in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #20 0x7f36b45236a6 in () at /usr/lib64/libQtGui.so.4 #21 0x7f36b62d7d4f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #22 0x7f36b62d8045 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #23 0x7f36b62dd499 in QCoreApplication::exec() () at /usr/lib64/libQtCore.so.4 #24 0x00429ded in () #25 0x7f36b36dbb05 in __libc_start_main () at /lib64/libc.so.6 #26 0x0042a092 in _start () Possible duplicates by query: bug 354329, bug 347915, bug 340933. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 360518] New: One message log for all rooms
https://bugs.kde.org/show_bug.cgi?id=360518 Bug ID: 360518 Summary: One message log for all rooms Product: konversation Version: unspecified Platform: unspecified OS: All Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: logging Assignee: konversation-de...@kde.org Reporter: shaloksha...@riseup.net Currently log konversation my sended messages for each channel seperately. Please offer the option, to log all messages into one single cache, thanks a lot. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 360518] One message log for all channels
https://bugs.kde.org/show_bug.cgi?id=360518 Matthias changed: What|Removed |Added Summary|One message log for all |One message log for all |rooms |channels -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 360056] crash
https://bugs.kde.org/show_bug.cgi?id=360056 --- Comment #5 from ybsar --- Created attachment 97891 --> https://bugs.kde.org/attachment.cgi?id=97891&action=edit backtrace with full debug symbols -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 360519] New: none/tests/arm64/memory.vgtest might fail with newer gcc
https://bugs.kde.org/show_bug.cgi?id=360519 Bug ID: 360519 Summary: none/tests/arm64/memory.vgtest might fail with newer gcc Product: valgrind Version: 3.11 SVN Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: m...@redhat.com The LDR (literal, int reg) testcase take a code label and compare the instructions around the label with known instructions in the code stream. The comment says: // This is a bit tricky. We load the value from just before and // just after the actual instruction. Because TESTINSN2_hide2 // generates two fixed insns either side of the test insn, these // should be constant and hence "safe" to check. However two fixed insns on either side of the checking instruction isn't enough given that offsets of +/-8 are used, instructions are only 4 wide and the values loaded are 64bit. Newer gcc versions would generate different code around the label and cause the tests to fail, The proposed solution is to add enough nops around the actual instruction to really give known expected constant values to check against. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 360519] none/tests/arm64/memory.vgtest might fail with newer gcc
https://bugs.kde.org/show_bug.cgi?id=360519 --- Comment #1 from Mark Wielaard --- Created attachment 97892 --> https://bugs.kde.org/attachment.cgi?id=97892&action=edit Place nops around ldr literal test instruction and adjust expected output -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 356012] Wish: Extra whitespace should be highlighted in git diff output
https://bugs.kde.org/show_bug.cgi?id=356012 Francis Herne changed: What|Removed |Added CC||francis.he...@yahoo.co.uk --- Comment #1 from Francis Herne --- The setting 'highlight trailing spaces' (Editor -> Appearance -> Whitespace Highlighting) applies to the diff view. The appearance isn't so conspicuous by default, but you can change the colour 'Tab and Space Markers' to something colourful. Additionally, setting 'Remove trailing spaces' (Editor -> Open/Save -> Automatic Cleanups on Save) to an option that isn't "Never" will prevent the whitespace from existing in the first place. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 357412] KDE user swap crash
https://bugs.kde.org/show_bug.cgi?id=357412 Christoph Feck changed: What|Removed |Added Assignee|unassigned-b...@kde.org |l.lu...@kde.org Resolution|BACKTRACE |--- Component|general |ui Product|kde |ksmserver Status|NEEDSINFO |UNCONFIRMED --- Comment #4 from Christoph Feck --- Backtrace from comment #2: Application: ksmserver (ksmserver), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2b53559940 (LWP 2307))] Thread 3 (Thread 0x7f2b217f1700 (LWP 11407)): #0 0x7f2b48cdc07f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f2b229a4cc3 in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f2b229a4507 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f2b48cd64a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f2b52ea0ded in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f2b23ff6700 (LWP 19133)): #0 0x7f2b52e9447d in read () from /lib64/libc.so.6 #1 0x7f2b473a5290 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f2b47362dc4 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f2b47363238 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f2b4736339c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f2b4da6552b in QEventDispatcherGlib::processEvents (this=0x7f2af81fb1d0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #6 0x7f2b4da0f61a in QEventLoop::exec (this=this@entry=0x7f2b23ff5c70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #7 0x7f2b4d83bb1c in QThread::exec (this=this@entry=0x2123940) at thread/qthread.cpp:503 #8 0x7f2b510547b5 in QQmlThreadPrivate::run (this=0x2123940) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141 #9 0x7f2b4d84094f in QThreadPrivate::start (arg=0x2123940) at thread/qthread_unix.cpp:331 #10 0x7f2b48cd64a4 in start_thread () from /lib64/libpthread.so.0 #11 0x7f2b52ea0ded in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f2b53559940 (LWP 2307)): [KCrash Handler] #6 QtPrivate::RefCount::ref (this=0x4) at /usr/include/qt5/QtCore/qrefcount.h:54 #7 QV4::Heap::String::toQString (this=) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/jsruntime/qv4string_p.h:84 #8 QV4::String::toQString (this=) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/jsruntime/qv4string_p.h:145 #9 QV4::Heap::StringObject::StringObject (this=, engine=0x2298e60, val=...) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/jsruntime/qv4stringobject.cpp:91 #10 0x7f2b50f19885 in QV4::MemoryManager::alloc (arg2=..., arg1=0x2298e60, this=) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/jsruntime/qv4mm_p.h:126 #11 QV4::ExecutionEngine::newStringObject (this=0x2298e60, value=...) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/jsruntime/qv4engine.cpp:557 #12 0x7f2b50fad5be in QV4::Runtime::getProperty (engine=0x2298e60, object=..., nameIndex=) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/jsruntime/qv4runtime.cpp:682 #13 0x7f2b51b7bde5 in ?? () #14 0x02129430 in ?? () #15 0x7ffd8a6d1480 in ?? () #16 0x00040003 in ?? () #17 0x7f2b50fac1f3 in QV4::Object::call (d=, this=) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/jsruntime/qv4object_p.h:305 #18 QV4::RuntimeHelpers::objectDefaultValue (object=0x7ffd8a6d1480, typeHint=) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/jsruntime/qv4runtime.cpp:408 #19 0x7f2b50f53b8a in QV4::SimpleScriptFunction::call (that=, callData=) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/jsruntime/qv4functionobject.cpp:564 #20 0x7f2b5103ab5e in QV4::Object::call (d=0x7f2b17c30008, this=) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/jsruntime/qv4object_p.h:305 #21 QQmlJavaScriptExpression::evaluate (this=this@entry=0x2136400, context=, function=..., callData=callData@entry=0x7f2b17c30008, isUndefined=isUndefined@entry=0x7ffd8a6d16b8) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/qqmljavascriptexpression.cpp:158 #22 0x7f2b5103b06d in QQmlJavaScriptExpression::evaluate (this=this@entry=0x2136400, context=, function=..., isUndefined=isUndefined@entry=0x7ffd8a6d16b8) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/qqmljavascriptexpression.cpp:116 #23 0x7f2b510414f4 in QQmlBinding::update (this=0x21363e0, flags=...) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/qqmlbinding.cpp:194 #24 0x7f2b5104a596 in QQmlAbstractBinding::setEnabled (f=..., e=true, this=0x2136418) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/qqmlabstractb
[ksmserver] [Bug 357412] KDE user swap crash
https://bugs.kde.org/show_bug.cgi?id=357412 Christoph Feck changed: What|Removed |Added Version|unspecified |5.5.5 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 354056] Deleted emails stay, but greyed out
https://bugs.kde.org/show_bug.cgi?id=354056 --- Comment #30 from David Brůha --- (In reply to Ben from comment #29) > You can select "Automatically compact folders" in the Advanced Tab of the > IMAP Ressource. > > This will instruct KMail to send the EXPUNGE command and you will get rid of > the greyed out messages. > > Why you cannot tell kmail to not display messages marked as deleted is > beyond my understanding though. That should be standard. > > Also, boo to the kmail developers, who failed to respond properly to this > bug report in weeks. And it is not the only report I noticed this behaviour. > Is there any active development in kmail? Ben, that doesn't work, that is the problem. When KMail connects to Courier IMAP server it simply doesn't expunge deleted messages no matter how you set KMail up. Older versions had been ok. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 360520] New: Can't import png and jpg files.
https://bugs.kde.org/show_bug.cgi?id=360520 Bug ID: 360520 Summary: Can't import png and jpg files. Product: krita Version: 2.9.11 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: twoal...@gmail.com Hi. When I trying to import png or jpg, Krita keep saying "Couldn't create the filter plugin." I don't know since when, but it never happened before last weekend. This is terminal output. aloel@20141017m2 ~ $ krita ### # Adding a tablet device: Wacom Intuos S Pen stylus Device Type: "Stylus" # Axes limits data X:0 15200 Y:0 9500 Z:0 0 Pressure: 0 2048 Rotation: -900 899 T. Pres: 0 0 ### # Adding a tablet device: Wacom Intuos S Pen eraser Device Type: "XFreeEraser" # Axes limits data X:0 15200 Y:0 9500 Z:0 0 Pressure: 0 2048 Rotation: 0 1 T. Pres: 0 0 Got bus address: "unix:abstract=/tmp/dbus-Q77n8qqDf4,guid=f31164fa5be1af196e32c92556e676f7" Connected to accessibility bus at: "unix:abstract=/tmp/dbus-Q77n8qqDf4,guid=f31164fa5be1af196e32c92556e676f7" Registered DEC: true krita(20590)/koffice (lib komain) KoPluginLoader::load: Loading plugin "Textdocument Inspection" failed, "Could not find plugin 'Textdocument Inspection' for application 'krita'" Object::connect: No such signal QToolButton::triggered() in /build/krita-2.9-INmjI7/krita-2.9-2+git20160202+r46/krita/plugins/extensions/dockers/defaultdockers/kis_layer_box.cpp:241 Object::connect: (sender name: 'bnRaise') Object::connect: No such signal QToolButton::triggered() in /build/krita-2.9-INmjI7/krita-2.9-2+git20160202+r46/krita/plugins/extensions/dockers/defaultdockers/kis_layer_box.cpp:242 Object::connect: (sender name: 'bnLower') Registered event listener change listener: true QSpiAccessible::accessibleEvent not handled: "8008" obj: QObject(0x0) " invalid interface!" QSpiAccessible::accessibleEvent not handled: "8008" obj: QSidebar(0x3e2f7d0, name = "sidebar") "sidebar" FIXME: handle dialog start. FIXME: handle dialog end. QSpiAccessible::accessibleEvent not handled: "6" obj: KMenu(0x3e99ea0) "" QSpiAccessible::accessibleEvent not handled: "7" obj: KMenu(0x3e99ea0) "" QSpiAccessible::accessibleEvent not handled: "6" obj: KMenu(0x3f2eb40, name = "help") "help" QSpiAccessible::accessibleEvent not handled: "7" obj: KMenu(0x3f2eb40, name = "help") "help" FIXME: handle dialog start. FIXME: handle dialog end. QSpiAccessible::accessibleEvent not handled: "8008" obj: QObject(0x0) " invalid interface!" QSpiAccessible::accessibleEvent not handled: "8008" obj: QSidebar(0x3cade40, name = "sidebar") "sidebar" FIXME: handle dialog start. FIXME: handle dialog end. krita(20590)/koffice (lib komain) KisFilterEntry::createFilter: "Could not find plugin 'Krita JPEG Import Filter' for application 'krita'" krita(20590)/koffice (filter manager): Couldn't create the filter. QSpiAccessible::accessibleEvent not handled: "2" obj: QMessageBox(0x7fffe4214a80) "" FIXME: handle dialog start. FIXME: handle dialog end. Loading "/home/aloel/Pictures/wallpaper/42593_1600x1200-wallpaper-cb1320062937.jpg" failed QSpiAccessible::accessibleEvent not handled: "8008" obj: QObject(0x0) " invalid interface!" QSpiAccessible::accessibleEvent not handled: "8008" obj: QSidebar(0x3f1b630, name = "sidebar") "sidebar" FIXME: handle dialog start. QSpiAccessible::accessibleEvent not handled: "8008" obj: QObject(0x0) " invalid interface!" QSpiAccessible::accessibleEvent not handled: "8008" obj: QObject(0x0) " invalid interface!" QSpiAccessible::accessibleEvent not handled: "8008" obj: QObject(0x0) " invalid interface!" QSpiAccessible::accessibleEvent not handled: "8008" obj: QObject(0x0) " invalid interface!" QSpiAccessible::accessibleEvent not handled: "8008" obj: QObject(0x0) " invalid interface!" QSpiAccessible::accessibleEvent not handled: "8008" obj: QObject(0x0) " invalid interface!" QSpiAccessible::accessibleEvent not handled: "8008" obj: QObject(0x0) " invalid interface!" QSpiAccessible::accessibleEvent not handled: "8008" obj: QObject(0x0) " invalid interface!" QSpiAccessible::accessibleEvent not handled: "8008" obj: QObject(0x0) " invalid interface!" QSpiAccessible::accessibleEvent not handled: "8008" obj: QObject(0x0) " invalid interface!" QSpiAccessible::accessibleEvent not handled: "8008" obj: QObject(0x0) " invalid interface!" QSpiAccessible::accessibleEvent not handled: "8008" obj: QObject(0x0) " invalid interface!" QSpiAccessible::accessibleEvent not handled: "8008" obj: QObject(0x0) " invalid interface!" QSpiAccessible::accessibleEvent not handled: "8008" obj: QObject(0x0) "
[krita] [Bug 360520] Can't import png and jpg
https://bugs.kde.org/show_bug.cgi?id=360520 twoal...@gmail.com changed: What|Removed |Added Summary|Can't import png and jpg|Can't import png and jpg |files. | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360493] plasma crash at startup (probably baloo)
https://bugs.kde.org/show_bug.cgi?id=360493 Marco Martin changed: What|Removed |Added CC||notm...@gmail.com Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Marco Martin --- *** This bug has been marked as a duplicate of bug 357300 *** -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 358421] Krunner search window repeatedly crashes
https://bugs.kde.org/show_bug.cgi?id=358421 Marco Martin changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||notm...@gmail.com --- Comment #3 from Marco Martin --- *** This bug has been marked as a duplicate of bug 357300 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 357300] plasmashell crash - mdb_env_pick_meta (env=0x7f634c178970) at mdb.c:3709
https://bugs.kde.org/show_bug.cgi?id=357300 Marco Martin changed: What|Removed |Added CC||br...@jikos.cz --- Comment #1 from Marco Martin --- *** Bug 358421 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 357300] plasmashell crash - mdb_env_pick_meta (env=0x7f634c178970) at mdb.c:3709
https://bugs.kde.org/show_bug.cgi?id=357300 Marco Martin changed: What|Removed |Added CC||verta...@hotmail.com --- Comment #2 from Marco Martin --- *** Bug 360493 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360494] Plasma Shell crashed unexpectedly after make a search on the application Launcher
https://bugs.kde.org/show_bug.cgi?id=360494 Marco Martin changed: What|Removed |Added CC||notm...@gmail.com Severity|normal |crash --- Comment #2 from Marco Martin --- Thread 4 (Thread 0x7f21fcdaf700 (LWP 1997)): [KCrash Handler] #6 __memcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:167 #7 0x7f21e9f7fa3a in memcpy (__len=6, __src=, __dest=) at /usr/include/x86_64-linux-gnu/bits/string3.h:53 #8 Baloo::PostingCodec::decode (this=this@entry=0x7f21fcdae49f, arr=...) at ../../../src/codecs/postingcodec.cpp:42 #9 0x7f21e9f6b99e in DBPostingIterator::DBPostingIterator (this=0x7f21f81b9ad0, data=, size=) at ../../../src/engine/postingdb.cpp:177 #10 0x7f21e9f6ba61 in Baloo::PostingDB::iter (this=this@entry=0x7f21fcdae590, term=...) at ../../../src/engine/postingdb.cpp:169 #11 0x7f21e9f749eb in Baloo::Transaction::postingIterator (this=this@entry=0x7f21fcdae990, query=...) at ../../../src/engine/transaction.cpp:294 #12 0x7f21ea3beb0c in Baloo::SearchStore::constructQuery (this=this@entry=0x7f21fcdaea80, tr=tr@entry=0x7f21fcdae990, term=...) at ../../../src/lib/searchstore.cpp:189 #13 0x7f21ea3becba in Baloo::SearchStore::constructQuery (this=this@entry=0x7f21fcdaea80, tr=tr@entry=0x7f21fcdae990, term=...) at ../../../src/lib/searchstore.cpp:163 #14 0x7f21ea3bfc9c in Baloo::SearchStore::exec (this=this@entry=0x7f21fcdaea80, term=..., offset=0, limit=10, sortResults=) at ../../../src/lib/searchstore.cpp:75 #15 0x7f21ea3aec32 in Baloo::Query::exec (this=this@entry=0x7f21fcdaeb40) at ../../../src/lib/query.cpp:210 #16 0x7f21ea5d0667 in SearchRunner::match (this=this@entry=0x693af80, context=..., type=..., category=...) at ../../../runners/baloo/baloosearchrunner.cpp:99 #17 0x7f21ea5d13e9 in SearchRunner::match (this=0x693af80, context=...) at ../../../runners/baloo/baloosearchrunner.cpp:164 #18 0x7f2212e24590 in Plasma::AbstractRunner::performMatch (this=0x693af80, localContext=...) at ../../src/abstractrunner.cpp:131 #19 0x7f2212338d10 in ThreadWeaver::Executor::run (this=, job=..., thread=) at ../../src/executor.cpp:52 #20 0x7f2212337860 in ThreadWeaver::Job::execute (this=, self=..., th=0x76aed50) at ../../src/job.cpp:83 #21 0x7f221233730a in ThreadWeaver::Thread::run (this=0x76aed50) at ../../src/thread.cpp:114 #22 0x7f22c9f77a6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7f22c90636aa in start_thread (arg=0x7f21fcdaf700) at pthread_create.c:333 #24 0x7f22c988ce9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360494] Plasma Shell crashed unexpectedly after make a search on the application Launcher
https://bugs.kde.org/show_bug.cgi?id=360494 Marco Martin changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Marco Martin --- *** This bug has been marked as a duplicate of bug 360386 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 360386] Plasma crashes first time startup menu has been triggered
https://bugs.kde.org/show_bug.cgi?id=360386 Marco Martin changed: What|Removed |Added CC||alf...@gmail.com --- Comment #1 from Marco Martin --- *** Bug 360494 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 360517] Gwenview crashes when using image viewer and navigating to next image with arrowkey on keyboard
https://bugs.kde.org/show_bug.cgi?id=360517 --- Comment #1 from pandora...@gmail.com --- Created attachment 97893 --> https://bugs.kde.org/attachment.cgi?id=97893&action=edit New crash information added by DrKonqi gwenview (4.14.0 pre) on KDE Platform 4.14.17 using Qt 4.8.6 - What I was doing when the application crashed: Browsing in folder with images using arrow keys on keyboard. Image viewer using OpenGL -- Backtrace (Reduced): #6 0x7f9ff4257598 in Xapian::Database::get_document(unsigned int) const () at /usr/lib64/libxapian.so.22 #7 0x7f9ff40068a4 in Baloo::XapianDatabase::document(unsigned int) () at /usr/lib64/libbalooxapian.so.4 #8 0x7f9ffa41f2ed in Baloo::FileModifyJob::doStart() () at /usr/lib64/libbaloofiles.so.4 #9 0x7f9ffe95949e in QObject::event(QEvent*) () at /usr/lib64/libQtCore.so.4 #10 0x7f9ffcaee79c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 360517] Gwenview crashes when using image viewer and navigating to next image with arrowkey on keyboard
https://bugs.kde.org/show_bug.cgi?id=360517 pandora...@gmail.com changed: What|Removed |Added CC||pandora...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360521] New: Simple shortcut in rules window isn't transfered to the text field
https://bugs.kde.org/show_bug.cgi?id=360521 Bug ID: 360521 Summary: Simple shortcut in rules window isn't transfered to the text field Product: kwin Version: 5.5.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: rules Assignee: kwin-bugs-n...@kde.org Reporter: k...@privat.broulik.de When I configure a custom rule for a window in KWin I can set a shortcut in Geometry & Access -> "Shortcut"; in the Edit menu there's a text field with a "Simple Shortcut" button. When I click the button I get a dialog with a KShortcut widget, the shortcut isn't transfered to the text field in the parent dialog, however. Reproducible: Always Steps to Reproduce: 1. Right click window decoration -> More Actions -> Custom settings for this program/window 2. Go to the third tab "Geometry & Access" 3. Check "Shortcut" 4. Chose any of the settings in the combobox (eg. "Force") 5. Click "Edit" button next to the text field 6. Click "Simple Shortcut" in the resulting dialog 7. Click the "None" button in the resulting dialog 8. Press a key combination 9. Click "OK" Actual Results: The shortcut I just specified is not transfered to the text field in the parent dialog. I can enter something like Ctrl+Alt+B manually, however. Expected Results: The shortcut I just specified is transfered to the textfield Also note that the QDialogButtonBox is misplaced in the dialog, the OK/Cancel button is at the top rather than the bottom. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360491] Panel resets size, width, height when display resolution changes
https://bugs.kde.org/show_bug.cgi?id=360491 Marco Martin changed: What|Removed |Added CC||notm...@gmail.com --- Comment #1 from Marco Martin --- the panel sizes are saved per screen resolution, relative sizing is not supported nor can work. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 344675] No menu items are displayed for Plugins
https://bugs.kde.org/show_bug.cgi?id=344675 --- Comment #17 from Mike --- Because not everybody can compile the sources it would be good if the correct compiled package find it's way to the repos ;-) Thanks to all who spent their time and "grey matter" :-) Mike -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360445] Plasma shell crashes after initializing multi-screen desktop badly.
https://bugs.kde.org/show_bug.cgi?id=360445 Marco Martin changed: What|Removed |Added Resolution|--- |DUPLICATE CC||notm...@gmail.com Status|UNCONFIRMED |RESOLVED --- Comment #1 from Marco Martin --- *** This bug has been marked as a duplicate of bug 345723 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 360520] Can't import png and jpg
https://bugs.kde.org/show_bug.cgi?id=360520 Boudewijn Rempt changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO CC||b...@valdyas.org Resolution|--- |WAITINGFORINFO --- Comment #1 from Boudewijn Rempt --- Hi, Thank you for your report. I'm afraid though that this must be a local installation issue. How exactly did you install Krita? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 345723] Plasmashell crashes on panel removal notification timeout
https://bugs.kde.org/show_bug.cgi?id=345723 Marco Martin changed: What|Removed |Added CC||kenaa...@gmail.com --- Comment #7 from Marco Martin --- *** Bug 360445 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 360510] oxygen5-icon-theme error processing archive
https://bugs.kde.org/show_bug.cgi?id=360510 Mike C. Fletcher changed: What|Removed |Added CC||mcfle...@vrplumber.com --- Comment #1 from Mike C. Fletcher --- The error on the attached log indicates that both the oxygen5-icon-theme and libkdepim5 plugins are providing: /usr/share/icons/oxygen/256x256/mimetypes/x-mail-distribution-list.png This is seen on my (neon) machine as well. -- You are receiving this mail because: You are watching all bug changes.
[Planet KDE] [Bug 360522] New: Usability issue for planetkde.org
https://bugs.kde.org/show_bug.cgi?id=360522
Bug ID: 360522
Summary: Usability issue for planetkde.org
Product: Planet KDE
Version: unspecified
Platform: Other
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: ranveeraggar...@gmail.com
Reporter: brokenca...@gmail.com
There are currently no options built into the planetkde.org site that would
allow visually impaired users to use a dark theme. This can easily be achieved
with css to provide the choice for users to opt into a dark theme.
Fully-functional code (changing the background to dark grey) to provide this
feature is listed below the break ;
--
@namespace url(http://www.w3.org/1999/xhtml);
/*text&background*/
html,
body,
tbody,
thead,
th,
tr,
td,
blockquote,
li,
ul,
h1,
h2,
h3,
h4,
h5,
h6,
font,
strong,
p,
form,
footer {
color: white !important;
background: #272B30 !important;
}
select,
button {
background: #272B30 !important;
}
div,
span,
a {
background-color: #272B30 !important;
}
select,
input,
span,
code,
textarea,
pre,
label,
div,
dd,
option {
color: white !important;
}
/*links*/
a {
color: grey !important;
}
a:visited {
color: #224375 !important;
}
/*highlight*/
textarea,
pre,
input,
code {
background: grey !important;
}
--
Bug submission was requested after an enquiry to the PlanetKDE webmaster was
responded to by Albert Astals Cid.
--
You are receiving this mail because:
You are watching all bug changes.
[korganizer] [Bug 352043] Regression: kOrganizer 5 systray reminder module does not open main application window on click
https://bugs.kde.org/show_bug.cgi?id=352043 --- Comment #2 from Gunter Ohrner --- Yes, at least with the kOrganizer version I've installed - which is, as far as I know, the most recent precompiled version you can get for (K)Ubuntu: ii korganizer 4:15.08.3-0ubuntu1~ubuntu15.10~ppa1 amd64calendar and personal organizer No idea if there are more recent versions in source form which already fix this. -- You are receiving this mail because: You are watching all bug changes.
