[killbots] [Bug 363005] New: Killbots score not being saved
https://bugs.kde.org/show_bug.cgi?id=363005 Bug ID: 363005 Summary: Killbots score not being saved Product: killbots Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: coa...@kde.org Reporter: jfcandidofi...@gmail.com CC: kde-games-b...@kde.org Killbots score isn't being saved. It isn't even showing up at the screen in which you chose to save it or forget it. Under Arch Linux - just updated (not the reason - first time playing). Killbots version 1.2 (not available on the menu above). I have two screenshots here, one showing the problematic screen and one showing the version and KDE and stuff version it is running into. I hope that suffices. Reproducible: Always Steps to Reproduce: 1. Open Killbots; 2. Play until you die; 3. No score saved or showed up. Actual Results: Not score being shown or at disposal to be saved. Expected Results: Showed the score and saved if I wanted it to. OK; it's not a critic software. But it does make my time pass by less stressful. ;P -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363003] opening png doesn't work
https://bugs.kde.org/show_bug.cgi?id=363003 --- Comment #1 from Boudewijn Rempt --- Is the screen black or blank? If black, your graphics card/driver combination might have bug and you might have to disable opengl in the settings/configure Krita dialog. If you see the transparency squares, something else is up. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 274931] Windows with no border (decoration) are visible on all activities
https://bugs.kde.org/show_bug.cgi?id=274931 --- Comment #33 from Jim Duchek --- (In reply to Martin Gräßlin from comment #32) > The reason for the noborder check is explained in: > http://commits.kde.org/kwin/ff82383f8d8acdc684468a3176e1d048a795209b > > By simply reverting as asked for in this bug report, we are ignoring the > problems outlined in this commit. This needs a smarter solution. The solution has already been implemented, and the noborder check is a leftover. I don't have the time right now to dig out all the proper commits (but I will tomorrow if you want me to :) you'll note in the HEAD version of manage.cpp, there is no more 'isOnAllActivities()' check as there was in this commit, because the proper way for windows to ask to be on all activities has been implemented. There is an additional comment just below the commit you referenced in manage.cpp: //TODO: if we are keeping it (at least as an option), replace noborder checking //with a public API for setting windows to be on all activities. //something like KWindowSystem::setOnAllActivities or //KActivityConsumer::setOnAllActivities And hi there... Client::setOnAllActivities() exists now -- there is no reason for this hack anymore, although it may potentially be masking bugs in other places wherein they are not properly asking for an all-activities window. But that is their bug to fix, and no reason to keep this one. This TODO needs to be removed along with the noborder check as well, I guess, lest it confuse future code browsers. The commit comment makes one still-valid point, in that indeed, users who WANT a no-border window to be on all activities, will need to figure out alt-f3, which is not obvious... But that is better than the current situation, wherein users who want no-border windows to act 'normally' have to figure out alt-f3. Somebody's going to need to find alt-f3 either way when it comes to no-border windows, and IMHO it should be the people who want the non-standard behavior. Jim -- You are receiving this mail because: You are watching all bug changes.
[killbots] [Bug 363005] Killbots score not being saved
https://bugs.kde.org/show_bug.cgi?id=363005 --- Comment #1 from José --- Created attachment 98943 --> https://bugs.kde.org/attachment.cgi?id=98943&action=edit Demonstration of the problem Score not shown or at disposal to be saved. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357047] Plasma 5.5 Crashes Immediately after Reboot
https://bugs.kde.org/show_bug.cgi?id=357047 Thomas Lübking changed: What|Removed |Added Resolution|WONTFIX |DUPLICATE --- Comment #2 from Thomas Lübking --- *** This bug has been marked as a duplicate of bug 355026 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355026] Plasmashell crashed when resuming from suspend
https://bugs.kde.org/show_bug.cgi?id=355026 Thomas Lübking changed: What|Removed |Added CC||kerryla...@islandnet.com --- Comment #2 from Thomas Lübking --- *** Bug 357047 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362948] [PERITAB] Krita crashes if I touch the tablet with the pen
https://bugs.kde.org/show_bug.cgi?id=362948 Boudewijn Rempt changed: What|Removed |Added Version|unspecified |2.9.11 Summary|Krita crashes if I touch|[PERITAB] Krita crashes if |the tablet with the pen |I touch the tablet with the ||pen Resolution|--- |WAITINGFORINFO Component|general |tablet support Status|UNCONFIRMED |NEEDSINFO CC||b...@valdyas.org --- Comment #3 from Boudewijn Rempt --- Could you check with the 3.0 beta? Your brand of tablet is very obscure and we don't have hardware to test with, but it sounds like the same problem Trust and Genius tablets give. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354054] Plasmashell crashed when resuming from suspend
https://bugs.kde.org/show_bug.cgi?id=354054 Thomas Lübking changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=355026 --- Comment #4 from Thomas Lübking --- Leaving aside the concurrent ::renderBatches call, this is similar to bug #355026 which was duped to bug #355578 where the crash happens in MESA *without* the concurrent calls. Smeels more like a bug in QtQuick than in MESA & nvidia at the same time. Also see http://stackoverflow.com/questions/16594901/segmentation-fault-while-unmapping-buffer-glbindbuffer -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361439] plasma crash when session locked
https://bugs.kde.org/show_bug.cgi?id=361439 --- Comment #9 from Thomas Lübking --- That's more like bug #354054, also see bug #355026 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355026] Plasmashell crashed when resuming from suspend
https://bugs.kde.org/show_bug.cgi?id=355026 Thomas Lübking changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=354054 -- You are receiving this mail because: You are watching all bug changes.
[killbots] [Bug 363005] Killbots score not being saved
https://bugs.kde.org/show_bug.cgi?id=363005 --- Comment #2 from José --- I'm not being able to upload a second screenshot so here what is written on it: Killbots Version 1.2.0 Using: - KDE Framework 5.21.0 - QT 5.6.0 (built against 5.6.0) - The xcb windowing system (? sorry, don't even know what it is haha) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362991] Task manager is filled with empty space when a dialog or window is opened
https://bugs.kde.org/show_bug.cgi?id=362991 Eike Hein changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #2 from Eike Hein --- By empty space you mean the space above the kmenu icon in your screenshot? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363003] opening png doesn't work
https://bugs.kde.org/show_bug.cgi?id=363003 --- Comment #2 from n1k0l4 --- Created attachment 98944 --> https://bugs.kde.org/attachment.cgi?id=98944&action=edit this is what I obtain -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 359058] Regression: Drag-n-drop of (Image-)URLs from Chromium does not work in kMail 5.0.x any more
https://bugs.kde.org/show_bug.cgi?id=359058 --- Comment #4 from Gunter Ohrner --- For me, kMail 5.1.3 inserts the image URL as text and some character garbage (URL-encoded UTF-16 as ASCII, or something, see below...) It does not ask whether to paste the address as text or to attach the actual file. If I now copy the image URL in chrome (right-click -> copy image url) and paste it into the editor, it just pasts the URL string and does not ask if it should add the linked file as an attachment instead. (IIRC it did so in previous kMail versions.) All stated holds for the plain text editor. (I do not use the HTML / richt text editor.) Software: kMail Version 5.1.3 KDE Frameworks 5.18.0 Qt 5.5.1 (kompiliert gegen 5.5.1) Das xcb Fenstersystem Example: If I go to http://www.ohrner-it.com/ and drag the company logo on the top left of the page to the plain text editor, the following will be pasted (the text between the lines): -- http://www.ohrner-it.com/images/logo.png %00O%00h%00r%00n%00e%00r%00 %00I%00T%00 %00G%00m%00b%00H -- This looks quite wrong to me... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 362994] middle click to close, in titlebar -passes click to whatever below
https://bugs.kde.org/show_bug.cgi?id=362994 --- Comment #3 from Allan --- (In reply to Martin Gräßlin from comment #1) > That sounds like a bug in the applications. They react on a release although > they never get a press event. The application should ignore that. > > Do you see this with all applications or just e.g. all Qt applications? I see it in everything I've tested over so far, including: xterm, konsole plasma desktop. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 363006] New: KWin crashed while started after reboot
https://bugs.kde.org/show_bug.cgi?id=363006 Bug ID: 363006 Summary: KWin crashed while started after reboot Product: kwin Version: 5.6.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: itarna...@yandex.ru Application: kwin_x11 (5.6.3) Qt Version: 5.6.0 Frameworks Version: 5.21.0 Operating System: Linux 4.4.9-300.fc23.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - KWin crashed after system update and reboot. Crashed while login in. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8a43d15940 (LWP 1593))] Thread 4 (Thread 0x7f8a3c6be700 (LWP 1600)): #0 0x7f8a5403cd0d in poll () from /lib64/libc.so.6 #1 0x7f8a550ad272 in _xcb_conn_wait () from /lib64/libxcb.so.1 #2 0x7f8a550aeee7 in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7f8a3cf25349 in QXcbEventReader::run() () from /lib64/libQt5XcbQpa.so.5 #4 0x7f8a55371d48 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7f8a56d9b60a in start_thread () from /lib64/libpthread.so.0 #6 0x7f8a5404878d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f8a3af60700 (LWP 1601)): #0 0x7f8a5403ea93 in select () from /lib64/libc.so.6 #1 0x7f8a5559629f in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () from /lib64/libQt5Core.so.5 #2 0x7f8a55597cde in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () from /lib64/libQt5Core.so.5 #3 0x7f8a555981f2 in QEventDispatcherUNIX::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f8a555434ca in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f8a5536cf34 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f8a5689c4b5 in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #7 0x7f8a55371d48 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f8a56d9b60a in start_thread () from /lib64/libpthread.so.0 #9 0x7f8a5404878d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f8a38d45700 (LWP 1696)): #0 0x7f8a5403ea93 in select () from /lib64/libc.so.6 #1 0x7f8a5559629f in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () from /lib64/libQt5Core.so.5 #2 0x7f8a55597cde in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () from /lib64/libQt5Core.so.5 #3 0x7f8a555981f2 in QEventDispatcherUNIX::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7f8a555434ca in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f8a5536cf34 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7f8a5ba611b5 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #7 0x7f8a55371d48 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f8a56d9b60a in start_thread () from /lib64/libpthread.so.0 #9 0x7f8a5404878d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f8a43d15940 (LWP 1593)): [KCrash Handler] #5 0x7f8a5540fae2 in QtPrivate::QStringList_contains(QStringList const*, QString const&, Qt::CaseSensitivity) () from /lib64/libQt5Core.so.5 #6 0x7f8a568a5f12 in QDBusConnectionPrivate::isServiceRegisteredByThread(QString const&) () from /lib64/libQt5DBus.so.5 #7 0x7f8a568ae248 in QDBusConnectionPrivate::sendWithReplyAsync(QDBusMessage const&, QObject*, char const*, char const*, int) () from /lib64/libQt5DBus.so.5 #8 0x7f8a5689d158 in QDBusConnection::asyncCall(QDBusMessage const&, int) const () from /lib64/libQt5DBus.so.5 #9 0x7f8a5d42e114 in KWin::LogindIntegration::logindServiceRegistered() () from /lib64/libkwin.so.5 #10 0x7f8a5d42e4c6 in QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () from /lib64/libkwin.so.5 #11 0x7f8a5557212e in QMetaObject::activate(QObject*, int, int, void**) () from /lib64/libQt5Core.so.5 #12 0x7f8a568f288f in QDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*) () from /lib64/libQt5DBus.so.5 #13 0x7f8a568f2988 in QDBusPendingCallWatcher::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /lib64/libQt5DBus.so.5 #14 0x7f8a55572c29 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #15 0x7f8a55e79c0c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #16 0x7f8a55e7ee76 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #17 0x7f8a55545748 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #18 0x7f8a5554760a in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64
[kwin] [Bug 274931] Windows with no border (decoration) are visible on all activities
https://bugs.kde.org/show_bug.cgi?id=274931 Martin Gräßlin changed: What|Removed |Added CC||ivan.cu...@kde.org --- Comment #34 from Martin Gräßlin --- @Ivan: can you please have a look whether the requirement for the noborder restriction is still needed. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 362280] KMail replaces addresses in the header by "Me"
https://bugs.kde.org/show_bug.cgi?id=362280 Florian Lindner changed: What|Removed |Added CC||florian.lind...@xgm.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 363006] KWin crashed while started after reboot
https://bugs.kde.org/show_bug.cgi?id=363006 Martin Gräßlin changed: What|Removed |Added Resolution|--- |BACKTRACE Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Martin Gräßlin --- The backtrace is unfortunately lacking debug symbols. Because of that we don't see exactly where it crashes. From what we see it looks like it crashes in QtDBus. If you are able to reproduce, please add a new backtrace with full debug symbols. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 362994] middle click to close, in titlebar -passes click to whatever below
https://bugs.kde.org/show_bug.cgi?id=362994 --- Comment #4 from Allan --- (In reply to Thomas Lübking from comment #2) > Latter is easily tested: press in an xterm, move over to the problematic > client and release the button there. > Is this with the breeze decoration, aurorae or both? (in doubt post output > of "qdbus org.kde.KWin /KWin supportInformation") I only tested with Breeze. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 362983] KWin does not depend on Qt5Multimedia
https://bugs.kde.org/show_bug.cgi?id=362983 Harald Sitter changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #2 from Harald Sitter --- As confirmed on IRC the relevant QML module is installed by kwin-data. As far as apt-get build-dep is concerned this is intentional behavior. It simply installs whatever is listed in the control's Build-Depends field and that in turn does not include the QML module as it is a runtime dependency. The build dependency list of the packaging would not include runtime dependencies to reduce build time from unnecessary dependencies. Also as I pointed out this would be better detected by KWin's cmakelists if it used purpose's magic cmake finder for finding qml modules rather than cmake packages (which ultimately suffer from the same problem anyway; i.e. qtmm-dev wouldn't pull in the qml module because it is not actually referenced or needed to build qtmm software). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 362994] middle click to close, in titlebar -passes click to whatever below
https://bugs.kde.org/show_bug.cgi?id=362994 --- Comment #5 from Allan --- (In reply to Martin Gräßlin from comment #1) > That sounds like a bug in the applications. They react on a release although > they never get a press event. The application should ignore that. I happens before release of the button. I can reproduce it by clicking to close, then while still holding the button -move the mouse and the paste happen at the move action. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 362969] user case scenario: donor relationship management
https://bugs.kde.org/show_bug.cgi?id=362969 --- Comment #2 from Martin Tlustos --- Yes, except that - it is very cumbersome to change a payee. It would be easier to have a dropdown list of payees somewhere - I can not display multiple payees in parallel, only sums. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 362994] middle click to close, in titlebar -passes click to whatever below
https://bugs.kde.org/show_bug.cgi?id=362994 --- Comment #6 from Martin Gräßlin --- at the move? That's something I would not have expected. -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway
https://bugs.kde.org/show_bug.cgi?id=75324 --- Comment #20 from David Faure --- "It's so productive to be able to mount ftp, sftp, smb, and others, and access them reliably from one app to another..." Even when you then close down the laptop and go home, and upon reopening the laptop, any operation on all of these mount points hangs (blockingly!) for 5 minutes because you lost the connection to the server? In my experience when this happens the application is completely blocked, not even repainting or anything, which is extremely annoying and counter-productive, isn't it? -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 363007] New: Konqueror Crash on opening e-mail from Web.de
https://bugs.kde.org/show_bug.cgi?id=363007 Bug ID: 363007 Summary: Konqueror Crash on opening e-mail from Web.de Product: konqueror Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: normankl...@gmail.com Application: konqueror (4.14.18) KDE Platform Version: 4.14.18 Qt Version: 4.8.6 Operating System: Linux 4.1.13-5-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Opening e-mail by Konqueror on web.de. That e-mail did not contain any links or attached files. This bug seems to be intermittent. The crash can be reproduced sometimes. -- Backtrace: Application: Konqueror (konqueror), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe386cda780 (LWP 8113))] Thread 9 (Thread 0x7fe36d614700 (LWP 8115)): #0 0x7fe384326bbd in poll () at /lib64/libc.so.6 #1 0x7fe381436e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fe381436f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fe385974fde in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #4 0x7fe385946d4f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #5 0x7fe385947045 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7fe3858444df in QThread::exec() () at /usr/lib64/libQtCore.so.4 #7 0x7fe385928653 in () at /usr/lib64/libQtCore.so.4 #8 0x7fe385846bbf in () at /usr/lib64/libQtCore.so.4 #9 0x7fe3855b00a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7fe38432efed in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7fe367fff700 (LWP 8124)): #0 0x7fe3855b6a7d in read () at /lib64/libpthread.so.0 #1 0x7fe381477b60 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fe381436999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7fe381436df8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fe381436f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7fe385974fde in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7fe385946d4f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #7 0x7fe385947045 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #8 0x7fe3858444df in QThread::exec() () at /usr/lib64/libQtCore.so.4 #9 0x7fe37b168e7e in () at /usr/lib64/libkio.so.5 #10 0x7fe385846bbf in () at /usr/lib64/libQtCore.so.4 #11 0x7fe3855b00a4 in start_thread () at /lib64/libpthread.so.0 #12 0x7fe38432efed in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7fe35d4a8700 (LWP 8128)): #0 0x7fe3855b403f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fe366516eb6 in WTF::TCMalloc_PageHeap::scavengerThread() () at /usr/lib64/libQtWebKit.so.4 #2 0x7fe366516ee9 in () at /usr/lib64/libQtWebKit.so.4 #3 0x7fe3855b00a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fe38432efed in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7fe35cca7700 (LWP 8129)): #0 0x7fe3855b6a7d in read () at /lib64/libpthread.so.0 #1 0x7fe381477b60 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fe381436999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7fe381436df8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fe381436f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7fe385974fde in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7fe385946d4f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #7 0x7fe385947045 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #8 0x7fe3858444df in QThread::exec() () at /usr/lib64/libQtCore.so.4 #9 0x7fe385846bbf in () at /usr/lib64/libQtCore.so.4 #10 0x7fe3855b00a4 in start_thread () at /lib64/libpthread.so.0 #11 0x7fe38432efed in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7fe317dce700 (LWP 8130)): #0 0x7fe3855b403f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fe366289b3d in JSC::BlockAllocator::blockFreeingThreadMain() () at /usr/lib64/libQtWebKit.so.4 #2 0x7fe36653ea06 in WTF::wtfThreadEntryPoint(void*) () at /usr/lib64/libQtWebKit.so.4 #3 0x7fe3855b00a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fe38432efed in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fe306e9b700 (LWP 8143)): #0 0x7fe3855b403f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fe301da0d79 in () at /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so #2 0x7fe301da1819 in () at /usr/lib64/java-1_8_0-op
[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup
https://bugs.kde.org/show_bug.cgi?id=346961 --- Comment #54 from Adam --- (In reply to Mika Norén from comment #52) > Here's an ugly workaround to use meanwhile: The workaround didn't work for me. I'm using the KDE Neon unstable archives now and the issue still exists - doesn't seem as bad as it used to be for me in that much of the time the configuration remains correct but every now and again it's still lost. This morning I logged in and the screens were mirrored ( rather than extended over both. ) Rebooted and it was fine again. This is with the kscreen config file set to read only. -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway
https://bugs.kde.org/show_bug.cgi?id=75324 --- Comment #21 from Ville Ranki --- (In reply to David Faure from comment #20) > Even when you then close down the laptop and go home, and upon reopening the > laptop, any operation on all of these mount points hangs (blockingly!) for 5 > minutes because you lost the connection to the server? Those hangs are an issue on some lower level components (FUSE/plugins/kernel) and needs to be fixed there. Personally I haven't seen these for some time, but I mostly use SSHFS. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362774] KDE Activities do not have a well-defined ordering
https://bugs.kde.org/show_bug.cgi?id=362774 Kai Uwe Broulik changed: What|Removed |Added CC||ivan.cu...@kde.org, ||k...@privat.broulik.de --- Comment #1 from Kai Uwe Broulik --- I thought activities were supposed to be sorted by last use, Ivan? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 349785] Add an option auto-hide intelligently if and only if some window is near it, or maximized. As seen on Cinnamon Panels.
https://bugs.kde.org/show_bug.cgi?id=349785 fl...@mailoo.org changed: What|Removed |Added CC||fl...@mailoo.org -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 359012] Redo of connected widgets do not restore the association
https://bugs.kde.org/show_bug.cgi?id=359012 Ralf Habacker changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=363008 -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 363008] New: No undo of associations possible
https://bugs.kde.org/show_bug.cgi?id=363008 Bug ID: 363008 Summary: No undo of associations possible Product: umbrello Version: 2.19.1 (KDE Applications 16.04.1) Platform: Other OS: All Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: umbrello-de...@kde.org Reporter: ralf.habac...@freenet.de It is not possible to undo an added connection. Undoing removes the latest class before adding the connection. Reproducible: Always Steps to Reproduce: 1. start umbrello 2. add a classes 3. add another class 4. connect them with an association 5. press undo in the menu or press STRG-Z Actual Results: The class added in 3. has been removed from the scene, not the connection. Expected Results: The connection should be undo'd. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 363008] No undo of associations possible
https://bugs.kde.org/show_bug.cgi?id=363008 Ralf Habacker changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=359012 -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359603 --- Comment #39 from Ben Cooksley --- In regards to DNS queries, Bugzilla doesn't execute those. Bugzilla passes the email off to the local mail server, which then handles things at it's discretion. This maximises the performance while minimizing the risk of email being lost or a query failing to complete successfully. Note that adding an option is not acceptable, as anyone with such an option enabled would potentially represent a risk to the proper operation of Bugzilla (as parts of the database are locked, then a DNS query is made to a domain which isn't functioning properly, meaning it has to wait for network timeout - during which time other users who want to make changes to Bugzilla are stuck while their pages wait for the database tables to become unlocked again). Bugzilla is a Perl application. Note that anyone's opinion on DMARC's validity is completely irrelevant. The reality is that clients of Bugzilla (users and developers) use providers who either publish DMARC policies or will enforce to a certain extent DMARC policies set by domain owners. We must ensure our email is not blocked by these policies. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 349785] Add an option auto-hide intelligently if and only if some window is near it, or maximized. As seen on Cinnamon Panels.
https://bugs.kde.org/show_bug.cgi?id=349785 --- Comment #6 from fl...@mailoo.org --- I also think intelligent autohide (i.e. visible panel when it is not in the way) is good design. @David Edmundson: I understand the comment about not having too much options. Maybe having intelligent autohide instead of plain hiding would help to have a good design without adding an option? I can't think of any usecase where plain hide is better than intelligent autohide. The latter is: - more discoverable (panel is visible at startup when no window is shown) - quickest (anytime the panel is not in the way, it is already available for interaction) - more elegant (but that's admittedly a personal and relative opinion) -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 359603] Incorrect and useless From header in emails generated by KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359603 --- Comment #40 from Pali Rohár --- Ok, and what about option which do not check DNS records when user change it? That will not lock bugzilla... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 349785] Add an option auto-hide intelligently if and only if some window is near it, or maximized. As seen on Cinnamon Panels.
https://bugs.kde.org/show_bug.cgi?id=349785 --- Comment #7 from adr.fant...@gmail.com --- (In reply to flyos from comment #6) > I also think intelligent autohide (i.e. visible panel when it is not in the > way) is good design. > > @David Edmundson: I understand the comment about not having too much > options. Maybe having intelligent autohide instead of plain hiding would > help to have a good design without adding an option? > > I can't think of any usecase where plain hide is better than intelligent > autohide. The latter is: > - more discoverable (panel is visible at startup when no window is shown) > - quickest (anytime the panel is not in the way, it is already available for > interaction) > - more elegant (but that's admittedly a personal and relative opinion) I fully agree. there is not a single case in which plain hiding is better than autohiding. I started to use the Plank dock for this reason, plain hiding in Plasma feels a decade old! -- You are receiving this mail because: You are watching all bug changes.
[phonon-backend-gstreamer] [Bug 334421] amarok will increase the memory usage after long time music switch
https://bugs.kde.org/show_bug.cgi?id=334421 Myriam Schweingruber changed: What|Removed |Added Target Milestone|2.9 |4.8 Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO Assignee|amarok-bugs-d...@kde.org|dvra...@kde.org Product|amarok |phonon-backend-gstreamer Version|2.8.0 |unspecified CC||myr...@kde.org, ||romain.per...@gmail.com, ||sit...@kde.org, ||tdfisc...@kde.org Component|general |general --- Comment #8 from Myriam Schweingruber --- Which exact phonon-gstreamer-backend version do you use? Reassigning the bug -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363003] opening png doesn't work
https://bugs.kde.org/show_bug.cgi?id=363003 --- Comment #3 from Boudewijn Rempt --- Is that with 2.9 or 3.0? And does it change if you disable opengl? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363003] opening png doesn't work
https://bugs.kde.org/show_bug.cgi?id=363003 --- Comment #4 from n1k0l4 --- As in first post, it's the last beta version (http://files.kde.org/krita/3/windows/devbuilds/krita-3.0-Beta-master-d330a4a-x64.zip). Disable opengl doesn't change. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 362994] middle click to close, in titlebar -passes click to whatever below
https://bugs.kde.org/show_bug.cgi?id=362994 --- Comment #7 from Allan --- (In reply to Martin Gräßlin from comment #6) > at the move? That's something I would not have expected. Affirmative, it only happens when mouse is moved during the press. If the click is clean without any movement with the mouse, the click is not passed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362991] Task manager is filled with empty space when a dialog or window is opened
https://bugs.kde.org/show_bug.cgi?id=362991 Sudhir Khanger changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |UNCONFIRMED --- Comment #3 from Sudhir Khanger --- Yes the space between the top and menu widget. So far random things like opening a chrome window or closing Emacs window would insert the space. The space goes away either automatically or with a click here and there. I started seeing this around 5.6.2 release. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 362794] Gmail notifications expand beyond screen
https://bugs.kde.org/show_bug.cgi?id=362794 l.allu...@gmail.com changed: What|Removed |Added CC||l.allu...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 362994] middle click to close, in titlebar -passes click to whatever below
https://bugs.kde.org/show_bug.cgi?id=362994 --- Comment #8 from Thomas Lübking --- press, close move, paste? that's incredibly odd - the move would at least have to generate a release then... running klipper process or plasmoid? still a problem when quitting those? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 343795] Accessing S/MIME encrypted attachments fails
https://bugs.kde.org/show_bug.cgi?id=343795 Dennis Schridde changed: What|Removed |Added CC||dennis.schridde@uni-heidelb ||erg.de -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 363009] New: Outlook generated S/MIME email body (Content-Disposition: attachment; filename="smime.p7m") not readable
https://bugs.kde.org/show_bug.cgi?id=363009 Bug ID: 363009 Summary: Outlook generated S/MIME email body (Content-Disposition: attachment; filename="smime.p7m") not readable Product: kmail2 Version: 4.14.10 Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: dennis.schri...@uni-heidelberg.de I received an email from what appears to be Outlook, which declares the body as being in following form: ``` Content-Type: application/pkcs7-mime; smime-type=signed-data; name="smime.p7m" Content-Disposition: attachment; filename="smime.p7m" Content-Transfer-Encoding: base64 ``` Thunderbird ignores the Content-Disposition header and just displays the contents of that "attachment". KMail 4.14.10, however, displays it as declared by the sender (as an attachment with name "smime.p7m") and provides no way to read the content. I am using Debian 9 / Stretch, with KMail being at version 4:4.14.10-2. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 363010] New: Crash when right clicking on video in dolphin after installing smplayer
https://bugs.kde.org/show_bug.cgi?id=363010 Bug ID: 363010 Summary: Crash when right clicking on video in dolphin after installing smplayer Product: dolphin Version: 15.12.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: rbabc...@gmail.com Application: dolphin (15.12.3) Qt Version: 5.5.1 Operating System: Linux 4.4.0-22-generic x86_64 Distribution: Ubuntu 16.04 LTS -- Information about the crash: - What I was doing when the application crashed: Right click on videos, scrolled down... around "activities" it crashes. Didn't click anything. - Custom settings of the application: Recently installed smplayer The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 [Current thread is 1 (Thread 0x7fb5486ae8c0 (LWP 2166))] Thread 4 (Thread 0x7fb545976700 (LWP 2167)): #0 0x7fb559f5ae8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fb54e6c8c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fb54e6ca8d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fb5482fa629 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7fb554b2c84e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fb5512da6fa in start_thread (arg=0x7fb545976700) at pthread_create.c:333 #6 0x7fb559f66b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7fb53a51d700 (LWP 2169)): #0 0x7fb559f5ae8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fb55074f31c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb55074f42c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb554d63a9b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fb554d0adea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fb554b278a4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fb554b2c84e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fb5512da6fa in start_thread (arg=0x7fb53a51d700) at pthread_create.c:333 #8 0x7fb559f66b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fb538b9c700 (LWP 2175)): [KCrash Handler] #6 0x7fb554b249a5 in QMutex::lock() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fb554b2b9ab in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fb554b2c86f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fb5512da6fa in start_thread (arg=0x7fb538b9c700) at pthread_create.c:333 #10 0x7fb559f66b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fb5486ae8c0 (LWP 2166)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fb54e6c8eb9 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fb54e6ca617 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fb54e6ca721 in xcb_wait_for_reply () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #4 0x7fb54831c266 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #5 0x7fb54831c318 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #6 0x7fb555269fd8 in QCursor::pos(QScreen const*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #7 0x7fb55526a0b1 in QCursor::pos() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #8 0x7fb55598e971 in QMenu::popup(QPoint const&, QAction*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7fb5559909b1 in QMenu::internalDelayedPopup() () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7fb554d3ce53 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fb555852cdb in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7fb555995a83 in QMenu::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7fb55581005c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7fb555815516 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7fb554d0d62b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7fb554d6289d in QTimerInfoList::activateTimers() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7fb554d62dd9 in ?? () from /usr/lib/x
[okular] [Bug 363011] New: Okular has incorrect zoom factors
https://bugs.kde.org/show_bug.cgi?id=363011 Bug ID: 363011 Summary: Okular has incorrect zoom factors Product: okular Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: i.m.j...@gmx.de Hello, I have Okular 0.19.3 under KDE 4.13.3 installed (Kubuntu 14.04 LTS). The zoom factors do not seem to be accurate. If I want to have a real 100% zoom to show my documents, I will have to set the zoom factor to around 128%. I can't say if this is the exact real 100% setting, but I compared this display to other program's 100% zoom displays and to real document papers. So it is quite uncomfortable having to enter "128+[ENTER]" each time if I want to watch a document in original size. I hope you can help. Reproducible: Always Steps to Reproduce: Open a document with Okular set the zoom factor to 100% and compare it with other program's 100% zoom (e.g. Libre Office's Writer). Actual Results: Okular's displayed document is far smaller (than others). Expected Results: Okular should display documents in 100% zoom view at its real size. -- You are receiving this mail because: You are watching all bug changes.
[killbots] [Bug 363005] Killbots score not being saved
https://bugs.kde.org/show_bug.cgi?id=363005 Frederik Schwarzer changed: What|Removed |Added CC||schwar...@kde.org --- Comment #3 from Frederik Schwarzer --- Interesting. For me the score is always 30 and it's always this one entry, so no new highscore entries are added. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362991] Undesired empty space appears in panel layout
https://bugs.kde.org/show_bug.cgi?id=362991 Eike Hein changed: What|Removed |Added Component|Task Manager|Panel Summary|Task manager is filled with |Undesired empty space |empty space when a dialog |appears in panel layout |or window is opened | Assignee|h...@kde.org|plasma-b...@kde.org --- Comment #4 from Eike Hein --- Nothing to do with the Task Manager then, reassigning to Panel. -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 356326] Code in kdenetwork is licensed under the non-free ARTISTIC license.
https://bugs.kde.org/show_bug.cgi?id=356326 Jonathan Riddell changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #13 from Jonathan Riddell --- Copyright holders confirm it can be changed so committed that change -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 363012] New: Baloo crashed on logging into an account
https://bugs.kde.org/show_bug.cgi?id=363012 Bug ID: 363012 Summary: Baloo crashed on logging into an account Product: Baloo Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: m...@vhanda.in Reporter: johngeoffreywal...@icloud.com CC: pinak.ah...@gmail.com Application: baloo_file (5.21.0) Qt Version: 5.5.1 Operating System: Linux 4.1.20-11-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Logging on. This has happened the last few times I have done this. The crash can be reproduced every time. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd6eebde780 (LWP 8282))] Thread 2 (Thread 0x7fd5a3739700 (LWP 8297)): #0 0x7fd6ec6eebbd in poll () at /lib64/libc.so.6 #1 0x7fd6e912de64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fd6e912df7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fd6ed31cd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fd6ed2c3d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x0041531b in () #6 0x7fd6ed0e7382 in () at /usr/lib64/libQt5Core.so.5 #7 0x7fd6ed0ea32f in () at /usr/lib64/libQt5Core.so.5 #8 0x7fd6eb7290a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fd6ec6f6fed in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fd6eebde780 (LWP 8282)): [KCrash Handler] #6 0x7fd6ec6a1d79 in __memcpy_sse2_unaligned () at /lib64/libc.so.6 #7 0x7fd6ed9b8535 in Baloo::IdTreeDB::get(unsigned long long) () at /usr/lib64/libKF5BalooEngine.so.5 #8 0x7fd6ed9b5dc0 in Baloo::DocumentUrlDB::getId(unsigned long long, QByteArray const&) const () at /usr/lib64/libKF5BalooEngine.so.5 #9 0x7fd6ed9c7949 in Baloo::Transaction::documentId(QByteArray const&) const () at /usr/lib64/libKF5BalooEngine.so.5 #10 0x0041d453 in () #11 0x0041d50d in () #12 0x7fd6ed2f573f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #13 0x00427145 in () #14 0x0041b6f6 in () #15 0x7fd6ed2f573f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #16 0x7fd6ed302f22 in QTimer::timerEvent(QTimerEvent*) () at /usr/lib64/libQt5Core.so.5 #17 0x7fd6ed2f68bc in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #18 0x7fd6ed2c618d in QCoreApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #19 0x7fd6ed2c5e95 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #20 0x7fd6ed31c77d in QTimerInfoList::activateTimers() () at /usr/lib64/libQt5Core.so.5 #21 0x7fd6ed31cad9 in () at /usr/lib64/libQt5Core.so.5 #22 0x7fd6e912dc84 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #23 0x7fd6e912ded8 in () at /usr/lib64/libglib-2.0.so.0 #24 0x7fd6e912df7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #25 0x7fd6ed31cd6c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #26 0x7fd6ed2c3d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #27 0x7fd6ed2cb8f6 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #28 0x0040a832 in () #29 0x7fd6ec633b05 in __libc_start_main () at /lib64/libc.so.6 #30 0x0040a9a8 in _start () Possible duplicates by query: bug 355876, bug 355633, bug 355371. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[killbots] [Bug 363005] Killbots score not being saved
https://bugs.kde.org/show_bug.cgi?id=363005 Frederik Schwarzer changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/kill ||bots/6e8797c26327dc7eb50246 ||a3d9356a42db540ba8 --- Comment #4 from Frederik Schwarzer --- Git commit 6e8797c26327dc7eb50246a3d9356a42db540ba8 by Frederik Schwarzer. Committed on 13/05/2016 at 10:09. Pushed by schwarzer into branch 'Applications/16.04'. Fix adding high scored. Find out later why that line broke adding high scores. Thanks José for the report. M +2-1mainwindow.cpp http://commits.kde.org/killbots/6e8797c26327dc7eb50246a3d9356a42db540ba8 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 362898] KWin Zoom seems to "forget" settings
https://bugs.kde.org/show_bug.cgi?id=362898 --- Comment #8 from Daniel <86d...@gmail.com> --- Restarting kwin shows a few errors like these> QMetaProperty::read: Unable to handle unregistered datatype 'KWayland::Server::SurfaceInterface*' for property 'KWin::Toplevel::surface' QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1656, resource id: 0, major code: 14 (GetGeometry), minor code: 0 QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1657, resource id: 0, major code: 14 (GetGeometry), minor code: 0 QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1658, resource id: 0, major code: 14 (GetGeometry), minor code: 0 I don't know whether they have anything to do with Zoom, but looking at the code it would make sense if the xcb_xfixes_get_cursor_image call fails - it is the only place where I see the tracking being explicitly set to proportional again. Why is this done? -- You are receiving this mail because: You are watching all bug changes.
[killbots] [Bug 363005] Killbots score not being saved
https://bugs.kde.org/show_bug.cgi?id=363005 Frederik Schwarzer changed: What|Removed |Added Latest Commit|http://commits.kde.org/kill |http://commits.kde.org/kill |bots/6e8797c26327dc7eb50246 |bots/b4c72a3229c882115c9c5c |a3d9356a42db540ba8 |0bfb54f5503156b28e --- Comment #5 from Frederik Schwarzer --- Git commit b4c72a3229c882115c9c5c0bfb54f5503156b28e by Frederik Schwarzer. Committed on 13/05/2016 at 10:15. Pushed by schwarzer into branch 'master'. Fix adding high scored. Find out later why that line broke adding high scores. Thanks José for the report. M +2-1mainwindow.cpp http://commits.kde.org/killbots/b4c72a3229c882115c9c5c0bfb54f5503156b28e -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 363013] New: Automatic brackets does not add a closing }
https://bugs.kde.org/show_bug.cgi?id=363013
Bug ID: 363013
Summary: Automatic brackets does not add a closing }
Product: frameworks-ktexteditor
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: kwrite-bugs-n...@kde.org
Reporter: massimo.burch...@gmx.de
This is kdevelop 4.90.91 and frameworks-ktexteditor 5.21.0:
[x] Enable automatic brackets
..is enabled.
But opening if () { does not add a closing } as before the updates.
However starting with if_ adds a () which is new but not possible to configure.
Reproducible: Always
Steps to Reproduce:
1. type iftrue){
2.
3.
Actual Results:
Nothing
Expected Results:
Closing } bracket
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 363003] opening png doesn't work
https://bugs.kde.org/show_bug.cgi?id=363003 --- Comment #5 from Boudewijn Rempt --- Hm, that's strange, I just tried the same build on my win7 desktop and my test png file loaded correctly. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363003] opening png doesn't work
https://bugs.kde.org/show_bug.cgi?id=363003 Raghavendra kamath changed: What|Removed |Added CC||raghavendr.ra...@gmail.com --- Comment #6 from Raghavendra kamath --- On linux I can open any png just fine i am on arch linux nvidia 750 ti (proprietary drivers) with opengl 'on' @ n1k0l4 if possible can you upload the png that doesn't open for you? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 347794] landscape A3 page incorrectly scaled down to printout A4 paper size
https://bugs.kde.org/show_bug.cgi?id=347794 --- Comment #5 from Burkhard Lueck --- (In reply to Björn Bidar from comment #4) > I think I have read something wrong, A3 printing works wrong it always > prints as a4. A3 printing works (landscape or portrait) for me in all combinations, printing to an A4 printer, printing to an A3 printer with A3 output and A4 output depending on my selection in the print dialog -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363003] opening png doesn't work
https://bugs.kde.org/show_bug.cgi?id=363003 --- Comment #7 from n1k0l4 --- @Raghavendra kamath sure.. But I can't open any kind of png... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363003] opening png doesn't work
https://bugs.kde.org/show_bug.cgi?id=363003 --- Comment #8 from n1k0l4 --- Created attachment 98945 --> https://bugs.kde.org/attachment.cgi?id=98945&action=edit png -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358719] fcitx creates blank unusable xembed icon in systray
https://bugs.kde.org/show_bug.cgi?id=358719 Sergio changed: What|Removed |Added CC||sergio.calleg...@gmail.com --- Comment #10 from Sergio --- Similar issue on Kubuntu 16.04, that ships with plasma 5.5.5. Hence plasma 5.5 does not solve the issue. Please reopen. At times the icons do not appear, at times they appear but still they are not functional (i.e. clicking on them does nothing). The issue seems to be fully repeatable with jitsi (the java based voip client), see https://jitsi.org/. Jitsi should make the problem easy to reproduce since it has packages ready for most distros and logs a lot of information. Among the information provided by the jitsi log you always find complaints about the systray that did not init properly. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363014] New: Crash on starting next line of artistic text
https://bugs.kde.org/show_bug.cgi?id=363014 Bug ID: 363014 Summary: Crash on starting next line of artistic text Product: krita Version: 3.0 Beta Platform: Debian testing URL: http://files.kde.org/krita/3/linux/devbuilds/krita-3.0 -Beta-master-562442e-x86_64.appimage OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Text Tool Assignee: krita-bugs-n...@kde.org Reporter: r...@rkfg.me Krita crashes after entering first character on the second line. Reproducible: Always Steps to Reproduce: 1. Create a new document 2. Add artistic text, type anything and press Enter 3. Press any key while the cursor is at the second line Actual Results: Krita crashes immediately Expected Results: The text should be displayed correctly on several lines. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363003] opening png doesn't work
https://bugs.kde.org/show_bug.cgi?id=363003 --- Comment #9 from n1k0l4 --- one test: I try to open the attached png with gimp, and then exported... it works :) So, is this kind of png the problem? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 347794] landscape A3 page incorrectly scaled down to printout A4 paper size
https://bugs.kde.org/show_bug.cgi?id=347794 --- Comment #6 from Björn Bidar --- Hm this is weird, i was using the kf5 version. Maybe there's a bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362675] Krita crashed while saving [ probably due to trigger of autosave while save]
https://bugs.kde.org/show_bug.cgi?id=362675 Dmitry Kazakov changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED Latest Commit|http://commits.kde.org/krit |http://commits.kde.org/krit |a/5ab2ed2f7b19d8be57f9408f8 |a/1082ada7268ef49c4acf5d717 |8614c282f0abaa0 |075a63c0d3bdb12 --- Comment #4 from Dmitry Kazakov --- Git commit 1082ada7268ef49c4acf5d717075a63c0d3bdb12 by Dmitry Kazakov. Committed on 13/05/2016 at 11:12. Pushed by dkazakov into branch 'master'. Fix some crashes/inconsistencies while saving the document 1) Deny double entry into the saving process 2) Don't try to save if the user has closed the waiting progress dialog. Otherwise it may cause a crash. 3) Make the saving progress bar modal. Otherwise it hides behind Krita window and the user sees a locked-up canvas. Fixes T2430 M +5-4libs/global/kis_global.h M +4-4libs/ui/KisDocument.cpp M +19 -0libs/ui/KisMainWindow.cpp M +4-1libs/ui/dialogs/kis_delayed_save_dialog.cpp M +1-1libs/ui/kis_async_action_feedback.cpp http://commits.kde.org/krita/1082ada7268ef49c4acf5d717075a63c0d3bdb12 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363003] opening png doesn't work
https://bugs.kde.org/show_bug.cgi?id=363003 --- Comment #10 from Raghavendra kamath --- @ n1k0l4 thank you for sharing the file. I can reproduce the bug with your file I logged in on a spare windows 10 machine and i could open pngs in my system , i also tried with png downloaded from internet ( ex: this one -> https://en.wikipedia.org/wiki/Portable_Network_Graphics#/media/File:PNG_transparency_demonstration_1.png) you can try it too. However when I open the png provided by you I get the same screen as you , so in a way I can reproduce the bug on windows 10 as stated by you but only with your file. Thank you for sharing the file once again , i'll try to open it in linux version of krita -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] I cannot set my short date to YYYY-MM-DD, nor my time to HH:MM
https://bugs.kde.org/show_bug.cgi?id=340982 --- Comment #68 from EMR_Kde --- ping? -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 363015] New: informal runtime requirements
https://bugs.kde.org/show_bug.cgi?id=363015
Bug ID: 363015
Summary: informal runtime requirements
Product: plasma-integration
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: mgraess...@kde.org
Reporter: sit...@kde.org
cmakelists has this:
> message("** plasma-integration uses Noto Sans
> (https://www.google.com/get/noto/) and Oxygen Mono
> (http://download.kde.org/stable/plasma/5.4.0/oxygen-fonts-5.4.0.tar.xz)
> fonts, ensure these are installed for use at runtime")
what it should do is find declare them RUNTIME features or packages such that
feature_summary() reports them in the standard format. Unless a human reads
this message it won't ever be noticed (and given distributions package some 300
tarballs once a month that is terribly unlikely)
Reproducible: Always
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 362445] Lags while drawing circular shapes (bended lines on Windows!)
https://bugs.kde.org/show_bug.cgi?id=362445 Raghavendra kamath changed: What|Removed |Added CC||raghavendr.ra...@gmail.com --- Comment #7 from Raghavendra kamath --- I don't get the jagged edges while using the dynamic brush but I get them when using the freehand brush tool. I used exact same settings given by you. I am also attaching the output I am using wacom intuos4 medium on windows 10, I am using the latest builds from kickstarter announcement -> http://files.kde.org/krita/3/windows/devbuilds/krita-3.0-Beta-master-d330a4a-x64.zip I have nvidia 750ti graphic card -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362445] Lags while drawing circular shapes (bended lines on Windows!)
https://bugs.kde.org/show_bug.cgi?id=362445 --- Comment #8 from Raghavendra kamath --- Created attachment 98946 --> https://bugs.kde.org/attachment.cgi?id=98946&action=edit test lines with wacom -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360300] remove panel setting menu at each panel widget
https://bugs.kde.org/show_bug.cgi?id=360300 andreas changed: What|Removed |Added Flags||Usability+ --- Comment #2 from andreas --- burger menu means in every application you can configure something so why the user should right click to the task manager to change the panel? If you want to offer to configure the panel from each widget than the panel options are missing when right click to the system tray. I only think it is confusing more than it helps. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360297] task manager right click more actions from window decoration
https://bugs.kde.org/show_bug.cgi?id=360297 andreas changed: What|Removed |Added Flags||Usability+ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360293] Improve Task Manager context menu
https://bugs.kde.org/show_bug.cgi?id=360293 andreas changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360995] task manager review
https://bugs.kde.org/show_bug.cgi?id=360995 andreas changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |LATER -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 360643] Dolphin doesn't obey time/date settings in "Formats" (Sys settings)
https://bugs.kde.org/show_bug.cgi?id=360643 EMR_Kde changed: What|Removed |Added CC||emre...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361709] With more than 1 curve based assistant, zooming in will black screen part or all of the drawing window
https://bugs.kde.org/show_bug.cgi?id=361709 Raghavendra kamath changed: What|Removed |Added CC||raghavendr.ra...@gmail.com --- Comment #15 from Raghavendra kamath --- I have the exact same card ( nvidia 750 ti 2gb) and I can reproduce the issue on windows 10. I tested with a driver dated 8/7/2015, I'll update the driver and text again , let me know if I can give any logs which may help find the issue more specifically -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360297] task manager right click more actions from window decoration
https://bugs.kde.org/show_bug.cgi?id=360297 Thomas Pfeiffer changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED CC||thomas.pfeif...@kde.org --- Comment #4 from Thomas Pfeiffer --- If even the code agrees that the two should be synced, then they probably should be, both ways ;) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362989] Suggestion: The ability to mirror the content within a selection, both vertically and horizontally
https://bugs.kde.org/show_bug.cgi?id=362989 Raghavendra kamath changed: What|Removed |Added CC||raghavendr.ra...@gmail.com --- Comment #1 from Raghavendra kamath --- +1 for mirroring to be active while drawing inside a selection. If a user has activated mirror or symmetry modes , the portion which he draws inside a selection (marching ants) don't get mirrored. Having this feature will be of great help. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 362898] KWin Zoom seems to "forget" settings
https://bugs.kde.org/show_bug.cgi?id=362898 --- Comment #9 from Martin Gräßlin --- no the pasted errors are not related, they are from GetGeometry calls. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362352] Brush engine scratchpad crashes krita now. (regression in Beta1 due to MinGW)
https://bugs.kde.org/show_bug.cgi?id=362352 Raghavendra kamath changed: What|Removed |Added CC||raghavendr.ra...@gmail.com --- Comment #6 from Raghavendra kamath --- It doesn't crash for me on windows 10 with the latest build -> http://files.kde.org/krita/3/windows/devbuilds/krita-3.0-Beta-master-d330a4a-x64.zip I have nvidia 750 ti i tested with both wacom and mouse -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361709] With more than 1 curve based assistant, zooming in will black screen part or all of the drawing window
https://bugs.kde.org/show_bug.cgi?id=361709 --- Comment #16 from Raghavendra kamath --- Still happens with new graphic drivers (11/5/2015) too -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 362898] KWin Zoom seems to "forget" settings
https://bugs.kde.org/show_bug.cgi?id=362898 --- Comment #10 from Thomas Lübking --- Because it's the only mode where the visual pointer position matches the actual one. If we cannot replace the pointer with an image, we cannot scale it nor show it off-place. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 363016] New: KRDC session disconnects after accessing remote host
https://bugs.kde.org/show_bug.cgi?id=363016 Bug ID: 363016 Summary: KRDC session disconnects after accessing remote host Product: krdc Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: uwol...@kde.org Reporter: jeffhel...@gmail.com I loose connection every time I try connect to my pc within 30secs Its intermittent and sometimes disconnect within 5secs Really frustrating and does this now every time I logon to my remote pc -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 362898] KWin Zoom seems to "forget" settings
https://bugs.kde.org/show_bug.cgi?id=362898 --- Comment #11 from Thomas Lübking --- PS, the warning would show up when the mode resets, not when restarting KWin. You may also need to explicitly enable effects debug out, but I don't see the string for the category, ie. it's probably not configurable at all? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 362898] KWin Zoom seems to "forget" settings
https://bugs.kde.org/show_bug.cgi?id=362898 --- Comment #12 from Daniel <86d...@gmail.com> --- Thanks, I see. To preserve the tracking mode, could we instead use the previous cursor image if the call to get a new one fails? I have no idea why the call would fail, but if it succeeds again soon thereafter, a few frames with the "incorrect" cursor image would be less of a problem than reverting to proportional tracking. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361709] With more than 1 curve based assistant, zooming in will black screen part or all of the drawing window
https://bugs.kde.org/show_bug.cgi?id=361709 --- Comment #17 from Raghavendra kamath --- I can reproduce this in linux too with latest nvidia proprietary graphic drivers -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 274931] Windows with no border (decoration) are visible on all activities
https://bugs.kde.org/show_bug.cgi?id=274931 --- Comment #35 from TOM Harrison --- I am now kde4 is simply remove the !noborder in if XD -- You are receiving this mail because: You are watching all bug changes.
[phonon-backend-gstreamer] [Bug 334421] amarok will increase the memory usage after long time music switch
https://bugs.kde.org/show_bug.cgi?id=334421 --- Comment #9 from TOM Harrison --- ii phonon-backend-gstreamer:amd64 4:4.7.80-0ubuntu2~ubuntu14.04 amd64Phonon GStreamer 1.0.x backend ii phonon-backend-gstreamer-common:amd644:4.7.80-0ubuntu2~ubuntu14.04 amd64Phonon GStreamer 1.0.x backend icons ii phonon-backend-gstreamer1.0 4:4.7.80-0ubuntu2~ubuntu14.04 all transitional package -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 363017] New: Crash on starting wine app
https://bugs.kde.org/show_bug.cgi?id=363017 Bug ID: 363017 Summary: Crash on starting wine app Product: plasmashell Version: 5.5.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: k...@kolivas.org CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.5.0-ck1 x86_64 Distribution: Ubuntu 16.04 LTS -- Information about the crash: - What I was doing when the application crashed: I started a full screen wine app from konsole and the crash occurred immediately after. The app had been run many times before without problems (and still started okay this time) so it may have been unrelated to the crash. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 [Current thread is 1 (Thread 0x7fd80a5eb900 (LWP 23686))] Thread 13 (Thread 0x7fd7f4f7a700 (LWP 23692)): #0 0x7fd804cfae8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fd808dbfc62 in _xcb_conn_wait (__timeout=-1, __nfds=1, __fds=0x7fd7f4f79bc0) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46 #2 0x7fd808dbfc62 in _xcb_conn_wait (c=c@entry=0x22e9730, cond=cond@entry=0x22e9770, vector=vector@entry=0x0, count=count@entry=0x0) at ../../src/xcb_conn.c:459 #3 0x7fd808dc18d7 in xcb_wait_for_event (c=0x22e9730) at ../../src/xcb_in.c:693 #4 0x7fd7f76fa629 in QXcbEventReader::run() (this=0x22f7890) at qxcbconnection.cpp:1253 #5 0x7fd8053f084e in QThreadPrivate::start(void*) (arg=0x22f7890) at thread/qthread_unix.cpp:331 #6 0x7fd8044dd6fa in start_thread (arg=0x7fd7f4f7a700) at pthread_create.c:333 #7 0x7fd804d06b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 12 (Thread 0x7fd7eddbc700 (LWP 23698)): #0 0x7fd804cf69cd in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fd7fd8a7073 in () at /usr/lib/x86_64-linux-gnu/tls/libnvidia-tls.so.361.42 #2 0x7fd801ad36c0 in g_wakeup_acknowledge (__nbytes=16, __buf=0x7fd7eddbbaa0, __fd=) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44 #3 0x7fd801ad36c0 in g_wakeup_acknowledge (wakeup=0x7fd7f00015b0) at /build/glib2.0-t9oPgV/glib2.0-2.48.0/./glib/gwakeup.c:210 #4 0x7fd801a8fe04 in g_main_context_check (context=context@entry=0x7fd7e80009b0, max_priority=2147483647, fds=fds@entry=0x7fd7e8003070, n_fds=n_fds@entry=1) at /build/glib2.0-t9oPgV/glib2.0-2.48.0/./glib/gmain.c:3632 #5 0x7fd801a902c0 in g_main_context_iterate (context=context@entry=0x7fd7e80009b0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-t9oPgV/glib2.0-2.48.0/./glib/gmain.c:3837 #6 0x7fd801a9042c in g_main_context_iteration (context=0x7fd7e80009b0, may_block=may_block@entry=1) at /build/glib2.0-t9oPgV/glib2.0-2.48.0/./glib/gmain.c:3901 #7 0x7fd805627a9b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fd7e80008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #8 0x7fd8055cedea in QEventLoop::exec(QFlags) (this=this@entry=0x7fd7eddbbca0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #9 0x7fd8053eb8a4 in QThread::exec() (this=) at thread/qthread.cpp:503 #10 0x7fd807c933c5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #11 0x7fd8053f084e in QThreadPrivate::start(void*) (arg=0x23f7270) at thread/qthread_unix.cpp:331 #12 0x7fd8044dd6fa in start_thread (arg=0x7fd7eddbc700) at pthread_create.c:333 #13 0x7fd804d06b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 11 (Thread 0x7fd7e3385700 (LWP 23717)): #0 0x7fd804cfae8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fd801a9031c in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7fd7dc002e70, timeout=, context=0x7fd7dc000990) at /build/glib2.0-t9oPgV/glib2.0-2.48.0/./glib/gmain.c:4135 #2 0x7fd801a9031c in g_main_context_iterate (context=context@entry=0x7fd7dc000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-t9oPgV/glib2.0-2.48.0/./glib/gmain.c:3835 #3 0x7fd801a9042c in g_main_context_iteration (context=0x7fd7dc000990, may_block=may_block@entry=1) at /build/glib2.0-t9oPgV/glib2.0-2.48.0/./glib/gmain.c:3901 #4 0x7fd805627a9b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fd7dc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7fd8055cedea in QEventLoop::exec(QFlags) (this=this@entry=0x7fd7e3384ca0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7fd8053eb8a4 in QThread::exec() (this=) at thread/qthread.cpp:503 #7 0x7fd807c933c5 in () at /usr/lib/x86_64-
[plasmashell] [Bug 363018] New: Wallpaper and widgets hidden after login when EGL is selected for OpenGL Interface
https://bugs.kde.org/show_bug.cgi?id=363018 Bug ID: 363018 Summary: Wallpaper and widgets hidden after login when EGL is selected for OpenGL Interface Product: plasmashell Version: 5.6.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ebre...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org When I log in using SDDM The task bar appears, but no widgets. I can run applications via Krunner, or through Kicker, and everything pretty much works. However, the wallpaper is the splash from SDDM. To restore functionality, I can disable and enable the compositor, or switch to GLX as the OpenGL interface. Selecting GLX removes the issue completely. Reproducible: Always Steps to Reproduce: 1. Log in normally 2. After splash screen loads, wallpaper looks like KDE splash screen, including the progress bar 3. No widgets appear, e.g. folder view Actual Results: Wallpaper appears t be KDE splash screen Expected Results: Normal desktop should appear, including all widgets Work around is to choose GLX instead of EGL. I am using intel processor and graphisc. Output of lcpci: linux-azyr:~ # lspci 00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 5500 (rev 09) 00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09) 00:04.0 Signal processing controller: Intel Corporation Broadwell-U Processor Thermal Subsystem (rev 09) 00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI Controller (rev 03) 00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI Controller #1 (rev 03) 00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #3 (rev e3) 00:1d.0 USB controller: Intel Corporation Wildcat Point-LP USB EHCI Controller (rev 03) 00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode] (rev 03) 00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03) 00:1f.6 Signal processing controller: Intel Corporation Wildcat Point-LP Thermal Management Controller (rev 03) 01:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59) edward@linux-azyr:~> glxinfo name of display: :0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.4 server glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_swap_control client glx vendor string: Mesa Project and SGI client glx version string: 1.4 client glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync GLX version: 1.4 GLX extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig
[valgrind] [Bug 356675] callgrind test apk in android 5.0.2
https://bugs.kde.org/show_bug.cgi?id=356675 winnie_hx changed: What|Removed |Added Component|callgrind |general -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 362892] test apk in android5.0.2,after fix the bug 344802, android log“Unable to create protected region in stack for implicit overflow check. Reason: Out of memory size: 4096”
https://bugs.kde.org/show_bug.cgi?id=362892 winnie_hx changed: What|Removed |Added Component|callgrind |general -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway
https://bugs.kde.org/show_bug.cgi?id=75324 --- Comment #23 from Jason Straight --- Closing them before suspending isn't that much of a problem, and even waiting for them to timeout isn't compared to the time it takes to mount via fuse ftp/sshfs/cifs.mount, etc so I can use an app like Brackets to edit a remote website, or watch a video with VLC, edit an image with gimp, etc. As much as I would like for all my favorite apps to be native KDE, they just aren't. On the other hand, as feature limited as gnome is, this is one area where they excel and I can use any apps, be they native gnome or not, with their gvfsd solution. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363019] New: Krita doesn't open Canon raw files (CR2)
https://bugs.kde.org/show_bug.cgi?id=363019 Bug ID: 363019 Summary: Krita doesn't open Canon raw files (CR2) Product: krita Version: 3.0 Beta Platform: Mac OS X Disk Images OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: scl.gp...@gmail.com Krita offers to open CR2 files, but at the end if fails with error "Could not open file: ... Reason: Unknown file type." Sometimes after that all menu items are disabled so I can't even close Krita properly and have to kill it from the OS X application menu bar. Reproducible: Always Steps to Reproduce: 1. File/Open, choose 'All files' or 'Camera raw files', 2. Select the CR2 file to open and confirm. Actual Results: Krita shows the thumbnails not grayed out indicating that the file can be opened. After my attempt to open the file Krita shows an error dialog with the message "Could not open file: Reason: Unknown file type." Sometimes after that all menu items are disabled so I can't even close Krita properly and have to kill it from the OS X application menu bar. Expected Results: Krita shows the thumbnails not grayed out. Krita opens the file. All menu items are enabled or disabled w.r.t. to the program state. Version: krita3-beta1-8ec9263 Operating system: OS X 10.9.5 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 363020] New: Konqueror crash while website loading
https://bugs.kde.org/show_bug.cgi?id=363020 Bug ID: 363020 Summary: Konqueror crash while website loading Product: konqueror Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: raf...@gmail.com Application: konqueror (4.14.18) KDE Platform Version: 4.14.18 Qt Version: 4.8.6 Operating System: Linux 4.1.20-11-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: Konqueror crashed while opening wikipedia website. This error is repetable on other websites The crash can be reproduced sometimes. -- Backtrace: Application: Konqueror (konqueror), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5319d83780 (LWP 2663))] Thread 5 (Thread 0x7f52f60a9700 (LWP 3470)): #0 0x7f531865303f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f52fb092eb6 in WTF::TCMalloc_PageHeap::scavengerThread() () at /usr/lib64/libQtWebKit.so.4 #2 0x7f52fb092ee9 in () at /usr/lib64/libQtWebKit.so.4 #3 0x7f531864f0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f531733ffed in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f5303605700 (LWP 3472)): #0 0x7f5317337bbd in poll () at /lib64/libc.so.6 #1 0x7f5314447e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f5314447f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f5318a13fde in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #4 0x7f53189e5d4f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #5 0x7f53189e6045 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7f53188e34df in QThread::exec() () at /usr/lib64/libQtCore.so.4 #7 0x7f53188e5bbf in () at /usr/lib64/libQtCore.so.4 #8 0x7f531864f0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f531733ffed in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f52b58a6700 (LWP 3474)): #0 0x7f531865303f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f52fae05b3d in JSC::BlockAllocator::blockFreeingThreadMain() () at /usr/lib64/libQtWebKit.so.4 #2 0x7f52fb0baa06 in WTF::wtfThreadEntryPoint(void*) () at /usr/lib64/libQtWebKit.so.4 #3 0x7f531864f0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f531733ffed in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f52a700 (LWP 3624)): #0 0x7f53186533e8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f53188e6084 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQtCore.so.4 #2 0x7f53188d9bda in () at /usr/lib64/libQtCore.so.4 #3 0x7f53188e5bbf in () at /usr/lib64/libQtCore.so.4 #4 0x7f531864f0a4 in start_thread () at /lib64/libpthread.so.0 #5 0x7f531733ffed in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f5319d83780 (LWP 2663)): [KCrash Handler] #6 0x7f52fad093a7 in QtMIMETypeSniffer::~QtMIMETypeSniffer() () at /usr/lib64/libQtWebKit.so.4 #7 0x7f52f9ce1a5c in WebCore::JSNodeOwner::isReachableFromOpaqueRoots(JSC::Handle, void*, JSC::SlotVisitor&) () at /usr/lib64/libQtWebKit.so.4 #8 0x7f52fae04a9a in JSC::WeakBlock::visit(JSC::HeapRootVisitor&) () at /usr/lib64/libQtWebKit.so.4 #9 0x7f52fae1233b in JSC::MarkedSpace::visitWeakSets(JSC::HeapRootVisitor&) () at /usr/lib64/libQtWebKit.so.4 #10 0x7f52fae07785 in JSC::Heap::markRoots(bool) () at /usr/lib64/libQtWebKit.so.4 #11 0x7f52fae09355 in JSC::Heap::collect(JSC::Heap::SweepToggle) () at /usr/lib64/libQtWebKit.so.4 #12 0x7f52fafdc872 in JSC::DefaultGCActivityCallback::doWork() () at /usr/lib64/libQtWebKit.so.4 #13 0x7f52fae0c3bd in JSC::HeapTimer::timerEvent(QTimerEvent*) () at /usr/lib64/libQtWebKit.so.4 #14 0x7f53189ff2b1 in QObject::event(QEvent*) () at /usr/lib64/libQtCore.so.4 #15 0x7f5317b6479c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #16 0x7f5317b6acdd in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #17 0x7f5319786e9a in KApplication::notify(QObject*, QEvent*) () at /usr/lib64/libkdeui.so.5 #18 0x7f53189e718d in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQtCore.so.4 #19 0x7f5318a16bbc in () at /usr/lib64/libQtCore.so.4 #20 0x7f5318a13e01 in () at /usr/lib64/libQtCore.so.4 #21 0x7f5314447c84 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #22 0x7f5314447ed8 in () at /usr/lib64/libglib-2.0.so.0 #23 0x7f5314447f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #24 0x7f5318a13fbe in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so
[kio] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway
https://bugs.kde.org/show_bug.cgi?id=75324 --- Comment #22 from Jason Straight --- Closing them before suspending isn't that much of a problem, and even waiting for them to timeout isn't compared to the time it takes to mount via fuse ftp/sshfs/cifs.mount, etc so I can use an app like Brackets to edit a remote website, or watch a video with VLC, edit an image with gimp, etc. As much as I would like for all my favorite apps to be native KDE, they just aren't. On the other hand, as feature limited as gnome is, this is one area where they excel and I can use any apps, be they native gnome or not, with their gvfsd solution. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 356675] callgrind test apk in android 5.0.2
https://bugs.kde.org/show_bug.cgi?id=356675 --- Comment #3 from winnie_hx --- Sorry,I think it's my fault,this problem must be in the core of valgrind ,i have modified it to "general".And Thank you very much! At 2016-05-12 20:02:23, "Josef Weidendorfer via KDE Bugzilla" wrote: >https://bugs.kde.org/show_bug.cgi?id=356675 > >--- Comment #2 from Josef Weidendorfer --- >Can you provide the complete output of the crash? >As the patch is about VG core stuff, I assume the crash also happens with other >VG tools? >If so, It seems better to re-assign this to "general" component. > >-- >You are receiving this mail because: >You are on the CC list for the bug. >You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363019] Krita doesn't open Canon raw files (CR2)
https://bugs.kde.org/show_bug.cgi?id=363019 --- Comment #1 from Boudewijn Rempt --- Can you attach a sample file? It should work, but I haven't got access to a camera which can produce raw files. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 362994] middle click to close, in titlebar -passes click to whatever below
https://bugs.kde.org/show_bug.cgi?id=362994 --- Comment #9 from Allan --- (In reply to Thomas Lübking from comment #8) > press, close move, paste? that's incredibly odd - the move would at least > have to generate a release then... > > running klipper process or plasmoid? still a problem when quitting those? No klipper. Also - this is the behaviour straight out of the box no addons or strange setups -you should be able to reproduce it easily just by following the steps to reproduce in the op. I certainly can on any computer with any mouse (with 2 buttons and a scroll wheel) and any recent kde5 I can remember (sorry I first got around to reporting the bugs now). -- You are receiving this mail because: You are watching all bug changes.
