[kde] [Bug 394837] KDE menu (start button) refuses to show any menu
https://bugs.kde.org/show_bug.cgi?id=394837 John Andersen changed: What|Removed |Added URL||https://forum.manjaro.org/t ||/kde-menu-wont-pop-up/48138 ||/12 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 394837] New: KDE menu (start button) refuses to show any menu
https://bugs.kde.org/show_bug.cgi?id=394837 Bug ID: 394837 Summary: KDE menu (start button) refuses to show any menu Product: kde Version: unspecified Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: jsam...@gmail.com Target Milestone: --- The KDE "start button", (K Button) usually found at the Left of the Panel, can cease to function (will not pop up the menu) if you: 1) accidentally drag some arbitrary distance while clicking the menu button, or 2) switch desktops with the menu open. Occurs with the menu alternatives: Application Menu, Application Launcher How to reproduce: (easiest way) Select either App-menu or App-launcher menu alternative. Click K button (start button) menu appears Switch desktop via pager (while menu still showing) Click K button again, and menu will no longer show, but K button becomes underlined briefly How to restore Menu functionality: Any of these methods will restore Menu functionality to the K button 1) Right click the K-button and choose a different Menu Alternative. 2) killall plasmashell && plasmashell (in krunner or a shell) 3) Logout. Found using Manjaro Stable packages KDE Plasma Version 5.12.5 KDE Frameworks Version 5.46.0 QT Version 5.10.1 Kernel 4.14.44-1 (Manjaro) x86-64. Can not reproduce with OpenSuse Leap 15 KDE Plasma Version 5.12.5 KDE Frameworks Version 5.45.0 <--<<< ? QT Version 5.9.4 Kernel 4.12.14-4 (Opensus Leap 15) x86-64. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #249 from John Andersen <jsam...@gmail.com> --- (In reply to lorne schachter from comment #248) > You've taken that away > without a replacement. There is a replacement. See post 212 above https://bugs.kde.org/show_bug.cgi?id=341143#c212 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #245 from John Andersen <jsam...@gmail.com> --- Instead of posting yet more rambling rants and recipes for trying to make activities work for this (most of which are unnecessarily complex and eliminate other uses of activities) I encourage all to look into Post 212: It simply works: https://bugs.kde.org/show_bug.cgi?id=341143#c212 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.
https://bugs.kde.org/show_bug.cgi?id=341143 John Andersen <jsam...@gmail.com> changed: What|Removed |Added CC||jsam...@gmail.com --- Comment #213 from John Andersen <jsam...@gmail.com> --- (In reply to Jonathan Marten from comment #212) > Please don't comment on this bug report or bother the Plasma developers > about this - it is unofficial and nothing to do with the Plasma project. Sorry, but I just can't help posting a THANK YOU for this Jonathan. Very cool. I've been waiting for over 2 years. Thank You. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 368357] Excessive log spamming
https://bugs.kde.org/show_bug.cgi?id=368357 --- Comment #2 from John Andersen <jsam...@gmail.com> --- Most of us are pretty well stuck with what ever our distro is pushing out. Did you mean to suggest all users shoud start compiling this application from stratch? I think the log level is simply set too high. Warning in the logs will do nothing to help joe user. If its important, and the user can actually do something about it, put it the application's screen. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 368357] New: Excessive log spamming
https://bugs.kde.org/show_bug.cgi?id=368357 Bug ID: 368357 Summary: Excessive log spamming Product: kdeconnect Version: 1.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: jsam...@gmail.com Each time I light up my phone I see a couple of these messages in Journalctl -ef kdeconnectd[]: "htc" - warning, device uses a different protocol version 7 expected 5 They seem unnecessary, especially since there isn't a thing the user can do about the asynchronous releases in Google Play and the KDE repositories. And sending a file from phone to linux causes boaloads of these messages "Could not find service for job "Job 7" with app name "org.kde.kdeconnectd" " Reproducible: Always Steps to Reproduce: 1. Open a shell and type journalctl -ef (or use your favorite log follower) 2. light up your Android. 3. View spew Actual Results: Spew in logs. (By far not the worst offender - but still part of the problem). Got more than one device? Lots more spew! Expected Results: Log failures and important stuff only. If the software can handle multiple protocol versions on the fly, then a variation is not a problem, its a feature, and need not fill the logs. Htc One M8, android 6.0 but same behavior with different devices. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 362685] Sending a file via the "Send to using kdeconnect freezes plasma
https://bugs.kde.org/show_bug.cgi?id=362685 John Andersen <jsam...@gmail.com> changed: What|Removed |Added CC||jsam...@gmail.com --- Comment #1 from John Andersen <jsam...@gmail.com> --- Cannot Replicate. How bog was the video? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 340318] lot of QXcbConnection: XCB error: 3 (BadWindow)
https://bugs.kde.org/show_bug.cgi?id=340318 John Andersen <jsam...@gmail.com> changed: What|Removed |Added CC||jsam...@gmail.com --- Comment #5 from John Andersen <jsam...@gmail.com> --- Wow. Two years later and this stuff is still flooding everybody's logs. People have no pride in workmanship these days. I've fired guys for less. -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 338079] Kleopatra will not import 4096 byte keys from keyserver
https://bugs.kde.org/show_bug.cgi?id=338079 --- Comment #3 from John Andersen <jsam...@gmail.com> --- Confirming this still fails on Opensuse 13.2 Total number processed: 0 Imported: 0 On Kleopatra Version 2.2.0 (latest in repository) Kde Dev platform 4.14.9 KGpg 2.14.1 gpg (GnuPG) 2.0.26 All from Opensuse 13.2 Repositories Confirm it WORKS on Manjaro (arch) Linux 15.12 Total number processed: 1 Imported: 1 On Kleopatra Version 2.2.0 (latest in repository) Kde Framework 5.20.0 KGpg 2.17.0 gpg (GnuPG) 2.1.11 All from Manjaro 15.12 Repositories - Summary: Failure on KDE 4.14 (opensuse) Success on KDE Framework 5. (manjaro) Entirely possible bug is in some of the underlying gpg systems that Kleopatra requires. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 353922] baloofilerc file created in two different places
https://bugs.kde.org/show_bug.cgi?id=353922 John Andersen <jsam...@gmail.com> changed: What|Removed |Added CC||jsam...@gmail.com --- Comment #1 from John Andersen <jsam...@gmail.com> --- Are you sure these don't date from different installs, such as upgrading a kde 4 machine to Kde Plasma 5? Have you checked dates on the files ? I have only one baloofilerc on a fresh install of Manjaro (arch) linux. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kfilemetadata] [Bug 341162] Please make exif.image.imagedescription available for jpeg information panels
https://bugs.kde.org/show_bug.cgi?id=341162 John Andersen <jsam...@gmail.com> changed: What|Removed |Added CC||jsam...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 358098] Baloo fails to index plain text files unless extension is .txt
https://bugs.kde.org/show_bug.cgi?id=358098 --- Comment #4 from John Andersen <jsam...@gmail.com> --- (In reply to Pinak Ahuja from comment #3) > This is the intended behavior, for files having text/plain mimetype. This > was done to avoid the mess caused by applications which have log files in > directories that are indexed by baloo. > > Though text files with a valid extension like .md .markdown should still be > indexed because they have the mimetype: text/markdown but right now they are > also not being indexed because baloo is somehow misinterpreting the > mimetype. I'm looking into it. But this is fundamentally the wrong approach, as extensions have never been a significant part of linux, and are (by your own admission) unreliable indicator of file content. This isn't a case of Baloo "misinterpreting" anything. The link I posted indicates that mimetype of plaintext is arbitrarily rejected for indexing unless the extension is "txt" (and size less then 50K). When this was put in place (2 years ago) it was indicated as a temporary hack. Yet it still exists. There is no indication that this was the intended behavior, when the comments in the code clearly label it as some sort of short term hack. Someone chose to keep all plaintext out of baloo (a questionable decision at best,). Rather than doing this with blacklist/whitelist (exclude filters) to address problematic file types, all plaintext was summarily rejected unless extension was txt. If all plaintext is to be rejected then the rational thing to do is to honor a whitelist (include filters) to override this rejection. (I believe that USED TO EXIST, but was removed in the rush to simplify the control set). If, on the other hand only SOME plaintext files are problematic, those should be handled by the exclude filters. Right now, logs could be handled by exclude filters. There is no longer a whitelist capability. But even the exclude filters is totally ignored for plaintext documents. So significant functionality has been lost ostensibly just to avoid logs (which could have been avoided by the exclude filters). Look in app.cpp : https://code.woboq.org/qt5/kf5/baloo/src/file/extractor/app.cpp.html Look for the word HACK. -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 358098] Baloo fails to index plain text files unless extension is .txt
https://bugs.kde.org/show_bug.cgi?id=358098 --- Comment #2 from John Andersen <jsam...@gmail.com> --- Persists in Baloo 5.19.0 as well. There should be a method to white-list extensions one purposely wants to content-index, perhaps stored in baloofilerc. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 350731] [4.81 beta1] akregator in kontact: read messages are removed from unread filter immediately
https://bugs.kde.org/show_bug.cgi?id=350731 John Andersen <jsam...@gmail.com> changed: What|Removed |Added CC||jsam...@gmail.com --- Comment #17 from John Andersen <jsam...@gmail.com> --- Still appearing in Akregator Version 5.1.1 KDE Frameworks 5.18.0 Manjaro/Arch repositories Running embedded within Kontact. Since this happens every single time, it pretty much makes it impossible to read feeds showing only unread posts, as they all disappear from view. Certainly, even volunteer developers can track this down in 6 months. -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 332421] Baloo file extractor ate all my PC's RAM
https://bugs.kde.org/show_bug.cgi?id=332421 --- Comment #43 from John Andersen <jsam...@gmail.com> --- Replacing dead link in above reply: http://osdir.com/ml/kde-commits/2014-05/msg02993.html This is becoming a very debilitating limitation for me. -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 358098] Baloo fails to index plain text files unless extension is .txt
https://bugs.kde.org/show_bug.cgi?id=358098 --- Comment #1 from John Andersen <jsam...@gmail.com> --- Error persists in Baloo 5.18 as well. -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 358098] New: Baloo fails to index plain text files unless extension is .txt
https://bugs.kde.org/show_bug.cgi?id=358098 Bug ID: 358098 Summary: Baloo fails to index plain text files unless extension is .txt Product: Baloo Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: General Assignee: m...@vhanda.in Reporter: jsam...@gmail.com CC: pinak.ah...@gmail.com Using Baloo 5.17 (Arch/Manjaro repositories) as well as Baloo 4.14 (Opensuse Repositories) baloo file content indexing has suddenly lost the ability to index the content of plain/text files unless the extension is .txt. I believe I have traced this to a so called "temporary" patch to /src/file/extractor/app.cpp on 8/May/2014. I rely on baloo indexing a large volume of source code, which cannot have extensions of .txt but which are plain text, and suddenly this capability has been taken away for the flimsiest of reasons. Reproducible: Always Steps to Reproduce: 1. In a working baloo environment create a file called delete-me.txt 2. Write some words in the file including the word uniqueword 3. Save the file to disk in your local directory 4. Copy delete-me.txt to delete-me.too 5. at command line type baloosearch uniqueword Actual Results: Only the file delete-me.txt will be listed by baloosearch Expected Results: Both files should be listed by baloosearch File names continue to be indexed, but content is not. This renders the Dolphin Content search useless for any work with files that are plain text without a ".txt" extension. This was supposed to be a temporary patch (clearly labeled a HACK in the original commit) SEE: http://webcache.googleusercontent.com/search?q=cache:LUTPrh1zmZ8J:r.git.net/kde-commits/2014-05/msg02993.html+=4=en=clnk=us See also http://bugs.kde.org/show_bug.cgi?id=332421 Test Environments: 1) Manjaro-kde (archlinux) 15.12 KDE Framework 5.17.0 2) Opensuse 13.2 Kde Platform Version 4.14.9 1)-- [jsa@ManjaroVM ~]$ baloosearch -v Baloo 5.17.0 2)- jsa@poulsbo:~> baloosearch -v Qt: 4.8.6 KDE Development Platform: 4.14.9 Baloo Search: 0.1 -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 348902] search is broken - searching in the status bar forever and never finds anything
https://bugs.kde.org/show_bug.cgi?id=348902 --- Comment #18 from John Andersen <jsam...@gmail.com> --- (In reply to Hussam Al-Tayeb from comment #16) > (In reply to John Andersen from comment #15) > > How can we force the reopening of this bug? It is Not Fixed. It is not > > resolved. > > Search (find) in Dolphin does not work in any scenario. > > > > Click Find (or Ctrl F) > > Select Content button, (and either From Here or Everywhere button - makes no > > difference) > > Type in a word that you know exists in a file in your own directory > > No results. > > > What kde applications version? 15.12? balooctl reports version 5.17 Baloo refuses to index plaintext documents. -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 348902] search is broken - searching in the status bar forever and never finds anything
https://bugs.kde.org/show_bug.cgi?id=348902 --- Comment #20 from John Andersen <jsam...@gmail.com> --- (In reply to Hussam Al-Tayeb from comment #19) > (In reply to John Andersen from comment #18) > > balooctl reports version 5.17 > > > > Baloo refuses to index plaintext documents. > > Baloo is part of frameworks. > This is supposed to be fixed in applications 15.12 in dolphin and *not* > baloo. What version is your dolphin package? > The current release is15.12.1 Dolphin version 15.12.0 KDE Frameworks 5.17.0 Qt 5.5.1 (built against 5.5.1) It would be a nifty trick if fixing Dolphin could some how make up for the fact that Baloo refuses to index plain text files. --- So, basically, I don't believe you, or I don't believe you understand the problem. Baloo indexer will not index the CONTENT of plain text files. It will index the file names. I checked and changed mimetypes: exclude mimetypes=image/jpeg It still refuses to index content of plain text files. I test at the command line with baloosearch. This is not a Dolphin problem. -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 332421] Baloo file extractor ate all my PC's RAM
https://bugs.kde.org/show_bug.cgi?id=332421
John Andersen <jsam...@gmail.com> changed:
What|Removed |Added
CC||jsam...@gmail.com
--- Comment #42 from John Andersen <jsam...@gmail.com> ---
Apparently the hack installed back in August of 2014 to prevent indexing
anything but .txt file under 50 Meg is still resident in some packages of
extractor/app.cpp:
if (mimetype == QLatin1String("text/plain")) {
+ if (!url.endsWith(".txt")) {
+ mimetype.clear();
+ }
+
+ QFileInfo fileInfo(url);
+ if (fileInfo.size() >= 50 * 1024 * 1024 ) {
+ mimetype.clear();
+ }
See:
http://webcache.googleusercontent.com/search?q=cache:LUTPrh1zmZ8J:r.git.net/kde-commits/2014-05/msg02993.html+=4=en=clnk=us
I would like to index a whole boatload of source code, but because it does not
have a file extension of .txt the extractor fails, so then Baloo gets nothing
to index.
It works fine on KDE4, but on Plasma 5 version 15.12.0 (Manjaro / Arch) I
can't index any plain text files that do not end with an extension of .txt.
--
You are receiving this mail because:
You are watching all bug changes.
[Baloo] [Bug 348902] search is broken - searching in the status bar forever and never finds anything
https://bugs.kde.org/show_bug.cgi?id=348902 John Andersen <jsam...@gmail.com> changed: What|Removed |Added CC||jsam...@gmail.com --- Comment #15 from John Andersen <jsam...@gmail.com> --- How can we force the reopening of this bug? It is Not Fixed. It is not resolved. Search (find) in Dolphin does not work in any scenario. Click Find (or Ctrl F) Select Content button, (and either From Here or Everywhere button - makes no difference) Type in a word that you know exists in a file in your own directory No results. Manjaro (arch) Linux KDE Frameworks 5.17.0 Qt 5.5.1 (built against 5.5.1) The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 333715] Search is not working unless current path is indexed
https://bugs.kde.org/show_bug.cgi?id=333715 John Andersen <jsam...@gmail.com> changed: What|Removed |Added CC||jsam...@gmail.com --- Comment #7 from John Andersen <jsam...@gmail.com> --- Confirmed in Plasma 5.17. Content search now refuses to work ANYWHERE. Oh, wait, it works on KDE4. Its been a year and a half guys... -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 357993] New: Kmail initial account setup wizard flashes error message too quick to read
https://bugs.kde.org/show_bug.cgi?id=357993 Bug ID: 357993 Summary: Kmail initial account setup wizard flashes error message too quick to read Product: kmail2 Version: 5.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: config dialog Assignee: kdepim-b...@kde.org Reporter: jsam...@gmail.com The initial setup of the first email account uses a Account Wizard (AKA Account Assistant) which attempts to guess everything based on only an email address and password and type of account (imap/pop). However, any error in this process flashes the error message too fast to read, and returns to the input window with no error message and the account is not set up. User is forced to set up account manually. The error coud be in the entered data, or it could be in contacting the server. In my case I was trying to set up an yahoo email as an imap account. All input was correct, but wizard could not make it work and the error flashed so fast it could not be read. Note: English menues list this wizard under Tools / Account Wizard. However when it launches the window it is titled Account Assistant. Reproducible: Always Steps to Reproduce: 1. Invoke the Account wizard for account setup on a common mail provider 2. induce an error on the account assistant screen 3. Click next to select account type, etc 4. Error message flashes extremely briefly - too fast to read Actual Results: Regardless of the source of the error, the error message flashes too briefly to read. It was necessary to set up the account manually, which worked fine. Expected Results: Stop with error message showing so that user can take the propper corrective action Kmail 5.1 KDE Frameworks 5.17.0 Qt 5.5.1 (built against 5.5.1) The xcb windowing system Manjaro (archlinux) repositories VmWare Virtual machine -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 343246] plasma 5 doesn't allow different wallpapers and widgets for each virtual desktop
https://bugs.kde.org/show_bug.cgi?id=343246 John Andersen <jsam...@gmail.com> changed: What|Removed |Added CC||jsam...@gmail.com --- Comment #36 from John Andersen <jsam...@gmail.com> --- (In reply to Marco Martin from comment #1) > was a very problematic feature that cause a lot of bugs. > it was removed as an explicit choice (and due to architectural changes can't > really get back) > for this behavior, there are activities The problematic claim was made way back in KDE4, and they said it couldn't possibly be returned, and then, magically this capability returned. So you can port this code directly out of 4.14. As you've been advised, activities are no substitute, and historically it is Activities that are the cause of all the bug reports, not multiple wall papers. Please return multiple wall papers, because the community wants them. -- You are receiving this mail because: You are watching all bug changes.
