[plasmashell] [Bug 434441] Autostart script to unlock ssh keys doesn't seem to be launched when using systemd startup
https://bugs.kde.org/show_bug.cgi?id=434441 Rémi Verschelde changed: What|Removed |Added CC||rversche...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421392] plasmashell crashes when opening the thermal monitor widget settings
https://bugs.kde.org/show_bug.cgi?id=421392 --- Comment #8 from Rémi Verschelde --- (In reply to Rémi Verschelde from comment #7) > This bug here is triggered specifically and in a reproducible way by the > Thermal Monitor plasmoid, and this only since a recent update that rolling > distros have received in May. To clarify, I mean a recent Plasma update. The plasmoid itself has not seen any upstream activity (commit) in 2 years. The upstream ticket is linked in comment 3. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421392] plasmashell crashes when opening the thermal monitor widget settings
https://bugs.kde.org/show_bug.cgi?id=421392 Rémi Verschelde changed: What|Removed |Added CC||rversche...@gmail.com --- Comment #7 from Rémi Verschelde --- (In reply to Marco Martin from comment #6) > > *** This bug has been marked as a duplicate of bug 366485 *** I don't understand why this would be a duplicate of that four year old bug. >From a quick look, the stack traces are not the same at all. This bug here is triggered specifically and in a reproducible way by the Thermal Monitor plasmoid, and this only since a recent update that rolling distros have received in May. My last Plasma-related updates were to plasma-desktop 5.18.5 and KF5 5.70.1: $ rpm -qa --last | grep plasma lib64kf5plasma-devel-5.70.1-1.mga8.x86_64 2020-05-16T10:50:59 CEST plasma-framework-5.70.1-1.mga8.x86_64 2020-05-16T10:50:58 CEST lib64kf5plasmaquick5-5.70.1-1.mga8.x86_64 2020-05-16T10:50:58 CEST lib64kf5plasma5-5.70.1-1.mga8.x86_64 2020-05-16T10:50:58 CEST task-plasma5-minimal-5.18.5-1.mga8.noarch 2020-05-09T14:36:25 CEST plasma-desktop-5.18.5-2.mga8.x86_64 2020-05-09T14:36:25 CEST I think most +1 reporters here might have similar versions. The widget did not trigger a crash of plasmashell before these updates. It's not fixed by a reboot, and can be triggered and reproduced consistently and easily: - Install said plasmoid - Try to configure it I would ask for this bug to be reopened. -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 332065] Metadata not shown for non-indexed files
https://bugs.kde.org/show_bug.cgi?id=332065 --- Comment #36 from Rémi Verschelde --- (In reply to Wolfgang Bauer from comment #35) > Btw, in openSUSE we never had this problem as the lib (libKF5BalooWidgets5) > and the tool (baloo_filemetadata_temp_extractor) are in one and the same > package named baloo5-widgets (which is required by dolphin and other > applications that might use it). That makes sense, I had missed this library. I'll make Mageia's lib64kf5baloowidgets5 package require our baloo-widgets (which contains baloo_filemetadata_temp_extractor) then. -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 332065] Metadata not shown for non-indexed files
https://bugs.kde.org/show_bug.cgi?id=332065 --- Comment #34 from Rémi Verschelde --- (In reply to Wolfgang Bauer from comment #33) > You may want to report that to your distribution though, they should > probably make sure that that package is installed by default... Yes I've packaged a fix for Mageia already: https://bugs.mageia.org/show_bug.cgi?id=23194 But thought I'd mention here for users of other distros who might have the same issue, as I'm not sure it's obvious to all distro packagers that baloo-widgets should always be installed with baloo. -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 332065] Metadata not shown for non-indexed files
https://bugs.kde.org/show_bug.cgi?id=332065 Rémi Verschelde changed: What|Removed |Added CC||rversche...@gmail.com --- Comment #32 from Rémi Verschelde --- Sorry for bumping an old bug report, but I've spent a morning trying to debug a similar issue (and this bug report is well referenced by search engines when looking for info on metadata in Dolphin). So here's what I found today: for metadata extraction to work on non-indexed files in Plasma 5, make sure that you have baloo-widgets installed on your distro (or the package containing /usr/bin/baloo_filemetadata_temp_extractor if named differently). This tool is the one used for on-the-fly extraction of metadata when Baloo's file indexing is off. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 384617] Meta information not shown in Dolphin inside home directory (video reproduce inside)
https://bugs.kde.org/show_bug.cgi?id=384617 --- Comment #18 from Rémi Verschelde --- (In reply to Rémi Verschelde from comment #17) > I'm having a similar issue on Mageia 6 (Plasma 5.12.2, KF5 5.42.0), but > there's something I don't understand. > > Bug 332065 hints that metadata *should* be available when file indexing is > disabled. In my case, I tried tweaking all settings and could never get any > EXIF metadata to show for photos with indexing disabled. False alarm, I found that the package "baloo-widgets" was not installed, and it's the one containing /usr/bin/baloo_filemetadata_temp_extractor which is used for extracting metadata on-the-fly when file indexing is disabled. I'll put a comment about it in 332065 for those who might have missed this too. (BTW, baloo-widgets contains *only* this tool, it sounds like it might be time to merge it into the main baloo repo and deprecate baloo-widgets.) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 384617] Meta information not shown in Dolphin inside home directory (video reproduce inside)
https://bugs.kde.org/show_bug.cgi?id=384617 Rémi Verschelde changed: What|Removed |Added CC||rversche...@gmail.com --- Comment #17 from Rémi Verschelde --- I'm having a similar issue on Mageia 6 (Plasma 5.12.2, KF5 5.42.0), but there's something I don't understand. Bug 332065 hints that metadata *should* be available when file indexing is disabled. In my case, I tried tweaking all settings and could never get any EXIF metadata to show for photos with indexing disabled. So is the resolution of bug 332065 "WONTFIX" in the end? Or should it be possible to get file metadata without having baloo indexing (possibly by rescanning all files of the currently opened folder to display the metadata, would be fine by me). If I turn indexing on, I get 10 GB of index, and on my limited /home partition I can't justify this just to get metadata displayed in Dolphin. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 360037] KF5 yakuake sometimes gets detached and shows up in the task manager
https://bugs.kde.org/show_bug.cgi?id=360037 --- Comment #14 from Rémi Verschelde <rversche...@gmail.com> --- I can also still reproduce the bug on Mageia 6 with Qt 5.6.2 and yakuake 3.0.3. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362941] Java Process Is Unresponsive In System Tray - Jitsi
https://bugs.kde.org/show_bug.cgi?id=362941 --- Comment #28 from Rémi Verschelde <rversche...@gmail.com> --- Nice work David, thanks! I've cherry-picked the patch for Mageia's plasma-workspace 5.8.6 package, we will report back once it has been tested. Note that you should probably edit the CMakeLists.txt to make XTest/xtst a required dependency, otherwise plasma-workspace fails building: [ 98%] Building CXX object xembed-sni-proxy/CMakeFiles/xembedsniproxy.dir/xtestsender.cpp.o /home/iurt/rpmbuild/BUILD/plasma-workspace-5.8.6/xembed-sni-proxy/xtestsender.cpp:21:34: fatal error: X11/extensions/XTest.h: No such file or directory compilation terminated. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 360037] KF5 yakuake sometimes gets detached and shows up in the task manager
https://bugs.kde.org/show_bug.cgi?id=360037 --- Comment #11 from Rémi Verschelde <rversche...@gmail.com> --- Actually I spoke too fast, following the steps in comment 0 does reproduce the behaviour described in comment 2. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 360037] KF5 yakuake sometimes gets detached and shows up in the task manager
https://bugs.kde.org/show_bug.cgi?id=360037 --- Comment #10 from Rémi Verschelde <rversche...@gmail.com> --- FWIW, I haven't reproduced this issue in a long time - I'm now running Yakuake 3.0.2 on Plasma 5.8.5 with Qt 5.6.2, all this on Mageia 6. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362941] Java Process Is Unresponsive In System Tray - Jitsi
https://bugs.kde.org/show_bug.cgi?id=362941 Rémi Verschelde <rversche...@gmail.com> changed: What|Removed |Added CC||rversche...@gmail.com --- Comment #16 from Rémi Verschelde <rversche...@gmail.com> --- May I suggest to rephrase the bug Summary to something more accurate, as this bug report has grown to encompass more than only java applications and/or jitsi. >From a bug triage point of view, you have two options: - Keep this bug report for java applications only, and rename it to something like "System tray icons for Java applications are not responsive". Then another bug report should be opened for the GTK+3 applications with unreponsive systray icons that were mentioned below and/or in bug reports that were closed as duplicates of this one. - Keep this bug report for both java and GTK+3 applications with an unresponsive systray icon, and rename it to something like "System tray icons for Java and GTK+3 applications are not responsive". Also, the Platform should likely be changed to something more accurate than Archlinux Packages Linux, as there have been enough bug reports from various distros to find out that it's not a distro-specific issue. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 368785] konsole tab title format only uses the first program you ever ran, not the current one
https://bugs.kde.org/show_bug.cgi?id=368785 Rémi Verschelde <rversche...@gmail.com> changed: What|Removed |Added CC||rversche...@gmail.com --- Comment #6 from Rémi Verschelde <rversche...@gmail.com> --- I can confirm the bug on 16.08.1, and that the patch in comment 5 fixes it. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 329740] Okular hangs in presentation mode when displaying PDFs when default printer is not accessible
https://bugs.kde.org/show_bug.cgi?id=329740 Rémi Verschelde <rversche...@gmail.com> changed: What|Removed |Added CC||rversche...@gmail.com --- Comment #12 from Rémi Verschelde <rversche...@gmail.com> --- Still valid in Mageia 6 today with okular 16.04.3: https://bugs.mageia.org/show_bug.cgi?id=16330 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 364387] kmymoney 4.8.0 builds libpayeeidentifier.so but asks for libkmm_payeeidentifier.so
https://bugs.kde.org/show_bug.cgi?id=364387 --- Comment #11 from Rémi Verschelde <rversche...@gmail.com> --- So to clarify, the bug is not "kmymoney 4.8.0 builds libpayeeidentifier.so but asks for libkmm_payeeidentifier.so" as currently titled, but more "kmymoney 4.8.0 names a lib binary libkmm_payeeidentifier.so instead of libkmm_payeeidentifier.so.$libmajor, triggering packaging issues". -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 364387] kmymoney 4.8.0 builds libpayeeidentifier.so but asks for libkmm_payeeidentifier.so
https://bugs.kde.org/show_bug.cgi?id=364387 Rémi Verschelde <rversche...@gmail.com> changed: What|Removed |Added CC||rversche...@gmail.com --- Comment #10 from Rémi Verschelde <rversche...@gmail.com> --- As José mentions in comment 9, the problem is that libkmm_payeeidentifier.so is not properly libified; it's only provided as a non-symlink .so and not a binary .so.4.14.21 symlinked to the .so. Excerpt from the (successful, after the parallel build issue was fixed) build on Mageia 6 x86_64 [0]: extracting debug info from /home/iurt/rpmbuild/BUILDROOT/kmymoney-4.8.0-1.mga6.x86_64/usr/lib64/libpayeeidentifier_iban_bic_widgets.so.4.14.21 extracting debug info from /home/iurt/rpmbuild/BUILDROOT/kmymoney-4.8.0-1.mga6.x86_64/usr/lib64/libkmm_widgets.so.4.14.21 extracting debug info from /home/iurt/rpmbuild/BUILDROOT/kmymoney-4.8.0-1.mga6.x86_64/usr/lib64/libkmm_kdchart.so.4.14.21 extracting debug info from /home/iurt/rpmbuild/BUILDROOT/kmymoney-4.8.0-1.mga6.x86_64/usr/lib64/kde4/kmm_ofximport.so extracting debug info from /home/iurt/rpmbuild/BUILDROOT/kmymoney-4.8.0-1.mga6.x86_64/usr/lib64/kde4/kmm_weboob.so extracting debug info from /home/iurt/rpmbuild/BUILDROOT/kmymoney-4.8.0-1.mga6.x86_64/usr/lib64/kde4/kmm_csvimport.so extracting debug info from /home/iurt/rpmbuild/BUILDROOT/kmymoney-4.8.0-1.mga6.x86_64/usr/lib64/kde4/payeeidentifier_nationalAccount_ui.so extracting debug info from /home/iurt/rpmbuild/BUILDROOT/kmymoney-4.8.0-1.mga6.x86_64/usr/lib64/kde4/kmm_reconciliationreport.so extracting debug info from /home/iurt/rpmbuild/BUILDROOT/kmymoney-4.8.0-1.mga6.x86_64/usr/lib64/kde4/kmm_printcheck.so extracting debug info from /home/iurt/rpmbuild/BUILDROOT/kmymoney-4.8.0-1.mga6.x86_64/usr/lib64/kde4/payeeidentifier_iban_bic_delegates.so extracting debug info from /home/iurt/rpmbuild/BUILDROOT/kmymoney-4.8.0-1.mga6.x86_64/usr/lib64/kde4/kmm_icalendarexport.so extracting debug info from /home/iurt/rpmbuild/BUILDROOT/kmymoney-4.8.0-1.mga6.x86_64/usr/lib64/kde4/konlinetasks_sepa.so extracting debug info from /home/iurt/rpmbuild/BUILDROOT/kmymoney-4.8.0-1.mga6.x86_64/usr/lib64/kde4/kmm_csvexport.so extracting debug info from /home/iurt/rpmbuild/BUILDROOT/kmymoney-4.8.0-1.mga6.x86_64/usr/lib64/kde4/kcm_kmm_printcheck.so extracting debug info from /home/iurt/rpmbuild/BUILDROOT/kmymoney-4.8.0-1.mga6.x86_64/usr/lib64/kde4/payeeidentifier_ibanbic_storageplugin.so extracting debug info from /home/iurt/rpmbuild/BUILDROOT/kmymoney-4.8.0-1.mga6.x86_64/usr/lib64/kde4/konlinetasks_national.so extracting debug info from /home/iurt/rpmbuild/BUILDROOT/kmymoney-4.8.0-1.mga6.x86_64/usr/lib64/kde4/kcm_kmm_icalendarexport.so extracting debug info from /home/iurt/rpmbuild/BUILDROOT/kmymoney-4.8.0-1.mga6.x86_64/usr/lib64/kde4/payeeidentifier_nationalaccount_storageplugin.so extracting debug info from /home/iurt/rpmbuild/BUILDROOT/kmymoney-4.8.0-1.mga6.x86_64/usr/lib64/libkmm_plugin.so.4.14.21 extracting debug info from /home/iurt/rpmbuild/BUILDROOT/kmymoney-4.8.0-1.mga6.x86_64/usr/lib64/libpayeeidentifier_nationalAccount.so.4.14.21 extracting debug info from /home/iurt/rpmbuild/BUILDROOT/kmymoney-4.8.0-1.mga6.x86_64/usr/lib64/libkmm_payeeidentifier.so extracting debug info from /home/iurt/rpmbuild/BUILDROOT/kmymoney-4.8.0-1.mga6.x86_64/usr/lib64/libpayeeidentifier_iban_bic.so.4.14.21 extracting debug info from /home/iurt/rpmbuild/BUILDROOT/kmymoney-4.8.0-1.mga6.x86_64/usr/lib64/libkmm_mymoney.so.4.14.21 I took the debuginfo extraction part, not because it is relevant for the issue, but because it shows the inconsistency in the naming of the binary libs (the ones from which debugging symbols will be extracted). All libs (in /usr/lib64) have the following naming scheme: libkmm_$name.so.4.14.21, apart from libkmm_payeeidentifier.so. On the other hand plugins in /usr/lib64/kde4 don't have a suffix after the .so, but that's fine for plugins. This is a simple issue that needs to be fixed in your CMake buildsystem. It's non critical in itself, but triggered various issues in Mageia's packaging [1] that José needs to workaround: - Since it had no .so suffix, José did not split libkmm_payeeidentifier.so in its own library package. Still, RPM's autorequires know that libkmm_mymoney.so.4.14.21 needs it, so RPM will look for it. - Against due to the unconventional .so suffix, the file was globbed by /usr/lib64/*.so and thus packaged within Mageia's lib64kmymoney-devel, i.e. the development package meant to hold .so symlinks and headers. - So the non-devel package that holds libkmm_mymoney.so.4.14.21 requires libkmm_payeeidentifier.so()(64bit), which is provided by lib64kmymoney-devel and thus needs to be installed, but it fails because the latter does not provide libkmm_payeeidentifier(64bit) due to the lack of a libkmm_payeeidentifier.so symlink. That triggers thi
[plasmashell] [Bug 360192] Pidgin (gtk2) tray icon is tiny, ksensors (kde3) tray icon is misplaced
https://bugs.kde.org/show_bug.cgi?id=360192 --- Comment #8 from Rémi Verschelde <rversche...@gmail.com> --- Using 5.6.4, I can't reproduce the bug anymore (I think David's fix mentioned in comment 6 fixed the bug properly). -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 358348] krunner crashes when doing a simple search
https://bugs.kde.org/show_bug.cgi?id=358348 Rémi Verschelde <rversche...@gmail.com> changed: What|Removed |Added CC||rversche...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 361975] krunner crashes when processing the expression "2^12", apparently linked to baloo
https://bugs.kde.org/show_bug.cgi?id=361975 --- Comment #1 from Rémi Verschelde <rversche...@gmail.com> --- (Note that it's potentially a duplicate, but there are so many open bugs for krunner crashes, quite often involving baloo, that I can't evaluate myself what bug report might be a duplicate of my issue, so I preferred to open a new one and leave it to the KDE bugsquad/krunner maintainers). -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 361975] New: krunner crashes when processing the expression "2^12", apparently linked to baloo
https://bugs.kde.org/show_bug.cgi?id=361975 Bug ID: 361975 Summary: krunner crashes when processing the expression "2^12", apparently linked to baloo Product: krunner Version: 5.6.2 Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: filesearch Assignee: m...@vhanda.in Reporter: rversche...@gmail.com Trying to compute "2^12" in krunner, I get a crash with this gdb backtrace: #0 0x745e0ea8 in __memcpy_sse2_unaligned () at /lib64/libc.so.6 #1 0x7fffc6e411a3 in Baloo::PostingCodec::decode(QByteArray const&) () at /lib64/libKF5BalooEngine.so.5 #2 0x7fffc6e2cebe in DBPostingIterator::DBPostingIterator(void*, unsigned int) () at /lib64/libKF5BalooEngine.so.5 #3 0x7fffc6e2cf61 in Baloo::PostingDB::iter(QByteArray const&) () at /lib64/libKF5BalooEngine.so.5 #4 0x7fffc6e36e5a in Baloo::Transaction::postingIterator(Baloo::EngineQuery const&) const () at /lib64/libKF5BalooEngine.so.5 #5 0x7fffc7282a5f in Baloo::SearchStore::constructQuery(Baloo::Transaction*, Baloo::Term const&) () at /lib64/libKF5Baloo.so.5 #6 0x7fffc7282cda in Baloo::SearchStore::constructQuery(Baloo::Transaction*, Baloo::Term const&) () at /lib64/libKF5Baloo.so.5 #7 0x7fffc7283be9 in Baloo::SearchStore::exec(Baloo::Term const&, unsigned int, int, bool) () at /lib64/libKF5Baloo.so.5 #8 0x7fffc72731df in Baloo::Query::exec() () at /lib64/libKF5Baloo.so.5 #9 0x7fffc7493600 in SearchRunner::match(Plasma::RunnerContext&, QString const&, QString const&) () at /usr/lib64/qt5/plugins/krunner_baloosearchrunner.so #10 0x7fffc7494316 in SearchRunner::match(Plasma::RunnerContext&) () at /usr/lib64/qt5/plugins/krunner_baloosearchrunner.so #11 0x7fffd8ba71f8 in Plasma::AbstractRunner::performMatch(Plasma::RunnerContext&) () at /lib64/libKF5Runner.so.5 #12 0x7fffd8986807 in ThreadWeaver::Executor::run(QSharedPointer const&, ThreadWeaver::Thread*) () at /lib64/libKF5ThreadWeaver.so.5 #13 0x7fffd8985570 in ThreadWeaver::Job::execute(QSharedPointer const&, ThreadWeaver::Thread*) () at /lib64/libKF5ThreadWeaver.so.5 #14 0x7fffd8984d30 in ThreadWeaver::Thread::run() () at /lib64/libKF5ThreadWeaver.so.5 #15 0x74d26579 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #16 0x7288a65d in start_thread () at /lib64/libpthread.so.0 #17 0x74640dad in clone () at /lib64/libc.so.6 Reproducible: Always Steps to Reproduce: 1. Start krunner (Alt+F2) 2. Type "2^1" (without the quotes): it works OK, returns 1 and shows matching files, etc. 3. Add a 2, i.e. type "2^12": krunner crashes (sometimes before showing the result, sometimes after) 4. To get the backtrace, kill krunner and run it through gdb, then do the above steps. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360192] Pidgin (gtk2) tray icon is tiny, ksensors (kde3) tray icon is misplaced
https://bugs.kde.org/show_bug.cgi?id=360192 --- Comment #5 from Rémi Verschelde <rversche...@gmail.com> --- > Can you confirm if that really is with 5.5.95 (5.6 beta) or git master (which > will also report itself as 5.5.95)? In my case it is 5.6 beta, as packaged in Mageia Cauldron. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360192] Pidgin (gtk2) tray icon is tiny, ksensors (kde3) tray icon is misplaced
https://bugs.kde.org/show_bug.cgi?id=360192 Rémi Verschelde <rversche...@gmail.com> changed: What|Removed |Added CC||rversche...@gmail.com --- Comment #2 from Rémi Verschelde <rversche...@gmail.com> --- Created attachment 97858 --> https://bugs.kde.org/attachment.cgi?id=97858=edit Screenshot of the systray in 5.5.95 with tiny hexchat icon Same issue for hexchat's systray icon, which is IINM also GTK+2. (see attached screenshot) I'm seeing this issue with plasma-workspace 5.5.95, it was working fine with 5.5.4. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 360037] KF5 yakuake sometimes gets detached and shows up in the task manager
https://bugs.kde.org/show_bug.cgi?id=360037 --- Comment #2 from Rémi Verschelde <rversche...@gmail.com> --- > 3. Pressing the toggle button again should fold it and remove it from the > taskbar; pressing the taskbar button makes Yakuake disappear, and quite hard > to find back. Erratum here: actually pressing the task in the task bar only folds the terminal again, but another press of the toggle button shows it again (i.e. normal behaviour). The behaviour I described was what happened in pre-3.0.0 git builds. The rest of the issue as described in the other points is of course still valid. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 360037] KF5 yakuake sometimes gets detached and shows up in the task manager
https://bugs.kde.org/show_bug.cgi?id=360037 --- Comment #1 from Rémi Verschelde <rversche...@gmail.com> --- Created attachment 97661 --> https://bugs.kde.org/attachment.cgi?id=97661=edit Screenshot of Yakuake in "detached task" mode -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 360037] New: KF5 yakuake sometimes gets detached and shows up in the task manager
https://bugs.kde.org/show_bug.cgi?id=360037 Bug ID: 360037 Summary: KF5 yakuake sometimes gets detached and shows up in the task manager Product: yakuake Version: 3.0.2 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: rversche...@gmail.com First of all thanks for the 3.0.2 release, it's great! Last bug that I have with it since the move to KF5 is as follows: when expanding the yakuake window, it may _at times_ be "detached" and show up like a normal application in the Plasma taskbar. I guess there is a focus conflict of some sort. Reproducible: Always Steps to Reproduce: 1. Press the toggle button repeatedly, without doing anything else in particular 2. After a few presses, the "Yakuake" task should appear in the taskbar 3. Pressing the toggle button again should fold it and remove it from the taskbar; pressing the taskbar button makes Yakuake disappear, and quite hard to find back. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 336228] pressing f12 (or the equivalent closekey) causes respawn of yakuake if mouse is in yakuake
https://bugs.kde.org/show_bug.cgi?id=336228 --- Comment #20 from Rémi Verschelde <rversche...@gmail.com> --- I can confirm the fix on the current HEAD of the frameworks branch, I've update my Mageia package and it works like a charm. Thanks a lot! I use yakuake extensively and this issue was quite annoying :) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 355410] the scroll speed of QML scroll area is too slow with Libinput
https://bugs.kde.org/show_bug.cgi?id=355410 Rémi Verschelde <rversche...@gmail.com> changed: What|Removed |Added CC||rversche...@gmail.com --- Comment #3 from Rémi Verschelde <rversche...@gmail.com> --- I have the exact same issue as Christian in comment 2, though I can't confirm if it's really the same one as comment 0. Many applications work fine but Dolphin and the application launcher have unbearably slow scrolling speeds. Testing on Mageia Cauldron (6) with Plasma 5.5.4, Dolphin 15.12.1, Qt 5.6.0 beta. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358143] New: Segmentation fault during normal usage (both autostart and manual start)
https://bugs.kde.org/show_bug.cgi?id=358143 Bug ID: 358143 Summary: Segmentation fault during normal usage (both autostart and manual start) Product: plasmashell Version: 5.5.3 Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: XembedSNIProxy Assignee: plasma-b...@kde.org Reporter: rversche...@gmail.com Created attachment 96702 --> https://bugs.kde.org/attachment.cgi?id=96702=edit Console output and gdb backtrace around a segfault Using Plasma 5.5.3 on Mageia Cauldron 64-bit with Qt 5.6.0-beta. XembedSNIProxy seems to segfault relatively often with (so far) no reliable pattern that I could identify. I've opened a bug report on Mageia's bugzilla about this issue, where I started to do some investigation: https://bugs.mageia.org/show_bug.cgi?id=17516 The utility is properly started with plasmashell, but apparently crashes after a short while. Running it again from a terminal seem to show that it's a segmentation fault, though it can happen after quite a long time of normal usage (including legacy icons for hexchat, clementine, Mageia's net_applet and mgaapplet). I ran it through gdb and just got this crash: --- kde.xembedsniproxy: trying to dock window 75497483 kde.xembedsniproxy: adding damage watch for 75497483 Program received signal SIGSEGV, Segmentation fault. 0x0040e697 in SNIProxy::SNIProxy (this=0x709d30, wid=75497483, parent=) at /usr/src/debug/plasma-workspace-5.5.3/xembed-sni-proxy/sniproxy.cpp:165 165 if (clientGeom->width > s_embedSize || clientGeom->height > s_embedSize ) --- And the backtrace: --- (gdb) bt #0 0x0040e697 in SNIProxy::SNIProxy(unsigned int, QObject*) (this=0x709d30, wid=75497483, parent=) at /usr/src/debug/plasma-workspace-5.5.3/xembed-sni-proxy/sniproxy.cpp:165 #1 0x0040c3f3 in FdoSelectionManager::dock(unsigned int) (this=this@entry=0x7fffd970, winId=75497483) at /usr/src/debug/plasma-workspace-5.5.3/xembed-sni-proxy/fdoselectionmanager.cpp:157 #2 0x0040c55c in FdoSelectionManager::nativeEventFilter(QByteArray const&, void*, long*) (this=0x7fffd970, eventType=..., message=0x7fffe4004ee0, result=) at /usr/src/debug/plasma-workspace-5.5.3/xembed-sni-proxy/fdoselectionmanager.cpp:124 #3 0x76958237 in QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) (this=, eventType=..., message=message@entry=0x7fffe4004ee0, result=result@entry=0x7fffd478) at kernel/qabstracteventdispatcher.cpp:460 #4 0x7fffee33a0c5 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) (this=this@entry=0x641be0, event=event@entry=0x7fffe4004ee0) at qxcbconnection.cpp:1062 #5 0x7fffee33afb6 in QXcbConnection::processXcbEvents() (this=0x641be0) at qxcbconnection.cpp:1672 #6 0x7698706a in QObject::event(QEvent*) (this=0x641be0, e=) at kernel/qobject.cpp:1256 #7 0x7695b1ea in QCoreApplication::notify(QObject*, QEvent*) (event=, receiver=) at kernel/qcoreapplication.cpp:1088 #8 0x7695b1ea in QCoreApplication::notify(QObject*, QEvent*) (this=, receiver=, event=) at kernel/qcoreapplication.cpp:1074 #9 0x7695b348 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x641be0, event=event@entry=0x7fffe4006d40) at kernel/qcoreapplication.cpp:1013 #10 0x7695d16b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (event=0x7fffe4006d40, receiver=) at kernel/qcoreapplication.h:227 #11 0x7695d16b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x635710) at kernel/qcoreapplication.cpp:1648 #12 0x7695d638 in QCoreApplication::sendPostedEvents(QObject*, int) (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1506 #13 0x769ad1d3 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x6910c0) at kernel/qeventdispatcher_glib.cpp:270 #14 0x72e70267 in g_main_context_dispatch (context=0x7fffe40016f0) at gmain.c:3154 #15 0x72e70267 in g_main_context_dispatch (context=context@entry=0x7fffe40016f0) at gmain.c:3769 #16 0x72e70498 in g_main_context_iterate (context=context@entry=0x7fffe40016f0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3840 #17 0x72e7053c in g_main_context_iteration (context=0x7fffe40016f0, may_block=may_block@entry=1) at gmain.c:3901 #18 0x769ad5e6 in QEventDispatcherGlib::processEvents(QFlags) (this=0x68edf0, flags=...) at kernel/qeventdispatcher_glib.cpp:417 #19 0x7695903a in QEventLoop::exec(QFlags) (this=this@entry=0x7fffd8d0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #20 0x76961541 in QCoreApplication::exec() () at kernel/qcoreapplication.cpp:1283 #21
[yakuake] [Bug 336228] pressing f12 (or the equivalent closekey) causes respawn of yakuake if mouse is in yakuake
https://bugs.kde.org/show_bug.cgi?id=336228 Rémi Verschelde <rversche...@gmail.com> changed: What|Removed |Added CC||rversche...@gmail.com --- Comment #13 from Rémi Verschelde <rversche...@gmail.com> --- I can confirm the bug on Plasma 5.5.3 with yakuake built from the current "frameworks" branch (as of 2016-01-16). As Till Schäfer pointed out, it seems to be triggered by the "Keep window open when it loses focus" option. If activated, toggling yakuake will work fine regardless of the position of the mouse pointer. If deactivated, toggling yakuake works when the mouse pointer is not over the yakuake panel, but produces an immediate re-toggle of the panel if the mouse pointer was over the panel. Screencast that shows the issue (7 MB): http://remi.verschelde.fr/files/misc/yakuake-retoggle.mkv -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 342638] Yakauke doesn't retract properly when you press F12
https://bugs.kde.org/show_bug.cgi?id=342638 Rémi Verschelde <rversche...@gmail.com> changed: What|Removed |Added CC||rversche...@gmail.com --- Comment #7 from Rémi Verschelde <rversche...@gmail.com> --- I think this bug is a duplicate of bug 336228 (or reciprocally, the bug triagers can keep the one with the most useful debugging info/bug diagnostic). -- You are receiving this mail because: You are watching all bug changes.
