[ktimetracker] [Bug 343563] Editing a task makes KTimeTracker crash
https://bugs.kde.org/show_bug.cgi?id=343563 --- Comment #3 from Juanma --- I have installed the app and I left it counting time, but I did not yet look at the specific details of the bug report. I will try to reproduce it more precisely. However, I can say that it has already crashed on me, when I went back and got the dialog about being inactive and whether I want to withdraw the amount of time counted during inactivity. I say yes and it crashed. But that is for another bug report, I guess. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 459954] New: digikam shows non existing new faces
https://bugs.kde.org/show_bug.cgi?id=459954 Bug ID: 459954 Summary: digikam shows non existing new faces Classification: Applications Product: digikam Version: 7.5.0 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Faces-Recognition Assignee: digikam-bugs-n...@kde.org Reporter: jux...@gmail.com Target Milestone: --- Created attachment 152577 --> https://bugs.kde.org/attachment.cgi?id=152577&action=edit Image of the false new faces found After a heave use of facial recognition digikam shows a few persons with new faces pending that does not exists (or at least are not shown when pressed the person in particular) *** STEPS TO REPRODUCE 1. Do facial recognition with plenty of photos 2. Confirm correct recognized faces and manually tag the rest OBSERVED RESULT Some faces show pending recognized faces that digikam don't show if you press the person icon EXPECTED RESULT No pending faces al all SOFTWARE/OS VERSIONS Linux: Ubuntu 22.04.1 LTS KDE Plasma Version: ??? KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #443 from Juanma --- On June 10, 2021 17:42:30 Lehmeier wrote: > https://bugs.kde.org/show_bug.cgi?id=341143 > > --- Comment #441 from Lehmeier --- > (In reply to michel from comment #440) > > ... > > It was also written Who is responsible for what, when and how is discussed. > Then one could initiate such a discussion. > It is strange, however, that this should only happen after about 7 years and > that it was not discussed earlier. > > -- > You are receiving this mail because: > You are on the CC list for the bug. I would indeed like to know who makes steering decisions at KDE, and how they do it. Are users asked about anything, anytime? It's slightly unfair to charge against the volunteering developers, who would a priori deserve appreciation, but OTOH it is unacceptable to hijack such a flagship project as KDE from it's users in this way. That's why it's important to know how is the project driven. Activities could have been a nice and OPTIONAL addition to Plasma, but should have never been imposed this way because they suck in a very clear and unavoidable way: they only make sense with Activities-aware programs. My browser of choice is not part of KDE, not is my editor. They won't abide by whatever rules Activities will want to impose on them. VDs worked with anything that was inside s window. They worked even with Emacs. They also worked with KNotes, which "lived" in non-standard windows (but, OK, they were a KDE program). By the way, what happened to KNotes? So, Activities is a client lock-up kind of move much like those we (should) hate in Microsoft or Apple. In fact, I suspect that the people behind this move might have grown up "inspired" by Jobs. KDE 5 lacks not only the usability I enjoyed there, but also lacks AmaroK and KNotes. At this point, it's all the same to me to stay out switch. Either way, the good times will be in the past. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 428659] New: Crash when opening any Dolphin window
https://bugs.kde.org/show_bug.cgi?id=428659 Bug ID: 428659 Summary: Crash when opening any Dolphin window Product: dolphin Version: 20.08.2 Platform: Debian testing OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: juanma_bel...@yahoo.es CC: kfm-de...@kde.org Target Milestone: --- Crash when opening any Dolphin window. STEPS TO REPRODUCE 1. Request opening any Dolphin window, by any available means (shortcut, through the application launcher, opening folder from any application...) OBSERVED RESULT No Dolphin window appears. Instead, the KDE Crash Handler pops up. EXPECTED RESULT A Dolphin window. SOFTWARE/OS VERSIONS Application: kdeinit5 (20.08.2) Qt Version: 5.14.2 Frameworks Version: 5.74.0 Operating System: Linux 5.9.0-1-amd64 x86_64 Distribution: Debian GNU/Linux bullseye/sid ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 428659] Crash when opening any Dolphin window
https://bugs.kde.org/show_bug.cgi?id=428659 --- Comment #2 from Juanma --- I will try to install the required packs to get the backtrace. Probably not until the weekend, though. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 428659] Crash when opening any Dolphin window
https://bugs.kde.org/show_bug.cgi?id=428659 --- Comment #3 from Juanma --- Hello, Nate. Last weekend a regular update of packages left my KDE installation all broken: I couldn't even log in. So I reinstalled Debian 9 from an old DVD. I want to go back to Plasma 4 anyway. But what I got instead is Plasma 5 with Dolphin still crashing from a fresh installation of an older version (16.08.3). This sounds as though the problem is in my machine, but my machine hasn't changed from the latest times Dolphin worked to the current situation. Plus, Dolphin is the only one that seems to be presenting this sort of behavior. Anyway, I wanted to generate a good backtrace, so I look at the list of missing files that the crash handler says I'm missing: /usr/bin/dolphin /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 /usr/lib/x86_64-linux-gnu/libkdeinit5_dolphin.so Wrong start: I have them all. Anyway, the I think I'm getting enough information from the stack trace and from running it with GDB: Thread 1 (Thread 0x7f8c111d8e00 (LWP 4464)): [KCrash Handler] #6 0x7f8c24b44fff in raise () from /lib/x86_64-linux-gnu/libc.so.6 #7 0x7f8c24b4642a in abort () from /lib/x86_64-linux-gnu/libc.so.6 #8 0x7f8c2246249b in KXMLGUIClient::setXML(QString const&, bool) () from /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #9 0x7f8c22462d19 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #10 0x7f8c2247ef27 in KXmlGuiWindow::createGUI(QString const&) () from /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #11 0x7f8c224801cb in KXmlGuiWindow::setupGUI(QSize const&, QFlags, QString const&) () from /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #12 0x7f8c224802e2 in KXmlGuiWindow::setupGUI(QFlags, QString const&) () from /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #13 0x7f8c24efc64d in DolphinMainWindow::DolphinMainWindow (this=0x5632141c0880, __in_chrg=, __vtt_parm=) at ./src/dolphinmainwindow.cpp:146 #14 0x7f8c24f1130f in kdemain (argc=, argv=) at ./src/main.cpp:130 #15 0x7f8c24b322e1 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #16 0x56321264b7ba in _start () Debugging, I get this message the third time I enter KXMLGUIClient::setXML : «Error parsing XML document: "unexpected character" at line 153 column 1». Unfortunately I haven't found out which XML file is it reading, which contains that "unexpected character". -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 400271] Need way to allow applications to handle invalid XML without crashing.
https://bugs.kde.org/show_bug.cgi?id=400271 --- Comment #7 from Juanma --- Created attachment 133267 --> https://bugs.kde.org/attachment.cgi?id=133267&action=edit Invalid XML in dolphinui.rc I see 2 problems here: 1. Something has broken this file. I don't know if it was a Debian APT script during an update, or Dolphin itself, or what. 2. Most definitely, no program should crash when reading wrong XML. I guess the latter point is what this bug is about. I would like to help, but I have never installed sources of any KDE app for such purpose. Could you give me some hints or point me to some tutorial so that I could debug it myself? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 475760] New: kde connect not working on android 4.4.4
https://bugs.kde.org/show_bug.cgi?id=475760 Bug ID: 475760 Summary: kde connect not working on android 4.4.4 Classification: Applications Product: kdeconnect Version: unspecified Platform: Android OS: Android 4.x Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: juanchelo...@gmail.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- In version 1.21.1 of kde connect, which was the last update that supported andoroid 4.4.4, it stopped working, it no longer detects linked devices or allows new devices to be linked. My device is a Samsung Tab E 9.6, the device is rooted, the problem started a while ago, previously it worked normally. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #468 from Juanma --- En domingo, 16 de enero de 2022 15:42:37 CET, Dominik Kummer escribió: > PS: to the conservative user base: did you ever try Activities? Or are you > waiting until M$ and @ppl are copying the feature again? @Dominik: I am one of those users who long for KDE4, and I don't think it is a matter of being conservative. I posted reasons for why I reject Activities on the 14th of June last year (as I saw now, in an HTML-formatted email, for which I apologize). Activities work badly in a very clear and unavoidable way: they only make sense with Activities-aware programs. My browser of choice is not part of KDE (is there a Plasma web browser currently?), nor is my editor. They won't abide by whatever rules Activities will want to impose on them. On the other hand, VDs worked with anything that was inside a window. They worked even with Emacs. They also worked with KNotes, which, though that was (also dead now?) part of KDE, had its notes placed in non-standard windows. And what is the gain with Activities? Filtering email boxes that belong to the current activity? Mmmmkey, not for me, but maybe for some people... Filtering files and folders? Nice, but I did that with configured widgets per Virtual Desktop together with tags. Tags: that is a feature worth focusing on, rather than Activities. I have been waiting so long for a simple and nice way to tag files and folders... Instead, I got Nepomuk, the semantic desktop concept (hated it, with files indexer killing my CPU for no added value). That thing is gone, is it not? So, Activities is a client lock-up kind of move much like those we (should) hate in, precisely, Microsoft or Apple. I guess you are thinking that I am sooo conservative (I stick with Emacs, right?). Well, I try to use the best things I find. I don't use Emacs to program, but it is still the best thing for me for a bunch of uses. I rejected the "semantic desktop" because I don't need a googlesque searcher in my own PC, as if it was the outer cyber-space, because the contents of my disk are my own, up to me to keep then and organized by me, so I never thought it was a great idea. But there is also the point of having your work-flows, specially if there was a learning (and/or configuring) curve to climb, and it hurts having to re-learn with each new release. I know that people do that all the time with M$ Office, but most of them never get to learn sh!t of how to use it well anyway. -- Juan -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #344 from Juanma --- > Eliminating a feature that many people relied on for good reason and that at > one time was fully supported is a very hazardous thing to do, And this begs for a question that maybe it's clear to all other commenters, but not to me: how are such decisions taken in KDE? Who makes such decisions, and how? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #345 from Juanma --- > Eliminating a feature that many people relied on for good reason and that at > one time was fully supported is a very hazardous thing to do, And this begs for a question that maybe it's clear to all other commenters, but not to me: how are such decisions taken in KDE? Who makes such decisions, and how? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387582] Window List lacks keyboard usability
https://bugs.kde.org/show_bug.cgi?id=387582 --- Comment #3 from Juanma --- (In reply to andydecleyre from comment #2) > I've got plasma-desktop 5.15.2 here, and the actions you list as 1, 2, and 4 > seem to work perfectly. To make it clear: can you execute the following steps without any TAB-skipping in between? - open the Window List widget by pressing its associated keyboard shortcut - select a window in the list using only the keyboard (presumably with arrow keys) - switch to that window (presumably with Enter key) or close the List with the Esc key Again, just to make sure we speak the same lingo: with "TAB-skipping" I mean pressing the Tab key on the keyboard, one or more times, to shift the focus over different elements in the screen. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420253] New: Crash when returning from Display settings
https://bugs.kde.org/show_bug.cgi?id=420253 Bug ID: 420253 Summary: Crash when returning from Display settings Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kwin_virtualdesktops Assignee: kwin-bugs-n...@kde.org Reporter: juanma_bel...@yahoo.es CC: plasma-b...@kde.org Target Milestone: --- Created attachment 127644 --> https://bugs.kde.org/attachment.cgi?id=127644&action=edit File generated by the KDE Crash Reporting Assistant. Crash when returning from Display settings STEPS TO REPRODUCE 1. Open System Settings. 2. Go to "Display and Monitor". 3. Clink on "All Settings" to return to the main screen. OBSERVED RESULT System Settings crashes. EXPECTED RESULT You know. SOFTWARE/OS VERSIONS Application: systemsettings5 (5.17.5) Qt Version: 5.12.5 Frameworks Version: 5.62.0 Operating System: Linux 5.5.0-1-amd64 x86_64 Distribution: Debian GNU/Linux bullseye/sid ADDITIONAL INFORMATION In attachment. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 390080] New: Swapped email: 2 entries in message list point to wrong (swapped) content
https://bugs.kde.org/show_bug.cgi?id=390080 Bug ID: 390080 Summary: Swapped email: 2 entries in message list point to wrong (swapped) content Product: kmail2 Version: 5.6.3 Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: message list Assignee: kdepim-b...@kde.org Reporter: juanma_bel...@yahoo.es Target Milestone: --- Created attachment 110432 --> https://bugs.kde.org/attachment.cgi?id=110432&action=edit Swapped messages When I first noticed the problem, the situation was as shown in the 2 screenshot pieces on the left side of the attached image, that is: selecting one entry in the message list (let's call it message A) showed the content of another email (message B); then, clicking on the message list entry seemingly representing message B actually showed message A. Then I restarted KMail and now it's similar but different, as showed in the 2 screenshot pieces on the right side of the attached image, that is: pairs of emails are threaded in wrong, swapped positions, but this time the content shown in the message pane belongs to the entry selected in the message list. This happens with several pairs of emails. -- 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 Juanma changed: What|Removed |Added CC||juanma_bel...@yahoo.es -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387582] New: Window List lacks keyboard usability
https://bugs.kde.org/show_bug.cgi?id=387582 Bug ID: 387582 Summary: Window List lacks keyboard usability Product: plasmashell Version: master Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Window List Assignee: plasma-b...@kde.org Reporter: juanma_bel...@yahoo.es Target Milestone: 1.0 The Window List plasma widget which has replaced the good old pop-up window cannot really be used without pointing device: it is possible to open the widget with an assigned shortcut, and close it again with the same shortcut (not with Esc), but it is not possible to select a window or actually anything at all with keyboard only. Before (I think up until KDE 4.x, but I'm not sure) it was possible to open the Window List with its shortcut (like now) and then: - select any window in the list with keyboard arrows - and press Enter to switch to it - or press the contextual menu button (if your keyboard has one) to get a helpful pop-up menu - or press Esc to close the Window List None of those 4 actions is possible anymore. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387582] Window List lacks keyboard usability
https://bugs.kde.org/show_bug.cgi?id=387582 Juanma changed: What|Removed |Added Version|master |5.8.6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387582] Window List lacks keyboard usability
https://bugs.kde.org/show_bug.cgi?id=387582 --- Comment #1 from Juanma --- Let me correct myself: it is possible to get keyboard focus on the window list per se, after 3 tab skips, and so it is possible to select a window and press Enter to switch to it. The rest is as I described before. It is worth mentioning that the pin icon of the widget gets focus before the list itself. I can't find much use for that pin, because pinning the widget makes it stay above all other windows. On the other hand, it is not possible to make the widget stay put but not cover other windows, so the whole pinning thing usefulness is outside my current scope of understanding. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 366682] Search doesn't yield any result
https://bugs.kde.org/show_bug.cgi?id=366682 Juanma changed: What|Removed |Added CC||juanma_bel...@yahoo.es --- Comment #2 from Juanma --- Steps to reproduce: - open KMail2 Version 5.1.3 in a more or less freshly installed Kubuntu: + KDE Frameworks 5.18.0 + Qt 5.5.1 (built against 5.5.1) + The xcb windowing system (got that from the "About Kmail" dialog) In this conditions, any search (not 'Quick Search' or 'Quick Filter'; those seem to work well) I have tried so far has failed, but I will specify more steps just to give some example: - mark a few mails as ToDo (Action Item), in different folders - go to "Tools > Find Messages..." - select the folders where you have marked mails, or just "Search in all folders" - select either "Match all" or "Match any": it won't work either way - choose "Message Status - is - Action Item" - Give the search folder a name, or not. It won't matter. The search is empty: no results. -- You are receiving this mail because: You are watching all bug changes.
