[plasmashell] [Bug 356261] everything crashes on X session startup after Upgrading Fedora from 20 to 23
https://bugs.kde.org/show_bug.cgi?id=356261 kde@jks.tupari.net changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |UNCONFIRMED --- Comment #12 from kde@jks.tupari.net --- Attached stderr. There wasn't anything in stdout except "GOT SIGHUP" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356261] everything crashes on X session startup after Upgrading Fedora from 20 to 23
https://bugs.kde.org/show_bug.cgi?id=356261 kde@jks.tupari.net changed: What|Removed |Added Attachment #95888|0 |1 is obsolete|| --- Comment #11 from kde@jks.tupari.net --- Created attachment 95892 --> https://bugs.kde.org/attachment.cgi?id=95892=edit Stderr from startx -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 356266] New: Settings dialog not updated after project change
https://bugs.kde.org/show_bug.cgi?id=356266 Bug ID: 356266 Summary: Settings dialog not updated after project change Product: lokalize Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: project management Assignee: sha...@ukr.net Reporter: schwar...@kde.org If I have one project open and switch to another project with Project -> Open recent project -> [projectname] the settings dialog is still showing the old project's settings. Reproducible: Always Steps to Reproduce: 1. Open Lokalize (loading the last edited project) 2. Switch project Project -> Open recent project -> [projectname] 3. Open Settings dialog -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 355152] reassigning kde menu to ctrl+esc does not work
https://bugs.kde.org/show_bug.cgi?id=355152 --- Comment #3 from illumilore--- "Did you try to change that KRunner global shortcut, so that it is free for other purposes?" No -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 355676] Many plasmoids missing icon in panel
https://bugs.kde.org/show_bug.cgi?id=355676 --- Comment #3 from Antonio Rojas--- Ping, can this be merged before 5.17 tagging tomorrow? Otherwise Plasma 5.5 will not have any icons in the new widget explorer -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 152585] Dual screen presentation mode
https://bugs.kde.org/show_bug.cgi?id=152585 --- Comment #13 from Sumit Sahrawat--- That's a good suggestion, thanks :) -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 356230] Ugly icon in System Tray
https://bugs.kde.org/show_bug.cgi?id=356230 --- Comment #1 from Ondřej Kučera--- Created attachment 95876 --> https://bugs.kde.org/attachment.cgi?id=95876=edit System Tray icons screenshot -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 355275] kdelibs upgrade - Kopete crashes after closing a window
https://bugs.kde.org/show_bug.cgi?id=355275 Michal Hlavacchanged: What|Removed |Added CC||hla...@hlavki.eu -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356242] New: Aplication Launcher causes Plasma Shell to crash when searching or viewing history tab [QSQLiteDriver::QSQLiteDriver | QSQLiteDriverPlugin::create | QSqlDatabasePrivate
https://bugs.kde.org/show_bug.cgi?id=356242 Bug ID: 356242 Summary: Aplication Launcher causes Plasma Shell to crash when searching or viewing history tab [QSQLiteDriver::QSQLiteDriver | QSQLiteDriverPlugin::create | QSqlDatabasePrivate::init] Product: plasmashell Version: 5.4.95 Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: k...@pmc.com.pt CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.4.95) Qt Version: 5.5.1 Operating System: Linux 4.3.0-desktop-2.mga6 x86_64 Distribution: "Mageia 6" -- Information about the crash: - What I was doing when the application crashed: Aplication Launcher causes Plasma Shell to crash when searching or viewing history tab. - Steps To reproduce: 1) Click on the Application Launcher icon in the panel. 2) Click on the "Histórico" tab (probably "History" or "Historic" tab in english locale). Or 1) Click on the Application Launcher icon in the panel. 2) Click on the search ("Escreva para pesquisar..." in pt-PT locale, probably "Write to search..." or "Type to search" in english locale) and start typing something. That is it. The Plasma Shell will crash every time one the the above is done. - Unusual behavior I noticed: Plasma Shell crashes. - System/Version information $ uname -a Linux marte 4.3.0-desktop-2.mga6 #1 SMP Sun Nov 29 13:27:42 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux $ cat /etc/os-release NAME="Mageia" VERSION="6" ID=mageia VERSION_ID=6 ID_LIKE="mandriva fedora" PRETTY_NAME="Mageia 6" ANSI_COLOR="1;36" HOME_URL="http://www.mageia.org/; SUPPORT_URL="http://www.mageia.org/support/; BUG_REPORT_URL="https://bugs.mageia.org/; $ rpm -qa | grep -i -e 'sqlite\|kdelibs' | sort kdelibs4-core-4.14.13-2.mga6 kdelibs4support-5.16.0-4.mga6 lib64kf5kdelibs4support5-5.16.0-4.mga6 lib64sqlite3_0-3.9.2-1.mga6 libsqlite3_0-3.9.2-1.mga6 qt4-database-plugin-sqlite-4.8.6-9.mga5 qtbase5-database-plugin-sqlite-5.4.0-7.mga5 sqlite3-tools-3.9.2-1.mga6 The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe6c8a0f800 (LWP 3369))] Thread 17 (Thread 0x7fe6ad31e700 (LWP 3372)): #0 0x7fe6c3161d4d in poll () at /lib64/libc.so.6 #1 0x7fe6c71d7ac2 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x7fe6c71d9697 in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7fe6af84dcc9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x7fe6c384c01f in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7fe6c295e65d in start_thread () at /lib64/libpthread.so.0 #6 0x7fe6c316dbbd in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7fe6a6635700 (LWP 3380)): #0 0x7fe6c03cb3ea in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #1 0x7fe6c03cb50c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #2 0x7fe6c3a6f92b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #3 0x7fe6c3a1980a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7fe6c38471bc in QThread::exec() () at /lib64/libQt5Core.so.5 #5 0x7fe6c60b3cd5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #6 0x7fe6c384c01f in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7fe6c295e65d in start_thread () at /lib64/libpthread.so.0 #8 0x7fe6c316dbbd in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7fe69ed10700 (LWP 3385)): #0 0x7fe6c315d65d in read () at /lib64/libc.so.6 #1 0x7fe6c040d750 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #2 0x7fe6c03caf34 in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7fe6c03cb3a8 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7fe6c03cb50c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7fe6c3a6f92b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7fe6c3a1980a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7fe6c38471bc in QThread::exec() () at /lib64/libQt5Core.so.5 #8 0x7fe6c60b3cd5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #9 0x7fe6c384c01f in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #10 0x7fe6c295e65d in start_thread () at /lib64/libpthread.so.0 #11 0x7fe6c316dbbd in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7fe69d4bc700 (LWP 3393)): #0 0x7fe6c03caa46 in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #1 0x7fe6c03cb333 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7fe6c03cb50c in
[okular] [Bug 354894] allow any graphic/symbol as stamp annotation
https://bugs.kde.org/show_bug.cgi?id=354894 Alexander Noltingchanged: What|Removed |Added CC||a.nolt...@almano.de --- Comment #1 from Alexander Nolting --- I would find creating stamp based on usual image formats also very useful. Aside from the PDF Form Barcode specification for adding a barcode into a PDF form using JavaScript I have from time to time the need to a barcode into a pdf file. This would easily done if I could create a stamp based on an image. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 355787] KDE5 (Plasma 5) returns black screen afeter xorg-server updated to 1.18
https://bugs.kde.org/show_bug.cgi?id=355787 --- Comment #14 from SinClaus--- Pleas read by characters: Comp with KDE4, same Nvidia driver and new Xorg works without problems. -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 353857] comments not visible when opening file
https://bugs.kde.org/show_bug.cgi?id=353857 --- Comment #31 from luo0...@students.nossalhs.vic.edu.au --- (In reply to Camilla Boemann from comment #30) > yes - both Calligra/2.9 and master branches have the fix > > so if you check either of those branches out the fix will be there - Just > note that building requires quite a number of dependencies to build and that > master depends on qt5/kf5 now Back to report! The comment in the one comment file is now visible when opened in the Calligra Words master build (Wow! Smooth scrolling!). However, attempting to open my fanfiction (ODT version) resulted in it crashing, with a similar error as before. This is probably just due to the exorbitant amount of comments in it. Should I open another bug? I'll post the error underneath anyway, just in case. Application: Calligra Words (calligrawords), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f322ad96840 (LWP 22431))] Thread 2 (Thread 0x7f3212bd6700 (LWP 22432)): #0 0x7f34f18d in poll () from /usr/lib/libc.so.6 #1 0x7f321b45bae2 in ?? () from /usr/lib/libxcb.so.1 #2 0x7f321b45d757 in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7f3213a88e89 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #4 0x7f3222e6496e in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f321f50c4a4 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f35813d in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7f322ad96840 (LWP 22431)): [KCrash Handler] #5 0x7f32236858ce in QTextLine::y() const () from /usr/lib/libQt5Gui.so.5 #6 0x7f322a1682f8 in KoTextDocumentLayout::positionAnchorTextRanges (this=0x2be6a90, pos=17644, length=95, effectiveDocument=0x2cdc3a0) at /home/chromace/kde/src/calligra/libs/textlayout/KoTextDocumentLayout.cpp:620 #7 0x7f322a13ea36 in KoTextLayoutArea::layoutBlock (this=0x34323e0, cursor=0x1394830) at /home/chromace/kde/src/calligra/libs/textlayout/KoTextLayoutArea.cpp:1261 #8 0x7f322a13b13b in KoTextLayoutArea::layout (this=0x34323e0, cursor=0x1394830) at /home/chromace/kde/src/calligra/libs/textlayout/KoTextLayoutArea.cpp:598 #9 0x7f322a1661c7 in KoTextLayoutRootArea::layoutRoot (this=0x34323e0, cursor=0x1394830) at /home/chromace/kde/src/calligra/libs/textlayout/KoTextLayoutRootArea.cpp:69 #10 0x7f322a169201 in KoTextDocumentLayout::doLayout (this=0x2be6a90) at /home/chromace/kde/src/calligra/libs/textlayout/KoTextDocumentLayout.cpp:820 #11 0x7f322a168856 in KoTextDocumentLayout::layout (this=0x2be6a90) at /home/chromace/kde/src/calligra/libs/textlayout/KoTextDocumentLayout.cpp:703 #12 0x7f322a1699d6 in KoTextDocumentLayout::executeScheduledLayout (this=0x2be6a90) at /home/chromace/kde/src/calligra/libs/textlayout/KoTextDocumentLayout.cpp:911 #13 0x7f322a18dd7a in KoTextDocumentLayout::qt_static_metacall (_o=0x2be6a90, _c=QMetaObject::InvokeMetaMethod, _id=7, _a=0x1452300) at /home/chromace/kde/build/calligra/libs/textlayout/moc_KoTextDocumentLayout.cpp:109 #14 0x7f3223074ff1 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #15 0x7f3223ffc01c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #16 0x7f32240014f6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #17 0x7f322a78f78f in KoApplication::notify (this=0x7fff7beb7f70, receiver=0x2be6a90, event=0x2a83ab0) at /home/chromace/kde/src/calligra/libs/main/KoApplication.cpp:626 #18 0x7f32230459ab in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #19 0x7f3223047da6 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQt5Core.so.5 #20 0x7f322309bf43 in ?? () from /usr/lib/libQt5Core.so.5 #21 0x7f321d79bdc7 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #22 0x7f321d79c020 in ?? () from /usr/lib/libglib-2.0.so.0 #23 0x7f321d79c0cc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #24 0x7f322309c34f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #25 0x7f32283331f8 in KoProgressUpdater::update (this=0x1432ff0) at /home/chromace/kde/src/calligra/libs/widgetutils/KoProgressUpdater.cpp:166 #26 0x7f322833e25a in KoProgressUpdater::qt_static_metacall (_o=0x1432ff0, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fff7beb6060) at /home/chromace/kde/build/calligra/libs/widgetutils/moc_KoProgressUpdater.cpp:72 #27 0x7f322307412a in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #28 0x7f322833e911 in KoUpdaterPrivate::sigUpdated (this=0x280ed10) at /home/chromace/kde/build/calligra/libs/widgetutils/moc_KoUpdaterPrivate_p.cpp:152 #29 0x7f32283367af in KoUpdaterPrivate::setProgress (this=0x280ed10, percent=100) at /home/chromace/kde/src/calligra/libs/widgetutils/KoUpdaterPrivate_p.cpp:45 #30 0x7f322833e733 in
[frameworks-kactivities] [Bug 356242] Aplication Launcher causes Plasma Shell to crash when searching or viewing history tab [QSQLiteDriver::QSQLiteDriver | QSQLiteDriverPlugin::create | QSqlDatabaseP
https://bugs.kde.org/show_bug.cgi?id=356242 Marco Martinchanged: What|Removed |Added Product|plasmashell |frameworks-kactivities Component|general |libkactivitiesstats Assignee|k...@davidedmundson.co.uk|ivan.cu...@kde.org CC||notm...@gmail.com Version|5.4.95 |unspecified Target Milestone|1.0 |--- -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 356243] New: Cannot login to Google account and account settings are not remembered
https://bugs.kde.org/show_bug.cgi?id=356243 Bug ID: 356243 Summary: Cannot login to Google account and account settings are not remembered Product: telepathy Version: 0.9.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: auth-handler Assignee: kde-telepathy-b...@kde.org Reporter: stu...@anchev.net Not sure how to check version as this is not working but the system is openSUSE Leap 42.1 with Plasma 5.4.3 Also /usr/share/doc/packages/telepathy-gabble/ChangeLog shows: commit f10f557fd67ec11738670828a553496960c0d411 Author: Guillaume DesmottesDate: 2014-05-07 16:33:17 +0200 0.18.2 The package version in YaST is 0.9.0-2.2 Reproducible: Always Steps to Reproduce: 1. Open System Settings > Online Accounts 2. Add new Jabber account with credentials the Gmail account and password 3. Click Advanced and enter: Server address: talk.google.com Sever port: 5223 Require encrypted connection - checked (but even without checked still can't connect) 4. Click OK and try to connect 5. After a while the login prompt dialog appears and asks again for password. Give it the password. Actual Results: It can never connect/authorize. Please see the journal log for details. Additionally when going to System Settings > Online Accounts > this same account > Configure - the login credentials are not remembered as well as server settings. Expected Results: Successful connection and remembering of login credentials. journalctl -f shows: Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]: New job started. 1 jobs currently running Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]: Unknown signature value: 795 Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]: Unknown signature value: 795 Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]: Unknown signature value: 795 Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]: Unknown signature value: 795 Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]: Unknown signature value: 7 Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]: Unknown signature value: 795 Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]: Unknown signature value: 795 Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]: Unknown signature value: 794 Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]: Unknown signature value: 795 Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]: Unknown signature value: 795 Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]: Unknown signature value: 795 Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]: No other jobs at the moment. Starting timer. Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]: Job finished. 0 jobs currently running Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]: New job started. 1 jobs currently running Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]: 0 Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]: ("X-OAUTH2", "X-GOOGLE-TOKEN", "PLAIN", "X-TELEPATHY-PASSWORD") Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]: Starting X-OAuth2 auth Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]: Status Not started Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]: (process:4639): accounts-glib-CRITICAL **: ag_manager_load_account: assertion 'account_id != 0' failed Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]: (process:4639): GLib-CRITICAL **: g_error_free: assertion 'error != NULL' failed Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]: Unable to find account for id 0 Dec 03 14:26:46 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]: Retrying in 2s Dec 03 14:26:48 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]: (process:4639): accounts-glib-CRITICAL **: ag_manager_load_account: assertion 'account_id != 0' failed Dec 03 14:26:48 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]: (process:4639): GLib-CRITICAL **: g_error_free: assertion 'error != NULL' failed Dec 03 14:26:48 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]: Unable to find account for id 0 Dec 03 14:26:48 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]: Retrying in 2s Dec 03 14:26:50 i7 org.freedesktop.Telepathy.Client.KTp.TLSHandler[1980]: (process:4639): accounts-glib-CRITICAL **: ag_manager_load_account: assertion 'account_id != 0' failed Dec 03 14:26:50 i7
[kwin] [Bug 356238] New: focus desktop shows remnants of windows in the corners
https://bugs.kde.org/show_bug.cgi?id=356238 Bug ID: 356238 Summary: focus desktop shows remnants of windows in the corners Product: kwin Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: bjou...@gmail.com I've bound M-d to kwin's focus desktop. When I press it I get remnants of the minimized windows in all the four screen corners. First I thought it was a gfx driver issue, but I've verified it on both Intel and Radeon cards with KDE 5. I've also tried changing the compositing backend but it doesn't change anything. Perhaps it is intentional, if so could you add an option to disable it? Because the effect doesn't look good and IMHO more like a graphics bug. Screenshot coming up. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356205] Applications are minimized and Windows decorations disappear after monitor turned off
https://bugs.kde.org/show_bug.cgi?id=356205 Marco Martinchanged: What|Removed |Added CC||notm...@gmail.com --- Comment #1 from Marco Martin --- kwin crashing? do you get any crash dialogs for kwin_x11? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 356241] New: Python indenter should not keep indentation level following complete class/function definitions with blank lines in between
https://bugs.kde.org/show_bug.cgi?id=356241 Bug ID: 356241 Summary: Python indenter should not keep indentation level following complete class/function definitions with blank lines in between Product: kate Version: unspecified Platform: Ubuntu Packages URL: http://pastebin.com/v7rUJZTJ OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: indentation Assignee: kwrite-bugs-n...@kde.org Reporter: thomaskola...@gmail.com At the moment, creating a new line anywhere in a python script where the last non-blank line is indented (and not a dedenter) will always indent that line to the previous indentation level. While this may have been indented (as was this pun), it is VERY annoying for editing files with many small class definitions. Not all code blocks have a natural dedenter; and as a matter of fact, if one follows pep8, most of the time, if there is more than one blank line between two lines, the second line will not be indented at all. See also: https://www.python.org/dev/peps/pep-0008/#blank-lines In this light, assuming that the user wants to continue at the same indentation level as a block many lines previous is likely a bug. Reproducible: Always Steps to Reproduce: 1. Open a new file, save as a python script 2. Enter the following: """ class Example(object): def example_method(self) self.mutate() # no return required """ 3. With the cursor on the last line, type Actual Results: two levels of indentation are inserted Expected Results: insert no indentation, that method is too far away I like Kate a lot and have been using it for years, it's my go-to editor when I have multiple files that i switch between a lot, but this is seriously annoying me, and I can't imagine that most people find this behaviour more useful than annoying. I crudely patched my own indenter and linked the diff, however, I can imagine that there are probably better solutions (my patch checks if the two previous lines are completely empty). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356238] focus desktop shows remnants of windows in the corners
https://bugs.kde.org/show_bug.cgi?id=356238 --- Comment #1 from Björn Lindqvist--- Created attachment 95878 --> https://bugs.kde.org/attachment.cgi?id=95878=edit screenie top left you see dolphin, top right you see konsole -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356238] focus desktop shows remnants of windows in the corners
https://bugs.kde.org/show_bug.cgi?id=356238 Martin Gräßlinchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #2 from Martin Gräßlin --- This is indeed expected behavior. You can disable this effect by disabling the "Window Aperture" effect in systemsettings. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356175] [wayland] plasmashell crashes at startup
https://bugs.kde.org/show_bug.cgi?id=356175 --- Comment #2 from Martin Gräßlin--- Do you have the abort message Qt prints? -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 332161] Add support for identifiers with special characters or equal to reserved words in queries
https://bugs.kde.org/show_bug.cgi?id=332161 Jarosław Staniekchanged: What|Removed |Added Summary|Identifiers equal to a |Add support for identifiers |reserved word not supported |with special characters or |in queries |equal to reserved words in ||queries -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 356240] New: lambda args by ref
https://bugs.kde.org/show_bug.cgi?id=356240 Bug ID: 356240 Summary: lambda args by ref Product: clazy Version: unspecified Platform: Other OS: other Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: eric.lemaniss...@gmail.com CC: smart...@kde.org A new check could be added to check arguments passing to lambda, the same way it is already done for functions when using -Wclazy-function-args-by-ref Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356238] focus desktop shows remnants of windows in the corners
https://bugs.kde.org/show_bug.cgi?id=356238 --- Comment #3 from Björn Lindqvist--- Oh I see, so dupe of #347281 then. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 356093] Kmail does not display PGP/Inline signed mails
https://bugs.kde.org/show_bug.cgi?id=356093 Marcus Behrendtchanged: What|Removed |Added Component|composer|general -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 356181] systemtray applet ConfigEntries failed to save Configuration
https://bugs.kde.org/show_bug.cgi?id=356181 --- Comment #5 from Marco Martin--- since the patch is specific for 5.4 that probably won't have new releases, you can send the patch to kde-packag...@kde.org for distributions that can consider to pick up the patch in their 5.4 packages -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 356237] New: Unable to change icon associated with mimetype if ~/.local/share/mime/packages does not already exist.
https://bugs.kde.org/show_bug.cgi?id=356237 Bug ID: 356237 Summary: Unable to change icon associated with mimetype if ~/.local/share/mime/packages does not already exist. Product: systemsettings Version: 5.4.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_filetypes Assignee: fa...@kde.org Reporter: pip@gmx.com openSUSE Tumbleweed (20151128) / KDE Frameworks 5.16.0 / System Settings 5.4.3 Attempting to change the icon associated with a mimetype (System Settings -> Applications -> File Associations) fails to work if the subdirectory "~/.local/share/mime/packages" does not already exist. Within system settings it gives the appearance of having worked, however having closed System Settings the icon is unchanged when viewing a directory listing using Dolphin, and if one again uses System Settings it shows the original icon. This section of ".xsession-errors-:0" gave the clue... m_userSpecifiedIcon has changed. Now set to "text-rdf+xml" Entry "application/rdf+xml" is dirty. Saving. m_userSpecifiedIcon has changed. Now set to "text-rdf+xml" writing "/home/paul/.local/share/mime/packages/application-rdf+xml.xml" Couldn't open "/home/paul/.local/share/mime/packages/application-rdf+xml.xml" for writing "application/rdf+xml" hasDefinitionFile: false Specifically, the "Couldn't open..." - The subdirectory didn't exist. Having manually created ~/.local/share/mime/packages changing the icon worked correctly. I have 3 users on that particular machine, none of whom had a "~/.local/share/mime/*" subdirectory. Interestingly, System Settings was able to create an additional subdirectory, "~/.local/share/mime/application". I tried again with one of the other users, initally just creating "~/.local/share/mime" - which failed, it had to be "~/.local/share/mime/packages". So it seems that System Settings expects that subdirectory to "just be there", and does not create it if missing. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356199] plasma crashes when starting KDE
https://bugs.kde.org/show_bug.cgi?id=356199 Marco Martinchanged: What|Removed |Added CC||notm...@gmail.com Status|UNCONFIRMED |NEEDSINFO Resolution|--- |BACKTRACE --- Comment #1 from Marco Martin --- debug symbols of Qt seems to be missing, the bt doesn't tell much -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356175] [wayland] plasmashell crashes at startup
https://bugs.kde.org/show_bug.cgi?id=356175 Marco Martinchanged: What|Removed |Added CC||mgraess...@kde.org, ||notm...@gmail.com --- Comment #1 from Marco Martin --- maybe it's trying to render on a surface not created yet? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356190] scripts in $HOME/.config/plasma-workspace/shutdown not executed at full shutdown
https://bugs.kde.org/show_bug.cgi?id=356190 Marco Martinchanged: What|Removed |Added CC||notm...@gmail.com --- Comment #1 from Marco Martin --- ksmserver issue? -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 356218] Won't play files with filenames that contain '#' (pound sign, hash)
https://bugs.kde.org/show_bug.cgi?id=356218 Harald Sitterchanged: What|Removed |Added Product|dragonplayer|Phonon CC||romain.per...@gmail.com Component|general |general -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 355787] KDE5 (Plasma 5) returns black screen afeter xorg-server updated to 1.18
https://bugs.kde.org/show_bug.cgi?id=355787 Thomas Lübkingchanged: What|Removed |Added Resolution|WONTFIX |DOWNSTREAM --- Comment #13 from Thomas Lübking --- I mean this: > Boot was stopped on "Reached target Graphical Interface". Xorg can't find > display driver, but don't try to load nvidia driver. It means that you fail to start X11 (because lacking a compatible display driver) - this has *nothing* (repeat after me: not a thing) to do with KDE. Not with KDE4 nor with KDE5. Not with Qt and not with SDDM or KDM or whatever. It means that you need to install a compatible display driver. Nouveau (and likely VESA) will require kms, while nvidia will require kms to be disabled. Once you have trouble *after* reaching the X11 layer, they *may* be related to KWin/KF5/Qt (or the driver), but until then, there's nothing we could do and certainly no (kwin) bug. -- You are receiving this mail because: You are watching all bug changes.
[kexi] [Bug 332161] Identifiers equal to a reserved word not supported in queries
https://bugs.kde.org/show_bug.cgi?id=332161 --- Comment #3 from Jarosław Staniek--- My conclusion. One requirement is to keep *format* compatibility with [] notation for query parameters. Another "nice to have" requirement is to avoid (I think) a bad practice of MSA, which treats undefined identifiers as query parameters. This is both confusing and error-prone practice, which once introduced, is hard to fix (so MSA is in a trap somehow here). Based on that: By format I mean representation of a query stored in Kexi projects. (note: it's represented in KEXISQL / KDBSQL format, normalized subset of SQL) Proposed solution is to introduce an internal format transparently: - in the format use [ ] for query parameters as before, so no change for Kexi <= 2.x - in the format use ` ` ("grave accent" quotes) for escaping identifiers - in the Kexi GUI use [[ ]] for query parameters, this is a change compared to Kexi <= 2.x - in the Kexi GUI use [ ] for escaping identifiers (Like in MSA) By 'internal' we mean that end-users never see queries in this format unless they read debug information of KDb. The above means that when saving user-supplied SQL (or fragments of it) to KEXISQL format, following conversions should be made: - [ ] to ` ` - [[ ]] to [ ] Similarly, opposite conversion is needed while reading stored SQL to the KEXISQL format. Conversions are deterministic, do not require complex parsing, we're not loosing any information. Update for the notations ([[ ]] and [ ]) used by Kexi GUI should be made by modification in the KEXISQL / KDBSQL parser. Conversions should happen in KDb's routines where KDbQuerySchema instances are stored/retrieved. The routines can be exposed in KDb's Utils API for engineers who wish to use the internal format. Extras: - '[', ']', ` characters should be escaped as \[, \], respectively, if they exist inside of [ ] or [[ ]] - ` characters should be escaped as \` respectively if they exist inside of ` ` -- You are receiving this mail because: You are watching all bug changes.
[parley] [Bug 356233] New: File is not writeable when creating a new collection
https://bugs.kde.org/show_bug.cgi?id=356233 Bug ID: 356233 Summary: File is not writeable when creating a new collection Product: parley Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: editor Assignee: parley-bugs-n...@kde.org Reporter: dimk...@gmail.com I managed to bypass the crash of https://bugs.kde.org/show_bug.cgi?id=356104 which prevents new collection functionality from being initiated, by moving /usr/share/parley/plugins/google_images.desktop to /usr/share/parley/plugins/google_images.desktop.bak. When I try to save my dummy collection somewhere in my home folder, I get the following in command line: "Cannot write to file file:///home/dimitric/test_collection.kvtml" SaveAs failed for "Untitled" why "File is not writeable." and a ...File is not writeable pop up error. Reproducible: Always Steps to Reproduce: 1.Move or delete /usr/share/parley/plugins/google_images.desktop 2.Open Parley 3.Click "Create a New Collection" 4.Select any language pair (E.g. English - English), 5. Add a dummy pair 6. Try to save Actual Results: File is not writeable popup error Expected Results: Collection to be saved -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 356124] Problem when start Skanlite and take a photo
https://bugs.kde.org/show_bug.cgi?id=356124 --- Comment #12 from David--- Hi Kare Sars, This afternoon I will try your solution (thanks very much!). This morning I tried Kubuntu 14.04.03 from LiveCD (no installation). In that release of Kubuntu, you can find only Skanlite. I tried Skanlite to take a photo and the result was excellent! No red/blue/orange pixels of image. After I installed digiKam: in the KDE-menù->Graphics you can find Skanlite and AcquireImages (in Italian: "Acquisizioni di immagini"). So I tried to take a photo with Skanlite and the result was incorrect (the same problem I wrote at the beginning of this discussion). Then I tried to take a photo with AcquireImages and the result was great (like Skanlite without digiKam). Maybe it is a conflict between Skanlite and digiKam+AcquireImages. Is it possible? (Excuse me for my low-level English!) Thanks for your help! Have a great day! :) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 356231] New: Build not respecting "ranlib" and "ar" binaries
https://bugs.kde.org/show_bug.cgi?id=356231 Bug ID: 356231 Summary: Build not respecting "ranlib" and "ar" binaries Product: kdevelop Version: git master Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: arkang...@gmail.com I'm not 100% certain this is an issue with KDevelop/KDevPlatform, but I don't know where else to look. I built everything git-head (including clang) with -flto under GCC 4.9.3. Just because - I'm just that silly. Clang builds and works fine. I then build KDevPlatform with the same configurations, but it failed to link with numerous linking errors. Those errors started after "ar" and "ranlib" failed to run because the objects being archived (or in the archive) do not have object code, only GIMPLE intermediate (due to -flto). The correct way of using LTO with those flags is to provide -plugin /path/to/libLTO.so OR use gcc-ar and gcc-ranlib. I opted for the second solution on clang, kdevplat and kdev CCMake configurations by adjusting CMAKE_AR and CMAKE_RANLIB. However, the build of KDevelop and KDevPlatform insist on using /usr/bin/ar and /usr/bin/ranlib instead of the CMake configured binary. On the plus side, if I make ar and ranlib shell scripts that call their corresponding "real" binaries with the -plugin option, KDev builds and works fine. Woo-hoo! Ultimately, whether Clang is built with flto is irrelevant. The issue is that the KDev components do not use the ar and ranlibs configured through CMake. I don't know where I should continue my investigation - I found no hard-coded "ranlib" binaries on either the source tree or the configured directory, which is why I suspect this problem comes from somewhere else. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356209] Copying Effects messes up parameters (Fade from black + Fade in)
https://bugs.kde.org/show_bug.cgi?id=356209 qubo...@gmail.com changed: What|Removed |Added Summary|Copying Effects messes up |Copying Effects messes up |parameters (Fade|parameters (Fade from black ||+ Fade in) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 353401] Feature requst: "typewriter" annotation tool
https://bugs.kde.org/show_bug.cgi?id=353401 --- Comment #11 from Sumit Sahrawat--- I looked through the poppler source once again. I realized that even though the freeText annotation is implemented internally, the poppler-qt4 package doesn't export it. Specifically, the Annotation class from poppler-qt4 has a SubType enumeration, which contains only 15 values. The Annot class from poppler has an AnnotSubtype enumeration, which contains 27 values. FreeText is one of the values in poppler but not in poppler-qt4. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 344969] Shortcut configuration for Folder View actions not handled by standard keys
https://bugs.kde.org/show_bug.cgi?id=344969 --- Comment #17 from Leslie Zhai--- please have a look at https://git.reviewboard.kde.org/r/126238/ thanks a lot ;-) -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 355945] Lancelot crash when trying to add a program to favourites
https://bugs.kde.org/show_bug.cgi?id=355945 Christoph Feckchanged: What|Removed |Added Product|kde |plasma4 Assignee|unassigned-b...@kde.org |ivan.cu...@kde.org Component|general |widget-lancelot -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 355787] KDE5 (Plasma 5) returns black screen afeter xorg-server updated to 1.18
https://bugs.kde.org/show_bug.cgi?id=355787 --- Comment #15 from Thomas Lübking--- You *clearly* stated: > Xorg can't find display driver, but don't try to load nvidia driver. If X doesn't find a usable display driver, it won't start. And that is *certainly* NOT related to the session that you're about to start *after* the X server started. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 356013] kdeinit crashed when using menu
https://bugs.kde.org/show_bug.cgi?id=356013 Christoph Feckchanged: What|Removed |Added Product|kde |ksmserver Component|general |general Assignee|unassigned-b...@kde.org |l.lu...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 355961] Desktop Crash (Desktop Configuration)
https://bugs.kde.org/show_bug.cgi?id=355961 Christoph Feckchanged: What|Removed |Added Product|kde |plasma4 Component|general |general Assignee|unassigned-b...@kde.org |plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 355232] Krunner crash at each login, after upgrade to Kubuntu 15.10
https://bugs.kde.org/show_bug.cgi?id=355232 Florianchanged: What|Removed |Added CC||floesc...@gmx.net --- Comment #1 from Florian --- Created attachment 95880 --> https://bugs.kde.org/attachment.cgi?id=95880=edit krunner crash report +1 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 353607] Akregator crashes upon start
https://bugs.kde.org/show_bug.cgi?id=353607 Christoph Feckchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 116482 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 354738] dbus interface not valid
https://bugs.kde.org/show_bug.cgi?id=354738 --- Comment #9 from Vit Pelcak--- After recent update of kde-connect I can confirm everything works as expected. I think you can close this bug. Thank you for your work. It is amazing and I really appreciate it. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 355826] Fall on changing window decoration
https://bugs.kde.org/show_bug.cgi?id=355826 Christoph Feckchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 345675 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 353825] Login by x2go in Plasma 5 crashes KCMInit
https://bugs.kde.org/show_bug.cgi?id=353825 Christoph Feckchanged: What|Removed |Added CC||lawrence.lafran...@gmail.co ||m --- Comment #7 from Christoph Feck --- *** Bug 355940 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 356247] New: [Feature Request Krita Animation] There is no simple way to import image sequences.
https://bugs.kde.org/show_bug.cgi?id=356247 Bug ID: 356247 Summary: [Feature Request Krita Animation] There is no simple way to import image sequences. Product: krita Version: 2.9.9 Platform: Other OS: All Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: dimim...@gmail.com Importing image sequences as an animated layer should be a no brainer. To fully use Krita as an animation tool it should be possible to import videos or image sequences. It's critical for most animation works to be able to import line tests or video references, whether it's for animating, doing clean up or painting frames. Right now rotoscoping, a pretty standard and basic animation technique, is impossible to do in Krita. Importing footage is an essential option of any animation software Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 347281] Window aperture effect should (optionally) not leave windows visible in the corners
https://bugs.kde.org/show_bug.cgi?id=347281 Thomas Lübkingchanged: What|Removed |Added CC||bjou...@gmail.com --- Comment #6 from Thomas Lübking --- *** Bug 356238 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356238] focus desktop shows remnants of windows in the corners
https://bugs.kde.org/show_bug.cgi?id=356238 Thomas Lübkingchanged: What|Removed |Added Resolution|INVALID |DUPLICATE --- Comment #4 from Thomas Lübking --- *** This bug has been marked as a duplicate of bug 347281 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 356038] crash if I close the systemsettings window
https://bugs.kde.org/show_bug.cgi?id=356038 Christoph Feckchanged: What|Removed |Added CC||cf...@kde.org Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Christoph Feck --- Error is "Could not initialize GLX". Please make sure X11 drivers for OpenGL 2 (or newer) are installed correctly. If unsure, ask in a forum of your distribution for help. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 344599] Thumbnails sidebar always open when okular starts
https://bugs.kde.org/show_bug.cgi?id=344599 Sumit Sahrawatchanged: What|Removed |Added CC||sumit.sahrawat.apm13@iitbhu ||.ac.in --- Comment #1 from Sumit Sahrawat --- Looks like this has been fixed. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 355613] Opening Window Decorations causes crash
https://bugs.kde.org/show_bug.cgi?id=355613 Christoph Feckchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 344278 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 356120] Crash when hovering or selecting any .h file
https://bugs.kde.org/show_bug.cgi?id=356120 Christoph Feckchanged: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=349295 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 356246] Kate spins endlessly doing getcwd()
https://bugs.kde.org/show_bug.cgi?id=356246 --- Comment #3 from jm.ouwerk...@gmail.com --- As you can see it appears that each call to i18n () is repeated a number of times. Playing a bit further it seems this factor is exactly 4 on my machine, which coincidentally is exactly the number of CPU cores/threads: continue Continuing. Breakpoint 2, __getcwd (buf=buf@entry=0x7fffb0c0 "yE|", size=size@entry=4098) at ../sysdeps/unix/sysv/linux/getcwd.c:47 47 in ../sysdeps/unix/sysv/linux/getcwd.c (gdb) bt #0 __getcwd (buf=buf@entry=0x7fffb0c0 "yE|", size=size@entry=4098) at ../sysdeps/unix/sysv/linux/getcwd.c:47 #1 0x71f711d7 in __dcigettext (domainname=0x7c3f58 "kate", msgid1=0x7c3078 "(c) 2000-2015 The Kate Authors", msgid2=0x0, plural=0, n=0, category=5) at dcigettext.c:640 #2 0x756f87f7 in KCatalog::translate (this=0x7d0200, msgid=...) at /home/prometheus/projects/kde/src/frameworks/ki18n/src/kcatalog.cpp:192 #3 0x756e75ed in KLocalizedStringPrivate::translateRaw (domain=..., languages=..., msgctxt=..., msgid=..., msgid_plural=..., n=0, language=..., msgstr=...) at /home/prometheus/projects/kde/src/frameworks/ki18n/src/klocalizedstring.cpp:434 #4 0x756e7c65 in KLocalizedStringPrivate::toString (this=0x7beb30, domain=..., languages=..., format=Kuit::UndefinedFormat, isArgument=false) at /home/prometheus/projects/kde/src/frameworks/ki18n/src/klocalizedstring.cpp:507 #5 0x756e771f in KLocalizedString::toString (this=0x7fffc7e0) at /home/prometheus/projects/kde/src/frameworks/ki18n/src/klocalizedstring.cpp:447 #6 0x0048447b in i18n(char const*) () #7 0x0047ed60 in main () (gdb) continue Continuing. Breakpoint 2, __getcwd (buf=buf@entry=0x7fffb0c0 "/home/prometheus/projects/kde/kde-5/bin/", size=size@entry=4098) at ../sysdeps/unix/sysv/linux/getcwd.c:47 47 in ../sysdeps/unix/sysv/linux/getcwd.c (gdb) bt #0 __getcwd (buf=buf@entry=0x7fffb0c0 "/home/prometheus/projects/kde/kde-5/bin/", size=size@entry=4098) at ../sysdeps/unix/sysv/linux/getcwd.c:47 #1 0x71f711d7 in __dcigettext (domainname=0x7c3f58 "kate", msgid1=0x7c3078 "(c) 2000-2015 The Kate Authors", msgid2=0x0, plural=0, n=0, category=5) at dcigettext.c:640 #2 0x756f87f7 in KCatalog::translate (this=0x7bd260, msgid=...) at /home/prometheus/projects/kde/src/frameworks/ki18n/src/kcatalog.cpp:192 #3 0x756e75ed in KLocalizedStringPrivate::translateRaw (domain=..., languages=..., msgctxt=..., msgid=..., msgid_plural=..., n=0, language=..., msgstr=...) at /home/prometheus/projects/kde/src/frameworks/ki18n/src/klocalizedstring.cpp:434 #4 0x756e7c65 in KLocalizedStringPrivate::toString (this=0x7beb30, domain=..., languages=..., format=Kuit::UndefinedFormat, isArgument=false) at /home/prometheus/projects/kde/src/frameworks/ki18n/src/klocalizedstring.cpp:507 #5 0x756e771f in KLocalizedString::toString (this=0x7fffc7e0) at /home/prometheus/projects/kde/src/frameworks/ki18n/src/klocalizedstring.cpp:447 #6 0x0048447b in i18n(char const*) () #7 0x0047ed60 in main () (gdb) continue Continuing. Breakpoint 2, __getcwd (buf=buf@entry=0x7fffb0c0 "/home/prometheus/projects/kde/kde-5/bin/", size=size@entry=4098) at ../sysdeps/unix/sysv/linux/getcwd.c:47 47 in ../sysdeps/unix/sysv/linux/getcwd.c (gdb) bt #0 __getcwd (buf=buf@entry=0x7fffb0c0 "/home/prometheus/projects/kde/kde-5/bin/", size=size@entry=4098) at ../sysdeps/unix/sysv/linux/getcwd.c:47 #1 0x71f711d7 in __dcigettext (domainname=0x7c3f58 "kate", msgid1=0x7c3078 "(c) 2000-2015 The Kate Authors", msgid2=0x0, plural=0, n=0, category=5) at dcigettext.c:640 #2 0x756f87f7 in KCatalog::translate (this=0x7d0200, msgid=...) at /home/prometheus/projects/kde/src/frameworks/ki18n/src/kcatalog.cpp:192 #3 0x756e75ed in KLocalizedStringPrivate::translateRaw (domain=..., languages=..., msgctxt=..., msgid=..., msgid_plural=..., n=0, language=..., msgstr=...) at /home/prometheus/projects/kde/src/frameworks/ki18n/src/klocalizedstring.cpp:434 #4 0x756e7c65 in KLocalizedStringPrivate::toString (this=0x7beb30, domain=..., languages=..., format=Kuit::UndefinedFormat, isArgument=false) at /home/prometheus/projects/kde/src/frameworks/ki18n/src/klocalizedstring.cpp:507 #5 0x756e771f in KLocalizedString::toString (this=0x7fffc7e0) at /home/prometheus/projects/kde/src/frameworks/ki18n/src/klocalizedstring.cpp:447 #6 0x0048447b in i18n(char const*) () #7 0x0047ed60 in main () (gdb) continue Continuing. Breakpoint 2, __getcwd (buf=buf@entry=0x7fffb0c0 "/home/prometheus/projects/kde/kde-5/bin/", size=size@entry=4098) at ../sysdeps/unix/sysv/linux/getcwd.c:47 47 in ../sysdeps/unix/sysv/linux/getcwd.c (gdb) bt #0 __getcwd (buf=buf@entry=0x7fffb0c0 "/home/prometheus/projects/kde/kde-5/bin/", size=size@entry=4098) at ../sysdeps/unix/sysv/linux/getcwd.c:47 #1 0x71f711d7 in __dcigettext
[krita] [Bug 356056] Krita Animation Beta - Ctrl+drag to Copy Single Animation Frame Not Working
https://bugs.kde.org/show_bug.cgi?id=356056 Dimichanged: What|Removed |Added CC||dimim...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 356250] New: Two "Help" buttons on crash reporting assistant, once helpful, one useless
https://bugs.kde.org/show_bug.cgi?id=356250 Bug ID: 356250 Summary: Two "Help" buttons on crash reporting assistant, once helpful, one useless Product: drkonqi Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: zi...@kayari.org The "Crash Reporting Assistant" (which I think is drkonqi) has two Help buttons, as shown in the attached screenshot. Only the left button does anything, the right one does nothing when clicked. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 349295] System Settings/Applications crashes on switching to file associations
https://bugs.kde.org/show_bug.cgi?id=349295 Christoph Feckchanged: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=356120 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 355569] kwin_wayland master doesn't display anything on the framebuffer
https://bugs.kde.org/show_bug.cgi?id=355569 --- Comment #13 from bluescreen_aven...@verizon.net --- How should I go about testing that? I have realized that there are some issues with the way libvirt is passing CPU features, but It seems that kwin is working under the Wayland backend under Weston on QEMU... ...It's usually breaking some things with LLVM, causing apps to crash, so it could be unrelated... So how's a good way for me to test why (or if) memory mapping for the qimage would be failing under just QEMU, only when using the framebuffer backend -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 356046] Crash KWin and desktop effects
https://bugs.kde.org/show_bug.cgi?id=356046 Christoph Feckchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 353784 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 353784] Plasma crashed after I tried to switch Desktop Cube
https://bugs.kde.org/show_bug.cgi?id=353784 Christoph Feckchanged: What|Removed |Added CC||grid...@yahoo.fr --- Comment #7 from Christoph Feck --- *** Bug 356046 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 350826] plasma desktop containment seems to intermediately switch window type to normal when showing desktop
https://bugs.kde.org/show_bug.cgi?id=350826 --- Comment #48 from Marco Martin--- there is an ensureWindowType() in DesktopView that seems a bit too happy about re setting the type on a lot of kinds of events, so yeah, that has to be redesigned a bit is it safe (and fast enough) checking what the existing window type is fairly often? -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 355284] password protected zipx wont extract with correct password
https://bugs.kde.org/show_bug.cgi?id=355284 --- Comment #5 from zezadas--- okular as a bug too, when asking for password. puting the correct password, okular cant decrypt the file. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 354358] Can't report bug because required programs won't install
https://bugs.kde.org/show_bug.cgi?id=354358 Christoph Feckchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DOWNSTREAM --- Comment #1 from Christoph Feck --- Please ask for help with package names in a forum of your distribution. -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 353942] Changing font for a chart crashes Calligra Sheets
https://bugs.kde.org/show_bug.cgi?id=353942 Christoph Feckchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 356251] New: [Krita animation beta] Merging layers (merge undo as well) with animation does not work
https://bugs.kde.org/show_bug.cgi?id=356251 Bug ID: 356251 Summary: [Krita animation beta] Merging layers (merge undo as well) with animation does not work Product: krita Version: unspecified Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: major Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: bhupen.a...@gmail.com Merging layers with animation does not work. All the keys from all layers are lost. Undo operation does not restore the keys as well. Reproducible: Always Steps to Reproduce: a1. Create 2 layers with 2 diff. animation sequences/keys. a2. Merge the 2 layers. b3. Undo the merge operation. Actual Results: a. All keys from both layers are lost. b. Undo does not restore all keys from both layers. Expected Results: a. Resulting animation and keys should be merged b. Layers should be separated and original keys restored. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 356202] wake from sleep crash notification
https://bugs.kde.org/show_bug.cgi?id=356202 Christoph Feckchanged: What|Removed |Added Product|kde |frameworks-knotifications Assignee|unassigned-b...@kde.org |mklape...@kde.org Component|general |general CC||kdelibs-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 356245] New: [Krita Animation Beta] Animation playback behaves differently when moving the brush tool on the canvas.
https://bugs.kde.org/show_bug.cgi?id=356245 Bug ID: 356245 Summary: [Krita Animation Beta] Animation playback behaves differently when moving the brush tool on the canvas. Product: krita Version: 2.9.9 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: dimim...@gmail.com When play-backing the animation it rarely plays at full speed without stuttering. Moving or wiggling the brush tool on the canvas helps considerably. Krita should be able to playback without slow downs. Reproducible: Always Steps to Reproduce: 1.Play animation 2.Move quickly the brush tool on the screen Actual Results: Playback gets to full speed or close to full speed. Expected Results: It shouldn't matter what the mouse is doing. Krita should always playback the animation smoothly. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 355527] mini app crashed desktop
https://bugs.kde.org/show_bug.cgi?id=355527 Christoph Feckchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 326140 *** -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 326140] Add widget, positioning with pressed LMB striving over possible Task manager positions
https://bugs.kde.org/show_bug.cgi?id=326140 Christoph Feckchanged: What|Removed |Added CC||dr.b...@expert-witness.de --- Comment #51 from Christoph Feck --- *** Bug 355527 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 355764] Systemsettings crashes on exit after monitor plugin
https://bugs.kde.org/show_bug.cgi?id=355764 Christoph Feckchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #2 from Christoph Feck --- Crashes in QXcbScreen from Qt library. Those are still being investigated, see e.g. https://bugreports.qt.io/browse/QTBUG-42985 -- You are receiving this mail because: You are watching all bug changes.
[qca] [Bug 356248] New: Multiple recepients encription support in qca-ossl plugin
https://bugs.kde.org/show_bug.cgi?id=356248 Bug ID: 356248 Summary: Multiple recepients encription support in qca-ossl plugin Product: qca Version: Git Platform: Other URL: https://bugzilla.suse.com/show_bug.cgi?id=868090 OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dr...@land.ru Reporter: tomas.chva...@gmail.com CC: br...@frogmouth.net, jus...@affinix.com Atm there is no code to support the multiple recepients encription in the plugin. With attached patch it is possible. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 350826] plasma desktop containment seems to intermediately switch window type to normal when showing desktop
https://bugs.kde.org/show_bug.cgi?id=350826 --- Comment #49 from Thomas Lübking--- (In reply to Marco Martin from comment #48) > is it safe (and fast enough) checking what the existing window type is > fairly often? I beg your pardon?? The KWindowSystem classes operate on locally cached data, so the X property isn't read on queries, but when it changes. The check is always "safe". Why do you think you need to "ensureWindowType()"? Nothing but the client (plasmashell) should ever change the type anyway. Indeed, it actually "should" (only) be set for an unmapped (before showing/managing) window - KWin is a bit graceful to respect runtime changes here (likely because the spec says "should" - and once more it's no way clear what the expected behavior is itr) => The "correct" behavior is to set the type before showing the screen and then "expecting" it to remain untouched. If "something else™" touches *your* property, "something else™" is maicious or broken. -- You are receiving this mail because: You are watching all bug changes.
[calligraauthor] [Bug 355287] calligraauthor crash on start when open from a screen
https://bugs.kde.org/show_bug.cgi?id=355287 Christoph Feckchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- Did you try to run as root? If not, which desktop environment are you using? KDE applications require a working D-Bus session. *** This bug has been marked as a duplicate of bug 270442 *** -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 270442] kill dbus makes inportand things instable
https://bugs.kde.org/show_bug.cgi?id=270442 Christoph Feckchanged: What|Removed |Added CC||opensou...@somekool.net --- Comment #59 from Christoph Feck --- *** Bug 355287 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355750] When setting up panels in Plasma, plasma shell crashes
https://bugs.kde.org/show_bug.cgi?id=355750 Marco Martinchanged: What|Removed |Added CC||opensuse.lietuviu.kalba@gma ||il.com --- Comment #5 from Marco Martin --- *** Bug 355916 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353578] Plasma Crash When Monitor Power-cycled
https://bugs.kde.org/show_bug.cgi?id=353578 --- Comment #8 from tobijk--- (In reply to Marco Martin from comment #7) > can you reproduce and get the console output as well when the assert gets > hit? It is reproducible and the output is (already stated above): Useful console output: ... requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 0 requesting unexisting screen 0 QXcbConnection: XCB error: 3 (BadWindow), sequence: 2286, resource id: 0, major code: 21 (ListProperties), minor code: 0 QXcbConnection: XCB error: 3 (BadWindow), sequence: 2336, resource id: 0, major code: 21 (ListProperties), minor code: 0 Maybe it is important to say: This is a notebook connected to an external monitor, where the internal monitor is disabled, thus when disabling the external monitor, the last output goes away. _Maybe_ the unexisting screen 0 is the internal notebook lcd... -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 356253] New: ark cannot open lrz files
https://bugs.kde.org/show_bug.cgi?id=356253 Bug ID: 356253 Summary: ark cannot open lrz files Product: ark Version: 2.19 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: rak...@freebsd.org Reporter: a...@fudokai.org.uk Ark is unable to open files created using lrzip (file extension .lrz, format rzip + gzip|bzip|lzma) Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 356245] [Krita Animation Beta] Animation playback behaves differently when moving the brush tool on the canvas.
https://bugs.kde.org/show_bug.cgi?id=356245 woltherachanged: What|Removed |Added CC||griffinval...@gmail.com --- Comment #1 from wolthera --- Can't confirm that here. What graphics card/drivers do you have, and is it capable of OpenGL 3.0? Perhaps it's because my device does have OpenGL 3.0 available? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 350769] Service menus require konqpopupmenuplugin.desktop
https://bugs.kde.org/show_bug.cgi?id=350769 artg...@tiscali.it changed: What|Removed |Added CC||artg...@tiscali.it -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353358] Breeze Dark Plasma Theme and Breeze (Light) Icon Theme mix
https://bugs.kde.org/show_bug.cgi?id=353358 Marco Martinchanged: What|Removed |Added CC||notm...@gmail.com --- Comment #4 from Marco Martin --- now the breeze icons themselves have the stylesheet info, so still needs testing, but all monochrome icons regardless where they come from, should be colored with theme colors -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 356251] [Krita animation beta] Merging layers (merge undo as well) with animation does not work
https://bugs.kde.org/show_bug.cgi?id=356251 woltherachanged: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED CC||griffinval...@gmail.com --- Comment #1 from wolthera --- Known limitation: https://phabricator.kde.org/T1106 Will probably be fixed before 3.0. Thanks for reporting! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 356058] Krita Animation Beta - Frame Ranges Cannot Be Selected With Graphic Tablet Stylus
https://bugs.kde.org/show_bug.cgi?id=356058 woltherachanged: What|Removed |Added CC||griffinval...@gmail.com --- Comment #3 from wolthera --- I cannot confirm this in 3.0 on Kubuntu 15.10 with the intuous 3. Maybe we can pinpoint if it only happens with certain resolutions? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 356222] G'mic crash krita
https://bugs.kde.org/show_bug.cgi?id=356222 woltherachanged: What|Removed |Added CC||griffinval...@gmail.com Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #1 from wolthera --- Known bug, this is due to a stack resize not having been applied. Can you check 2.9.10 once it's out whether it still happens? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 344569] Gmic filter crash krita immediately when select colorize interactive and some other
https://bugs.kde.org/show_bug.cgi?id=344569 woltherachanged: What|Removed |Added CC||ivanx...@openmailbox.org --- Comment #24 from wolthera --- *** Bug 356222 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 356222] G'mic crash krita
https://bugs.kde.org/show_bug.cgi?id=356222 woltherachanged: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from wolthera --- *** This bug has been marked as a duplicate of bug 344569 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 342752] Crash KNotification::id()
https://bugs.kde.org/show_bug.cgi?id=342752 Martin Klapetekchanged: What|Removed |Added CC||br3an...@gmail.com --- Comment #36 from Martin Klapetek --- *** Bug 356202 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 356202] wake from sleep crash notification
https://bugs.kde.org/show_bug.cgi?id=356202 Martin Klapetekchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Martin Klapetek --- Thanks for the report This has been fixed for some time, please update your framework-knotifications package. *** This bug has been marked as a duplicate of bug 342752 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356090] Plasmashell crashes often
https://bugs.kde.org/show_bug.cgi?id=356090 --- Comment #2 from k...@kiekerjan.isdronken.nl --- Apologies for the noise, but how do you figure this is a duplicate of 329779? I don't use kontakt nor was there a pop3 connection as far as I know. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355916] Plasma 5.4.3 crash after adding/removing new panel
https://bugs.kde.org/show_bug.cgi?id=355916 Marco Martinchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||notm...@gmail.com --- Comment #1 from Marco Martin --- *** This bug has been marked as a duplicate of bug 355750 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 337301] Crash during screen resolution change
https://bugs.kde.org/show_bug.cgi?id=337301 Marco Martinchanged: What|Removed |Added CC||traba...@gmail.com --- Comment #2 from Marco Martin --- *** Bug 355355 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 356252] New: Konsole randomly crashes
https://bugs.kde.org/show_bug.cgi?id=356252 Bug ID: 356252 Summary: Konsole randomly crashes Product: konsole Version: 15.08.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: steve.mck...@gmail.com Application: konsole (15.08.3) Qt Version: 5.5.1 Operating System: Linux 4.2.6-300.fc23.x86_64 x86_64 Distribution: "Fedora release 23 (Twenty Three)" -- Information about the crash: - What I was doing when the application crashed: Nothing in particular. - Unusual behavior I noticed: Plasma crashed a few times for the past 2 days while docking/undocking (it doesn't crash right on dock/undock but some time after, random enough though so I can't be too specific). The option of suggesting a duplicate doesn't work so I'm putting this in here: this appears to be a duplicate of https://bugs.kde.org/show_bug.cgi?id=355612 -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 84T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7fdd6a315940 (LWP 3385))] Thread 2 (Thread 0x7fdd2a7fb700 (LWP 27660)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fdd6308265b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x55ad629423a0) at thread/qwaitcondition_unix.cpp:136 #2 QWaitCondition::wait (this=this@entry=0x55ad62942790, mutex=mutex@entry=0x55ad62942788, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #3 0x7fdd6417be6a in QFileInfoGatherer::run (this=0x55ad62942778) at dialogs/qfileinfogatherer.cpp:211 #4 0x7fdd630813ce in QThreadPrivate::start (arg=0x55ad62942778) at thread/qthread_unix.cpp:331 #5 0x7fdd603ff60a in start_thread (arg=0x7fdd2a7fb700) at pthread_create.c:334 #6 0x7fdd62484a7d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fdd6a315940 (LWP 3385)): [KCrash Handler] #6 0x7fdd4cccb85f in QXcbWindow::handleClientMessageEvent (this=0x55ad613aae60, event=0x7fdd44016060) at qxcbwindow.cpp:1943 #7 0x7fdd4ccb4dcb in QXcbConnection::handleXcbEvent (this=this@entry=0x55ad6125aa80, event=event@entry=0x7fdd44016060) at qxcbconnection.cpp:1080 #8 0x7fdd4ccb5433 in QXcbConnection::processXcbEvents (this=0x55ad6125aa80) at qxcbconnection.cpp:1527 #9 0x7fdd632921b1 in QObject::event (this=0x55ad6125aa80, e=) at kernel/qobject.cpp:1239 #10 0x7fdd63f4841c in QApplicationPrivate::notify_helper (this=0x55ad6126cf50, receiver=0x55ad6125aa80, e=0x7fdd440032b0) at kernel/qapplication.cpp:3716 #11 0x7fdd63f4d8e6 in QApplication::notify (this=0x7fffdddc95f0, receiver=0x55ad6125aa80, e=0x7fdd440032b0) at kernel/qapplication.cpp:3499 #12 0x7fdd6326277b in QCoreApplication::notifyInternal (this=0x7fffdddc95f0, receiver=0x55ad6125aa80, event=event@entry=0x7fdd440032b0) at kernel/qcoreapplication.cpp:965 #13 0x7fdd63264b76 in QCoreApplication::sendEvent (event=0x7fdd440032b0, receiver=) at kernel/qcoreapplication.h:224 #14 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x55ad6121b600) at kernel/qcoreapplication.cpp:1593 #15 0x7fdd63265058 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1451 #16 0x7fdd632b8ae3 in postEventSourceDispatch (s=0x55ad612ade50) at kernel/qeventdispatcher_glib.cpp:271 #17 0x7fdd5dc3ae3a in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #18 0x7fdd5dc3b1d0 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #19 0x7fdd5dc3b27c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #20 0x7fdd632b8eef in QEventDispatcherGlib::processEvents (this=0x55ad612afc60, flags=...) at kernel/qeventdispatcher_glib.cpp:418 #21 0x7fdd6325ff0a in QEventLoop::exec (this=this@entry=0x7fffdddc94a0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #22 0x7fdd63267fec in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1229 #23 0x7fdd6379660c in QGuiApplication::exec () at kernel/qguiapplication.cpp:1527 #24 0x7fdd63f44855 in QApplication::exec () at kernel/qapplication.cpp:2976 #25 0x7fdd69ffe986 in kdemain (argc=, argv=) at ../../src/main.cpp:113 #26 0x7fdd623a2580 in __libc_start_main (main=0x55ad607f3b70, argc=1, argv=0x7fffdddc9738, init=, fini=, rtld_fini=, stack_end=0x7fffdddc9728) at libc-start.c:289 #27 0x55ad607f3ba9 in _start () Possible duplicates by query: bug 355764, bug 355612, bug 355221, bug 353605, bug 353563. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug
[plasmashell] [Bug 355587] Manually control number of rows/columns in system tray
https://bugs.kde.org/show_bug.cgi?id=355587 Marco Martinchanged: What|Removed |Added Severity|normal |wishlist CC||notm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355355] Plasmashell crash when change the screen
https://bugs.kde.org/show_bug.cgi?id=355355 Marco Martinchanged: What|Removed |Added Status|CONFIRMED |RESOLVED CC||notm...@gmail.com Resolution|--- |DUPLICATE --- Comment #1 from Marco Martin --- *** This bug has been marked as a duplicate of bug 337301 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 356245] [Krita Animation Beta] Animation playback behaves differently when moving the brush tool on the canvas.
https://bugs.kde.org/show_bug.cgi?id=356245 --- Comment #2 from Dimi--- Yes, my graphics card should be capable of OpenGl 3.0. It's an Intel HD 3000 and it doesn't have any problems with other opengl features of Krita. Maybe your pc is faster and you simply don't notice a difference because it always plays at full speed. On my slower machine it makes a big difference. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 356254] New: Search order is not alphabetical
https://bugs.kde.org/show_bug.cgi?id=356254 Bug ID: 356254 Summary: Search order is not alphabetical Product: digikam Version: 4.13.0 Platform: Mac OS X Disk Images OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: Searches Assignee: digikam-de...@kde.org Reporter: gski...@gmail.com I have several saved searches. I would like them to be organized alphabetically. Reproducible: Always Steps to Reproduce: 1. Search tool 2. Create search 3. They are randomly organized, or somewhat alphabetical -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 287405] BQM AdjustCurves tool : Load curves settings file
https://bugs.kde.org/show_bug.cgi?id=287405 caulier.gil...@gmail.com changed: What|Removed |Added CC||elv1...@gmail.com --- Comment #2 from caulier.gil...@gmail.com --- *** Bug 356229 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 351971] Plasma freezes for about 3 minutes periodically
https://bugs.kde.org/show_bug.cgi?id=351971 Marco Martinchanged: What|Removed |Added CC||germano.massu...@gmail.com --- Comment #1 from Marco Martin --- *** Bug 356108 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355932] plasmashell segfaults after wakeup from suspend with one display less connected
https://bugs.kde.org/show_bug.cgi?id=355932 Marco Martinchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||notm...@gmail.com --- Comment #1 from Marco Martin --- *** This bug has been marked as a duplicate of bug 355885 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 350826] plasma desktop containment seems to intermediately switch window type to normal when showing desktop
https://bugs.kde.org/show_bug.cgi?id=350826 --- Comment #51 from Marco Martin--- because the whole api of that class was done around that yeah, was fine to change window type at runtime. since it turned out it isn't, the dashboard thing was removed, still a lot of untangling has to be done. probably it should be able to set the window type only before a window show? -- You are receiving this mail because: You are watching all bug changes.