[frameworks-kio] [Bug 466115] Custom horizontal lines/bars in context menu no longer possible
https://bugs.kde.org/show_bug.cgi?id=466115 --- Comment #10 from Ignacio Serantes --- Thank you so much to Robert-André Mauchin for it's fix -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466115] [Regression] Custom horizontal lines/bars in context menu no longer possible
https://bugs.kde.org/show_bug.cgi?id=466115 --- Comment #8 from Ignacio Serantes --- (In reply to Robert-André Mauchin from comment #6) > Fix proposal: > > https://invent.kde.org/frameworks/kio/-/merge_requests/1608 > > > Commit 33785332 has purposely ordered actions by their name. However, this > break separators in service context menus. > > For example: > > Actions=progressive;optimize;SEPARATOR;compress_50;compress_70;compress_75 > > The separator would end up at the end of the list: > > Actions=compress_50;compress_70;compress_75;progressive|optimize;SEPARATOR > > And since the logic check is the separator is the last item to add it: > > !actions.last()->isSeparator() > > separators basically disappear from service context menus. > > The purpose of this commit is then to create groups of actions between each > separator. Actions will be sorted withing these groups, but it will keep > service menus original organisation. I don't understand the main reason for 33785332 commit, previous behavior, the sort is the one in Actions property, seems the right one behavior for me. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466115] [Regression] Custom horizontal lines/bars in context menu no longer possible
https://bugs.kde.org/show_bug.cgi?id=466115 --- Comment #3 from Ignacio Serantes --- In Dolphin 24.02.1 this behavior is worst because service menu is ordered using name instead of action name. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466115] [Regression] Custom horizontal lines/bars in context menu no longer possible
https://bugs.kde.org/show_bug.cgi?id=466115 Ignacio Serantes changed: What|Removed |Added CC||k...@aynoa.net -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 396275] Wishlist: support Subsonic music service
https://bugs.kde.org/show_bug.cgi?id=396275 Ignacio changed: What|Removed |Added CC||k...@i.itorres.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442301] system monitor sensor widget: "could not prompt the user for which application to start"
https://bugs.kde.org/show_bug.cgi?id=442301 Ignacio Felipe Medina changed: What|Removed |Added CC||djk...@gmail.com --- Comment #5 from Ignacio Felipe Medina --- I think that this is not really a bug. A change have been made and if you select to launch "system monitor" plasma-systemmonitor is launched. KSysGuard is not launched anymore. They are different applications. If you try to perform these actions without having "plasma-systemmonitor" installed you get "could not prompt the user for which application to start" message. But if you install "plasma-systemmonitor" on your computer... it will be lauched successfully every time it is requested from any widget. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 443096] New: Music is not detected when music folder is symlinked
https://bugs.kde.org/show_bug.cgi?id=443096 Bug ID: 443096 Summary: Music is not detected when music folder is symlinked Product: Elisa Version: 21.08.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: baloo Assignee: matthieu_gall...@yahoo.fr Reporter: k...@aynoa.net Target Milestone: --- SUMMARY Using fast native indexer when your music folder is symlinked no music at all is detected by Elisa. STEPS TO REPRODUCE 1. Symlink your music folder. 2. Start Elisa. OBSERVED RESULT No music at all. EXPECTED RESULT Music must be detected exactly like "scan the filesystem directly" do. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Maybe related to https://bugs.kde.org/show_bug.cgi?id=435383 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439815] Window randomly become transparent, when close ghost image remains
https://bugs.kde.org/show_bug.cgi?id=439815 Ignacio Serantes changed: What|Removed |Added CC||k...@aynoa.net -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 359932] Okular is very slow at opening some EPUB's
https://bugs.kde.org/show_bug.cgi?id=359932 Ignacio Taranto changed: What|Removed |Added CC|itaran...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 392793] Renamed files are not updated in the index
https://bugs.kde.org/show_bug.cgi?id=392793 --- Comment #16 from Ignacio Serantes --- Created attachment 137190 --> https://bugs.kde.org/attachment.cgi?id=137190=edit A fix for directories? This is my first attempt to fix the directories part. If I'm not sure about my file rename fix with this one is worst. Seems to work for me but sometimes I get some debug DB warnings so probably I'm missing something or doing something wrong. More test needed to confirm I am not breaking the DB. When I have time I will update my Tumbleweed packages with this patch for the brave. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 392793] Renamed files are not updated in the index
https://bugs.kde.org/show_bug.cgi?id=392793 --- Comment #15 from Ignacio Serantes --- (In reply to tagwerk19 from comment #14) > (In reply to Ignacio Serantes from comment #12) > > Maybe you have a problem with iNotify. > I will check that... > > Heads up though that you and Stefan are now chasing this/these bugs. Don't > know if independently or together. Happy to run tests and will try to make > sure I'm clear about what I'm testing :-/ > > My Comment 11 was for Neon Unstable and baloo 5.81.0 (Stefan) I'm independent. I look for a fix because this bug is really annoying and was not fixed for a long time. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 392793] Renamed files are not updated in the index
https://bugs.kde.org/show_bug.cgi?id=392793 --- Comment #13 from Ignacio Serantes --- (In reply to tagwerk19 from comment #11) > Re, fix in: > Baloo 5.81.0 > mentioned: > https://bugs.kde.org/show_bug.cgi?id=433116#c10 > > On Neon Unstable: > > I see the test as per Comment 10 working > No change with the test of renaming a parent folder, Comment 3 Confirmed. My patch only fixed filename renaming and not parent folders renaming. I will try to guess the reason. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 392793] Renamed files are not updated in the index
https://bugs.kde.org/show_bug.cgi?id=392793 --- Comment #12 from Ignacio Serantes --- (In reply to tagwerk19 from comment #10) > Created attachment 137080 [details] > Log of adding the test repo > > (In reply to Ignacio Serantes from comment #9) > > Packages are available at > > https://download.opensuse.org/repositories/home:/serantes:/branches:/ > > openSUSE:/Factory/openSUSE_Factory/ > Installed a new tumbleweed and added your repo. Log attached so you can see > if I've missed anything (no guarantee I've got it right :-) Rebooted after > the update. > > If I test baloo 'noticing' that a file's been moved, I'm not seeing it. > After a 'balooctl check', it works. > > echo "Hello Penguin" > file1.txt > > balooshow -x file1.txt > > d160036 54 3350 file1.txt [/home/test/Documents/file1.txt] > Mtime: 1616757267 2021-03-26T12:14:27 > Ctime: 1616757267 2021-03-26T12:14:27 > > Internal Info > Terms: Mplain Mtext T5 T8 > File Name Terms: Ffile1 Ftxt > XAttr Terms: > > baloosearch file1.txt > > /home/test/Documents/file1.txt > Elapsed: 0.280144 msecs > > mv file1.txt file2.txt > > balooshow -x file2.txt > > d160036 54 3350 file2.txt [/home/test/Documents/file1.txt] > Mtime: 1616757267 2021-03-26T12:14:27 > Ctime: 1616757267 2021-03-26T12:14:27 > > Internal Info > Terms: Mplain Mtext T5 T8 > File Name Terms: Ffile1 Ftxt > XAttr Terms: > > baloosearch file2.txt > > Elapsed: 0.242654 msecs > > balooctl check > > balooshow -x file2.txt > > d160036 54 3350 file2.txt [/home/test/Documents/file2.txt] > Mtime: 1616757267 2021-03-26T12:14:27 > Ctime: 1616757272 2021-03-26T12:14:32 > > Internal Info > Terms: Mplain Mtext T5 T8 > File Name Terms: Ffile2 Ftxt > XAttr Terms: > > baloosearch file2.txt > > /home/test/Documents/file2.txt > Elapsed: 0.286758 msecs Seems not exactly the problem I fixed because in your case seems like renaming notification it not yet processed. I'm guessing that because file name terms are not emptied a has old values. Maybe you have a problem with iNotify. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 392793] Renamed files are not updated in the index
https://bugs.kde.org/show_bug.cgi?id=392793 --- Comment #9 from Ignacio Serantes --- If someone is interested I created patched packages for openSUSE using 5.80.0 version. Packages are available at https://download.opensuse.org/repositories/home:/serantes:/branches:/openSUSE:/Factory/openSUSE_Factory/ I intend to maintain these packages until the problem if fixed. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 433116] Baloo looses filename after rename
https://bugs.kde.org/show_bug.cgi?id=433116 --- Comment #5 from Ignacio Serantes --- This is a duplicate bug. I wrote a fix in https://bugs.kde.org/show_bug.cgi?id=392793. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 392793] Renamed files are not updated in the index
https://bugs.kde.org/show_bug.cgi?id=392793 --- Comment #7 from Ignacio Serantes --- Comment on attachment 136755 --> https://bugs.kde.org/attachment.cgi?id=136755 A fix? diff --git a/src/file/metadatamover.cpp b/src/file/metadatamover.cpp index abb22dd1..ccd4e4e9 100644 --- a/src/file/metadatamover.cpp +++ b/src/file/metadatamover.cpp @@ -10,6 +10,7 @@ #include "database.h" #include "transaction.h" #include "baloodebug.h" +#include "termgenerator.h" #include @@ -102,6 +103,9 @@ void MetadataMover::updateMetadata(Transaction* tr, const QString& from, const Q doc.setId(id); doc.setParentId(parentId); doc.setUrl(toPath); +const QByteArray fileName = toPath.mid(lastSlash + 1); +TermGenerator tg(doc); +tg.indexFileNameText(fileName); tr->replaceDocument(doc, DocumentUrl | FileNameTerms); // Possible scenarios -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 392793] Renamed files are not updated in the index
https://bugs.kde.org/show_bug.cgi?id=392793 --- Comment #6 from Ignacio Serantes --- Created attachment 136755 --> https://bugs.kde.org/attachment.cgi?id=136755=edit A fix? This is a proper fix I guessed surfing in Baloo code. Don't know it is the right solution but works for me and maybe for others. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 392793] Renamed files are not updated in the index
https://bugs.kde.org/show_bug.cgi?id=392793
Ignacio Serantes changed:
What|Removed |Added
CC||k...@aynoa.net
--- Comment #4 from Ignacio Serantes ---
Hi,
Maybe I'm wrong but I'm was revising the code and seems the problem is git
commit bd1041ea "Make renames a DB only operation".
I apply add next few lines to MetadataMover::updateMetadata() method in
"metadatamover.cpp" file and renaming works again for me.
Document doc;
doc.setId(id);
doc.setParentId(parentId);
doc.setUrl(toPath);
+QFileInfo fileInfo(to);
+doc.addFileNameTerm("F" + fileInfo.baseName().toUtf8());
+doc.addFileNameTerm("F" + fileInfo.suffix().toUtf8());
tr->replaceDocument(doc, DocumentUrl | FileNameTerms);
Please consider this code a simple proof of concept and not a repair attempt
because I'm not a C++ developer.
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-baloo] [Bug 433116] Baloo looses filename after rename
https://bugs.kde.org/show_bug.cgi?id=433116 Ignacio Serantes changed: What|Removed |Added CC||k...@aynoa.net -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 421401] New: Similar photos banning
https://bugs.kde.org/show_bug.cgi?id=421401 Bug ID: 421401 Summary: Similar photos banning Product: digikam Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Searches-Similarity Assignee: digikam-bugs-n...@kde.org Reporter: k...@aynoa.net Target Milestone: --- Sometimes you want to maintain two similar pictures and, over time, you have a lot of hits you have to ignore when you search for duplicates. I'm actually using a tag "Duplicate" to ignore that pictures but that solution it's not working well because you are ignoring that pictures and not filtering results. I think that the ideal solution will be a banning method over the resultset, and a filter to hide banning results. You can activate/deactivate that filter so you can view and hide banned duplicates. You should be able to unban a previously banned result. OBSERVED RESULT There is no method to banning duplicates. EXPECTED RESULT A method to banning/unbanning duplicates and a filter to show/hide banned results. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 408315] Dolphins prepends "http://" when using "fish://" or "sftp://" in the location bar with a defined path
https://bugs.kde.org/show_bug.cgi?id=408315 --- Comment #3 from Ignacio Taranto --- Yes, it only happens when you supply a path. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 408315] Dolphins prepends "http://" when using "fish://" or "sftp://" in the location bar
https://bugs.kde.org/show_bug.cgi?id=408315 --- Comment #1 from Ignacio Taranto --- The observed result is http://fish/r...@xxx.xxx.xxx.xxx:~/ -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 408315] New: Dolphins prepends "http://" when using "fish://" or "sftp://" in the location bar
https://bugs.kde.org/show_bug.cgi?id=408315 Bug ID: 408315 Summary: Dolphins prepends "http://; when using "fish://" or "sftp://; in the location bar Product: dolphin Version: 18.12.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: itaran...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- SUMMARY Dolphins prepends "http://; when using "fish://" or "sftp://; in the location bar. STEPS TO REPRODUCE 1. Type fish://r...@xxx..xxx.xxx:~ in the location bar and press Enter OBSERVED RESULT Dolphin resolves to the location: http://fish/root@10.218.72.83:~/ and opens the previous address in a web browser. EXPECTED RESULT Dolphin does not modify the typed address and displays the working dir of the SSH session. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.12.8 KDE Frameworks Version: 5.55.0 Qt Version: 5.9.7 ADDITIONAL INFORMATION OS: openSUSE Leap 15.1 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 357321] Assigning "`" key (back quote) for Open/Retract does not work
https://bugs.kde.org/show_bug.cgi?id=357321 Ignacio Taranto changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Ignacio Taranto --- I will close this since it is fixed in the latest Plasma versions. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 406385] Filesystem expose only works at one level for copying (non-recursive)
https://bugs.kde.org/show_bug.cgi?id=406385 --- Comment #2 from Ignacio --- I performed the copy using Dolphin, both with the context menu and the shortcuts (Ctrl + c, Ctrl + v). I didn't tried using the terminal. About the "sub_dir": This directory was not empty. I first attempted to copy "sub_dir" (which contained several files) under the exposed dir (/storage/self/primary/Music). That resulted in only the sub_dir being copied but not its files. Any further attempt to put files/dirs under "sub_sir" was not possible. I can perform the same test using the terminal when I get home. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 406385] New: Filesystem expose only works at one level for copying (non-recursive)
https://bugs.kde.org/show_bug.cgi?id=406385 Bug ID: 406385 Summary: Filesystem expose only works at one level for copying (non-recursive) Product: kdeconnect Version: 1.3.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: itaran...@gmail.com Target Milestone: --- SUMMARY Filesystem expose only works at one level for copying (non-recursive). STEPS TO REPRODUCE 1. Pair a device 2. From the external device select option "Filesystem expose" and select a directory (for instance, /storage/self/primary/Music) 3. Try to copy files/directories at in the previous directory 4. Try to copy files/directories into a sub-directory OBSERVED RESULT Copying to the /storage/self/primary/Music works fine Copying to the /storage/self/primary/Music/ does not EXPECTED RESULT Copying to the /storage/self/primary/Music works fine Copying to the /storage/self/primary/Music/ works fine SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20190312 (available in About System) KDE Plasma Version: 5.15 2 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION Android application version: 1.12.6 Android version 6.0.1 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 406132] vex amd64->IR: CMPS without rep prefix is not handled
https://bugs.kde.org/show_bug.cgi?id=406132 Ignacio Losiggio changed: What|Removed |Added CC||iglosig...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 406132] vex amd64->IR: CMPS without rep prefix is not handled
https://bugs.kde.org/show_bug.cgi?id=406132 --- Comment #1 from Ignacio Losiggio --- Created attachment 119206 --> https://bugs.kde.org/attachment.cgi?id=119206=edit Example strcmp implementation using cmpsb without a rep prefix Added example code. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 406132] New: vex amd64->IR: CMPS without rep prefix is not handled
https://bugs.kde.org/show_bug.cgi?id=406132
Bug ID: 406132
Summary: vex amd64->IR: CMPS without rep prefix is not handled
Product: valgrind
Version: 3.14.0
Platform: unspecified
OS: All
Status: REPORTED
Severity: normal
Priority: NOR
Component: vex
Assignee: jsew...@acm.org
Reporter: iglosig...@gmail.com
Target Milestone: ---
Created attachment 119205
--> https://bugs.kde.org/attachment.cgi?id=119205=edit
Patch fixing the issue like it was fixed in movs
SUMMARY
The instruction CMPS{B,W,D,Q} can be used with or without prefix, the x86->IR
valgrind backend supports the instruction without prefix but the amd64 one does
not.
Attached to the issue is a patch fixing it.
STEPS TO REPRODUCE
1. Write any small program that uses cmps{b,w,d,q} on amd64.
OBSERVED RESULT
VEX will say that the instructions is not handled.
EXPECTED RESULT
Correct handling of the instruction like in the x86->IR backend
--
You are receiving this mail because:
You are watching all bug changes.
[Falkon] [Bug 394049] Windows version doesn't scale on high DPI
https://bugs.kde.org/show_bug.cgi?id=394049 Ignacio Serantes changed: What|Removed |Added CC||k...@aynoa.net -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 403693] New: screen inversion during selection of capture
https://bugs.kde.org/show_bug.cgi?id=403693 Bug ID: 403693 Summary: screen inversion during selection of capture Product: Spectacle Version: 18.12.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: ignaciocardona2...@yahoo.es Target Milestone: --- Created attachment 117701 --> https://bugs.kde.org/attachment.cgi?id=117701=edit screen recording of bug SUMMARY STEPS TO REPRODUCE 1. capture mode: rectangular region 2. click on "take a new screenshot" 3. OBSERVED RESULT both monitors screens flip horizontally and then you can select the area to capture The actual screen capture image is ok EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: KDE neon User Edition 5.14 (available in About System) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 x86_64 GNU/Linux -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 386542] New: Allow to set up default Format Type (scientific, decimal, etc.) and Precision in Configuration
https://bugs.kde.org/show_bug.cgi?id=386542 Bug ID: 386542 Summary: Allow to set up default Format Type (scientific, decimal, etc.) and Precision in Configuration Product: LabPlot2 Version: 2.4.0 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: frontend Assignee: alexander.se...@web.de Reporter: ignaciomo...@gmail.com Target Milestone: --- Dear Developers, It would be great to allow defining default Format Type and Precision in the Configuration dialog. Thanks in advance -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360478] Desktop widgets are permanently repositioned when fullscreen games lower display resolution
https://bugs.kde.org/show_bug.cgi?id=360478 Ignacio Serantes <k...@aynoa.net> changed: What|Removed |Added CC||k...@aynoa.net -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 359932] Okular is very slow at opening some EPUB's
https://bugs.kde.org/show_bug.cgi?id=359932 Ignacio <itaran...@gmail.com> changed: What|Removed |Added CC||itaran...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 377592] New: Kinfo Center crashes after selecting OpenGL menu twice
https://bugs.kde.org/show_bug.cgi?id=377592 Bug ID: 377592 Summary: Kinfo Center crashes after selecting OpenGL menu twice Product: kinfocenter Version: 5.8.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: hubn...@gmail.com Reporter: itaran...@gmail.com Target Milestone: --- Application: kinfocenter (5.8.2) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.49-1.ga6fa6e0-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: After launching KInfo Center, if I click the OpenGL menu twice the application crashes (segmentation fault). The crash can be reproduced every time. -- Backtrace: Application: Info Center (kinfocenter), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff40fcca780 (LWP 2899))] Thread 3 (Thread 0x7ff3f30f1700 (LWP 2901)): #0 0x7ff40c78351d in read () at /lib64/libc.so.6 #1 0x7ff4043e8073 in () at /usr/lib64/tls/libnvidia-tls.so.375.39 #2 0x7ff40855b670 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7ff40851ae49 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #4 0x7ff40851b2a8 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7ff40851b42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #6 0x7ff40d09432b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7ff40d041fdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #8 0x7ff40ce7cf1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #9 0x7ff40afcf1d5 in () at /usr/lib64/libQt5DBus.so.5 #10 0x7ff40ce819e9 in () at /usr/lib64/libQt5Core.so.5 #11 0x7ff408f4c734 in start_thread () at /lib64/libpthread.so.0 #12 0x7ff40c78fd3d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7ff3fc81c700 (LWP 2900)): #0 0x7ff40c78749d in poll () at /lib64/libc.so.6 #1 0x7ff4057fd3e2 in () at /usr/lib64/libxcb.so.1 #2 0x7ff4057fefcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7ff3ff3a8839 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7ff40ce819e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7ff408f4c734 in start_thread () at /lib64/libpthread.so.0 #6 0x7ff40c78fd3d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7ff40fcca780 (LWP 2899)): [KCrash Handler] #6 0x7ff3df47ac66 in () at /usr/lib64/libnvidia-eglcore.so.375.39 #7 0x7ff3df59b42e in () at /usr/lib64/libnvidia-eglcore.so.375.39 #8 0x7ff3df46c385 in () at /usr/lib64/libnvidia-eglcore.so.375.39 #9 0x7ff3df46c922 in () at /usr/lib64/libnvidia-eglcore.so.375.39 #10 0x7ff3df46fbda in () at /usr/lib64/libnvidia-eglcore.so.375.39 #11 0x7ff3df47d99d in () at /usr/lib64/libnvidia-eglcore.so.375.39 #12 0x7ff3df47dffe in () at /usr/lib64/libnvidia-eglcore.so.375.39 #13 0x7ff3df422ab6 in () at /usr/lib64/libnvidia-eglcore.so.375.39 #14 0x7ff3df3edafc in () at /usr/lib64/libnvidia-eglcore.so.375.39 #15 0x7ff3df404e43 in () at /usr/lib64/libnvidia-eglcore.so.375.39 #16 0x7ff3e590922c in () at /usr/X11R6/lib64/libGLESv1_CM_nvidia.so.1 #17 0x7ff3e6adceba in () at /usr/X11R6/lib64/libEGL_nvidia.so.0 #18 0x7ff3e6ae08ba in () at /usr/X11R6/lib64/libEGL_nvidia.so.0 #19 0x7ff3e70b76b1 in eglMakeCurrent () at /usr/X11R6/lib64/libEGL.so.1 #20 0x7ff3e7545004 in () at /usr/lib64/qt5/plugins/kcm_opengl.so #21 0x7ff3e75461d6 in () at /usr/lib64/qt5/plugins/kcm_opengl.so #22 0x7ff3e754722b in () at /usr/lib64/qt5/plugins/kcm_opengl.so #23 0x7ff40e7e168f in KPluginFactory::create(char const*, QWidget*, QObject*, QList const&, QString const&) () at /usr/lib64/libKF5CoreAddons.so.5 #24 0x7ff40f8d8859 in KCModuleLoader::loadModule(KCModuleInfo const&, KCModuleLoader::ErrorReporting, QWidget*, QStringList const&) () at /usr/lib64/libKF5KCMUtils.so.5 #25 0x7ff40f8e008c in () at /usr/lib64/libKF5KCMUtils.so.5 #26 0x7ff40f8e0c85 in KCModuleProxy::realModule() const () at /usr/lib64/libKF5KCMUtils.so.5 #27 0x7ff40f8e10b4 in KCModuleProxy::quickHelp() const () at /usr/lib64/libKF5KCMUtils.so.5 #28 0x00413cae in () #29 0x00410a1e in () #30 0x004173a0 in () #31 0x7ff40d06dbb1 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #32 0x0041719f in () #33 0x004172a9 in () #34 0x7ff40d06dbb1 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #35 0x7ff40df93c55 in QAbstractItemView::clicked(QModelIndex const&) () at /usr/lib64/libQt5Widgets.so.5 #36 0x7ff40df9c843 in QAbstractItemView::mouseReleaseEvent(QMouseEvent*) () at /usr/lib64/libQt5Widgets.so.5 #37 0x7ff40dfdd33b in
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 Ignacio R. Morelle <shadowm2...@gmail.com> changed: What|Removed |Added CC||shadowm2...@gmail.com --- Comment #112 from Ignacio R. Morelle <shadowm2...@gmail.com> --- For the record, I had the same issue with tray icons and CPU usage with Plasma 5.8.4 from Debian sid before applying the patch from <https://phabricator.kde.org/D2986> locally. I've been running a patched build for the last four days and I've not experienced any unintended side-effects. I imagine downstream will be more likely to adopt the patch once it becomes part of Plasma 5.8.6. (It doesn't seem like it made it to 5.8.5, sadly.) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372957] Scrolling in system tray switches desktop
https://bugs.kde.org/show_bug.cgi?id=372957 Ignacio R. Morelle <shadowm2...@gmail.com> changed: What|Removed |Added CC||shadowm2...@gmail.com --- Comment #4 from Ignacio R. Morelle <shadowm2...@gmail.com> --- So after reading Marco's comment above I decided to have a look at Plasma's configuration files, .config/plasma-org.kde.plasma.desktop-appletsrc in particular, and I found this bit: [ActionPlugins][129] MidButton;NoModifier=org.kde.paste RightButton;NoModifier=org.kde.contextmenu wheel:Vertical;NoModifier=org.kde.switchdesktop I stopped plasmashell, removed the `wheel:Vertical;NoModifier=org.kde.switchdesktop` line and started plasmashell again, and the wheel no longer has an effect on the system tray icons or arrow or the dead space between icons. Not sure how this configuration ended up here in the first place. I thought it could be related to the Mouse Actions tab in the desktop configuration, but adding an action to switch desktops on wheel presses didn't seem to affect the system tray at all. Note that before editing the config file I had tried removing and readding the system tray widget, and adding a new panel using the Default Panel preset; neither made a difference. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372812] Changing the volume with the wheel switches open windows
https://bugs.kde.org/show_bug.cgi?id=372812 Ignacio R. Morelle <shadowm2...@gmail.com> changed: What|Removed |Added CC||shadowm2...@gmail.com --- Comment #2 from Ignacio R. Morelle <shadowm2...@gmail.com> --- I'm using Plasma 5.8.4 on Debian sid as it landed there yesterday and I also getdthis issue when using the scroll wheel on the KMix icon, which makes it actually quite unusable. I also notice that accidentally using the scroll wheel on certain native Plasma 5 widgets that do not handle it (the Networks and Clipboard icons) triggers the same behavior. Plasma's own PulseAudio-based audio volume icon (which I don't normally use) seems unaffected -- perhaps it's because it handles its own wheel events? In previous 5.8.x versions, using the wheel on the Show Hidden Icons arrow or the tiny empty space between tray icons also triggered a desktop switch, which I personally found a bit annoying and counterintuitive as there's a separate Pager widget for this kind of thing. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364904] New: Plasma crashed while switching windows with Alt+Tab
https://bugs.kde.org/show_bug.cgi?id=364904 Bug ID: 364904 Summary: Plasma crashed while switching windows with Alt+Tab Product: plasmashell Version: 5.6.4 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: zoreths...@yahoo.com.ar CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.6.4) (Compiled from sources) Qt Version: 5.6.0 Frameworks Version: 5.22.0 Operating System: Linux 4.5.7-200.fc23.x86_64 x86_64 Distribution: "Fedora release 23 (Twenty Three)" -- Information about the crash: - What I was doing when the application crashed: I was changing from an open Firefox window to a Sametime chat I had open with Alt+Tab -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcd0d6a4940 (LWP 3006))] Thread 7 (Thread 0x7fcd029b9700 (LWP 3010)): #0 0x7fcd1cf84e44 in QMutex::lock() () from /lib64/libQt5Core.so.5 #1 0x7fcd1d1b50cf in postEventSourcePrepare(_GSource*, int*) () from /lib64/libQt5Core.so.5 #2 0x7fcd17a3172d in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #3 0x7fcd17a320bb in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #4 0x7fcd17a3229c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7fcd1d1b5a4b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7fcd1d15e4ca in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #7 0x7fcd1cf87f34 in QThread::exec() () from /lib64/libQt5Core.so.5 #8 0x7fcd1d94d4b5 in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #9 0x7fcd1cf8cd48 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #10 0x7fcd1b6b761a in start_thread () from /lib64/libpthread.so.0 #11 0x7fcd1c38659d in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7fcd01179700 (LWP 3088)): #0 0x7fffac1df969 in ?? () #1 0x7fffac1dfc65 in clock_gettime () #2 0x7fcd1c394816 in clock_gettime () from /lib64/libc.so.6 #3 0x7fcd1d038d86 in qt_gettime() () from /lib64/libQt5Core.so.5 #4 0x7fcd1d1b35d9 in QTimerInfoList::updateCurrentTime() () from /lib64/libQt5Core.so.5 #5 0x7fcd1d1b3b45 in QTimerInfoList::timerWait(timespec&) () from /lib64/libQt5Core.so.5 #6 0x7fcd1d1b4f2e in timerSourcePrepare(_GSource*, int*) () from /lib64/libQt5Core.so.5 #7 0x7fcd17a3172d in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #8 0x7fcd17a320bb in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #9 0x7fcd17a3229c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #10 0x7fcd1d1b5a4b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #11 0x7fcd1d15e4ca in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #12 0x7fcd1cf87f34 in QThread::exec() () from /lib64/libQt5Core.so.5 #13 0x7fcd203970d5 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #14 0x7fcd1cf8cd48 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #15 0x7fcd1b6b761a in start_thread () from /lib64/libpthread.so.0 #16 0x7fcd1c38659d in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7fccf1074700 (LWP 3111)): #0 0x7fcd1c37ab1d in poll () from /lib64/libc.so.6 #1 0x7fcd17a3218c in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7fcd17a3229c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7fcd1d1b5a4b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7fcd1d15e4ca in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7fcd1cf87f34 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7fcd203970d5 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #7 0x7fcd1cf8cd48 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7fcd1b6b761a in start_thread () from /lib64/libpthread.so.0 #9 0x7fcd1c38659d in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7fcceb612700 (LWP 3135)): #0 0x7fcd17a31771 in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #1 0x7fcd17a320bb in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7fcd17a3229c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7fcd1d1b5a4b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7fcd1d15e4ca in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7fcd1cf87f34 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7fcd203970d5 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #7 0x7fcd1cf8cd48 in QThreadPrivate::start(void*) () from
[choqok] [Bug 364447] New: Random segfault at exit
https://bugs.kde.org/show_bug.cgi?id=364447 Bug ID: 364447 Summary: Random segfault at exit Product: choqok Version: Git Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mehrdad.mom...@gmail.com Reporter: shadowm2...@gmail.com CC: scarp...@kde.org The Git master version as of 136e9f27f25d85d2573d9f0eede6963818cdba20 sometimes segfaults at exit. This happens silently (the KDE crash handler doesn't appear) other than a line like the following being written to the system log: [196447.905520] choqok[8551]: segfault at 7fef761fb340 ip 004106cb sp 7ffd87cb0ac0 error 4 in choqok[40+23000] I have not been able to obtain a backtrace from gdb thus far because the bug seems to elude observation when under a debugger, but I was able to get this from Valgrind (using master @ 6b646e86a466bdb92966092826c18a50f4aefe34 for line numbers), which might be related. These are the only invalid memory accesses reported by Valgrind otherwise: ==27682== Invalid read of size 4 ==27682==at 0xA3BAFD0: QCoreApplicationPrivate::deref() (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.6.1) ==27682==by 0xA3B5CA3: QEventLoopLocker::~QEventLoopLocker() (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.6.1) ==27682==by 0x5082703: Choqok::PluginManager::~PluginManager() (pluginmanager.cpp:100) ==27682==by 0x5085E9C: Choqok::PluginManagerPrivate::~PluginManagerPrivate() (pluginmanager.cpp:49) ==27682==by 0x50825AB: Choqok::(anonymous namespace)::Q_QGS__kpmp::innerFunction()::Holder::~Holder() (pluginmanager.cpp:87) ==27682==by 0xAED1DE7: __run_exit_handlers (in /lib/x86_64-linux-gnu/libc-2.22.so) ==27682==by 0xAED1E34: exit (in /lib/x86_64-linux-gnu/libc-2.22.so) ==27682==by 0xAEBC5F6: (below main) (in /lib/x86_64-linux-gnu/libc-2.22.so) ==27682== Address 0x16d32c00 is 112 bytes inside a block of size 352 free'd ==27682==at 0x4C2B2CB: operator delete(void*) (vg_replace_malloc.c:575) ==27682==by 0xA3EBF2B: QObject::~QObject() (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.6.1) ==27682==by 0xA3B9B61: QCoreApplication::~QCoreApplication() (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.6.1) ==27682==by 0x939A523: QApplication::~QApplication() (in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.6.1) ==27682==by 0x507E891: Choqok::Application::~Application() (application.cpp:42) ==27682==by 0x40BD10: ChoqokApplication::~ChoqokApplication() (choqokapplication.cpp:50) ==27682==by 0x418AA4: main (main.cpp:77) ==27682== Block was alloc'd at ==27682==at 0x4C2A16F: operator new(unsigned long) (vg_replace_malloc.c:333) ==27682==by 0x939F83D: QApplication::QApplication(int&, char**, int) (in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.6.1) ==27682==by 0x507E82C: Choqok::Application::Application(int&, char**) (application.cpp:38) ==27682==by 0x40BAF8: ChoqokApplication::ChoqokApplication(int&, char**) (choqokapplication.cpp:33) ==27682==by 0x418907: main (main.cpp:77) ==27682== ==27682== Invalid read of size 4 ==27682==at 0xA3BAF30: QCoreApplicationPrivate::maybeQuit() (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.6.1) ==27682==by 0xA3B5CA3: QEventLoopLocker::~QEventLoopLocker() (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.6.1) ==27682==by 0x5082703: Choqok::PluginManager::~PluginManager() (pluginmanager.cpp:100) ==27682==by 0x5085E9C: Choqok::PluginManagerPrivate::~PluginManagerPrivate() (pluginmanager.cpp:49) ==27682==by 0x50825AB: Choqok::(anonymous namespace)::Q_QGS__kpmp::innerFunction()::Holder::~Holder() (pluginmanager.cpp:87) ==27682==by 0xAED1DE7: __run_exit_handlers (in /lib/x86_64-linux-gnu/libc-2.22.so) ==27682==by 0xAED1E34: exit (in /lib/x86_64-linux-gnu/libc-2.22.so) ==27682==by 0xAEBC5F6: (below main) (in /lib/x86_64-linux-gnu/libc-2.22.so) ==27682== Address 0x16d32c00 is 112 bytes inside a block of size 352 free'd ==27682==at 0x4C2B2CB: operator delete(void*) (vg_replace_malloc.c:575) ==27682==by 0xA3EBF2B: QObject::~QObject() (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.6.1) ==27682==by 0xA3B9B61: QCoreApplication::~QCoreApplication() (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.6.1) ==27682==by 0x939A523: QApplication::~QApplication() (in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.6.1) ==27682==by 0x507E891: Choqok::Application::~Application() (application.cpp:42) ==27682==by 0x40BD10: ChoqokApplication::~ChoqokApplication() (choqokapplication.cpp:50) ==27682==by 0x418AA4: main (main.cpp:77) ==27682== Block was alloc'd at ==27682==at 0x4C2A16F: operator new(unsigned long) (vg_replace_malloc.c:333) ==27682==by 0x939F83D: QApplication::QApplication(int&, char**, int) (in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.6.1) ==27682==by 0x507E82C:
[choqok] [Bug 364408] Version info dialog comes up mostly empty
https://bugs.kde.org/show_bug.cgi?id=364408 --- Comment #3 from Ignacio R. Morelle <shadowm2...@gmail.com> --- (In reply to Andrea Scarpino from comment #2) > Thank you! > > If it's possible please send the patch on https://git.reviewboard.kde.org/r/ > otherwise I'll apply this in the evening. Done: https://git.reviewboard.kde.org/r/128220/ -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 364408] Version info dialog comes up mostly empty
https://bugs.kde.org/show_bug.cgi?id=364408 --- Comment #1 from Ignacio R. Morelle <shadowm2...@gmail.com> --- Created attachment 99543 --> https://bugs.kde.org/attachment.cgi?id=99543=edit Patch that fixes the issue. -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 364408] New: Version info dialog comes up mostly empty
https://bugs.kde.org/show_bug.cgi?id=364408
Bug ID: 364408
Summary: Version info dialog comes up mostly empty
Product: choqok
Version: Git
Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: mehrdad.mom...@gmail.com
Reporter: shadowm2...@gmail.com
CC: scarp...@kde.org
On the current Git master version (at commit
136e9f27f25d85d2573d9f0eede6963818cdba20), the Help -> About Choqok dialog
comes up mostly empty except for the library versions on the Version tab.
I'm attaching a patch that fixes the issue for me.
Reproducible: Always
Steps to Reproduce:
1. Navigate to the Help menu
2. Choose About Choqok
Actual Results:
All tabs are missing information, except as mentioned above
Expected Results:
Display the software description ("KDE Micro-Blogging Client"), copyright and
license info, list of authors, etc.
Using KDE Frameworks version 5.22.0 and Qt 5.6.1 on Debian unstable.
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 350849] Konsole hides tab bar when moving tabs
https://bugs.kde.org/show_bug.cgi?id=350849 Ignacio R. Morelle <shadowm2...@gmail.com> changed: What|Removed |Added CC||shadowm2...@gmail.com --- Comment #1 from Ignacio R. Morelle <shadowm2...@gmail.com> --- Posted a patch that fixes this issue for me: https://git.reviewboard.kde.org/r/128151/ -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 357321] New: Assigning "`" key (back quote) for Open/Retract does not work
https://bugs.kde.org/show_bug.cgi?id=357321 Bug ID: 357321 Summary: Assigning "`" key (back quote) for Open/Retract does not work Product: yakuake Version: Git (Frameworks 5) Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: itaran...@gmail.com Assigning "`" key (back quote) for Open/Retract in the Global Keyboard Shortcuts from Desktop Settings does not work. Pressing "`" only triggers Retract but not Open. $ kf5-config --version Qt: 5.5.1 KDE Frameworks: 5.16.0 kf5-config: 1.0 $ yakuake --version Qt: 4.8.6 KDE Development Platform: 4.14.10 Yakuake: 2.9.9 Reproducible: Always Steps to Reproduce: 1. Go to KDE Settings -> Global Keyboard Shortcuts -> Yakuake 2. Assign "`" for Open/Retract Actual Results: Pressing "`" only triggers Retract but not Open. Expected Results: Pressing "`" triggers Retract as well as Open. -- You are receiving this mail because: You are watching all bug changes.
