[krunner] [Bug 374758] New: Krunner crash after few keys input
https://bugs.kde.org/show_bug.cgi?id=374758 Bug ID: 374758 Summary: Krunner crash after few keys input Product: krunner Version: 5.5.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: laurent.poin...@laposte.net Target Milestone: --- Application: krunner (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.4.0-57-generic x86_64 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: Typing pyzo to locate/start it, Krunner crashed after pyz (but has completed to pyzo in the field). The crash can be reproduced every time. -- Backtrace: Application: krunner (krunner), signal: Aborted 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 0x7fa3156828c0 (LWP 2309))] Thread 12 (Thread 0x7fa2d97fa700 (LWP 4267)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fa3127d4a5b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x1d623b0) at thread/qwaitcondition_unix.cpp:136 #2 QWaitCondition::wait (this=, mutex=0x11a33a0, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #3 0x7fa2ef31c50b in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked (this=this@entry=0x13dcd90, th=) at ../../src/weaver.cpp:594 #4 0x7fa2ef31d2bf in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x13dcd90, th=th@entry=0x7fa2d4003190, threadWasBusy=threadWasBusy@entry=false, suspendIfInactive=suspendIfInactive@entry=false, justReturning=justReturning@entry=false) at ../../src/weaver.cpp:554 #5 0x7fa2ef3214e8 in ThreadWeaver::WorkingHardState::applyForWork (this=0x1d62690, th=0x7fa2d4003190, wasBusy=) at ../../src/workinghardstate.cpp:66 #6 0x7fa2ef31c46d in ThreadWeaver::Weaver::applyForWork (this=, th=0x7fa2d4003190, wasBusy=) at ../../src/weaver.cpp:568 #7 0x7fa2ef321542 in ThreadWeaver::WorkingHardState::applyForWork (this=0x1d62690, th=0x7fa2d4003190, wasBusy=) at ../../src/workinghardstate.cpp:73 #8 0x7fa2ef31c46d in ThreadWeaver::Weaver::applyForWork (this=, th=0x7fa2d4003190, wasBusy=) at ../../src/weaver.cpp:568 #9 0x7fa2ef31f353 in ThreadWeaver::Thread::run (this=0x7fa2d4003190) at ../../src/thread.cpp:103 #10 0x7fa3127d37be in QThreadPrivate::start (arg=0x7fa2d4003190) at thread/qthread_unix.cpp:331 #11 0x7fa31032d6ba in start_thread (arg=0x7fa2d97fa700) at pthread_create.c:333 #12 0x7fa3120e982d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 11 (Thread 0x7fa2d9ffb700 (LWP 4266)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fa3127d4a5b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x1d623b0) at thread/qwaitcondition_unix.cpp:136 #2 QWaitCondition::wait (this=, mutex=0x11a33a0, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #3 0x7fa2ef31c50b in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked (this=this@entry=0x13dcd90, th=) at ../../src/weaver.cpp:594 #4 0x7fa2ef31d2bf in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x13dcd90, th=th@entry=0x7fa2dc002990, threadWasBusy=threadWasBusy@entry=true, suspendIfInactive=suspendIfInactive@entry=false, justReturning=justReturning@entry=false) at ../../src/weaver.cpp:554 #5 0x7fa2ef3214e8 in ThreadWeaver::WorkingHardState::applyForWork (this=0x1d62690, th=0x7fa2dc002990, wasBusy=) at ../../src/workinghardstate.cpp:66 #6 0x7fa2ef31c46d in ThreadWeaver::Weaver::applyForWork (this=, th=0x7fa2dc002990, wasBusy=) at ../../src/weaver.cpp:568 #7 0x7fa2ef31f353 in ThreadWeaver::Thread::run (this=0x7fa2dc002990) at ../../src/thread.cpp:103 #8 0x7fa3127d37be in QThreadPrivate::start (arg=0x7fa2dc002990) at thread/qthread_unix.cpp:331 #9 0x7fa31032d6ba in start_thread (arg=0x7fa2d9ffb700) at pthread_create.c:333 #10 0x7fa3120e982d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 10 (Thread 0x7fa2da7fc700 (LWP 4265)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fa3127d4a5b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x1d623b0) at thread/qwaitcondition_unix.cpp:136 #2 QWaitCondition::wait (this=, mutex=0x11a33a0, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #3 0x7fa2ef31c50b in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked (this=this@entry=0x13dcd90, th=) at ../../src/weaver.cpp:594 #4 0x7fa2ef31d2bf in
[QtCurve] [Bug 374568] Applications crash when menu bar is accessed
https://bugs.kde.org/show_bug.cgi?id=374568 --- Comment #22 from RJVB--- Re: alignment: you could compare the function addresses, i.e. event in HackedMenu::send() (printing that will also teach us which function call takes the hyperjump) vs. static_cast (menu)->event -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 374568] Applications crash when menu bar is accessed
https://bugs.kde.org/show_bug.cgi?id=374568 --- Comment #21 from RJVB--- I have nothing against your initial explicit cast to a QObject*, what about you Yichao? I do think this has to be reported to GCC though. I think the vptr warning is more a bad-semantics-practice warning than one about something that could cause a crash like you're seeing. Although: I don't know about C-style casting to a different class, but casting to a *non packed* struct might let you run into issues caused by different alignment. And *that* could explain the jump into the unknown. Anyway, bug or feature, in the end this is probably something that only people intimately familiar with GCC's internals might be able to explain. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374689] desktop settings - wallpapers disappear
https://bugs.kde.org/show_bug.cgi?id=374689 Kai Uwe Broulikchanged: What|Removed |Added Latest Commit||https://commits.kde.org/pla ||sma-workspace/f6ce91499a16c ||d9e8fa4b56fdadf254e3ab79bd1 Resolution|--- |FIXED Version Fixed In||5.9.0 Status|CONFIRMED |RESOLVED --- Comment #3 from Kai Uwe Broulik --- Git commit f6ce91499a16cd9e8fa4b56fdadf254e3ab79bd1 by Kai Uwe Broulik. Committed on 08/01/2017 at 15:12. Pushed by broulik into branch 'master'. [Image Wallpaper] Simplify width/height management Directly expose "targetSize" as property. The wallpaper is already initialized with the correct size for some time now but the fact that we had two properties width and height in there had it still do unneccessary work when it emitted "sizeChanged(2560, 0)" and then the final "sizeChanged(2560, 1440)" afterwards. Also, I didn't really see a point in storing the wallpaper size in its config, it's overwritten by the wallpaper anyway and only used in the wallpaper config dialog for the aspect ratio. We can just ask the view directly then. FIXED-IN: 5.9.0 Differential Revision: https://phabricator.kde.org/D4001 M +3-29 wallpapers/image/image.cpp M +2-11 wallpapers/image/image.h M +0-8wallpapers/image/imagepackage/contents/config/main.xml M +2-3wallpapers/image/imagepackage/contents/ui/config.qml M +1-14 wallpapers/image/imagepackage/contents/ui/main.qml M +0-8wallpapers/image/slideshowpackage/contents/config/main.xml https://commits.kde.org/plasma-workspace/f6ce91499a16cd9e8fa4b56fdadf254e3ab79bd1 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 354508] Support GMail's XOAUTH authentication method
https://bugs.kde.org/show_bug.cgi?id=354508 Daniel Vrátilchanged: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Version Fixed In||5.5.0 Latest Commit||https://commits.kde.org/kde ||pim-runtime/ca4b3f0907b5cbf ||77a7f081bcd41f328ad066c54 --- Comment #3 from Daniel Vrátil --- Git commit ca4b3f0907b5cbf77a7f081bcd41f328ad066c54 by Daniel Vrátil. Committed on 08/01/2017 at 15:11. Pushed by dvratil into branch 'master'. IMAP: add support for native GMail OAuth authentication This change adds support for XOAUTH2 authentication method used by Gmail to the IMAP resource. The XOAUTH2 support is implemented in a custom SASL plugin. The token request/refresh is done via KGAPI. When user sets imap.gmail.com as IMAP server in the resource config dialog, the dialog automatically sets all the configuration to match the one of Gmail and selects XOAUTH2 as authentication method. The access and refresh tokens are stored in KWallet like a regular password, but a special PasswordRequesterInterface implementation is used to handle the tokens and pass the right data to KIMAP::LoginJob. With this change it's no longer necessary to have the "Allow less secure apps" option enabled in Google Account settings and it's no longer necessary to use app-specific password for accounts with two-step verification (2FA) enabled. The actual password is no longer stored in KWallet and has only be typed into Google Auth form once. FIXED-IN: 5.5.0 CHANGELOG: Implement native Gmail authentication into IMAP resource M +21 -1resources/imap/CMakeLists.txt A +1-0resources/imap/config.h.cmake A +141 -0resources/imap/gmailpasswordrequester.cpp [License: LGPL (v2+)] C +20 -23 resources/imap/gmailpasswordrequester.h [from: resources/imap/settingspasswordrequester.h - 051% similarity] M +13 -1resources/imap/imapresource.cpp A +67 -0resources/imap/passwordrequester.cpp [License: LGPL (v2+)] A +44 -0resources/imap/passwordrequester.h [License: LGPL (v2+)] M +1-0resources/imap/resourcestate.cpp A +24 -0resources/imap/saslplugin/CMakeLists.txt A +579 -0resources/imap/saslplugin/config.h [License: GENERATED FILE] * A +969 -0resources/imap/saslplugin/plugin_common.c [License: UNKNOWN] * A +221 -0resources/imap/saslplugin/plugin_common.h [License: UNKNOWN] * A +246 -0resources/imap/saslplugin/xoauth2plugin.c [License: LGPL (v2+)] A +53 -0resources/imap/saslplugin/xoauth2plugin_init.c [License: LGPL (v2+)] M +5-27 resources/imap/settings.cpp M +1-2resources/imap/settings.h M +24 -1resources/imap/settingspasswordrequester.cpp M +2-0resources/imap/settingspasswordrequester.h M +41 -6resources/imap/setupserver.cpp M +1-0resources/imap/setupserver.h A +32 -0resources/imap/utils.cpp [License: LGPL (v2+)] A +32 -0resources/imap/utils.h [License: LGPL (v2+)] M +8-2resources/imap/wizard/imapwizard.es The files marked with a * at the end have a non valid license. Please read: http://techbase.kde.org/Policies/Licensing_Policy and use the headers which are listed at that page. https://commits.kde.org/kdepim-runtime/ca4b3f0907b5cbf77a7f081bcd41f328ad066c54 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 369147] Regression: Cannot disable delete confirmation any more
https://bugs.kde.org/show_bug.cgi?id=369147 Denis Kurzchanged: What|Removed |Added Version|Git (master)|5.3.3 Resolution|INVALID |--- Status|RESOLVED|UNCONFIRMED --- Comment #8 from Denis Kurz --- dag, I'm sorry, I misread your Comment 3. Your report is of course not invalid. I'd like to set the bug to Confirmed for version 5.3.3, but for some reason, bugzilla doesn't offer 'Confirmed' atm... I set it to Unconfirmed instead. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 374313] wrong icon usage revisited [patch]
https://bugs.kde.org/show_bug.cgi?id=374313 --- Comment #14 from caulier.gil...@gmail.com --- No problem too to get and compile lensfun under MXE in 64 bits... What's your complete trace exactly ? Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 374313] wrong icon usage revisited [patch]
https://bugs.kde.org/show_bug.cgi?id=374313 --- Comment #13 from caulier.gil...@gmail.com --- Simon, No problem for me to get Lensfun tarball and compile it with MXE. See my trace below : [gilles@localhost mxe]$ ./01-build-mxe.sh 01-build-mxe.sh : build a bundle MXE install with digiKam dependencies. --- Target Windows architecture: 32 bits. CPU Cores to use : 7 ... -- Building digiKam 3rd-party dependencies with MXE == Using MXE wrapper: /mnt/devel/GIT/5.x/project/bundles/mxe/build.win32/usr/bin/i686-w64-mingw32.shared-cmake == Using MXE toolchain: /mnt/devel/GIT/5.x/project/bundles/mxe/build.win32/usr/i686-w64-mingw32.shared/share/cmake/mxe-conf.cmake == Using MXE runresult: /mnt/devel/GIT/5.x/project/bundles/mxe/build.win32/usr/share/cmake/modules/TryRunResults.cmake loading initial cache file /mnt/devel/GIT/5.x/project/bundles/mxe/build.win32/usr/share/cmake/modules/TryRunResults.cmake -- The C compiler identification is GNU 4.9.4 -- The CXX compiler identification is GNU 4.9.4 -- Check for working C compiler: /mnt/devel/GIT/5.x/project/bundles/mxe/build.win32/usr/bin/i686-w64-mingw32.shared-gcc -- Check for working C compiler: /mnt/devel/GIT/5.x/project/bundles/mxe/build.win32/usr/bin/i686-w64-mingw32.shared-gcc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Detecting C compile features -- Detecting C compile features - done -- Check for working CXX compiler: /mnt/devel/GIT/5.x/project/bundles/mxe/build.win32/usr/bin/i686-w64-mingw32.shared-g++ -- Check for working CXX compiler: /mnt/devel/GIT/5.x/project/bundles/mxe/build.win32/usr/bin/i686-w64-mingw32.shared-g++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Detecting CXX compile features -- Detecting CXX compile features - done -- CMAKE_GENERATOR: Unix Makefiles -- CMAKE_CL_64: -- -- KF5 component: extra-cmake-modules -- Component version: 5.29 -- Component MD5: dd3e13ee27fb421a9d215fc708ae02b3 -- Configure options: -- Patch to apply : -- -- KF5 component: kconfig -- Component version: 5.29 -- Component MD5: d9686ba5a3b1732236a3dcf3b7d1b4a4 -- Configure options: -- Patch to apply : -- -- KF5 component: breeze-icons -- Component version: 5.29 -- Component MD5: 799c237be7c59ee0a452cea034565f43 -- Configure options: -DBINARY_ICONS_RESOURCE=OFF -- Patch to apply : -- -- KF5 component: solid -- Component version: 5.29 -- Component MD5: f118ab316c536b84500d472c4141f3d7 -- Configure options: -- Patch to apply : -- -- KF5 component: kcoreaddons -- Component version: 5.29 -- Component MD5: f0a3330cd34e3269cd65b65bb465b02c -- Configure options: -- Patch to apply : -- -- KF5 component: threadweaver -- Component version: 5.29 -- Component MD5: 629079e41766c0b40e350287e493e5b1 -- Configure options: -- Patch to apply : -- -- KF5 component: kwindowsystem -- Component version: 5.29 -- Component MD5: e2e4416e793f72cfada80d85dd4e84dc -- Configure options: -- Patch to apply : -- -- KF5 component: karchive -- Component version: 5.29 -- Component MD5: 9a0a1d8e13b45bbed97cf6945eafadff -- Configure options: -- Patch to apply : -- -- KF5 component: kdbusaddons -- Component version: 5.29 -- Component MD5: dceedee3876d1d792995e70466af8977 -- Configure options: -- Patch to apply : -- -- KF5 component: ki18n -- Component version: 5.29 -- Component MD5: 5619f4e80d97c9ee697f0e8b9300d2e3 -- Configure options: -- Patch to apply : -- -- KF5 component: kcrash -- Component version: 5.29 -- Component MD5: d85c85ecfe38a796c3bce4313df8ece7 -- Configure options: -- Patch to apply : -- -- KF5 component: kcodecs -- Component version: 5.29 -- Component MD5: baf7fdef49333280abed66420f741b88 -- Configure options: -- Patch to apply : -- -- KF5
[korganizer] [Bug 317656] Korganizer alert reminders are not reliable (they're lost after logout)
https://bugs.kde.org/show_bug.cgi?id=317656 Denis Kurzchanged: What|Removed |Added Version|5.1.2 |5.3.3 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 369389] tab key does not cycle input fields in right order
https://bugs.kde.org/show_bug.cgi?id=369389 --- Comment #2 from Thomas Baumgart--- That's right. You could simply use the Qt designer to assign the tab order in a graphical manner. Patches are welcome through reviewboard at https://git.reviewboard.kde.org . -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 374757] New: "Devices" entries do not give enough information.
https://bugs.kde.org/show_bug.cgi?id=374757 Bug ID: 374757 Summary: "Devices" entries do not give enough information. Product: dolphin Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: panels: information Assignee: dolphin-bugs-n...@kde.org Reporter: jes...@uh.edu Target Milestone: --- All you get in the devices panel is what kind of drive it is and how big it is when there is much more info available. A right-click menu entry could easily deliver this kind of "get info" data, as it does in nearly every other OS: Device type, mount point, free space, file system type, mount options, etc. If there are many devices they can be difficult to tell apart! -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 374756] New: Help docbook not found
https://bugs.kde.org/show_bug.cgi?id=374756 Bug ID: 374756 Summary: Help docbook not found Product: kmail2 Version: Git (master) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: lu...@hube-lueck.de CC: kde-doc-engl...@kde.org Target Milestone: --- Using Help->KMail Handbook or F1 the docbook for KMail is not found and KHelpcenter displays the "Documentation not found" page. Possible fixes: 1) change the componentname in kaboutdata to kmail ~/src/pim/kmail(trunk)$ git diff src/ diff --git a/src/aboutdata.cpp b/src/aboutdata.cpp index 9c356e5..9a380c9 100644 --- a/src/aboutdata.cpp +++ b/src/aboutdata.cpp @@ -360,7 +360,7 @@ static const about_data credits[] = { }; AboutData::AboutData() -: KAboutData(QStringLiteral("kmail2"), +: KAboutData(QStringLiteral("kmail"), i18n("KMail"), QStringLiteral(KDEPIM_VERSION), i18n("KDE Email Client"), But this maybe have unwanted side effects? 2) Install into subdir kmail2 ~/src/pim/kmail(trunk)$ git diff doc/kmail/CMakeLists.txt diff --git a/doc/kmail/CMakeLists.txt b/doc/kmail/CMakeLists.txt index 381d075..7388d88 100644 --- a/doc/kmail/CMakeLists.txt +++ b/doc/kmail/CMakeLists.txt @@ -1 +1 @@ -kdoctools_create_handbook(index.docbook INSTALL_DESTINATION ${KDE_INSTALL_DOCBUNDLEDIR}/en SUBDIR kmail) +kdoctools_create_handbook(index.docbook INSTALL_DESTINATION ${KDE_INSTALL_DOCBUNDLEDIR}/en SUBDIR kmail2) For this fix the X-DocPath has to be changed as well and we have to "translate" kmail to kmail2 via scripts/documentation_paths or rename the folder doc/kmail to doc/kmail2, so that autogen.sh generates the correct install path for the translated docbooks. -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 374568] Applications crash when menu bar is accessed
https://bugs.kde.org/show_bug.cgi?id=374568 --- Comment #20 from Eugene Shalygin--- GCC 5.4.0 does not crash too, although -fsanitize=vptr prints out the same errors as the version 6.3.0 does. Anyway, since the hack is not needed, let's replace it with a proper cast and QObject::event() call? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341963] After full HDD home/.cache gets corrupted, plasmashell stuck on file locking
https://bugs.kde.org/show_bug.cgi?id=341963 Rex Dieterchanged: What|Removed |Added CC||rdie...@math.unl.edu -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 362856] [Frameworks] Wrong render resolution, possibly caused by Plasma 5 "Scale Display"
https://bugs.kde.org/show_bug.cgi?id=362856 Christoph Cullmannchanged: What|Removed |Added CC||cullm...@kde.org --- Comment #21 from Christoph Cullmann --- I did take a look, IMHO the problem (beside the missing // These attributes must be set before a Q(Gui)Application is constructed. +QCoreApplication::setAttribute(Qt::AA_EnableHighDpiScaling); +QCoreApplication::setAttribute(Qt::AA_UseHighDpiPixmaps); calls) is that the generators render the stuff in a QImage but that has not set the right scale factor nor dimensions. During writing our company PDF helper viewer (https://github.com/AbsInt/FirstAid), I run into the same issue with libpoppler and altered our rendering code to: /** * we render in too high resolution and then set the right ratio */ cachedPage = new QImage(page->renderToImage(resX() * devicePixelRatio(), resY() * devicePixelRatio(), -1, -1, -1, -1, Poppler::Page::Rotate0)); cachedPage->setDevicePixelRatio(devicePixelRatio()); This did the trick, unfortunately Okular is more complex than our toy program therefore I am not that sure where to adjust that :/ -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 374753] no refresh during google photos import
https://bugs.kde.org/show_bug.cgi?id=374753 --- Comment #4 from caulier.gil...@gmail.com --- no. If you use DK Software Collection repository here, and if all dependencies are resolve, DK and kipi-plugins will be compiled and installed. I'm sure, i use it : https://www.digikam.org/download/GIT Take a look in README for more details : https://cgit.kde.org/digikam-software-compilation.git/tree/README Gilles Caulier Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 374753] no refresh during google photos import
https://bugs.kde.org/show_bug.cgi?id=374753 Kusichanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Kusi --- fixed in 374293 *** This bug has been marked as a duplicate of bug 374293 *** -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 374293] Google albums reload button still display albums which have been removed from google photos
https://bugs.kde.org/show_bug.cgi?id=374293 Kusichanged: What|Removed |Added CC||k...@forum.titlis.org --- Comment #2 from Kusi --- *** Bug 374753 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374755] New: KWin crashed immediately after Plasma login
https://bugs.kde.org/show_bug.cgi?id=374755 Bug ID: 374755 Summary: KWin crashed immediately after Plasma login Product: kwin Version: 5.8.4 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: germano.massu...@gmail.com Target Milestone: --- Application: kwin_x11 (5.8.4) Qt Version: 5.7.1 Frameworks Version: 5.27.0 Operating System: Linux 4.8.15-300.fc25.x86_64 x86_64 Distribution: "Fedora release 25 (Twenty Five)" -- Information about the crash: - What I was doing when the application crashed: I logged into Plasma, then I got the Drkonqi crashreport even before the Plasma was completely loaded -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 185 62: movl(%rsp), %edi [Current thread is 1 (Thread 0x7f463ecd1940 (LWP 1418))] Thread 13 (Thread 0x7f46164dd700 (LWP 1944)): #0 0x7f4651eb4460 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f46576fe2f4 in QTWTF::TCMalloc_PageHeap::scavengerThread() (this=0x7f46577ea380 ) at /usr/src/debug/qtscript-opensource-src-5.7.1/src/3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359 #2 0x7f46576fe339 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*) (context=) at /usr/src/debug/qtscript-opensource-src-5.7.1/src/3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464 #3 0x7f4651eae6ca in start_thread (arg=0x7f46164dd700) at pthread_create.c:333 #4 0x7f464f085f7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 12 (Thread 0x7f4616d77700 (LWP 1939)): #0 0x7f4651eb4809 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7f464fc93038 in QWaitConditionPrivate::wait_relative(unsigned long) (time=3, this=0x55d64e7b1800) at thread/qwaitcondition_unix.cpp:133 #2 0x7f464fc93038 in QWaitConditionPrivate::wait(unsigned long) (time=3, this=0x55d64e7b1800) at thread/qwaitcondition_unix.cpp:141 #3 0x7f464fc93038 in QWaitCondition::wait(QMutex*, unsigned long) (this=this@entry=0x55d64ed67900, mutex=mutex@entry=0x55d64e5e8880, time=3) at thread/qwaitcondition_unix.cpp:215 #4 0x7f464fc8fa6d in QThreadPoolThread::run() (this=0x55d64ed678f0) at thread/qthreadpool.cpp:133 #5 0x7f464fc929da in QThreadPrivate::start(void*) (arg=0x55d64ed678f0) at thread/qthread_unix.cpp:368 #6 0x7f4651eae6ca in start_thread (arg=0x7f4616d77700) at pthread_create.c:333 #7 0x7f464f085f7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 11 (Thread 0x7f462700 (LWP 1938)): #0 0x7f4651eb4809 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7f464fc93038 in QWaitConditionPrivate::wait_relative(unsigned long) (time=3, this=0x55d64e5eda50) at thread/qwaitcondition_unix.cpp:133 #2 0x7f464fc93038 in QWaitConditionPrivate::wait(unsigned long) (time=3, this=0x55d64e5eda50) at thread/qwaitcondition_unix.cpp:141 #3 0x7f464fc93038 in QWaitCondition::wait(QMutex*, unsigned long) (this=this@entry=0x55d64e5ebb30, mutex=mutex@entry=0x55d64e5e8880, time=3) at thread/qwaitcondition_unix.cpp:215 #4 0x7f464fc8fa6d in QThreadPoolThread::run() (this=0x55d64e5ebb20) at thread/qthreadpool.cpp:133 #5 0x7f464fc929da in QThreadPrivate::start(void*) (arg=0x55d64e5ebb20) at thread/qthread_unix.cpp:368 #6 0x7f4651eae6ca in start_thread (arg=0x7f462700) at pthread_create.c:333 #7 0x7f464f085f7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 10 (Thread 0x7f4617578700 (LWP 1785)): #0 0x7f4651eb4460 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f462d29445b in cnd_wait (mtx=0x55d64e774758, cond=0x55d64e774780) at ../../../include/c11/threads_posix.h:159 #2 0x7f462d29445b in util_queue_thread_func (input=input@entry=0x55d64e7d69c0) at util/u_queue.c:76 #3 0x7f462d2942b7 in impl_thrd_routine (p=) at ../../../include/c11/threads_posix.h:87 #4 0x7f4651eae6ca in start_thread (arg=0x7f4617578700) at pthread_create.c:333 #5 0x7f464f085f7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 9 (Thread 0x7f4617d79700 (LWP 1784)): #0 0x7f4651eb4460 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f462d29445b in cnd_wait (mtx=0x55d64e774758, cond=0x55d64e774780) at ../../../include/c11/threads_posix.h:159 #2 0x7f462d29445b in util_queue_thread_func
[khotkeys] [Bug 353596] Kcalc should be started when pressing calculator keyboard button
https://bugs.kde.org/show_bug.cgi?id=353596 vindica...@live.com changed: What|Removed |Added CC||vindica...@live.com --- Comment #2 from vindica...@live.com --- I am finding this issue as well after a clean install of archlinux along with kcalc. Settings->Shortcuts->"Global Shortcuts"->"KDE Daemon"->Calculator IS set to "Launch (1)" which IS correct, but still won't launch. Adding in "Custom Shortcuts", Edit->New->"Global Shortcut"->Command/URL using "Launch (1)" and running "kcalc" DOES work. -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 374753] no refresh during google photos import
https://bugs.kde.org/show_bug.cgi?id=374753 Kusichanged: What|Removed |Added Version|5.5.0 |5.2.0 --- Comment #2 from Kusi --- I tried digikam master and wrongly assumed I was also using kipi master. But no, I was using kipi-plugins 5.2 provided with current Opensuse Leap. I'll correct it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374554] Crash when enabling DPMS
https://bugs.kde.org/show_bug.cgi?id=374554 --- Comment #1 from Roman Gilg--- Since you thought a few days ago the org.kde.KWin.InputDeviceManager interface is the problem because of the backtrace, something else: When issuing kwin_wayland --xwayland from terminal, it gives a segfault. Removing the registerObject of the interface in connection.cpp solves this. So there is indeed a problem with the current implementation, which seems to be related to the multiple threads in the Connection class. Atleast there are correlated warning messages spamed to the log. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374142] Contiguous selection tool not always works
https://bugs.kde.org/show_bug.cgi?id=374142 David REVOYchanged: What|Removed |Added CC||i...@davidrevoy.com --- Comment #4 from David REVOY --- I confirm this one also on Manjaro/XFCE + 3.1.1appimage. "Contiguous selection tool" is not alone in this problem, but the easiest to trigger/reproduce the bug. Here is a video when rectangular selection tool get also locked: https://share.kde.org/index.php/s/5ld58LjpExouKCF .In this case no workaround, just restarting Krita and loosing session. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 373301] Problems in user menu
https://bugs.kde.org/show_bug.cgi?id=373301 --- Comment #6 from merlin--- I do not have any explanation for this behavior. The only thing, whichs remains to do, is to take a look at your configuration file 'usuario.xml' (usually in '.local/share/kile/usermenu/'). Search for your entry named 'Llanes' and look for the entries of the checkboxes: Llaves {%M%C} ... true true true Add these lines, if they are not present. But this is just a guess... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374754] New: startup crash
https://bugs.kde.org/show_bug.cgi?id=374754 Bug ID: 374754 Summary: startup crash Product: plasmashell Version: 5.8.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: raffamai...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.8.3) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.27-2-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: When I boot the PC, I can get until the moving circle just before the desktop appears. When the desktop should appear, instead the screen just goes completely black - Unusual behavior I noticed: I get a completely black screen instead of the desktop The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd4b8ebe900 (LWP 1582))] Thread 11 (Thread 0x7fd3d0edc700 (LWP 1737)): #0 0x7fd4b25d651d in read () at /lib64/libc.so.6 #1 0x7fd4aece2670 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fd4aeca1e49 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7fd4aeca22a8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fd4aeca242c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7fd4b2ee632b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fd4b2e93fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7fd4b2ccef1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7fd3d23048f7 in KCupsConnection::run() () at /usr/lib64/libkcupslib.so #9 0x7fd4b2cd39e9 in () at /usr/lib64/libQt5Core.so.5 #10 0x7fd4b1de3734 in start_thread () at /lib64/libpthread.so.0 #11 0x7fd4b25e2d3d in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7fd3e11fa700 (LWP 1730)): #0 0x7fd4b25da49d in poll () at /lib64/libc.so.6 #1 0x7fd4aeca2314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fd4aeca242c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fd4b2ee632b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fd4b2e93fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fd4b2ccef1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fd4b5fda9b8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7fd4b2cd39e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7fd4b1de3734 in start_thread () at /lib64/libpthread.so.0 #9 0x7fd4b25e2d3d in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7fd3f2504700 (LWP 1699)): #0 0x7fd4b25d651d in read () at /lib64/libc.so.6 #1 0x7fd4aece2670 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fd4aeca1e49 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7fd4aeca22a8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fd4aeca242c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7fd4b2ee632b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fd4b2e93fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7fd4b2ccef1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7fd4b6b5d632 in () at /usr/lib64/libQt5Quick.so.5 #9 0x7fd4b2cd39e9 in () at /usr/lib64/libQt5Core.so.5 #10 0x7fd4b1de3734 in start_thread () at /lib64/libpthread.so.0 #11 0x7fd4b25e2d3d in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7fd3fbd98700 (LWP 1698)): #0 0x7fd4b1de80af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fd402ef2533 in () at /usr/lib64/dri/r600_dri.so #2 0x7fd402ef1d57 in () at /usr/lib64/dri/r600_dri.so #3 0x7fd4b1de3734 in start_thread () at /lib64/libpthread.so.0 #4 0x7fd4b25e2d3d in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7fd483fff700 (LWP 1697)): #0 0x7fd4b1de80af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fd4b859693b in () at /usr/lib64/libQt5Script.so.5 #2 0x7fd4b8596969 in () at /usr/lib64/libQt5Script.so.5 #3 0x7fd4b1de3734 in start_thread () at /lib64/libpthread.so.0 #4 0x7fd4b25e2d3d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7fd48b78c700 (LWP 1696)): #0 0x7fd4b25d651d in read () at /lib64/libc.so.6 #1 0x7fd4aece2670 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fd4aeca1e49 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7fd4aeca22a8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fd4aeca242c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7fd4b2ee632b in
[kipiplugins] [Bug 374753] no refresh during google photos import
https://bugs.kde.org/show_bug.cgi?id=374753 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- kipi plugins 5.5.0 do not exist yet... Do you mean git/master ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374752] Choose holidays
https://bugs.kde.org/show_bug.cgi?id=374752 Alex Loeschanged: What|Removed |Added CC||a...@loes.org.lu -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 374753] no refresh during google photos import
https://bugs.kde.org/show_bug.cgi?id=374753 Kusichanged: What|Removed |Added CC||k...@forum.titlis.org -- You are receiving this mail because: You are watching all bug changes.
[kipiplugins] [Bug 374753] New: no refresh during google photos import
https://bugs.kde.org/show_bug.cgi?id=374753 Bug ID: 374753 Summary: no refresh during google photos import Product: kipiplugins Version: 5.5.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: GoogleServices Assignee: kde-imag...@kde.org Reporter: k...@forum.titlis.org Target Milestone: --- After opening the Google Photos import dialog in Digikam, there's no way to reread again new albums from Google Photos. Neither the refresh button nor closing/reopening the import dialog will update the albums. If you create a new album on photos.google.com while digikam is open, you need to restart digikam in order to make the album visible -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374752] New: Choose holidays
https://bugs.kde.org/show_bug.cgi?id=374752 Bug ID: 374752 Summary: Choose holidays Product: plasmashell Version: 5.8.4 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: a...@loes.org.lu Target Milestone: 1.0 Hello I've choosen US-english as system language and Luxemburgish as time format (in System Settings->Regional Settings->Format. The holidays shown in the calendar are the one's for US, but I want them for Luxembourg. Therefore, I have changed the Time Format to Luxembourgish. This doesn't affect the holidays shown in the calendar. But when I choose Digital Clock settings->Holidays, I got an error message: Could not load file:///usr/lib/x86_64-linux-gnu/qt5/plugins/plasmacalendarplugins/holidays/HolidaysConfig.qml:29 module "org.kde.kholidays" is not installed. The package libkholidays4 is installed. When I go to /usr/lib/x86_64-linux-gnu/qt5/plugins/plasmacalendarplugins/holidays, I can see a file HolidaysConfig.qml. How can I choose the Luxembourgish holidays shown by digital-clocks calendar? Thanks for your help. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 374751] New: qmake project manager: incorrect targets on Mac
https://bugs.kde.org/show_bug.cgi?id=374751 Bug ID: 374751 Summary: qmake project manager: incorrect targets on Mac Product: kdevelop Version: git master Platform: Other OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: Build tools: QMake Assignee: kdevelop-bugs-n...@kde.org Reporter: rjvber...@gmail.com Target Milestone: --- Normally QMake .pro files will build applications as app bundles on Mac, regardless of whether macdeployqt is used to create standalone bundles or not. For instance, the "menus" Qt example has the following menus.pro file: QT += widgets HEADERS = mainwindow.h SOURCES = mainwindow.cpp \ main.cpp # install target.path = $$[QT_INSTALL_EXAMPLES]/widgets/mainwindows/menus INSTALLS += target Running qmake on it will create a Makefile that contains the following: QMAKE_TARGET = menus DESTDIR = TARGET= menus.app/Contents/MacOS/menus first: all ### Build rules $(TARGET): $(OBJECTS) @test -d menus.app/Contents/MacOS/ || mkdir -p menus.app/Contents/MacOS/ $(LINK) $(LFLAGS) -o $(TARGET) $(OBJECTS) $(OBJCOMP) $(LIBS) The qmake project manager still picks up the QMAKE_TARGET short name. Evidently a failure occurs when it tries to invoke `make menus` instead of `make menus.app/Contents/MacOS/menus`. This also makes it impossible to update a project before running one of its build targets. Handling this is not completely trivial as it *is* possible to tell QMake to generate traditional executables on Mac. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 374614] Pasting text in title clip window changes color when element loses focus
https://bugs.kde.org/show_bug.cgi?id=374614 Jean-Baptiste Mardellechanged: What|Removed |Added Latest Commit||https://commits.kde.org/kde ||nlive/fa4acc48e15c1d5c46ecf ||0b04bd81f7b7290f5b0 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from Jean-Baptiste Mardelle --- Git commit fa4acc48e15c1d5c46ecf0b04bd81f7b7290f5b0 by Jean-Baptiste Mardelle. Committed on 08/01/2017 at 13:05. Pushed by mardelle into branch 'Applications/16.1'. Fix various titler bugs (pasting breaks color & font, incorrect selection) M +34 -11 src/effectstack/graphicsscenerectmove.cpp M +2-0src/effectstack/graphicsscenerectmove.h M +1-0src/titler/titledocument.cpp M +2-2src/titler/titlewidget.cpp https://commits.kde.org/kdenlive/fa4acc48e15c1d5c46ecf0b04bd81f7b7290f5b0 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 372208] kwrite File -> New directory fails to follow current, defaults to $HOME
https://bugs.kde.org/show_bug.cgi?id=372208 Toralf Försterchanged: What|Removed |Added CC||toralf.foers...@gmx.de --- Comment #2 from Toralf Förster --- The issue appeared here for me too after upgrading from kde-plasma 5.8.4 to 5.8.5 at a stable hardened Gentoo Linux (qt 5.7.1, kf, 5.29, ka 16.12.0) and is still present. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374750] New: After login kde logo does not disappear
https://bugs.kde.org/show_bug.cgi?id=374750 Bug ID: 374750 Summary: After login kde logo does not disappear Product: plasmashell Version: 5.8.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: slartibar...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Have sddm.service (or lightdm.service) running as login manager. Log into the system The display manager screen gets replaced by the kde logo and a rotating 'spinner' beneath it. The 'spinner' disappears and ... nothing happens. Kde logo is still there and remains visible... (on other systems, the plasma desktop is now shown and replaces the kde logo) Workaround to get to the desktop: press Ctrl-Alt F2, and then Alt-F1 to go back. Now, the desktop is here in its full glory :-) Same workaround is sometimes necessary when working with plasma, the taskbar is stuck (no updates, no context menu, no kicker) and the context menu on the desktop does not appear when right-clicking. Just make a short detour to the vconsole and back to the gui and all is fine again. This is _very_ annoying!!! Happens on different systems - with a fresh install of fedora25/kde spin (kernel 4.6 and plasma < 5.8) it is happening on every system i installed recently (lenovo laptops t420, t440, both intel graphics, desktop with core2 q8200 and intel graphics) - it seems to be fixed when updated to current repo releases on the more current systems (lenovo laptops), but it happens often - not always - on the desktop with the q8200/intel graphics I already tried different compositing options, openGL 3.1/2.0/XRender but the problem remains. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 374749] New: privacy leak in search debug output
https://bugs.kde.org/show_bug.cgi?id=374749 Bug ID: 374749 Summary: privacy leak in search debug output Product: kmail2 Version: 5.2.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: search Assignee: kdepim-b...@kde.org Reporter: mar...@lichtvoll.de Target Milestone: --- This debug output might be done by some Akonadi component. Feel free to reassign. Akonadi and KDEPIM is 16.04.3 from Debian Unstable packages (Debian unfortunately has no newer packages due to difficultity / time constraints regarding packaging Qt Webengine which is needed for newer KDEPIM versions). After starting KMail on command line it outputs search debug messages which reveal the exact search query including the mail address being searched for. # How to reproduce - Start kmail on console You may need to do a search, but on my system it automatically does this one search on startup, querying whatever mail item is highlighted after start of KMail. # Actual results When starting KMail via desktop session this goes to ~/.xsession-errors and/or systemd-journald user session login and thus leaks private information to log files. Debug output is disabled globally in kdebugdialog, which I learnt before may not yet used anymore. Executing search "searchUpdate-1483877954" searchUpdateResultsAvailable 396 0 results Got 0 results, out of which 0 are already in the collection Added 0 Search done "searchUpdate-1483877954" (without remote search) Search update finished All results: 0 Removed results: 0 Executing search "searchUpdate-1483877954" searchUpdateResultsAvailable 395 0 results Got 0 results, out of which 0 are already in the collection Added 0 Search done "searchUpdate-1483877954" (without remote search) Search update finished All results: 0 Removed results: 0 posting retrieval request for item 3013668 there are 1 queues and 0 items in mine request for item 3013668 still pending - waiting processing retrieval request for item 3013668 parts: ("RFC822", "HEAD") of resource: "akonadi_maildir_resource_0" continuing request for item 3013668 succeeded Database "akonadi" opened using driver "QMYSQL" SEARCH: Query: "{\n\"limit\": -1,\n\"negated\": false,\n\"rel\": 1,\n\"subTerms\": [\n{\n\"cond\": 0,\n \"key\": \"email\",\n\"negated\": false,\n\"value\": \"bugzilla_nore...@kde.org\"\n}\n]\n}\n" MimeTypes: ("text/directory") Collections: QVector(0, 276) Remote: false Recursive true Executing search "kmail2-1186278907-SearchSession" Search done "kmail2-1186278907-SearchSession" (without remote search) Result: 0 matches SEARCH: Query: "{\n\"limit\": -1,\n\"negated\": false,\n\"rel\": 1,\n\"subTerms\": [\n{\n\"cond\": 0,\n \"key\": \"email\",\n\"negated\": false,\n\"value\": \"bugzilla_nore...@kde.org\"\n}\n]\n}\n" MimeTypes: ("text/directory") Collections: QVector(0, 276) Remote: false Recursive true Executing search "kmail2-1186278907-SearchSession" Search done "kmail2-1186278907-SearchSession" (without remote search) Result: 0 matches Executing search "searchUpdate-1483877969" searchUpdateResultsAvailable 396 0 results Got 0 results, out of which 0 are already in the collection Added 0 Search done "searchUpdate-1483877969" (without remote search) Search update finished All results: 0 Removed results: 0 Executing search "searchUpdate-1483877969" searchUpdateResultsAvailable 395 0 results Got 0 results, out of which 0 are already in the collection Added 0 Search done "searchUpdate-1483877969" (without remote search) Search update finished All results: 0 Removed results: 0 # Expected results No debug output which leaks privacy sensitive information in production builds. Preferably no debug output at all unless manually enabled. Ideally also sanitize optionally switchable debug output which are intended to be included in bug reports. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 332684] [Maildir] lots of stats calls to /etc/localtime on synchronizing folders
https://bugs.kde.org/show_bug.cgi?id=332684 Martin Steigerwaldchanged: What|Removed |Added Version|4.12|5.2.3 Resolution|UNMAINTAINED|--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #5 from Martin Steigerwald --- This still is happening with KMail 5.2.3 (Debian unstable has no newer package unfortunately and currently I don´t self-compile KDEPIM). How to reproduce? 1. Start KMail with TZ variable unset. 2. Trace it like this: strace -f -o strace-kmail-stat-localtime.txt -p 16925 3. Click between some (larger) folders. # Actual Results ~> strace -f -o strace-kmail-stat-localtime.txt -p 16925 strace: Process 16925 attached with 22 threads ~> grep -c "stat(\"/etc/localtime" strace-kmail-stat-localtime.txt 5496 in just a few seconds of KMail runtime. # Expected results Cache what KMail needs from /etc/localtime at least for a while to reduce the number of calls to that syscall. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374748] New: Cursor dissapears when brush-size is 0px without pressure
https://bugs.kde.org/show_bug.cgi?id=374748 Bug ID: 374748 Summary: Cursor dissapears when brush-size is 0px without pressure Product: krita Version: 3.1.1 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: minor Priority: NOR Component: Brush engine Assignee: krita-bugs-n...@kde.org Reporter: tobias.00...@gmail.com Target Milestone: --- You can try it with this Brush: https://drive.google.com/file/d/0B6R-92sgOUCAODlnT1VoNEU1WlE/view It also depends on the zoom-level. When i use the tablet to move the cursor it is visible, but when i use the mouse it disappears. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374747] New: "Overwrite Preset" grayed when preview image is changed
https://bugs.kde.org/show_bug.cgi?id=374747 Bug ID: 374747 Summary: "Overwrite Preset" grayed when preview image is changed Product: krita Version: 3.1.1 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: minor Priority: NOR Component: Brush engine Assignee: krita-bugs-n...@kde.org Reporter: tobias.00...@gmail.com Target Milestone: --- When i only want to edit the preview image of a brush-preset the button "Overwrite Preset" stays grayed out. When i change an attribute and than change it back to it's initial value the button is not grayed out anymore and I can overwrite it and change the preview-image. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 374564] File search opens multiple sessions of the same file
https://bugs.kde.org/show_bug.cgi?id=374564 Kåre Särschanged: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED CC||kare.s...@iki.fi --- Comment #2 from Kåre Särs --- Hi, The problem here is that KTextEditor resolves symbolic links, while Kate's document manages does not. There are two solutions: 1) We add sym-link resolving in Kate 2) We stop resolving sym-links in KTextEditor Alternative 2 is a change in behavior and might not be the best option, but it is a bit strange to try to open foo.txt and get baar.txt... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374746] New: Removing the color from multiple selected Frames does not work
https://bugs.kde.org/show_bug.cgi?id=374746 Bug ID: 374746 Summary: Removing the color from multiple selected Frames does not work Product: krita Version: 3.1.1 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: minor Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: tobias.00...@gmail.com Target Milestone: --- I can select multiple frames and assign a color with right-click. But i can't remove it. I can only do this Layer by Layer. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 279091] Filling the message list is too slow
https://bugs.kde.org/show_bug.cgi?id=279091 Albert Astals Cidchanged: What|Removed |Added Resolution|UNMAINTAINED|--- Version|1.99.0 |5.2.3 Status|RESOLVED|REOPENED --- Comment #3 from Albert Astals Cid --- I'm not going to open a new one, it already exists, and it's this one. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374745] tooltips are wrong
https://bugs.kde.org/show_bug.cgi?id=374745 --- Comment #1 from tobias.00...@gmail.com --- interesting, now it's as it should be. strange -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374745] New: tooltips are wrong
https://bugs.kde.org/show_bug.cgi?id=374745 Bug ID: 374745 Summary: tooltips are wrong Product: krita Version: 3.1.1 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: minor Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: tobias.00...@gmail.com Target Milestone: --- the tooltip in the animation-docker says: new frame (), copy frame (), remove frame () -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 336581] accidental database loss causes Akonadi / KMail to silently break correct folder assignments
https://bugs.kde.org/show_bug.cgi?id=336581 Martin Steigerwaldchanged: What|Removed |Added Platform|Compiled Sources|Debian unstable Version|GIT (master)|5.2.3 --- Comment #10 from Martin Steigerwald --- This is indeed still the case with KMail 5.2.3 (Debian Unstable unfortunately does not have any newer packages due to the difficulty to properly package Qt Webengine in order to enable newer KDEPIM versions, which likely means that Debian will go with KDEPIM 16.04 for next stable version Stretch). The principal issue of relying on database IDs outside of the database itself and thus using wrong folders in case of a database loss, potentially causing data loss, is still present. For mailfilters: ~/.config> grep action- akonadi_mailfilter_agentrc | head -20 […] action-args-0=95 action-name-0=transfer action-args-0=209 action-name-0=transfer action-args-0=209 action-name-0=transfer action-args-0=208 action-name-0=transfer action-args-0=211 action-name-0=transfer action-args-0=422 action-name-0=transfer Action "transfer" means to move the mail into a folder. The corresponding args-0 is the numerical id of the folder. For folder settings: ~/.config> fgrep '[Folder-' kmail2rc | head [Folder-1] [Folder-10] [Folder-100] [Folder-101] [Folder-102] [Folder-103] [Folder-104] [Folder-105] [Folder-106] [Folder-107] For default folders for mail identities: ~/.config> egrep -i "draft|template" emailidentities | head -10 Drafts=21 Templates=31 Drafts=21 Templates=31 Drafts=21 Templates=31 Drafts=21 Templates=31 Drafts=411 Templates=378 Default inbox folder for POP mail resources: martin@merkaba:~/.config> grep targetCollection akonadi_pop3_resource_0rc targetCollection=361 I bet is similar for IMAP resources. My expected result is this: 1) Either keep / rebuild / reassign references after a database loss properly *or* 2) *loose* the references and require the user to reconfigure. Yet *never ever* use *wrong* references, just do to a database loss. Use a unique hash for identification, not just the index number of the database entry. In that way you can at least *know* when the reference is no more valid. *Or* store *all* of these reference into the database itself, so that they are gone for good if the database is rebuilt. For user convenience I would aim for approach 1 wherever possible which is easier to do with a hash based approach. For maildir resource, you can store the folder identification in the maildir filesystem, or IMAP it becomes more difficult tough, yet you could at least also store the name and then if the reference by hash is gone, you can show the folder name to the user and possibly even autoselect it for confirmation. You can argue that a database loss should not happen and with proper MariaDB configuration, proper filesystem and proper storage media you might well be right about that – *yet* in practice it did happen to a lot of users. So please make Akonadi *failure proof* and more *robust* in cases like this. Another approach would be to use something else than a database for metadata or rethink the Akonadi caching concept completely like Aaron and others do with Sink for Kubemail. I don´t see this happening for KMail from KDEPIM soon, so I think it makes sense to make it more failure proof even before that may happen. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 369389] tab key does not cycle input fields in right order
https://bugs.kde.org/show_bug.cgi?id=369389 --- Comment #1 from MK--- Tab order must be located somewhere in kmymoney/kmymoney/plugins/onlinetasks/sepa/ui/sepacredittransferedit.ui Unfortunatety I'm no Qt expert. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374744] New: "import animation frames" grayed out
https://bugs.kde.org/show_bug.cgi?id=374744 Bug ID: 374744 Summary: "import animation frames" grayed out Product: krita Version: 3.1.1 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: tobias.00...@gmail.com Target Milestone: --- When I create a new document and go tu "import animation frames" it's grayed out at first. As soon as I create a new Frame it's available. I think the creation of the Frame should happen automatically when using "import animation frames" and it should never be grayed out. -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 373213] Assertion failure "!inputUrl.fileName().isEmpty()" in shell/documentcontroller.cpp, line 226
https://bugs.kde.org/show_bug.cgi?id=373213 Kevin Funkchanged: What|Removed |Added Latest Commit|https://commits.kde.org/kde |https://commits.kde.org/kde |vplatform/d42d074299295308f |vplatform/28c38e3b9dd6eda0e |22d36fe4ce456e26e4cd398 |db8cfa763db64897314eb4b --- Comment #3 from Kevin Funk --- Git commit 28c38e3b9dd6eda0edb8cfa763db64897314eb4b by Kevin Funk, on behalf of Sven Brauch. Committed on 08/01/2017 at 12:10. Pushed by kfunk into branch '5.0'. Fix opening of remote URLs without filename Differential Revision: https://phabricator.kde.org/D3999 (cherry picked from commit d42d074299295308f22d36fe4ce456e26e4cd398) M +1-1language/backgroundparser/backgroundparser.cpp M +2-2shell/documentcontroller.cpp M +8-2sublime/urldocument.cpp https://commits.kde.org/kdevplatform/28c38e3b9dd6eda0edb8cfa763db64897314eb4b -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 373213] Assertion failure "!inputUrl.fileName().isEmpty()" in shell/documentcontroller.cpp, line 226
https://bugs.kde.org/show_bug.cgi?id=373213 Sven Brauchchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kde ||vplatform/d42d074299295308f ||22d36fe4ce456e26e4cd398 Resolution|--- |FIXED --- Comment #2 from Sven Brauch --- Git commit d42d074299295308f22d36fe4ce456e26e4cd398 by Sven Brauch. Committed on 08/01/2017 at 12:07. Pushed by brauch into branch 'master'. Fix opening of remote URLs without filename Differential Revision: https://phabricator.kde.org/D3999 M +1-1language/backgroundparser/backgroundparser.cpp M +2-2shell/documentcontroller.cpp M +8-2sublime/urldocument.cpp https://commits.kde.org/kdevplatform/d42d074299295308f22d36fe4ce456e26e4cd398 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374726] The levels filter does not have a channel selecttor
https://bugs.kde.org/show_bug.cgi?id=374726 Boudewijn Remptchanged: What|Removed |Added Severity|grave |wishlist Summary|Filter Levels no Channel|The levels filter does not ||have a channel selecttor CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- Marked as wish, since it's a feature request, not a bug. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368311] Add a new warning during fetching git repo
https://bugs.kde.org/show_bug.cgi?id=368311 Kevin Funkchanged: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kde ||vplatform/2d18d030aeb1247ab ||84995196d31d34b33b1a49c Status|CONFIRMED |RESOLVED Version Fixed In||5.2.0 --- Comment #2 from Kevin Funk --- Git commit 2d18d030aeb1247ab84995196d31d34b33b1a49c by Kevin Funk, on behalf of Nilesh Sah. Committed on 08/01/2017 at 12:02. Pushed by kfunk into branch 'master'. Add a new warning during fetching git repo Summary: Improved the warning message showed during fetching a git repo if the specified folder is empty. FIXED-IN: 5.2.0 Test Plan: Tested working for all possible cases while fetching a repo from git or Bazaar. Reviewers: kfunk, #kdevelop Subscribers: kdevelop-devel Differential Revision: https://phabricator.kde.org/D3970 M +7-7shell/projectsourcepage.cpp https://commits.kde.org/kdevplatform/2d18d030aeb1247ab84995196d31d34b33b1a49c -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 374650] Duplicate okular_poppler backend selection entry
https://bugs.kde.org/show_bug.cgi?id=374650 --- Comment #9 from Oliver Sander--- I confirm that the patch avoids the duplicate 'poppler' entry for me. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 374736] balooctl clear doesn't clear deleted files
https://bugs.kde.org/show_bug.cgi?id=374736 --- Comment #1 from k...@web.de --- Hmm it's not that simple, since the next check also fails if id is 0, and we seem to need the id to remove the record, but it is 0 for non-existing files. tr.removeDocument(id) Can we remove using only the url instead? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 374613] Project bin shows clip length of "00:00:04:30" when the clip is 5 seconds
https://bugs.kde.org/show_bug.cgi?id=374613 --- Comment #8 from Christian Weiske--- The project I'm working on consists mainly of AVI videos recorded with a Fujifilm FinePix JX300 camera. kdenlive shows their FPS in the clip properties as "30,0003". Maybe kdenlive asked me if I wanted to match my project FPS with the clip FPS and I confirmed that - I can't remember. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 374614] Pasting text in title clip window changes color when element loses focus
https://bugs.kde.org/show_bug.cgi?id=374614 Jean-Baptiste Mardellechanged: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 325699] Akonadi stores absolute path to maildir resource maildir in database, making it difficult to create a test setup
https://bugs.kde.org/show_bug.cgi?id=325699 Martin Steigerwaldchanged: What|Removed |Added Status|RESOLVED|REOPENED Platform|unspecified |Debian unstable Version|4.10|5.2.3 Resolution|UNMAINTAINED|--- --- Comment #9 from Martin Steigerwald --- Thank you Denis for taking care to close old bugs. However this one still happens. As this is still quite concise I do not see much sense in opening another one about the same issue. I tested it by starting KMail 5.2.3 with empty home directory. This is what I get: martin2@merkaba ~/.local/share/akonadi/socket-merkaba % mysql --socket mysql.socket Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 60 Server version: 10.0.28-MariaDB-3 Debian buildd-unstable Copyright (c) 2000, 2016, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MariaDB [(none)]> use akonadi; Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Database changed MariaDB [akonadi]> select id, remoteId from collectiontable; ++---+ | id | remoteId | ++---+ | 1 | NULL | | 2 | akonadi_birthdays_resource| | 3 | /home/martin2/.local/share/contacts/ | | 5 | /home/martin2/.local/share/akonadi_maildir_resource_0 | | 6 | outbox| | 7 | sent-mail | | 8 | /home/martin2/.local/share/apps/korganizer/std.ics| | 10 | /home/martin2/.local/share/notes/ | | 11 | inbox | | 12 | drafts| | 13 | trash | | 14 | templates | | 15 | Test | | 16 | Test2 | ++---+ 14 rows in set (0.00 sec) MariaDB [akonadi]> % ls -l akonadi_maildir_resource_0 insgesamt 0 drwxr-xr-x 1 martin2 martin2 18 Jan 8 12:33 drafts drwxr-xr-x 1 martin2 martin2 18 Jan 8 12:33 inbox drwxr-xr-x 1 martin2 martin2 18 Jan 8 12:33 outbox drwxr-xr-x 1 martin2 martin2 18 Jan 8 12:33 sent-mail drwxr-xr-x 1 martin2 martin2 18 Jan 8 12:33 templates drwxr-xr-x 1 martin2 martin2 18 Jan 8 12:33 Test drwxr-xr-x 1 martin2 martin2 18 Jan 8 12:33 Test2 drwxr-xr-x 1 martin2 martin2 18 Jan 8 12:33 trash while ~/.local/share/local-mail appears to be empty, except cur, new and tmp directories. So while there is a change as it uses the name of the maildir resource and not "local-mail" anymore, it still has that reference to an absolute path instead of using something relative to $HOME or the suitable XDG directory. At least it seems to store an absolute path just once for each resource and not once for every folder or item as I verified with PimItemTable. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 374736] balooctl clear doesn't clear deleted files
https://bugs.kde.org/show_bug.cgi?id=374736 Simone Gaiarinchanged: What|Removed |Added CC||simg...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 374613] Project bin shows clip length of "00:00:04:30" when the clip is 5 seconds
https://bugs.kde.org/show_bug.cgi?id=374613 --- Comment #7 from Jean-Baptiste Mardelle--- The profile was probably created automatically by Kdenlive when you tried adding a clip having that frame rate (if you have enabled the option to check clip profile on first added clip). You can delete this profile in Kdenlive Settings > Project Defaults > Manage profile button. It should be called "1280x720, 30.00fps" I have now added a check in the automatic profile feature that will use integer fps instead of 30.003 in case a clip has a non exact frame rate, should solve the problem. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 374735] kdenlive render crashes on start
https://bugs.kde.org/show_bug.cgi?id=374735 Jean-Baptiste Mardellechanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Jean-Baptiste Mardelle --- This is most likely a packaging issue, you should ping the package maintainer. As a workaround, you can consider trying our AppImage package that provides the latest Kdenlive version and should run on any distro: https://kdenlive.org/download/ -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 374743] New: Crash van akonadi after moving messages from one IMAP folder to a folder on another IMAP server
https://bugs.kde.org/show_bug.cgi?id=374743 Bug ID: 374743 Summary: Crash van akonadi after moving messages from one IMAP folder to a folder on another IMAP server Product: kontact Version: 5.4.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: freekdekru...@kde.nl Target Milestone: --- Application: kontact (5.4.0) Qt Version: 5.7.1 Frameworks Version: 5.29.0 Operating System: Linux 4.9.0-2-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I moved three messages from the GMail IMAP server to a folder on another IMAP server, not on localhost, based on dovecot. After that I selected the destination folder, but I am not sure this was the cause of the crash or the previous move. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4771a86e80 (LWP 2406))] Thread 31 (Thread 0x7f45e6efc700 (LWP 3244)): #0 0x7f476e4aa66d in poll () at /lib64/libc.so.6 #1 0x7f4768163876 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f476816398c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f476efe118b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f45d80072f0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f476ef8aaea in QEventLoop::exec(QFlags) (this=this@entry=0x7f45e6efbc80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f476edb8813 in QThread::exec() (this=) at thread/qthread.cpp:507 #6 0x7f476edbd4c8 in QThreadPrivate::start(void*) (arg=0x5e2f490) at thread/qthread_unix.cpp:368 #7 0x7f476a351454 in start_thread () at /lib64/libpthread.so.0 #8 0x7f476e4b337f in clone () at /lib64/libc.so.6 Thread 30 (Thread 0x7f45e7fff700 (LWP 2564)): #0 0x7f476a35710f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f46597e7873 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f4659b1dc61 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f476a351454 in start_thread () at /lib64/libpthread.so.0 #4 0x7f476e4b337f in clone () at /lib64/libc.so.6 Thread 29 (Thread 0x7f45ecf58700 (LWP 2563)): #0 0x7f476a35710f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f46597e7873 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f4659b1dc61 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f476a351454 in start_thread () at /lib64/libpthread.so.0 #4 0x7f476e4b337f in clone () at /lib64/libc.so.6 Thread 28 (Thread 0x7f45ed759700 (LWP 2562)): #0 0x7f476a35710f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f46597e7873 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f4659b1dc61 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f476a351454 in start_thread () at /lib64/libpthread.so.0 #4 0x7f476e4b337f in clone () at /lib64/libc.so.6 Thread 27 (Thread 0x7f45edf5a700 (LWP 2561)): #0 0x7f476a35710f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f46597e6721 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f4659b1dc61 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f476a351454 in start_thread () at /lib64/libpthread.so.0 #4 0x7f476e4b337f in clone () at /lib64/libc.so.6 Thread 26 (Thread 0x7f462e964700 (LWP 2560)): #0 0x7f476a35710f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4659aecf6b in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f4659aecfa9 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f476a351454 in start_thread () at /lib64/libpthread.so.0 #4 0x7f476e4b337f in clone () at /lib64/libc.so.6 Thread 25 (Thread 0x7f463cb0c700 (LWP 2536)): #0 0x7f4768162742 in g_main_context_acquire () at /usr/lib64/libglib-2.0.so.0 #1 0x7f4768163725 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f476816398c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f476efe118b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f46340008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f476ef8aaea in QEventLoop::exec(QFlags) (this=this@entry=0x7f463cb0bc80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f476edb8813 in QThread::exec() (this=) at thread/qthread.cpp:507 #6 0x7f476edbd4c8 in QThreadPrivate::start(void*) (arg=0x3213470) at thread/qthread_unix.cpp:368 #7 0x7f476a351454 in start_thread () at /lib64/libpthread.so.0 #8 0x7f476e4b337f in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7f463d94e700 (LWP 2531)): #0 0x7f476a35710f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f47615216d9 in () at
[systemsettings] [Bug 374742] New: click back after change settings
https://bugs.kde.org/show_bug.cgi?id=374742 Bug ID: 374742 Summary: click back after change settings Product: systemsettings Version: 5.8.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: vision1...@mail.ru Target Milestone: --- Application: systemsettings5 (5.8.5) Qt Version: 5.7.1 Frameworks Version: 5.29.0 Operating System: Linux 4.8.15-300.fc25.x86_64 x86_64 Distribution: "Fedora release 25 (Twenty Five)" -- Information about the crash: - Unusual behavior I noticed: -system settings -style interfae -change style - click apply - click all parameters and so crash The crash can be reproduced every time. -- Backtrace: Application: Параметры системы (systemsettings5), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f923ead56c0 (LWP 5021))] Thread 4 (Thread 0x7f9219a63700 (LWP 5058)): #0 0x7f92435497f9 in g_mutex_lock () at /lib64/libglib-2.0.so.0 #1 0x7f92435036a6 in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #2 0x7f924350407b in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #3 0x7f924350426c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #4 0x7f924b47b73b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f924b42c73a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f924b2895f3 in QThread::exec() () at /lib64/libQt5Core.so.5 #7 0x7f9249e4d4e5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #8 0x7f924b28d9da in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #9 0x7f924774b6ca in start_thread () at /lib64/libpthread.so.0 #10 0x7f924a680f7f in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f922b41f700 (LWP 5024)): #0 0x7f924a670bed in read () at /lib64/libc.so.6 #1 0x7f9243548450 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #2 0x7f9243503c60 in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7f92435040f4 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7f924350426c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7f924b47b73b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f924b42c73a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7f924b2895f3 in QThread::exec() () at /lib64/libQt5Core.so.5 #8 0x7f924bbb4739 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #9 0x7f924b28d9da in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #10 0x7f924774b6ca in start_thread () at /lib64/libpthread.so.0 #11 0x7f924a680f7f in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f9233ad4700 (LWP 5023)): #0 0x7f924a67501d in poll () at /lib64/libc.so.6 #1 0x7f9247d8ad10 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x7f9247d8caa9 in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7f923817cd69 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x7f924b28d9da in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7f924774b6ca in start_thread () at /lib64/libpthread.so.0 #6 0x7f924a680f7f in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f923ead56c0 (LWP 5021)): [KCrash Handler] #6 0x7f924a5ae91f in raise () at /lib64/libc.so.6 #7 0x7f924a5b051a in abort () at /lib64/libc.so.6 #8 0x7f924a5f2200 in __libc_message () at /lib64/libc.so.6 #9 0x7f924a5fa1a3 in malloc_consolidate () at /lib64/libc.so.6 #10 0x7f924a5fceaf in _int_malloc () at /lib64/libc.so.6 #11 0x7f924a5fef14 in malloc () at /lib64/libc.so.6 #12 0x7f924a5ff7b8 in realloc () at /lib64/libc.so.6 #13 0x7f924c4e47a9 in QTextEngine::LayoutData::reallocate(int) () at /lib64/libQt5Gui.so.5 #14 0x7f924c4ec5d9 in QTextEngine::attributes() const () at /lib64/libQt5Gui.so.5 #15 0x7f924c4f8f58 in QTextLine::layout_helper(int) () at /lib64/libQt5Gui.so.5 #16 0x7f924c4fae1b in QTextLine::setLineWidth(double) () at /lib64/libQt5Gui.so.5 #17 0x7f924c537825 in QTextDocumentLayoutPrivate::layoutBlock(QTextBlock const&, int, QTextBlockFormat const&, QTextLayoutStruct*, int, int, QTextBlockFormat const*) () at /lib64/libQt5Gui.so.5 #18 0x7f924c5388d0 in QTextDocumentLayoutPrivate::layoutFlow(QTextFrame::iterator, QTextLayoutStruct*, int, int, QFixed) () at /lib64/libQt5Gui.so.5 #19 0x7f924c53ca94 in QTextDocumentLayoutPrivate::layoutFrame(QTextFrame*, int, int, QFixed, QFixed, QFixed) () at /lib64/libQt5Gui.so.5 #20 0x7f924c53cf5d in QTextDocumentLayoutPrivate::layoutFrame(QTextFrame*, int, int, QFixed) () at /lib64/libQt5Gui.so.5 #21 0x7f924c53d710 in QTextDocumentLayout::doLayout(int, int, int) () at /lib64/libQt5Gui.so.5 #22
[frameworks-baloo] [Bug 362226] Baloo index keeps obsolete directory entries
https://bugs.kde.org/show_bug.cgi?id=362226 k...@web.de changed: What|Removed |Added CC||k...@web.de --- Comment #2 from k...@web.de --- Searching for the term indexcleaner in the repo, i noticed that there are only definitions for the index-cleaning class, but no code calls the method IndexCleaner::run() ? https://github.com/KDE/baloo/search?utf8=%E2%9C%93=indexcleaner Could this be the reason that baloo fails to remove deleted files from the database? The database should be cleaned of deleted files at least once after baloo is started, since it can not know about files removed in its absence. Also, it should clean its database after the include/exclude configuration was changed. > balooctl clear I also made a bugreport about this, since its an error in balooctl. https://bugs.kde.org/show_bug.cgi?id=374736 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 374613] Project bin shows clip length of "00:00:04:30" when the clip is 5 seconds
https://bugs.kde.org/show_bug.cgi?id=374613 Jean-Baptiste Mardellechanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kde ||nlive/c27117f07bfdedad10462 ||b587f1b1b7f01f7ef33 --- Comment #6 from Jean-Baptiste Mardelle --- Git commit c27117f07bfdedad10462b587f1b1b7f01f7ef33 by Jean-Baptiste Mardelle. Committed on 08/01/2017 at 11:23. Pushed by mardelle into branch 'Applications/16.12'. Fix creation of project profile with messy fps M +37 -3src/doc/kdenlivedoc.cpp M +2-2src/mltcontroller/clipcontroller.cpp https://commits.kde.org/kdenlive/c27117f07bfdedad10462b587f1b1b7f01f7ef33 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 374741] download.kde.org over https
https://bugs.kde.org/show_bug.cgi?id=374741 Bruno Paganichanged: What|Removed |Added URL||https://download.kde.org CC||bruno.n.pag...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 374650] Duplicate okular_poppler backend selection entry
https://bugs.kde.org/show_bug.cgi?id=374650 Antonio Rojaschanged: What|Removed |Added CC||aro...@archlinux.org --- Comment #8 from Antonio Rojas --- https://git.reviewboard.kde.org/r/129791/ -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 369147] Regression: Cannot disable delete confirmation any more
https://bugs.kde.org/show_bug.cgi?id=369147 --- Comment #6 from d...@newtech.fi --- Created attachment 103288 --> https://bugs.kde.org/attachment.cgi?id=103288=edit No checkbox in kmail delete dialog Here we go. No checkbox... -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 369147] Regression: Cannot disable delete confirmation any more
https://bugs.kde.org/show_bug.cgi?id=369147 --- Comment #7 from d...@newtech.fi --- Created attachment 103289 --> https://bugs.kde.org/attachment.cgi?id=103289=edit Version info And here the version information -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 374741] New: download.kde.org over https
https://bugs.kde.org/show_bug.cgi?id=374741 Bug ID: 374741 Summary: download.kde.org over https Product: kde Version: unspecified Platform: Other OS: All Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bruno.n.pag...@gmail.com Target Milestone: --- Hi, First of all, sorry for not being able to file it under the download.kde.org component, but I’ve failed to find under which product it lies. Now, the issue: download.kde.org is not accessible over https (403 forbidden). I’m not sure if that’s wanted, and if so why, but I’d be glad if you could fix it. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 374740] New: Unplugging controller causes 100% usage of one CPU core
https://bugs.kde.org/show_bug.cgi?id=374740 Bug ID: 374740 Summary: Unplugging controller causes 100% usage of one CPU core Product: systemsettings Version: 5.8.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_joystick Assignee: unassigned-b...@kde.org Reporter: ras...@gmail.com Target Milestone: --- When in the joystick section of the input settings, unplugging my controller (Sony Dualshock 4) causes 25% CPU usage (quad core CPU -> 100% of one core). Always reproducible. -- You are receiving this mail because: You are watching all bug changes.
[parley] [Bug 368489] Download new vocabularies not working
https://bugs.kde.org/show_bug.cgi?id=368489 --- Comment #2 from Dimitris Kardarakos--- Yes, a set of vocabularies is retrieved now, after selecting any option (Parley or KWordQuiz). Nevertheless, a quite different record set from the one found in KDE Store > Parley > Parley Vocabularies (https://store.kde.org/browse/cat/216/ord/latest/). So, there are multiple vocabulary repositories, right? -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 225498] agenda view day labels do not match the day
https://bugs.kde.org/show_bug.cgi?id=225498 Martin Kollerchanged: What|Removed |Added Resolution|UNMAINTAINED|--- Status|RESOLVED|REOPENED --- Comment #4 from Martin Koller --- Still valid in 5.4.10 alpha1 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 261729] quickfilter filters favourite folders too
https://bugs.kde.org/show_bug.cgi?id=261729 Martin Kollerchanged: What|Removed |Added Version|2.0.89 |5.4.0 Resolution|UNMAINTAINED|--- Status|RESOLVED|REOPENED --- Comment #8 from Martin Koller --- It still does so with kmail 5.4.41 alpha1 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 374650] Duplicate okular_poppler backend selection entry
https://bugs.kde.org/show_bug.cgi?id=374650 --- Comment #7 from Patrick--- As far as I can see the problem isn't a duplicate generator but a problem with mimetypes. Freedesktop defines "application/x-pdf" as an alias of "application/pdf". The poppler backend supports both mimetypes, but in the mimetype lookup (QMimeType mimeType = mimeDatabase.mimeTypeForName(supported) in DocumentPrivate::generatorForMimeType) the result is the same mimetype "application/pdf". -- You are receiving this mail because: You are watching all bug changes.
[parley] [Bug 368489] Download new vocabularies not working
https://bugs.kde.org/show_bug.cgi?id=368489 Andreas Cord-Landwehrchanged: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Andreas Cord-Landwehr --- Please test again, should work now. However, for now you have to select "Parley" specifically as category. (at the right). There is a pending review for GHNS that will also fix this. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 374650] Duplicate okular_poppler backend selection entry
https://bugs.kde.org/show_bug.cgi?id=374650 --- Comment #6 from Oliver Sander--- Sure, here it is: [/home/sander/okular-{test|save}] are two additional source trees that I happen to have in my home directory.] ~> locate okularGenerator_poppler /home/sander/okular/build/generators/poppler/okularGenerator_poppler.so /home/sander/okular/build/generators/poppler/okularGenerator_poppler_automoc.cpp /home/sander/okular/build/generators/poppler/okularGenerator_poppler_automoc.dir /home/sander/okular/build/generators/poppler/CMakeFiles/okularGenerator_poppler.dir /home/sander/okular/build/generators/poppler/CMakeFiles/okularGenerator_poppler_automoc.dir /home/sander/okular/build/generators/poppler/CMakeFiles/okularGenerator_poppler.dir/CXX.includecache /home/sander/okular/build/generators/poppler/CMakeFiles/okularGenerator_poppler.dir/DependInfo.cmake /home/sander/okular/build/generators/poppler/CMakeFiles/okularGenerator_poppler.dir/annots.cpp.o /home/sander/okular/build/generators/poppler/CMakeFiles/okularGenerator_poppler.dir/build.make /home/sander/okular/build/generators/poppler/CMakeFiles/okularGenerator_poppler.dir/cmake_clean.cmake /home/sander/okular/build/generators/poppler/CMakeFiles/okularGenerator_poppler.dir/depend.internal /home/sander/okular/build/generators/poppler/CMakeFiles/okularGenerator_poppler.dir/depend.make /home/sander/okular/build/generators/poppler/CMakeFiles/okularGenerator_poppler.dir/flags.make /home/sander/okular/build/generators/poppler/CMakeFiles/okularGenerator_poppler.dir/formfields.cpp.o /home/sander/okular/build/generators/poppler/CMakeFiles/okularGenerator_poppler.dir/generator_pdf.cpp.o /home/sander/okular/build/generators/poppler/CMakeFiles/okularGenerator_poppler.dir/link.txt /home/sander/okular/build/generators/poppler/CMakeFiles/okularGenerator_poppler.dir/okularGenerator_poppler_automoc.cpp.o /home/sander/okular/build/generators/poppler/CMakeFiles/okularGenerator_poppler.dir/pdfsettings.cpp.o /home/sander/okular/build/generators/poppler/CMakeFiles/okularGenerator_poppler.dir/progress.make /home/sander/okular/build/generators/poppler/CMakeFiles/okularGenerator_poppler_automoc.dir/AutogenInfo.cmake /home/sander/okular/build/generators/poppler/CMakeFiles/okularGenerator_poppler_automoc.dir/AutomocOldMocDefinitions.cmake /home/sander/okular/build/generators/poppler/CMakeFiles/okularGenerator_poppler_automoc.dir/DependInfo.cmake /home/sander/okular/build/generators/poppler/CMakeFiles/okularGenerator_poppler_automoc.dir/build.make /home/sander/okular/build/generators/poppler/CMakeFiles/okularGenerator_poppler_automoc.dir/cmake_clean.cmake /home/sander/okular/build/generators/poppler/CMakeFiles/okularGenerator_poppler_automoc.dir/depend.internal /home/sander/okular/build/generators/poppler/CMakeFiles/okularGenerator_poppler_automoc.dir/depend.make /home/sander/okular/build/generators/poppler/CMakeFiles/okularGenerator_poppler_automoc.dir/progress.make /home/sander/okular/build/generators/poppler/okularGenerator_poppler_automoc.dir/moc_generator_pdf_24QWUT7JV56U7I.cpp /home/sander/okular/generators/poppler/libokularGenerator_poppler.json /home/sander/okular-inst/lib/x86_64-linux-gnu/plugins/okular/generators/okularGenerator_poppler.so /home/sander/okular-save/build/generators/poppler/okularGenerator_poppler.so /home/sander/okular-save/build/generators/poppler/okularGenerator_poppler_automoc.cpp /home/sander/okular-save/build/generators/poppler/CMakeFiles/okularGenerator_poppler.dir /home/sander/okular-save/build/generators/poppler/CMakeFiles/okularGenerator_poppler_automoc.dir /home/sander/okular-save/build/generators/poppler/CMakeFiles/okularGenerator_poppler.dir/CXX.includecache /home/sander/okular-save/build/generators/poppler/CMakeFiles/okularGenerator_poppler.dir/DependInfo.cmake /home/sander/okular-save/build/generators/poppler/CMakeFiles/okularGenerator_poppler.dir/annots.cpp.o /home/sander/okular-save/build/generators/poppler/CMakeFiles/okularGenerator_poppler.dir/build.make /home/sander/okular-save/build/generators/poppler/CMakeFiles/okularGenerator_poppler.dir/cmake_clean.cmake /home/sander/okular-save/build/generators/poppler/CMakeFiles/okularGenerator_poppler.dir/depend.internal /home/sander/okular-save/build/generators/poppler/CMakeFiles/okularGenerator_poppler.dir/depend.make /home/sander/okular-save/build/generators/poppler/CMakeFiles/okularGenerator_poppler.dir/flags.make /home/sander/okular-save/build/generators/poppler/CMakeFiles/okularGenerator_poppler.dir/formfields.cpp.o /home/sander/okular-save/build/generators/poppler/CMakeFiles/okularGenerator_poppler.dir/generator_pdf.cpp.o /home/sander/okular-save/build/generators/poppler/CMakeFiles/okularGenerator_poppler.dir/link.txt /home/sander/okular-save/build/generators/poppler/CMakeFiles/okularGenerator_poppler.dir/okularGenerator_poppler_automoc.cpp.o /home/sander/okular-save/build/generators/poppler/CMakeFiles/okularGenerator_poppler.dir/pdfsettings.cpp.o
[kwin] [Bug 374664] KWin crash on startup
https://bugs.kde.org/show_bug.cgi?id=374664 Martin Gräßlinchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Martin Gräßlin --- *** This bug has been marked as a duplicate of bug 372114 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372114] Crash in threaded KWin::X11StandalonePlatform::createOpenGLSafePoint
https://bugs.kde.org/show_bug.cgi?id=372114 Martin Gräßlinchanged: What|Removed |Added CC||barnaba...@gmail.com --- Comment #9 from Martin Gräßlin --- *** Bug 374664 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374664] KWin crash on startup
https://bugs.kde.org/show_bug.cgi?id=374664 Martin Gräßlinchanged: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|UNCONFIRMED --- Comment #2 from Martin Gräßlin --- Created attachment 103287 --> https://bugs.kde.org/attachment.cgi?id=103287=edit attachment-617-0.html -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 152150] Cannot 'Open as Root' files/directories
https://bugs.kde.org/show_bug.cgi?id=152150 Elvis Angelacciochanged: What|Removed |Added CC||alx...@gmail.com --- Comment #6 from Elvis Angelaccio --- *** Bug 374717 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374666] Snap to screen edge, simplify creating uneven partitions by mouse resizing
https://bugs.kde.org/show_bug.cgi?id=374666 Martin Gräßlinchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Martin Gräßlin --- There is a 3rd party extension: https://store.kde.org/p/1112552/ -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 374717] Open as root
https://bugs.kde.org/show_bug.cgi?id=374717 Elvis Angelacciochanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||elvis.angelac...@kde.org Resolution|--- |DUPLICATE --- Comment #1 from Elvis Angelaccio --- *** This bug has been marked as a duplicate of bug 152150 *** -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 374660] Krunner first run accepts only one character
https://bugs.kde.org/show_bug.cgi?id=374660 Martin Gräßlinchanged: What|Removed |Added Product|kwin|krunner Component|wayland-generic |general -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374711] Kwin crashed for unknown reasons
https://bugs.kde.org/show_bug.cgi?id=374711 Martin Gräßlinchanged: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|DUPLICATE |--- --- Comment #2 from Martin Gräßlin --- Created attachment 103284 --> https://bugs.kde.org/attachment.cgi?id=103284=edit attachment-32221-0.html -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361236] Aurorae crashes in QQmlBinding::write on creation - Qt 5.6
https://bugs.kde.org/show_bug.cgi?id=361236 Martin Gräßlinchanged: What|Removed |Added CC||bill6...@alumni.rutgers.edu --- Comment #91 from Martin Gräßlin --- *** Bug 374711 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 369147] Regression: Cannot disable delete confirmation any more
https://bugs.kde.org/show_bug.cgi?id=369147 --- Comment #5 from Laurent Montel--- Put a screenshot of your dialogbox as I have one checkbox here. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374711] Kwin crashed for unknown reasons
https://bugs.kde.org/show_bug.cgi?id=374711 Martin Gräßlinchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Martin Gräßlin --- As a workaround use the breeze decoration. *** This bug has been marked as a duplicate of bug 361236 *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 374595] allow the use of Kontakt / Kmail without the use of Akonadi (as you do not manage to make it work)
https://bugs.kde.org/show_bug.cgi?id=374595 Norbert Blobelchanged: What|Removed |Added Platform|Other |openSUSE RPMs -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 374595] allow the use of Kontakt / Kmail without the use of Akonadi (as you do not manage to make it work)
https://bugs.kde.org/show_bug.cgi?id=374595 --- Comment #2 from Norbert Blobel--- (In reply to Denis Kurz from comment #1) > Norbert, thanks for your report. I'm afraid it won't happen, though, unless > some extremely motivated new developers show up. Akonadi is deeply rooted in > the PIM apps. > > However, you might want to try a (much) more recent version of the KDE PIM > suite. KDE PIM 4.14 has been unsupported since August 2015, and a huge > amount of bugs has been fixed since then. Hi Denis, LOL, extremely motivated developers. I am afraid they are needed regardless. Since KDE PIM 4.x.x Kontakt, Kmail and Akonadi have not been working properly. In fact, KDE PIM has been destroyed. It just does not work properly. Now, just look at OpenSuSE Leap 42.2 with kmail5. The mailing list is full with complaints. People are fed up. I considered upgrading to leap 42.2. But since the kmail nightmare continues with kamil5, I wont. Under Leap 42.1 I have a "workable" Kmail/Kontakt. But I all honesty, I am growing increasingly tiered of a bodged KDE which can't get its act together. If anything, a migration to a new email client/PIM/Desktop is on order. I've been using KDE since SuSE 7.1 Kind Regards Norbert Blobel -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374727] HiDPI display, snapping windows zone
https://bugs.kde.org/show_bug.cgi?id=374727 Martin Gräßlinchanged: What|Removed |Added Component|general |core --- Comment #3 from Martin Gräßlin --- Ok, I understand. That might require a larger restructuring as the ui also needs changing. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 374174] dolphin crashed on trying to change dir
https://bugs.kde.org/show_bug.cgi?id=374174 --- Comment #4 from Elvis Angelaccio--- (In reply to Martin Jost from comment #3) > I have a question to the request: > "If you can reproduce the crash again, please install debug symbols and > attach a new backtrace in this report. > See also: https://community.kde.org/Guidelines_and_HOWTOs/Debugging; > > Do I get this right: I need to compile from source to do so ? > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/Debugging_symbols > > Or do I need to just add some '*Devel*'-RPMs ? Neither. You just need to install the "debug" packages from the repository. This differs across distributions, ask in openSUSE channels for more details. > > Martin -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 374739] New: Video shrunk and not rendering
https://bugs.kde.org/show_bug.cgi?id=374739 Bug ID: 374739 Summary: Video shrunk and not rendering Product: kdenlive Version: 16.12.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: edward.l...@gmail.com Target Milestone: --- Created attachment 103282 --> https://bugs.kde.org/attachment.cgi?id=103282=edit This is what I see when I load this project. Ok, this is a very strange thing that has happened... Yesterday I was working on a video and all looked ok, but when trying to render it it would immediately say "Rendering finished in 00:00:00" and never produce a file. I tried all manner of formats, even a series of PNG exports, but nothing. It was anyways late so I decided on shutting it down and maybe starting it fresh tomorrow would solve things. But things seem to only get worse... Now the wide-screen video has gotten an aspect of 4:3 and ended up in the middle of the screen as if I had a 800x600 video in a 720p project. Also, the rendering still refuses to work. The video clip is from a JVC HD camera that calls the file .MTS and I've had no problems with it in the past. /Edward Kdenlive: 16.12.0 MLT: 6.5.0 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 309300] Esc as the default shortcut of "Set Focus to The Panel" is problematic for the embedded terminal
https://bugs.kde.org/show_bug.cgi?id=309300 --- Comment #14 from Toni Asensi Esteve--- Created attachment 103281 --> https://bugs.kde.org/attachment.cgi?id=103281=edit Instead of using a "Show-Hide" nomenclature, KDE normally uses a "Show" nomenclature and a disabled-or-enabled tick. Instead of using a "Show-Hide" nomenclature, KDE normally uses a "Show" nomenclature and a disabled-or-enabled tick. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 374737] Moving emails from a local folder to another duplicates mails
https://bugs.kde.org/show_bug.cgi?id=374737 Christian Boltzchanged: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christian Boltz --- Sorry, this bugreport was accidently submitted twice, see bug 374738 for it's (still open, and valid) twin. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 294517] Moving emails from a local folder to another duplicates mails
https://bugs.kde.org/show_bug.cgi?id=294517 --- Comment #7 from Christian Boltz--- I'm sorry to disappoint you, but I've seen this with KMail 5.4.0 some days ago. I just opened bug 374738 ;-) -- You are receiving this mail because: You are watching all bug changes.
[parley] [Bug 368148] Cannot upload vocabulary collection
https://bugs.kde.org/show_bug.cgi?id=368148 Andreas Cord-Landwehrchanged: What|Removed |Added Assignee|parley-bugs-n...@kde.org|cordlandw...@kde.org CC||cordlandw...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 374737] New: Moving emails from a local folder to another duplicates mails
https://bugs.kde.org/show_bug.cgi?id=374737 Bug ID: 374737 Summary: Moving emails from a local folder to another duplicates mails Product: kmail2 Version: 5.4.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: folders Assignee: kdepim-b...@kde.org Reporter: kde-b...@cboltz.de Target Milestone: --- [copy from https://bugs.kde.org/show_bug.cgi?id=294517 ] When moving (by drag & drop) emails from a folder (say 'inbox') to another (say 'filtered'), the emails are moved, but marked as unread in the new location, before after a few seconds they reappear, duplicated, in the original folder and marked as unread as well (even if they were marked as read before). The emails are all local, no remote server involved. Emails were fetched from a POP3 account before. [end copy] In my case, I moved the mails from a local folder to a folder in an IMAP account, and they re-appeared in the local folder. Note: This doesn't happen always. Moving _lots of mails_ (select 30 mails, move them at once) makes this more likely to happen. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 374738] New: Moving emails from a local folder to another duplicates mails
https://bugs.kde.org/show_bug.cgi?id=374738 Bug ID: 374738 Summary: Moving emails from a local folder to another duplicates mails Product: kmail2 Version: 5.4.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: folders Assignee: kdepim-b...@kde.org Reporter: kde-b...@cboltz.de Target Milestone: --- [copy from https://bugs.kde.org/show_bug.cgi?id=294517 ] When moving (by drag & drop) emails from a folder (say 'inbox') to another (say 'filtered'), the emails are moved, but marked as unread in the new location, before after a few seconds they reappear, duplicated, in the original folder and marked as unread as well (even if they were marked as read before). The emails are all local, no remote server involved. Emails were fetched from a POP3 account before. [end copy] In my case, I moved the mails from a local folder to a folder in an IMAP account, and they re-appeared in the local folder. Note: This doesn't happen always. Moving _lots of mails_ (select 30 mails, move them at once) makes this more likely to happen. -- You are receiving this mail because: You are watching all bug changes.
[parley] [Bug 368490] Get New Themes shows collections instead of themes
https://bugs.kde.org/show_bug.cgi?id=368490 Andreas Cord-Landwehrchanged: What|Removed |Added CC||cordlandw...@kde.org Assignee|parley-bugs-n...@kde.org|cordlandw...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[parley] [Bug 368489] Download new vocabularies not working
https://bugs.kde.org/show_bug.cgi?id=368489 Andreas Cord-Landwehrchanged: What|Removed |Added Assignee|parley-bugs-n...@kde.org|cordlandw...@kde.org CC||cordlandw...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 374180] Other tags assigned to the picture is disturbing when looking at face tags
https://bugs.kde.org/show_bug.cgi?id=374180 --- Comment #8 from ohm196...@gmail.com --- (In reply to Simon from comment #7) > Thanks for the screenshot, it definitely helped me understand. > This is however not a bug but intended. The information displayed below > the thumbnail in icon view is specific to the entire image also with > active people sidebar. Only the overlay that allows to confirm/type the > name or discard the face rectangle are specific to the view shown with > people sidebar active. > > Regarding your other two questions: > - There is no way to mark a face but not use this face for face > recognition. > - There is also no way to separate tags applied to the entire image and > only to areas. Every tag applied to an area (i.e. face) is also applied > as a tag to the entire image. Hi Simon I agree that this is not quite a bug. I believed I had classified it as a wish, not a bug, but I may have failed. It is good that the picture helped you understand. Here is a further explaination on why I found it confusing. When I add names to the automatically selected rectangles with detected faces after running face detection I simly chose the people tag, and then I worked in the thumbnail view. If a picture had a face which I already had given a name this name would appear below the thumbnail of someone elses face. It is not a big problem, but it is confusing. Especially as I ended up in the thumnail mode without choosing this actively. It is more confusing when I have only chosen the people tag, than when I already have chosen one particular name to look at. In the "preview image" mode it works perfectly when I let it "Show Face Tags". So again, I agree that this is not a bug, but I am still of the opinion that the interface could be further improved when the people tags is chosen and we are in the thumbnail mode. It is a thumbnail of the marked face which is shown, not a thumbnail of the picture. Odd Harry -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 369147] Regression: Cannot disable delete confirmation any more
https://bugs.kde.org/show_bug.cgi?id=369147 --- Comment #4 from d...@newtech.fi --- INVALID? Really? The checkbox it still missing... -- You are receiving this mail because: You are watching all bug changes.