[korganizer] [Bug 486230] New: Events disappear from korganizer after upgrading from plasma 5 to 6
https://bugs.kde.org/show_bug.cgi?id=486230 Bug ID: 486230 Summary: Events disappear from korganizer after upgrading from plasma 5 to 6 Classification: Applications Product: korganizer Version: 6.0.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: da...@ciarniello.ca Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY I just updated my system from Fedora 39 to 40 which also updated plasma from 5 to 6. After updating, I noticed that events were missing from the digital clock widget in the taskbar. I opened korganizer to see whether it still my events listed and found that they were still there. I added a dummy event to korganizer and had it appear, temporarily in the digital clock. I'm not entirely certain of the subsequent steps but I think it was something like this. I closed korganizer and noticed that the dummy event that I had added disappeared from the digital clock. When I reopened korganizer, I found that all events, including the dummy event, had all disappeared from korganizer. STEPS TO REPRODUCE 1. ??? 2. 3. OBSERVED RESULT Events disappear from korganizer and digital clock after upgrading from plasma 5 to 6 EXPECTED RESULT Events don't disappear upgrading plasma SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION This likely related message appears in the log: korganizer[26164]: qt.core.qobject.connect: QObject::disconnect: Unexpected nullptr parameter The event data is still present in the akonadi database .local/share/akonadi/db_data/akonadi/parttable.ibd -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485588] New: Application Dashboard: Can't run searched commands using keyboard
https://bugs.kde.org/show_bug.cgi?id=485588 Bug ID: 485588 Summary: Application Dashboard: Can't run searched commands using keyboard Classification: Plasma Product: plasmashell Version: 6.0.3 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ad...@leinir.dk CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY In Plasma 5's Application Dashboard, it was possible to use it effectively as one would use krunner. This is no longer possible, and you end up having to use either mouse or touch screen to activate results from a search (pressing enter does not work, and neither tab nor arrow keys will move focus around) STEPS TO REPRODUCE 1. Open Application Dashboard 2. Type some search term (for example "kons") 3. Attempt to launch the first result in the list by pressing the enter key OBSERVED RESULT Nothing happens (at least it doesn't for e.g. close the overlay or whatnot, which is certainly nice) EXPECTED RESULT The first result is activated (in the case of the example, konsole would be launched and the overlay closed) Versions and such as per selections (openSUSE Tumbleweed current as of 2024/04/15) -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 475133] Opening a file while another one is already open won't set focus to the file tab
https://bugs.kde.org/show_bug.cgi?id=475133 --- Comment #3 from Dan Dascalescu --- @Pedro: I've set the Focus stealing prevention to "Extreme" and still see the issue in Krusader 2.8.0. Not sure how to tell the default mode for KrViewer. But the issue persists if I press F4 on .txt files, which launched KrViewer in text editing mode. @Toni: I've looked at the build steps and unfortunately I'm short on time right now to follow them (from experience, hunting for the deps was a time-consuming and error prone operation). A suggestion to make building easier for non-contributors would be to add a copy/pasteable `sudo apt/dnf install` line that would install/update all required dependencies, and another one for optional dependencies. Or even better, a copy/pasteable code section with all the installation steps, that could be run unattended (still 爛 that there will be no errors). -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 482594] Screen sharing/recording fails with error message "Failed to connect PipeWire context"
https://bugs.kde.org/show_bug.cgi?id=482594 Dan changed: What|Removed |Added CC||da...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 483905] New: Can't generate icons on Windows
https://bugs.kde.org/show_bug.cgi?id=483905 Bug ID: 483905 Summary: Can't generate icons on Windows Classification: Plasma Product: Breeze Version: master Platform: Compiled Sources OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: d...@dankeenan.org CC: kain...@gmail.com, m...@nueljl.in Target Milestone: --- SUMMARY I noticed that generating icons (i.e. dark variants) is expressly disabled on Windows as of commit 6324f834 from 3 years ago. Is there any backstory or previous efforts in fixing this? My searches didn't turn anything up and I'd love to know if there have been previous attempts before diving into it myself. STEPS TO REPRODUCE 1. Try to cmake configure the project, even with Python and lxml installed. 2. cmake --build OBSERVED RESULT Generating icons is always disabled with an admonition to ensure Python and lxml are always installed (as if they weren't). This means that, with very few exceptions, dark icons are identical to light icons when built on Windows. EXPECTED RESULT Dark icons generated properly. SOFTWARE/OS VERSIONS Windows: Windows 11 Home 23H2 macOS: Not tested Linux/KDE Plasma: Not tested (available in About System) KDE Plasma Version: Not tested KDE Frameworks Version: Not tested Qt Version: Qt 6.6 breeze-icons commit 98c004456cf3ba9aa46b201a916c9e6b0e31f1a2 ADDITIONAL INFORMATION https://invent.kde.org/frameworks/breeze-icons/-/commit/6324f834e991ace73a07503877420c7ec44e49c1 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 449414] System Monitor reports misleadingly low cpu usage
https://bugs.kde.org/show_bug.cgi?id=449414 --- Comment #6 from Dan Dascalescu --- I still see this behavior. I've recorded a video with my phone during a Google Meet call running in Firefox. It was impossible to identify which process was consuming the CPU. https://youtu.be/8ogXjP1kdRg Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 Kernel Version: 6.7.7-100.fc38.x86_64 (64-bit) Graphics Platform: Wayland Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: TUXEDO Product Name: TUXEDO InfinityBook Pro Gen7 (MK1) -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 483360] New: Rectangle position isn't restored from one launch to the next if more than ~30 seconds pas
https://bugs.kde.org/show_bug.cgi?id=483360 Bug ID: 483360 Summary: Rectangle position isn't restored from one launch to the next if more than ~30 seconds pas Classification: Applications Product: Spectacle Version: 23.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: ddascalescu+...@gmail.com CC: k...@david-redondo.de Target Milestone: --- I'm watching s presentation and want to take screenshots from time to time, of the rectangular region of the video. If I take screenshots quickly one after another, Spectacle remembers the rectangle position. But if more than, say, 30 seconds pass since I took the last screenshot, and I press Print Screen or Shift+Meta+PrtSc, the position is lost and I have to draw the rectangle again around the video. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 38 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 I upgraded all packages last week but haven't upgraded to Fedora 39 not. Sorry if the bug was fixed in later versions. Was hoping to get the latest Spectacle via Discover without having to upgrade to a new major distro version. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444335] Full sticky keys functionality does not work under Wayland
https://bugs.kde.org/show_bug.cgi?id=444335 --- Comment #17 from Dan Snis --- (In reply to Marius P from comment #11) > "Turn on sticky keys in System Settings -> Input & Output > Accessibility > > Modifier Keys > make sure that the checkbox "Enable" is turned on. > Apply. > Open kate. > Press & release shift > Press a letter key > An upper case letter is typed" > > Is 444335 only about this scenario and therefore we can close this issue? Its 'only' about sticky modifier keys. As of today with plasma6 in wayland it sort of works. SHIFT and CTRL works (both left and right) However even Win, ALT and Alt Gr is needed with this behaivour. as of now I can't switch between activities (Win+TAB), switch between programs (ALT+TAB) or type '$' (Alt Gr+4 (swedish layout)) Meta key labels according to 'xev': keycode 50 (keysym 0xffe1, Shift_L) keycode 37 (keysym 0xffe3, Control_L) keycode 133 (keysym 0xffeb, Super_L) (key marked 'windows logo') keycode 64 (keysym 0xffe9, Alt_L) keycode 108 (keysym 0xfe03, ISO_Level3_Shift) (key marked 'alt gr') keycode 105 (keysym 0xffe4, Control_R) keycode 62 (keysym 0xffe2, Shift_R) -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 456843] [Feature request]: skip summary when entering a feed and go directly to next unread message
https://bugs.kde.org/show_bug.cgi?id=456843 Dan changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #2 from Dan --- Closing this one, since nobody replied and I don't use Akregator anymore. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456372] kwin_x11 (EGL): Creating the OpenGL rendering failed: "Invalid QOpenGLContext::globalShareContext()"
https://bugs.kde.org/show_bug.cgi?id=456372 Dan changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #5 from Dan --- Clsoing this one, since the issue doesn't happen with Plasma 6. -- You are receiving this mail because: You are watching all bug changes.
[massif-visualizer] [Bug 479434] Snap of massif-visualizer is not configured properly with dot/graphviz
https://bugs.kde.org/show_bug.cgi?id=479434 --- Comment #4 from Dan --- Ping. Who is the person to responsible for maintaining official KDE nap packages https://snapcraft.io/publisher/kde ? Could this issue be reassigned to them? -- You are receiving this mail because: You are watching all bug changes.
[massif-visualizer] [Bug 479434] Snap of massif-visualizer is not configured properly with dot/graphviz
https://bugs.kde.org/show_bug.cgi?id=479434 --- Comment #3 from Dan --- (In reply to Milian Wolff from comment #2) > and I'm not maintaining any snap packages, please reach out to your > distribution or packager Who is maintaining https://snapcraft.io/massif-visualizer ? It says it's an official KDE account and "Contact publisher" leads to https://kde.org/support/ which leads to a bug tracker. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 479434] New: Snap of massif-visualizer is not configured properly with dot/graphviz
https://bugs.kde.org/show_bug.cgi?id=479434 Bug ID: 479434 Summary: Snap of massif-visualizer is not configured properly with dot/graphviz Classification: Developer tools Product: valgrind Version: unspecified Platform: Snap OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: massif Assignee: n...@valgrind.org Reporter: d.malju...@yandex.ru Target Milestone: --- SUMMARY Opening callgraph tab in massif-visualizer snap leads to a crash STEPS TO REPRODUCE 1. install massif-visualizer snap (sudo snap install massif-visualizer) 2. snap run massif-visualizer 3. open some massif profile 4. Try to open callgraph tab OBSERVED RESULT Program crashes with ``` creating new dot file in "/tmp/massif-visualizer.VVnjIJ" show dot graph in output file "/tmp/massif-visualizer.VVnjIJ" Error: Layout type: "dot" not recognized. Use one of: Error: Layout was not done ``` EXPECTED RESULT Callgraph tab is opened (and shows something) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Rocky Linux 8 snap info massif-visualzer: snap-id: 1ChRFuKzm7aeJVDVCLzRXHf3CwXz00Xx tracking: latest/stable refresh-date: 8 days ago, at 21:01 +04 channels: latest/stable:0.7.0 2023-11-01 (10) 178MB - latest/candidate: 0.7.0 2023-11-01 (10) 178MB - latest/beta: ↑ latest/edge: master+6003291 2019-01-16 (3) 34MB - installed: 0.7.0 (10) 178MB - ADDITIONAL INFORMATION Perhaps it's missing explicit gvAddLibrary? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 478250] Sorting is very slow
https://bugs.kde.org/show_bug.cgi?id=478250 --- Comment #7 from Dan --- (In reply to Kåre Särs from comment #6) > Hi, > > This has been improved in master and will be released with 24.02.0 in > February. > > If you need the improvement _now_, you have to compile your self or use some > bleeding development edge distribution that packages beta versions of KDE > software. > > Instructions for building it your self: > https://kate-editor.org/build-it/ > > Br, > Kåre Hi, no need to hurry. Thank you for the info. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 478250] Sorting is very slow
https://bugs.kde.org/show_bug.cgi?id=478250 Dan changed: What|Removed |Added Status|RESOLVED|VERIFIED Resolution|FIXED |REMIND --- Comment #5 from Dan --- (In reply to Waqar Ahmed from comment #1) > Hi, would it be possible for you to try the latest Kate? You seem to be on > Arch, so the latest version should be available Hi, I have tried it with the latest version available in Arch: * kate 23.08.4 * KDE Frameworks 5.113.0 * Qt 5.15.11 *Still too slow*: * sort ~ 2sec * kate >> minute -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 477891] Digest authentication failure
https://bugs.kde.org/show_bug.cgi?id=477891 --- Comment #5 from Dan Fandrich --- For the record, the Qt issue seems to be https://bugreports.qt.io/browse/QTBUG-98280 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 477891] Digest authentication failure
https://bugs.kde.org/show_bug.cgi?id=477891 Dan Fandrich changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #4 from Dan Fandrich --- I traced the Akregator code and found that it seems to use the QtNetwork classes to perform HTTP requests. I created a standalone Qt application to perform a similar request and discovered that it truncates the response field to 128 bits as well. So, it seems to be a problem in Qt itself (I tried both 5.15.2 and 5.15.7). -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 478250] Sorting is very slow
https://bugs.kde.org/show_bug.cgi?id=478250 --- Comment #2 from Dan --- Hi, thanks for the reaction. Will try in a few days (need update but not interrupt the work ...) Dan. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 478250] Sorting is very slow
https://bugs.kde.org/show_bug.cgi?id=478250 Dan changed: What|Removed |Added Summary|Sorting os very slow|Sorting is very slow -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 478250] New: Sorting os very slow
https://bugs.kde.org/show_bug.cgi?id=478250 Bug ID: 478250 Summary: Sorting os very slow Classification: Applications Product: kate Version: 23.04.3 Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: scripting Assignee: kwrite-bugs-n...@kde.org Reporter: roze...@volny.cz Target Milestone: --- SUMMARY *** The sorting plugins: Tool->Scripts->Editing->Sort Selected Text ... ...-> Remove Duplicates and sort ...) are *very* slow. What sort can make is seconds, kate/kwrite need hour(s) to achieve. *** STEPS TO REPRODUCE 1. Create very large text file (50MB+) 2. Make it sort (and unique) 3. Compare times with `sort -u` on the same file OBSERVED RESULT Kate is not responding for a very long time EXPECTED RESULT *Much* faster result SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.7 KDE Frameworks Version 5.108.0 Qt Version: 5.15.10 (built against 5.15.10) -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 405886] opening/comparing large text files is slow (80MB)
https://bugs.kde.org/show_bug.cgi?id=405886 Dan changed: What|Removed |Added CC||roze...@volny.cz --- Comment #3 from Dan --- As for the version kdiff3 1.10.5 (64 bit), the comparison of large files is still far too slow. Whak diff can make in seconds, kdiff makes in minutes (or more). I understand that it has low priority (kdiff3 works nicely after all), but improvement in this area would be highly appreciated. Thank you very much. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444335] Full sticky keys functionality does not work under Wayland
https://bugs.kde.org/show_bug.cgi?id=444335 --- Comment #12 from Dan Snis --- If it'a a meta bug or not I'm not aware of. As a user with only one "finger" or a single key press every time It needs to be more than "shift", "ctrl", "alt gr" and "alt" are also required and sometimes in combination, like if I want to make a circle in Inkscape that starts in the center you are suppose to hold "ctrl" + "shift" + left mouse button. My mouse button is sticky as well (under X), with ''' xinput --set-prop --type=int --format=8 "$id" 'libinput Drag Lock Buttons' 8 ''' ps. try putting a pen in your mouth and then use the computer inputs without hands and only pen. I love your work and understand that it's hard to imagine different user scenarios, I couldn't imagine it before I had my accident. And everybody has different needs. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 477891] Digest authentication failure
https://bugs.kde.org/show_bug.cgi?id=477891 --- Comment #3 from Dan Fandrich --- Unfortunately, my server isn't public. I could probably come up with a dockerfile to run a local server if you'd like. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 477891] Digest authentication failure
https://bugs.kde.org/show_bug.cgi?id=477891 --- Comment #1 from Dan Fandrich --- One thing I just noted: the other clients respond with 64 hexadecimal characters (i.e. 256 bits) in the "response" field of the Authorization: header, but akregator responds with 32 hex bytes (i.e. 128 bits). It doesn't look like Akregator is responding properly to an algorithm=SHA-256 authorization. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 477891] New: Digest authentication failure
https://bugs.kde.org/show_bug.cgi?id=477891 Bug ID: 477891 Summary: Digest authentication failure Classification: Applications Product: akregator Version: 5.24.3 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: d...@coneharvesters.com Target Milestone: --- SUMMARY Accessing a feed on a lighttpd server protected with HTTP Digest authentication with algorithm=SHA-256 fails with a server error: mod_auth.c.1334) digest: (a2ca643c55f46828b66002b5bed0e4e0): invalid format akregator just silently fails to download the feed and shows the name in red. STEPS TO REPRODUCE 1. Configure a feed served by a lighttpd server protected with SHA-256 Digest authentication 2. Try to "Fetch feed" OBSERVED RESULT No feed and a red feed name EXPECTED RESULT Feed contents available for browsing SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Frameworks Version: 5.111.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION The protected RSS feed link can be accessed fine (including authentication) with Firefox, Chrome, curl and xh, so it's unlikely to be a server problem. Running this from Flatpak will first hit #477889 before it gets to the point where this bug is encountered. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 477889] New: Cannot access password-protected feeds
https://bugs.kde.org/show_bug.cgi?id=477889 Bug ID: 477889 Summary: Cannot access password-protected feeds Classification: Applications Product: akregator Version: 5.24.3 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: d...@coneharvesters.com Target Milestone: --- SUMMARY Trying to access a feed URL protected with HTTP Digest authentication fails. For the feed I encountered this on the UI shows dialogs to accept a self-signed certificate, then silently fails to download the feed and the feed name in the list on the left turns red. The console shows these messages: kf.kio.core: Can't communicate with kiod_kpasswdserver (for checkAuthInfo)! kf.kio.core: Can't communicate with kiod_kpasswdserver (for queryAuthInfo)! An older version (20.12.0) installed locally (not with via Flatpak) works fine, and requests the username and password from the user the first time, then automatically uses those credentials on subsequent uses. kf.kio.core: Can't communicate with kiod_kpasswdserver (for checkAuthInfo)! kf.kio.core: Can't communicate with kiod_kpasswdserver (for queryAuthInfo)! STEPS TO REPRODUCE 1. Configure a feed that requires Digest authentication 2. Try to "Fetch feed" 3. Go out and do some gardening because you aren't going to be reading RSS feeds OBSERVED RESULT No feed and a red feed name EXPECTED RESULT Feed contents available for browsing SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: KDE Frameworks Version: 5.111.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION The Flatpak permissions for org.kde.akregator do not include org.kde.kpasswdserver in the [Session Bus Policy] section. Running "sudo flatpak override org.kde.akregator --talk-name=org.kde.kpasswdserver" lets akregator get past this problem (but then it encounters another, which I'll open momentaryily). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 469730] Night color shifting happens at the wrong time during daylight savings time when using manual Date & Time setting
https://bugs.kde.org/show_bug.cgi?id=469730 --- Comment #43 from Dan Dascalescu --- Glad to see a fix. Until it rolls out so I can test, I'd like to share that actually I'm still experiencing Night Color not changing even in the middle of the day (~3pm now), with "Set date and time automatically" checked. I've just checked and unchecked it, and Night Color still remained on. Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.6-200.fc38.x86_64 (64-bit) Graphics Platform: Wayland Processors: 20 × 12th Gen Intel® Core™ i7-12700H Product Name: TUXEDO InfinityBook Pro Gen7 (MK1) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477314] Ctrl+Alt+F11 freezes the GUI and the shortcut isn't listed in the System Settings
https://bugs.kde.org/show_bug.cgi?id=477314 --- Comment #3 from Dan Dascalescu --- (In reply to fanzhuyifan from comment #2) > Ctrl-Alt-Fx are used to switch to virtual consoles. I don't see any visual feedback after pressing Ctrl+Alt+F11, other than the mouse cursor freezing. Is this expected? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477314] Ctrl+Alt+F11 freezes the GUI and the shortcut isn't listed in the System Settings
https://bugs.kde.org/show_bug.cgi?id=477314 --- Comment #1 from Dan Dascalescu --- Correction: this may not be a regression. The bookmark shortcut in my IDE was Ctr+Shift+F11. Still, Ctrl+Alt+F11 is too easy to press accidentally compared to its destructive effect. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477314] Ctrl+Alt+F11 freezes the GUI and the shortcut isn't listed in the System Settings
https://bugs.kde.org/show_bug.cgi?id=477314 Dan Dascalescu changed: What|Removed |Added Summary|Regression: Ctrl+Alt+F11|Ctrl+Alt+F11 freezes the |freezes the GUI and the |GUI and the shortcut isn't |shortcut isn't listed in|listed in the System |the System Settings |Settings -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477314] New: Regression: Ctrl+Alt+F11 freezes the GUI and the shortcut isn't listed in the System Settings
https://bugs.kde.org/show_bug.cgi?id=477314 Bug ID: 477314 Summary: Regression: Ctrl+Alt+F11 freezes the GUI and the shortcut isn't listed in the System Settings Classification: Plasma Product: plasmashell Version: 5.27.8 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: ddascalescu+...@gmail.com Target Milestone: 1.0 I was trying to use my IDE's shortcut for showing bookmarks, Ctrl+Alt+F11, and instead noticed that KDE had frozen. After fumbling with the keyboard without any feedback from the OS, the system ended up rebooting into grub. This is a regression, because Ctrl+Alt+F11 worked as intended about a month ago (showing bookmarks in WebStorm). I don't quite understand the point of Ctrl+Alt+F11 nowadays (https://askubuntu.com/a/280687/116961), but it would be nice to be able to remove that shortcut, as I have more interest in using my IDEs bookmarks than in freezing the desktop. However, it's not listed in System Settings -> Shortcuts when I type "F11". Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.6-200.fc38.x86_64 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477313] New: System Settings: incremental search through shortcuts produces fewer results when relaxing the search
https://bugs.kde.org/show_bug.cgi?id=477313 Bug ID: 477313 Summary: System Settings: incremental search through shortcuts produces fewer results when relaxing the search Classification: Plasma Product: plasmashell Version: 5.27.8 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ddascalescu+...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 163336 --> https://bugs.kde.org/attachment.cgi?id=163336=edit screencast In System Settings -> Workspace -> Shortcuts, searching for a string then backspacing the last few characters may no longer show the shortcuts matching the prefix of that string. This apparently happens because one of the items in the middle panel gets selected, and that filters the results. This is easy to miss by the user (I missed it when recording the screencast several times, and only noticed it when watching the recording) STEPS TO REPRODUCE 1. Go to System Settings, Shortctus 2. In the "Search..." field, type "f". Notice the many matches. 3. Continue typing "1", for "f1". Notice 3 matches. 4. Continue typing "2", for "f12". Notice one match. 5. Now press backspace. Instead of the 3 matches from step 3, only 2 will be shown. 6. Press backspace once more. Instead of the many matches for "f", only 9 will be shown. OBSERVED RESULT EXPECTED RESULT Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 450034] Searching for "audio" in the launcher finds the System Settings after many applications
https://bugs.kde.org/show_bug.cgi?id=450034 --- Comment #6 from Dan Dascalescu --- Created attachment 16 --> https://bugs.kde.org/attachment.cgi?id=16=edit Plasma 5.27.8 screenshot I still see this in Plasma 5.27.8. Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.6-200.fc38.x86_64 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[pulseaudio-qt] [Bug 477309] New: Audio settings profile dowpdown too narrow
https://bugs.kde.org/show_bug.cgi?id=477309 Bug ID: 477309 Summary: Audio settings profile dowpdown too narrow Classification: Plasma Product: pulseaudio-qt Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: nicolas.fe...@gmx.de Reporter: ddascalescu+...@gmail.com Target Milestone: --- Created attachment 163332 --> https://bugs.kde.org/attachment.cgi?id=163332=edit screenshot The "Profile" dropdowns in the Audio settings are too narrow and unnecessarily hide the profile values. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 38 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 477249] Sever failure of Capture RectangularRegion
https://bugs.kde.org/show_bug.cgi?id=477249 --- Comment #4 from Dan --- I couldn'tfind an appimage, snap or a flatpak. i coud probably figure out the last 2 but prefer appimage rather than loading a massive subsystem just to install one app On Sun, Nov 19, 2023, at 4:31 PM, Noah Davis wrote: > https://bugs.kde.org/show_bug.cgi?id=477249 > > --- Comment #3 from Noah Davis --- > (In reply to Dan from comment #2) >> That is useful information. But, I installed it from the Software Center. >> Are you telling me that doing it that way does not always install the latest >> version? >> >> sudo apt install spectacle says: >> package not found. >> >> What am I missing? >> >> thx > > In short, certain kinds of Linux distributions such as Debian Stable and > Ubuntu > have long upgrade cycles where very few changes happen in between distribution > versions. This leads to their users being stuck with outdated versions. The > solutions available to you are the following: > > - Try to use a Flatpak, Snap, AppImage or other distribution independent > package that provides a newer version of the software you want to use. > - Add a repository that provides a newer Debian package for the software you > want to use. You might not have this option with Debian since extra > repositories aren't as common for Debian as they are for other stable Linux > distributions, AFAIK. > - Install a newer version by building it from source code. I don't expect most > users to do this, let alone stable Linux distribution users. For users with > the > latest software versions from a distro like Arch Linux it's not so hard, but > stable linux distribution users would probably need to set up a whole KDE > development environment because their developer package versions are too old. > - Install a Linux distribution that provides newer packages. You can consider > this a last resort, but it might solve a lot of problems if you eventually > find > yourself needing a lot of newer software versions. > > You can ignore the following if the info above was all you needed to read: > > Linux distributions that don't change much between versions are called > "stable" > Linux distributions. That is helpful for system administrators who need to > manage hundreds or thousands of computers. It's a common misconception among > Linux users who install Linux on their personal computers to think that > "stable" means fewer bugs when stable distributions are usually just as buggy > as any other kind. The difference is that the bugs you have to deal with > remain > the same for a long time. If you have a support contract with a company like > Canonical, SUSE or RedHat, you may get patches specific to their supported > Linux distributions to fix some of the bugs. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 477249] Sever failure of Capture RectangularRegion
https://bugs.kde.org/show_bug.cgi?id=477249 --- Comment #2 from Dan --- That is useful information. But, I installed it from the Software Center. Are you telling me that doing it that way does not always install the latest version? sudo apt install spectacle says: package not found. What am I missing? thx -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 477249] New: Sever failure of Capture RectangularRegion
https://bugs.kde.org/show_bug.cgi?id=477249 Bug ID: 477249 Summary: Sever failure of Capture RectangularRegion Classification: Applications Product: Spectacle Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: es...@ieee.org CC: k...@david-redondo.de Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. open app 2. choose capture rectangular region 3. click take screenshot 4. Screen goes completely black 5 . After a minute or two some of the desktop reappears but none of the desktop launchers display. 6. Log off and on 7. Screen returns to normal 8. Uninstall Spectacle 9. Report Bug OBSERVED RESULT EXPECTED RESULT duh... SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian 12 KDE Plasma Version: Latest - just installed KDE Frameworks Version: Latest - just installed Qt Version: Latest - just installed ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 476373] New: "Submitting bug report..." never finishes
https://bugs.kde.org/show_bug.cgi?id=476373 Bug ID: 476373 Summary: "Submitting bug report..." never finishes Classification: Applications Product: drkonqi Version: 5.27.8 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ddascalescu+...@gmail.com Target Milestone: --- Created attachment 162764 --> https://bugs.kde.org/attachment.cgi?id=162764=edit screenshot Spectacle crashed, so I went through the process of submitting a bug report. But it's been 5+ minutes and the process looks like in the screenshot. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 38 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 476372] New: Spectacle crashed when I wanted to edit the annotations
https://bugs.kde.org/show_bug.cgi?id=476372 Bug ID: 476372 Summary: Spectacle crashed when I wanted to edit the annotations Classification: Applications Product: Spectacle Version: 23.08.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: ddascalescu+...@gmail.com CC: k...@david-redondo.de Target Milestone: --- Application: spectacle (23.08.1) Qt Version: 5.15.10 Frameworks Version: 5.110.0 Operating System: Linux 6.5.6-200.fc38.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 38 (KDE Plasma) DrKonqi: 5.27.8 [KCrashBackend] -- Information about the crash: While capturing the screenshot, I added some text annotations. Then I pushed the image into Spectacle because I wanted to edit one of the texts. That's when Spectacle crashed. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Spectacle (spectacle), signal: Segmentation fault [KCrash Handler] #4 0x7f57c0808c19 in QFont::operator==(QFont const&) const () from /lib64/libQt5Gui.so.5 #5 0x7f57c15aa192 in QQuickValueTypeProvider::equal(int, void const*, QVariant const&) () from /lib64/libQt5Quick.so.5 #6 0x7f57c11136d3 in QQmlValueTypeProvider::equalValueType(int, void const*, QVariant const&) () from /lib64/libQt5Qml.so.5 #7 0x7f57c10987a0 in QQmlVMEMetaObject::metaCall(QObject*, QMetaObject::Call, int, void**) () from /lib64/libQt5Qml.so.5 #8 0x7f57c1120608 in QV4::QQmlValueTypeWrapper::write(QObject*, int) const () from /lib64/libQt5Qml.so.5 #9 0x7f57c111a0be in GenericBinding<0>::write(QV4::Value const&, bool, QFlags) () from /lib64/libQt5Qml.so.5 #10 0x7f57c111b59d in QQmlNonbindingBinding::doUpdate(QQmlJavaScriptExpression::DeleteWatcher const&, QFlags, QV4::Scope&) () from /lib64/libQt5Qml.so.5 #11 0x7f57c1118d15 in QQmlBinding::update(QFlags) () from /lib64/libQt5Qml.so.5 #12 0x7f57c0fc46e2 in QV4::QObjectWrapper::getProperty(QV4::ExecutionEngine*, QObject*, QQmlPropertyData*) () from /lib64/libQt5Qml.so.5 #13 0x7f57c0fa0d37 in QV4::QQmlContextWrapper::lookupScopeObjectProperty(QV4::Lookup*, QV4::ExecutionEngine*, QV4::Value*) () from /lib64/libQt5Qml.so.5 #14 0x7f57a44f3f69 in ?? () #15 0x in ?? () [Inferior 1 (process 65025) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[knetattach] [Bug 463510] Cannot "Confirm Website Access", does not react to clicks
https://bugs.kde.org/show_bug.cgi?id=463510 Dan Hutter changed: What|Removed |Added CC||d...@dantheman.me --- Comment #4 from Dan Hutter --- FYI I ran into this bug myself on Kubuntu and found a work around (for SSH anyway). First connect to the remote server over SSH via the terminal. Add the host key to cache and this bug no longer prevents adding the remote folder to Dolphin. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 469730] Night color shifting happens at the wrong time during daylight savings time when using manual Date & Time setting
https://bugs.kde.org/show_bug.cgi?id=469730 --- Comment #29 from Dan Dascalescu --- (In reply to Nate Graham from comment #27) > In that case I think your issue is probably something different, as turning > on automatic time sync worked for Dan. > > Dan, was your clock wrong by 1 hour while automatic time sync was turned off? The clock was correct. I did change timezones a couple times over the course of a month, but I had set it manually as soon as I landed. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 469730] Night color shifting does not start at the correct time or end at the correct time
https://bugs.kde.org/show_bug.cgi?id=469730 --- Comment #23 from Dan Dascalescu --- > do you have "Set date and time automatically" unchecked in Date & Time? And > if so, does it start working of you turn that feature on? Since I've checked that, Night color shifting has been behaving as expected. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 461479] Backlight briefly flashes to full brightness on screen wake
https://bugs.kde.org/show_bug.cgi?id=461479 Dan Robinson changed: What|Removed |Added Ever confirmed|1 |0 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 475134] New: Too many ways to start Kate (sessions) via the launcher menu
https://bugs.kde.org/show_bug.cgi?id=475134 Bug ID: 475134 Summary: Too many ways to start Kate (sessions) via the launcher menu Classification: Applications Product: kate Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: ddascalescu+...@gmail.com Target Milestone: --- Created attachment 162026 --> https://bugs.kde.org/attachment.cgi?id=162026=edit Launcher screenshot after typing "kate" SUMMARY Kate appears to pollute the KDE Launcher with too many options to start itself or its sessions. Some are just duplicates. There is no context menu to remove them. Can't find them in the KDE Menu Editor (only Kate itself is there). SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 38 KDE spin KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 475133] New: Opening a file while another one is already open won't set focus to the file tab
https://bugs.kde.org/show_bug.cgi?id=475133 Bug ID: 475133 Summary: Opening a file while another one is already open won't set focus to the file tab Classification: Applications Product: krusader Version: 2.8.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: krviewer Assignee: krusader-bugs-n...@kde.org Reporter: ddascalescu+...@gmail.com CC: krusader-bugs-n...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. Open a txt/jpg file (F3). Notice how KrViewer gets focus. 2. Alt+Tab back to the Krusader window. 3. Open another txt/jpg file. OBSERVED RESULT The file manager window keeps focus. EXPECTED RESULT KrViewer should receive focus. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 38 KDE spin KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 474939] New: Freeze when trying to open KML file
https://bugs.kde.org/show_bug.cgi?id=474939 Bug ID: 474939 Summary: Freeze when trying to open KML file Classification: Applications Product: krusader Version: 2.8.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: krviewer Assignee: krusader-bugs-n...@kde.org Reporter: ddascalescu+...@gmail.com CC: krusader-bugs-n...@kde.org Target Milestone: --- Created attachment 161911 --> https://bugs.kde.org/attachment.cgi?id=161911=edit F3, then Esc STEPS TO REPRODUCE 1. Press F3 to open the attached KML file 2. Click "Cancel" The viewer will freeze. Trying to close its window won't work. Clicking back into Krusader will cause it to freeze too. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora KDE 38 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 474867] New: Crash while doing nothing
https://bugs.kde.org/show_bug.cgi?id=474867 Bug ID: 474867 Summary: Crash while doing nothing Classification: Applications Product: krusader Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: ddascalescu+...@gmail.com CC: krusader-bugs-n...@kde.org Target Milestone: --- Application: krusader (2.8.0 "A New Day") Qt Version: 5.15.10 Frameworks Version: 5.109.0 Operating System: Linux 6.4.15-200.fc38.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 38 (KDE Plasma) DrKonqi: 5.27.8 [KCrashBackend] -- Information about the crash: Krusader wasn't the active window at the moment of the crash. I had renamed a file and after a few seconds, Krusader crashed. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Krusader (krusader), signal: Segmentation fault [KCrash Handler] #4 0x7fab6b8de937 in QObject::property(char const*) const () from /lib64/libQt5Core.so.5 #5 0x7fab6cef9e05 in KUiServerV2JobTracker::registerJob(KJob*) () from /lib64/libKF5JobWidgets.so.5 #6 0x7fab6cef7334 in QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () from /lib64/libKF5JobWidgets.so.5 #7 0x7fab6b8e8481 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #8 0x7fab6b8e8481 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #9 0x7fab6cc63ec4 in QDBusServiceWatcher::serviceOwnerChanged(QString const&, QString const&, QString const&) () from /lib64/libQt5DBus.so.5 #10 0x7fab6cc649ae in QDBusServiceWatcher::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /lib64/libQt5DBus.so.5 #11 0x7fab6cc64d82 in QDBusServiceWatcher::qt_metacall(QMetaObject::Call, int, void**) () from /lib64/libQt5DBus.so.5 #12 0x7fab6cc1338b in QDBusConnectionPrivate::deliverCall(QObject*, int, QDBusMessage const&, QVector const&, int) () from /lib64/libQt5DBus.so.5 #13 0x7fab6b8ded2b in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #14 0x7fab6c5aeb75 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #15 0x7fab6b8b41a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #16 0x7fab6b8b7655 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #17 0x7fab6b906c5f in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #18 0x7fab6a1134fc in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #19 0x7fab6a1716b8 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #20 0x7fab6a110b83 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #21 0x7fab6b906749 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #22 0x7fab6b8b2b6b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #23 0x7fab6b8badfb in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #24 0x558ec4d0d3a3 in main () [Inferior 1 (process 19813) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 461479] Backlight briefly flashes to full brightness on screen wake
https://bugs.kde.org/show_bug.cgi?id=461479 --- Comment #8 from Dan Robinson --- Just confirmed it does still happen with or without the screen lock according to inotify-wait, but it's not as visible usually if there's no lock screen enabled. For some reason it also seemed more visible on an X11 session despite the actual reported numbers from inotify-wait being the same, but that might be because due to the display scaling there was more light-colored area visible on my display. This is current to 5.27.7. Don't have a 6 build handy to check, if you need that I'm happy to do it but I'm on a Sandy Bridge i7 so that's going to take some time to build, and if Nate says it's broken anyway I probably won't invest that time. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 469730] Night color shifting does not start at the correct time or end at the correct time
https://bugs.kde.org/show_bug.cgi?id=469730 Dan Dascalescu changed: What|Removed |Added CC||ddascalescu+...@gmail.com --- Comment #13 from Dan Dascalescu --- Created attachment 161806 --> https://bugs.kde.org/attachment.cgi?id=161806=edit Screencast of Night Color not working I have the same problem and I've attached a narrated screencast. Today 50 minutes after when Night color should've kicked in, I noticed I also had "Set date and time automatically" unchecked. When I checked it, Night color kicked in. Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 Kernel Version: 6.4.15-200.fc38.x86_64 (64-bit) Graphics Platform: Wayland Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: TUXEDO -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 474731] "Failed to load signature: need more input"
https://bugs.kde.org/show_bug.cgi?id=474731 --- Comment #2 from Dan Dascalescu --- Thanks for clarifying. I was using Fedora 38 with the KDE spin. Where upstream could I report this? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 461479] Backlight briefly flashes to full brightness on screen wake
https://bugs.kde.org/show_bug.cgi?id=461479 --- Comment #7 from Dan Robinson --- I had the screen set to lock when I was testing it, and I don't think it ever occurred to me to test without a lock set. I want to say it is only with the screen locked because I think when I just changed the DPMS timer I didn't notice it. Not in front of my laptop right now but I can try to verify on 5.27. by this weekend at the latest. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 474731] New: "Failed to load signature: need more input"
https://bugs.kde.org/show_bug.cgi?id=474731 Bug ID: 474731 Summary: "Failed to load signature: need more input" Classification: Applications Product: Discover Version: 5.27.8 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: ddascalescu+...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 161744 --> https://bugs.kde.org/attachment.cgi?id=161744=edit Error message needs improvement Getting this unhelpful error when starting Discover. What signature? What input is needed? Error messages 101. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 474444] Pixelate function should add random noise too so it's truly secure
https://bugs.kde.org/show_bug.cgi?id=47 --- Comment #3 from Dan Duris --- (In reply to Noah Davis from comment #1) > Created attachment 161589 [details] > pixelated text > > While I don't know that much about decoding pixelated images, are you sure > it's possible to decode this? I know there's an issue where large text can't > be securely pixelated, but that could be solved by adding an option to > increase the pixelation. So this is where it becomes weird. I have now added a test case where the same characters (6 digits: 161589) are pixelated in three different ways. But when I tried it on a different image - I was getting only black and white pixels instead of colors as here and I could reverse decode the number from standard sized text (e.g. around 12px). The problem seems to be that there is only one pass of pixelization. When one tries to use the pixel tool again, it does nothing over already pixelized area. So it should be adding random noise + allowing user to do multiple passes. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 474444] Pixelate function should add random noise too so it's truly secure
https://bugs.kde.org/show_bug.cgi?id=47 --- Comment #2 from Dan Duris --- Created attachment 161590 --> https://bugs.kde.org/attachment.cgi?id=161590=edit test of pixelation - three times with number 161589 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 474444] New: Spectacle Pixelate function is not secure
https://bugs.kde.org/show_bug.cgi?id=47 Bug ID: 47 Summary: Spectacle Pixelate function is not secure Classification: Applications Product: Spectacle Version: 23.04.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: kdeb...@staznosti.sk CC: k...@david-redondo.de Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Pixelate needs random noise added instead of pixelating same text over with the same pixels. It is definitely not random as second pixelation does not even work (pixelate just does same pixels over and over instead of pixelating with random noise added). STEPS TO REPRODUCE 1. Pixelate some text OBSERVED RESULT Text is note securely pixelated and can be reverse decoded EXPECTED RESULT Text is securely pixelated, i.e. with random noise added -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413406] Night color only working while settings window open
https://bugs.kde.org/show_bug.cgi?id=413406 Dan Dascalescu changed: What|Removed |Added CC||ddascalescu+...@gmail.com --- Comment #10 from Dan Dascalescu --- Created attachment 161400 --> https://bugs.kde.org/attachment.cgi?id=161400=edit Screencast of Night Color not kicking in for Custom Times Night colors stopped working for me either at some point within the last year of KDE updates (I had used macOS for ~6 months so I can't pinpoint exactly when). I have to switch them on and off manually. I recorded a screencast with what happens, but the color change wasn't recorded, so I narrated it: * I had set "Custom times" for night color between 19:00 and 06:00 * At 09:00, the night color was still on * Switched it to "Always off" - nothing happened * Switched it to "Always on" - then it went off instantly, then transitioned back to on within about 1 second * Switched to "Always off" again worked * Choosing "Custom times" appeared to work again (screen was left at cooler temp) Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 Kernel Version: 6.4.13-200.fc38.x86_64 (64-bit) Graphics Platform: Wayland Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: TUXEDO Product Name: TUXEDO InfinityBook Pro Gen7 (MK1) -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 473820] New: Context menu option to bring application window into foreground
https://bugs.kde.org/show_bug.cgi?id=473820 Bug ID: 473820 Summary: Context menu option to bring application window into foreground Classification: Applications Product: plasma-systemmonitor Version: 5.27.6 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: ddascalescu+...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- If I select "Applications" in the left pane, System Monitor will show applications, rather than processes. It would be nice here to have a context menu option for each application to activate its window / bring it into the foreground. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 467966] Crash when stopping recording
https://bugs.kde.org/show_bug.cgi?id=467966 Dan Dascalescu changed: What|Removed |Added CC||ddascalescu+...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 473166] New: Crashed when trying to capture a screenshot again
https://bugs.kde.org/show_bug.cgi?id=473166
Bug ID: 473166
Summary: Crashed when trying to capture a screenshot again
Classification: Applications
Product: Spectacle
Version: 23.04.3
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: General
Assignee: noaha...@gmail.com
Reporter: ddascalescu+...@gmail.com
CC: k...@david-redondo.de
Target Milestone: ---
Application: spectacle (23.04.3)
Qt Version: 5.15.10
Frameworks Version: 5.108.0
Operating System: Linux 6.4.7-200.fc38.x86_64 x86_64
Windowing System: Wayland
Distribution: Fedora Linux 38 (KDE Plasma)
DrKonqi: 5.27.6 [KCrashBackend]
-- Information about the crash:
Captured a screenshot, added some annotations, copied to clipboard. Pressed
Print Screen again -> crash
The crash can be reproduced sometimes.
-- Backtrace:
Application: Spectacle (spectacle), signal: Segmentation fault
[KCrash Handler]
#4 0x55b1b08b462d in SelectedActionWrapper::setEditAction(EditAction*) ()
#5 0x55b1b08bc3ee in AnnotationDocument::clearAnnotations() ()
#6 0x55b1b08ab29e in
QtPrivate::QFunctorSlotObject
const&)#1}, 1, QtPrivate::List const&>, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) [clone .lto_priv.0] ()
#7 0x7f8a0d6e8461 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#8 0x55b1b08cfefc in
QtPrivate::QFunctorSlotObject
const&)#1}, 1, QtPrivate::List const&>, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) [clone .lto_priv.0] ()
#9 0x7f8a0d6e8461 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#10 0x55b1b08c43a0 in ScreenShotSourceMeta2::handleSourceFinished() ()
#11 0x7f8a0d6e8461 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#12 0x55b1b08cc226 in
QtPrivate::QFunctorSlotObject const&)::{lambda()#8}, 0, QtPrivate::List<>, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) [clone .lto_priv.0] ()
#13 0x7f8a0d6e8461 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#14 0x7f8a0d4ffa25 in QFutureWatcherBase::event(QEvent*) () from
/lib64/libQt5Core.so.5
#15 0x7f8a0efaeb75 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#16 0x7f8a0d6b4188 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#17 0x7f8a0d6b7635 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#18 0x7f8a0d706c3f in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#19 0x7f8a0b11348c in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#20 0x7f8a0b171648 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#21 0x7f8a0b110b13 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#22 0x7f8a0d706729 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#23 0x7f8a0d6b2b4b in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#24 0x7f8a0d6baddb in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#25 0x55b1b087c952 in main ()
[Inferior 1 (process 171323) detached]
The reporter indicates this bug may be a duplicate of or related to bug 470217,
bug 472401.
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[Spectacle] [Bug 472302] Text in input doesn't wrap and become a multi-line string after hitting Shift+Enter
https://bugs.kde.org/show_bug.cgi?id=472302 Dan Dascalescu changed: What|Removed |Added Ever confirmed|0 |1 CC||ddascalescu+...@gmail.com Status|REPORTED|CONFIRMED --- Comment #2 from Dan Dascalescu --- Seconding this feature request: there's no way to create multi-line text annotations? This is extremely common for screenshots. I've tried pressing all combinations of Shift/Ctrl/Alt +Enter and nothing creates a new line. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468609] Loads heif only with 8 bits color depth
https://bugs.kde.org/show_bug.cgi?id=468609 --- Comment #4 from Dan --- One of the images I've used for testing is: https://drive.google.com/file/d/1R8nlefUAu5fgwKc57Sd0AzU4R_nE-ZoA/view?usp=drive_link With the patch it does 10 bit to 16bit scaling shift fine rather than the direct to 8 bit conversion before. The colours are a bit washed out as with 8 bit. My reading regarding the colour profile: ITU-R BT.2100 PQ is that this is a non linear conversion. I think canon are using nclx so dropping through to the "Unknown HEIF color profile type discarded" warning. There is more reading/hacking before I get my head around that part. Dan -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468609] Loads heif only with 8 bits color depth
https://bugs.kde.org/show_bug.cgi?id=468609
Dan changed:
What|Removed |Added
CC||dkb...@tofubar.com
--- Comment #2 from Dan ---
My canon HEIF images appear washed out and I thought this might be the solution
but am now convinced otherwise. I'm now slowly going down the education path on
colour profiles. I think this patch fixes the bit depth problem as a start. It
works for my canon images but I haven't tested for the full combination of
alpha and bit depth.
diff --git a/core/dplugins/dimg/heif/dimgheifloader_load.cpp
b/core/dplugins/dimg/heif/dimgheifloader_load.cpp
index eb8862c91f..f3d0bdc071 100644
--- a/core/dplugins/dimg/heif/dimgheifloader_load.cpp
+++ b/core/dplugins/dimg/heif/dimgheifloader_load.cpp
@@ -335,7 +335,7 @@ bool DImgHEIFLoader::readHEICImageByHandle(struct
heif_image_handle* image_handl
{
int lumaBits = heif_image_handle_get_luma_bits_per_pixel(image_handle);
int chromaBits =
heif_image_handle_get_chroma_bits_per_pixel(image_handle);
-
+int colorDepth = lumaBits;
if ((lumaBits == -1) || (chromaBits == -1))
{
qCWarning(DIGIKAM_DIMG_LOG_HEIF) << "HEIC luma or chroma bits
information not valid!";
@@ -352,8 +352,8 @@ bool DImgHEIFLoader::readHEICImageByHandle(struct
heif_image_handle* image_handl
struct heif_decoding_options* const decode_options =
heif_decoding_options_alloc();
decode_options->ignore_transformations = 1;
m_hasAlpha =
heif_image_handle_has_alpha_channel(image_handle);
-heif_chroma chroma = m_hasAlpha ?
heif_chroma_interleaved_RGBA
-:
heif_chroma_interleaved_RGB;
+heif_chroma chroma = m_hasAlpha ?
((colorDepth==8) ? heif_chroma_interleaved_RGBA :
heif_chroma_interleaved_RRGGBBAA_LE)
+:
((colorDepth==8) ? heif_chroma_interleaved_RGB :
heif_chroma_interleaved_RRGGBB_LE );
// Trace to check image size properties before decoding, as these values
can be different.
@@ -385,8 +385,6 @@ bool DImgHEIFLoader::readHEICImageByHandle(struct
heif_image_handle* image_handl
}
heif_decoding_options_free(decode_options);
-
-int colorDepth = heif_image_get_bits_per_pixel_range(heif_image,
heif_channel_interleaved);
imageWidth() = heif_image_get_width(heif_image,
heif_channel_interleaved);
imageHeight() = heif_image_get_height(heif_image,
heif_channel_interleaved);
--
You are receiving this mail because:
You are watching all bug changes.
[drkonqi] [Bug 472404] New: KDE Crash Handler never finishes "Submitting bug report..."
https://bugs.kde.org/show_bug.cgi?id=472404 Bug ID: 472404 Summary: KDE Crash Handler never finishes "Submitting bug report..." Classification: Applications Product: drkonqi Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ddascalescu+...@gmail.com Target Milestone: --- Created attachment 160396 --> https://bugs.kde.org/attachment.cgi?id=160396=edit Screenshot Spactacle crashed and invoked the Crash Handler. At the end of the process, after logging in, finding similar bugs and writing the description, all that work seems to be lost because the "Submitting bug report" spinner never stops, and it's been 15+ minutes. I've never had any connectivity interruptions on this network and I highly doubt that one happened exactly when it tried to submit the report (in which case there should be a retry mechanism). I don't see any UI affordance to display log information. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Kernel Version: 6.3.12-200.fc38.x86_64 (64-bit) Graphics Platform: Wayland Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® Graphics Product Name: TUXEDO InfinityBook Pro Gen7 (MK1) -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 472401] New: Spectacle crashed when I presed PrintScreen after successfully copying to the clipboard a previous screenshot
https://bugs.kde.org/show_bug.cgi?id=472401
Bug ID: 472401
Summary: Spectacle crashed when I presed PrintScreen after
successfully copying to the clipboard a previous
screenshot
Classification: Applications
Product: Spectacle
Version: 23.04.2
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: General
Assignee: noaha...@gmail.com
Reporter: ddascalescu+...@gmail.com
CC: k...@david-redondo.de
Target Milestone: ---
Application: spectacle (23.04.2)
Qt Version: 5.15.10
Frameworks Version: 5.107.0
Operating System: Linux 6.3.12-200.fc38.x86_64 x86_64
Windowing System: Wayland
Distribution: Fedora Linux 38 (KDE Plasma)
DrKonqi: 5.27.6 [KCrashBackend]
-- Information about the crash:
Took a rectangular screenshot, annotated it, copyed it to the clipboard, pasted
it in a browser.
Then I presed PrintScreen again to capture a new screenshot, and Spectacle just
crashed.
Maybe it's time to rewrite things in Rust?
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: Spectacle (spectacle), signal: Segmentation fault
[KCrash Handler]
#4 0x560ae2a1762d in SelectedActionWrapper::setEditAction(EditAction*) ()
#5 0x560ae2a1f3ee in AnnotationDocument::clearAnnotations() ()
#6 0x560ae2a05bbd in
QtPrivate::QFunctorSlotObject, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) [clone .lto_priv.0] ()
#7 0x7f48c82e8461 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#8 0x560ae2a2ee3a in
QtPrivate::QFunctorSlotObject, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) [clone .lto_priv.0] ()
#9 0x7f48c82e8461 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#10 0x560ae2a2f226 in
QtPrivate::QFunctorSlotObject const&)::{lambda()#8}, 0, QtPrivate::List<>, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) [clone .lto_priv.0] ()
#11 0x7f48c82e8461 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#12 0x7f48c80ffa25 in QFutureWatcherBase::event(QEvent*) () from
/lib64/libQt5Core.so.5
#13 0x7f48c9baeb75 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#14 0x7f48c82b4188 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#15 0x7f48c82b7635 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#16 0x7f48c8306c3f in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#17 0x7f48c5f1348c in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#18 0x7f48c5f71638 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#19 0x7f48c5f10b13 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#20 0x7f48c8306729 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#21 0x7f48c82b2b4b in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#22 0x7f48c82baddb in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#23 0x560ae29df952 in main ()
[Inferior 1 (process 71139) detached]
The reporter indicates this bug may be a duplicate of or related to bug 426320,
bug 430007, bug 439450, bug 439525, bug 462645, bug 464465, bug 465049, bug
465370, bug 467595, bug 467966, bug 468694, bug 468989, bug 469336, bug 469897,
bug 469919, bug 469952, bug 470009, bug 470027, bug 470217, bug 471129, bug
471346, bug 471830, bug 472313.
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[choqok] [Bug 472338] No longer loading twitter timelines
https://bugs.kde.org/show_bug.cgi?id=472338 Dan changed: What|Removed |Added CC||da...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 472099] New: Kalendar crashes on startup
https://bugs.kde.org/show_bug.cgi?id=472099 Bug ID: 472099 Summary: Kalendar crashes on startup Classification: Applications Product: kalendar Version: 22.12.3 Platform: Kubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: claudio.cam...@kde.org Reporter: dobin...@protonmail.com CC: c...@carlschwan.eu Target Milestone: --- Application: kalendar (22.12.3) Qt Version: 5.15.8 Frameworks Version: 5.104.0 Operating System: Linux 6.2.0-24-generic x86_64 Windowing System: X11 Distribution: Ubuntu 23.04 DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: When executing Kalendar it immediatly crashes The crash can be reproduced every time. -- Backtrace: Application: Kalendar (kalendar), signal: Segmentation fault [KCrash Handler] #4 0x7fd8e8406c04 in KCalendarCore::Calendar::isLoading() const () at /lib/x86_64-linux-gnu/libKF5CalendarCore.so.5abi2 #5 0x564555bb9875 in () #6 0x7fd8e60f39af in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fd8e60f798e in QTimer::timeout(QTimer::QPrivateSignal) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fd8e60e7bf5 in QObject::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fd8e6d6bf92 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7fd8e60bae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fd8e6114201 in QTimerInfoList::activateTimers() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7fd8e6114b34 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fd8e3f1549d in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7fd8e3f70178 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7fd8e3f141b0 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7fd8e6114e7a in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7fd8e60b97cb in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7fd8e60c1c1a in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x564555b76e5a in () #20 0x7fd8e5623a90 in __libc_start_call_main (main=main@entry=0x564555b74d30, argc=argc@entry=1, argv=argv@entry=0x7ffc4dc32b68) at ../sysdeps/nptl/libc_start_call_main.h:58 #21 0x7fd8e5623b49 in __libc_start_main_impl (main=0x564555b74d30, argc=1, argv=0x7ffc4dc32b68, init=, fini=, rtld_fini=, stack_end=0x7ffc4dc32b58) at ../csu/libc-start.c:360 #22 0x564555b77e55 in () [Inferior 1 (process 21703) detached] The reporter indicates this bug may be a duplicate of or related to bug 468031, bug 467600, bug 469065. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 468140] Songs in a playlist created automatically from files in folder don't play sporadically, can be only fixed by scrolling forward.
https://bugs.kde.org/show_bug.cgi?id=468140 --- Comment #4 from Dan --- works nicely -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 469082] Freecell game modes automatically put unsafe cards on the foundation
https://bugs.kde.org/show_bug.cgi?id=469082 Dan Ciarniello changed: What|Removed |Added CC||da...@ciarniello.ca --- Comment #5 from Dan Ciarniello --- This bug is not specific to freecell as kpatience is overly aggressive in moving cards to the foundation in Castle as well. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 470317] New: Rectangle highlighter missing in the latest release
https://bugs.kde.org/show_bug.cgi?id=470317 Bug ID: 470317 Summary: Rectangle highlighter missing in the latest release Classification: Applications Product: Spectacle Version: 23.04.1 Platform: Neon OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: kdeb...@staznosti.sk CC: k...@david-redondo.de Target Milestone: --- SUMMARY Rectangular highlighter is nowhere to be found in the latest version. STEPS TO REPRODUCE 1. Screenshot 2. Want to highlight using rectangle... 3. ? OBSERVED RESULT No rectangle - highlighter EXPECTED RESULT Rectangular highlighter available SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 469395] Reddit RSS: "error occurred while parsing element" on line 1
https://bugs.kde.org/show_bug.cgi?id=469395 Dan changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #2 from Dan --- (In reply to Laurent Montel from comment #1) > Work fine here. So I'll investigate a bit more. Thanks for replying! -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 469395] New: Reddit RSS: "error occurred while parsing element" on line 1
https://bugs.kde.org/show_bug.cgi?id=469395 Bug ID: 469395 Summary: Reddit RSS: "error occurred while parsing element" on line 1 Classification: Applications Product: akregator Version: 5.23.0 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: feed parser Assignee: kdepim-b...@kde.org Reporter: da...@protonmail.com Target Milestone: --- STEPS TO REPRODUCE 1. https://www.reddit.com/r/kde/.rss OBSERVED RESULT Akregator returns in the log: "error occurred while parsing element" on line 1 EXPECTED RESULT It should get the feed without error. This error started to happen 5 days ago, so I don't know if Reddit changed something that broke Akregator feed parsing code or something else. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462673] Clipboard does not include items copied via copy/paste (CTRL+C or right click+copy) until plasmashell is restarted
https://bugs.kde.org/show_bug.cgi?id=462673 --- Comment #31 from Dan Duris --- (In reply to Nate Graham from comment #30) > Oleg, your issue does sound different. In the futur, please submit a new bug > report rather than adding a comment to an existing one that's about > something else. Thanks. > > Dan, has it happened again? Hello, it hasn't happened in a long time, but if it appears again sometime later I might reopen. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435747] Truncated panel button tooltip
https://bugs.kde.org/show_bug.cgi?id=435747 Dan Dascalescu changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #5 from Dan Dascalescu --- The preview now includes a thumbnail of the window, so it looks like this was fixed. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468270] No contrast in account connection error message
https://bugs.kde.org/show_bug.cgi?id=468270 --- Comment #3 from Dan Dascalescu --- Sorry for the delay. I haven't touched the color schemes at all. I noticed this issues either from the Live ISO, or shortly after installing int -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468741] New: [Spectacle suggestion] Kpipewire as an optional dependency
https://bugs.kde.org/show_bug.cgi?id=468741 Bug ID: 468741 Summary: [Spectacle suggestion] Kpipewire as an optional dependency Classification: Applications Product: Spectacle Version: 23.04.0 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: da...@protonmail.com CC: k...@david-redondo.de Target Milestone: --- Since Spectacle 23.04, Kpipewire is a required dependency. Would it be possible to turn Kpipewire into a optional dependency instead? I ask it because I don't use Pipewire and I don't need this feature in Spectacle. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 468699] New: Dolphin crashed after clicking to remove external SSD
https://bugs.kde.org/show_bug.cgi?id=468699 Bug ID: 468699 Summary: Dolphin crashed after clicking to remove external SSD Classification: Applications Product: dolphin Version: 22.12.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: ddascalescu+...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (22.12.3) Qt Version: 5.15.9 Frameworks Version: 5.104.0 Operating System: Linux 6.2.11-300.fc38.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 38 (KDE Plasma) DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: SSD had two partitions, one encrypted with LUKS. I had mounted and unmounted it 2-3 times, then I clicked to safely remove the entire SSD. At the point, Dolphin crashed. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x56316a30fa02 in TerminalPanel::sendCdToTerminal(QString const&, TerminalPanel::HistoryPolicy) () #5 0x56316a2ee3c3 in DolphinMainWindow::slotStorageTearDownFromPlacesRequested(QString const&) () #6 0x7f320d6e8651 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #7 0x56316a30eb6a in PlacesPanel::slotTearDownRequested(QModelIndex const&) () #8 0x7f320f695fd8 in QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) [clone .lto_priv.0] () from /lib64/libKF5KIOFileWidgets.so.5 #9 0x7f320d6e8651 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #10 0x7f320f6900dc in KFilePlacesEventWatcher::actionClicked(QModelIndex const&) () from /lib64/libKF5KIOFileWidgets.so.5 #11 0x7f320f68b206 in KFilePlacesEventWatcher::eventFilter(QObject*, QEvent*) () from /lib64/libKF5KIOFileWidgets.so.5 #12 0x7f320d6b3af6 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #13 0x7f320e3aeb65 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #14 0x7f320e3b7456 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #15 0x7f320d6b3d48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #16 0x7f320e3b56a4 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /lib64/libQt5Widgets.so.5 #17 0x7f320e40d1a9 in QWidgetWindow::handleMouseEvent(QMouseEvent*) () from /lib64/libQt5Widgets.so.5 #18 0x7f320e41072f in QWidgetWindow::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #19 0x7f320e3aeb75 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #20 0x7f320d6b3d48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #21 0x7f320db6c44b in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib64/libQt5Gui.so.5 #22 0x7f320db4aa0c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib64/libQt5Gui.so.5 #23 0x7f320ab639e4 in userEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5WaylandClient.so.5 #24 0x7f320b511f58 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #25 0x7f320b571cd8 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #26 0x7f320b513233 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #27 0x7f320d706919 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #28 0x7f320d6b270b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #29 0x7f320d6ba99b in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #30 0x56316a2e31d7 in main () [Inferior 1 (process 42143) detached] The reporter indicates this bug may be a duplicate of or related to bug 465694, bug 467403. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 468528] New: "Error while fetching reviews: The specified configuration cannot be used"
https://bugs.kde.org/show_bug.cgi?id=468528 Bug ID: 468528 Summary: "Error while fetching reviews: The specified configuration cannot be used" Classification: Applications Product: Discover Version: 5.27.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: ddascalescu+...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 158124 --> https://bugs.kde.org/attachment.cgi?id=158124=edit Example application Seems that for every application I see in Discover, the reviews aren't shown. Instead I see an orange banner, "Error while fetching reviews: The specified configuration cannot be used" SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 37 KDE Spin KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 468516] New: Peek doesn't launch after installation
https://bugs.kde.org/show_bug.cgi?id=468516 Bug ID: 468516 Summary: Peek doesn't launch after installation Classification: Applications Product: Discover Version: 5.27.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: Flatpak Backend Assignee: plasma-b...@kde.org Reporter: ddascalescu+...@gmail.com CC: aleix...@kde.org, jgrul...@redhat.com, trav...@redhat.com Target Milestone: --- Created attachment 158116 --> https://bugs.kde.org/attachment.cgi?id=158116=edit Can't launch Peek on Fedora STEPS TO REPRODUCE 1. On a system without Peek, install it from Discover 2. (Notice the quoted size is a few hundred KB, but if you install it on a fresh system, the installation will take far longer that would be warranted for a few hundred KB; I guess this is due to installing Flatpak?) 3. Attempt to launch Peek from the Application Launcher SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 37 KDE spin, Wayland KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468375] Add option to automatically show annotation tools after taking a screenshot in the main window
https://bugs.kde.org/show_bug.cgi?id=468375 --- Comment #2 from Dan Dascalescu --- > Perhaps we could even remove the separate "annotations mode" and just always > have the annotation toolbar visible in the main window. Having enjoyed the usability of Flameshot in this regard, I support this idea. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 468379] New: Can't update UEFI DBX
https://bugs.kde.org/show_bug.cgi?id=468379 Bug ID: 468379 Summary: Can't update UEFI DBX Classification: Applications Product: Discover Version: 5.27.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: ddascalescu+...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 158009 --> https://bugs.kde.org/attachment.cgi?id=158009=edit Update UEFI dbx doesn't work No matter how many times I click "Update All", the "UEFI dbx" item remains in the list as seen in the screenshot. SOFTWARE/OS VERSIONS Fedora 37 KDE spin KDE Plasma Version: 5.27.4 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468231] Contradictory touchpad settings for right click two-finger vs. pressing bottom-right corner of touchpad
https://bugs.kde.org/show_bug.cgi?id=468231 Dan Dascalescu changed: What|Removed |Added Version|5.24.7 |5.27.4 --- Comment #3 from Dan Dascalescu --- What confused me is that on one hand (#460102) it's impossible to right click both via pressing the bottom-right corner and with a two-finger tap, and on the other if you want to right click, there seem to be two different ways to do so (indicated in the screenshot): "Two-finger tap" and 'Press bottom-right corner". In the meantime I've moved to Fedora 37 + Plasma 5.27.4, and I can in fact activate the right click action in both ways mentioned above, with the settings from the screenshot. So I have all the functionality I need now, and I just think the language of the right click option could be clarified by having the "Right click" option should be only one checkbox, "Right click also by pressing in the bottom-right corner". -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468375] New: Usability suggestion: After taking a screenshot, open annotations
https://bugs.kde.org/show_bug.cgi?id=468375 Bug ID: 468375 Summary: Usability suggestion: After taking a screenshot, open annotations Classification: Applications Product: Spectacle Version: 22.12.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: ddascalescu+...@gmail.com CC: k...@david-redondo.de, m...@baloneygeek.com Depends on: 468369 Target Milestone: --- I'd like to make a usability suggestion inspired from Flameshot. I believe this would great improve the ergonomics of Spectacle, and help make Spectacle superior to Flameshot, thanks to the annotation library which allows more powerful capabilities not present in Flameshot (eg. moving objects around). Most of the times I take a screenshot, I want to annotate it. It would be great to add "Annotate" among the options under Configure -> General -> After taking a screenshot. Right now, if I want to annotate, I have to press Enter, click the Spectacle popup notification (this requires not copying the image to the clipboard after taking the screenshot - see bug 468369), choose Annotate, make my annotation, click Annotation done, then Copy image to clipboard. SOFTWARE/OS VERSIONS Fedora 37 KDE Plasma Version: 5.27.4 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=468369 [Bug 468369] Usability suggestion: add "Copy to clipboard" and "Annotate" to the capture instructions -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468369] Usability suggestion: add "Copy to clipboard" and "Annotate" to the capture instructions
https://bugs.kde.org/show_bug.cgi?id=468369 Dan Dascalescu changed: What|Removed |Added Blocks||468375 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=468375 [Bug 468375] Usability suggestion: After taking a screenshot, open annotations -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468369] Usability suggestion: add "Copy to clipboard" and "Annotate" to the capture instructions
https://bugs.kde.org/show_bug.cgi?id=468369 Dan Dascalescu changed: What|Removed |Added Summary|Usability suggestion: copy |Usability suggestion: add |to clipboard directly |"Copy to clipboard" and ||"Annotate" to the capture ||instructions -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 468229] Broken link to Snap at apps.kde.org/spectacle/
https://bugs.kde.org/show_bug.cgi?id=468229 --- Comment #3 from Dan Dascalescu --- > In general, if your preference is to be using up-to-date software, LTS > Kubuntu releases aren't the best option. I've hopped to Fedora 37. Spectacle is at 22.12.3. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468369] Usability suggestion: copy to clipboard directly
https://bugs.kde.org/show_bug.cgi?id=468369 --- Comment #1 from Dan Dascalescu --- Created attachment 158006 --> https://bugs.kde.org/attachment.cgi?id=158006=edit This notification would become unnecessary -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468369] New: Usability suggestion: copy to clipboard directly
https://bugs.kde.org/show_bug.cgi?id=468369 Bug ID: 468369 Summary: Usability suggestion: copy to clipboard directly Classification: Applications Product: Spectacle Version: 22.12.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: ddascalescu+...@gmail.com CC: k...@david-redondo.de Target Milestone: --- Created attachment 158005 --> https://bugs.kde.org/attachment.cgi?id=158005=edit Suggested UI I'd like to make a usability suggestions inspired from Flameshot. I believe they would great improve the ergonomics of Spectacle. The use case ic taking screenshots for pasting in other tools, more and more of which support pasting from clipboard directly: online collaboration tools (GitHub, Slack, Discord, Gmail, Trello etc.), document editing (LibreOffice Writer), other image editors, IM programs like Facebook Messenger etc. I'd say that in 90% of the cases I need a screenshot, I can paste it directly, without needing to save it. Having an option to do so from Spectacle directly would be great. Right now if I want the image in the clipboard, I have to press Enter, click the Spectacle popup notification, choose Copy (which doesn't actually copy the image to the clipboard, but that's a moot bug). SOFTWARE/OS VERSIONS Fedora 37 KDE Plasma Version: 5.27.4 -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 468140] Songs in a playlist created automatically from files in folder don't play sporadically, can be only fixed by scrolling forward.
https://bugs.kde.org/show_bug.cgi?id=468140 --- Comment #2 from Dan --- I have changed the following options from default as far as I remember: open last played file on startup, seek to last playback position. remember last playlist state and auto load videos from same folder. this is really weird problem. looks like when I don't use my wireless headphones, the bug doesn't appear. to describe it a little further, some songs start with a big delay, about 3-5 seconds, some don't start at all, and if I let it be for a minute or more, it eventually jumps to the playing next song. in some cases I noticed that the song actually starts, but only first few milliseconds of it and it's stuck in a loop, as if something doesn't let it play. and what's weird is that other songs play normally. the bug doesn't happen in celluloid. -- You are receiving this mail because: You are watching all bug changes.
[Welcome Center] [Bug 468270] New: No contrast in account connection error message
https://bugs.kde.org/show_bug.cgi?id=468270 Bug ID: 468270 Summary: No contrast in account connection error message Classification: Applications Product: Welcome Center Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ddascalescu+...@gmail.com CC: n...@kde.org Target Milestone: --- Created attachment 157946 --> https://bugs.kde.org/attachment.cgi?id=157946=edit Screenshot STEPS TO REPRODUCE 1. Start the connection process to e.g. Google 2. Click Cancel OBSERVED RESULT Black bar EXPECTED RESULT Readable error message SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 37 (available in About System) KDE Plasma Version: 5.27.4 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468266] New: Wrong tab order in the Keyboard repeat rate window, Delay -> Rate
https://bugs.kde.org/show_bug.cgi?id=468266 Bug ID: 468266 Summary: Wrong tab order in the Keyboard repeat rate window, Delay -> Rate Classification: Applications Product: systemsettings Version: 5.27.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_keyboard Assignee: plasma-b...@kde.org Reporter: ddascalescu+...@gmail.com CC: butir...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Go to Input Devices -> Keyboard -> Delay 2. Press Tab twice. OBSERVED RESULT The cursor lands on the Help button EXPECTED RESULT The cursor should go to the Rate text input field. It does that if you press Shift+Tab instead at step 2. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 37 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468231] Contradictory touchpad settings for right click two-finger vs. pressing bottom-right corner of touchpad
https://bugs.kde.org/show_bug.cgi?id=468231 --- Comment #1 from Dan Dascalescu --- Just saw the note in bug 460102 about support for both two-finger tap and clicking the bottom-right corner. Can someone from the KDE team please make that feature request at https://gitlab.freedesktop.org/libinput/libinput/-/issues? Not only do they carry much more weight than one of us random users, but their Gitlab also says, "Due to an influx of spam, we have had to impose restrictions on new accounts." -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468231] New: Contradictory touchpad settings for right click two-finger vs. pressing bottom-right corner of touchpad
https://bugs.kde.org/show_bug.cgi?id=468231 Bug ID: 468231 Summary: Contradictory touchpad settings for right click two-finger vs. pressing bottom-right corner of touchpad Classification: Applications Product: systemsettings Version: 5.24.7 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_touchpad Assignee: plasma-b...@kde.org Reporter: ddascalescu+...@gmail.com Target Milestone: --- Created attachment 157916 --> https://bugs.kde.org/attachment.cgi?id=157916=edit Screenshot STEPS TO REPRODUCE 1. Image you're a user wanting to configure right clicking via the touchpad in the System Settings. 2. See the screenshot Two-finger tapping and pressing in the bottom-right corner of the touchapd don't have to be mutually exclusive. Proposed solution: the "Right click" option should be only one checkbox, "Right click also be pressing in the bottom-right corner" SOFTWARE/OS VERSIONS Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468230] New: Default color for text should be red instead of white
https://bugs.kde.org/show_bug.cgi?id=468230 Bug ID: 468230 Summary: Default color for text should be red instead of white Classification: Applications Product: Spectacle Version: 21.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: ddascalescu+...@gmail.com CC: k...@david-redondo.de Target Milestone: --- This would match arrows and other shapes, which are by default red. PS: sorry for using an old version. This is due to bug 468229. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468229] New: Broken link to Snap at apps.kde.org/spectacle/
https://bugs.kde.org/show_bug.cgi?id=468229 Bug ID: 468229 Summary: Broken link to Snap at apps.kde.org/spectacle/ Classification: Applications Product: Spectacle Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: ddascalescu+...@gmail.com CC: k...@david-redondo.de Target Milestone: --- At https://apps.kde.org/spectacle/, the link under "Get it from the Snap store" leads to https://snapcraft.io/spectacle, which is a 404. Side note, how do I get the latest version into my Kubuntu 22.04? It ships with 21.12.3, and if I click "Install on Linux" on that page, I land in Discover, which shows that version installed, not any of the v22 ones I see on the page, or v23 that I see in this bug tracker. Not having the latest version makes it dubious to report bugs. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 430465] Add Crop option in annotation tool
https://bugs.kde.org/show_bug.cgi?id=430465 Dan Dascalescu changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #16 from Dan Dascalescu --- Almost a year later, I still don't see cropping in Spectacle :-/ Probably not surprising, as Help -> About shows v21.12.3, copyright 2015? I'm on Kubuntu 22.04, up to date. -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 468161] New: Dragon Player crashes after closing video player
https://bugs.kde.org/show_bug.cgi?id=468161 Bug ID: 468161 Summary: Dragon Player crashes after closing video player Classification: Applications Product: dragonplayer Version: 22.12.3 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: dannydubyav...@gmail.com CC: myr...@kde.org, sit...@kde.org Target Milestone: --- Application: dragon (22.12.3) Qt Version: 5.15.8 Frameworks Version: 5.104.0 Operating System: Linux 6.2.8-1-default x86_64 Windowing System: X11 Distribution: openSUSE Tumbleweed DrKonqi: 5.27.3 [KCrashBackend] -- Information about the crash: I play a video, I watch about 98-99% of it, and then close it... the video player crashes as I close it. Not a big deal, doesn't really interfere with anything, but it happens most of the time I use this program and I figured I should report it anyway. I just assume you'd want to know about this sort of thing. The crash can be reproduced every time. -- Backtrace: Application: Dragon Player (dragon), signal: Aborted [KCrash Handler] #4 0x7f5f77e94d7c in __pthread_kill_implementation () at /lib64/libc.so.6 #5 0x7f5f77e43356 in raise () at /lib64/libc.so.6 #6 0x7f5f77e2b897 in abort () at /lib64/libc.so.6 #7 0x7f5f76c6fed6 in flush (f=) at ../src/pulsecore/fdsem.c:163 #8 flush (f=f@entry=0x5616fbba01c0) at ../src/pulsecore/fdsem.c:139 #9 0x7f5f76c7013f in pa_fdsem_after_poll (f=0x5616fbba01c0) at ../src/pulsecore/fdsem.c:286 #10 0x7f5f76c9004d in semread_cb (m=, e=, fd=, events=, userdata=0x5616fbd611d0) at ../src/pulsecore/srbchannel.c:209 #11 0x7f5f7825c808 in dispatch_func (source=0x5616fbf483d0, callback=, userdata=) at ../src/pulse/glib-mainloop.c:581 #12 0x7f5f77116f96 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #13 0x7f5f77117358 in () at /lib64/libglib-2.0.so.0 #14 0x7f5f771173ec in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #15 0x7f5f787460b6 in QEventDispatcherGlib::processEvents(QFlags) (this=0x5616fb598b50, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #16 0x7f5f786eb5cb in QEventLoop::exec(QFlags) (this=this@entry=0x7ffc750e4f20, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #17 0x7f5f786f3a50 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #18 0x5616f98c5f38 in main(int, char**) (argc=, argv=) at /usr/src/debug/dragon-22.12.3/src/app/main.cpp:80 [Inferior 1 (process 10023) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 468140] New: Songs in a playlist created automatically from files in folder don't play sporadically, can be only fixed by scrolling forward.
https://bugs.kde.org/show_bug.cgi?id=468140 Bug ID: 468140 Summary: Songs in a playlist created automatically from files in folder don't play sporadically, can be only fixed by scrolling forward. Classification: Applications Product: Haruna Version: 0.10.3 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic Assignee: georgefb...@gmail.com Reporter: ors...@li.ru Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. double click on an audio file in the directory which creates a playlist automatically in haruna 2. switch songs by clicking or just leave it play automatically 3. OBSERVED RESULT some songs don't play automatically EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 468106] New: RAM and CPU usage do not reflect user experience and are not as useful
https://bugs.kde.org/show_bug.cgi?id=468106 Bug ID: 468106 Summary: RAM and CPU usage do not reflect user experience and are not as useful Classification: Applications Product: plasma-systemmonitor Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: ddascalescu+...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 157809 --> https://bugs.kde.org/attachment.cgi?id=157809=edit Screenshot I ran into a state in which my new ThinkPad P1 Gen5's fan remained at max speed for over an hour, even though System Monitor showed a total CPU utilization of under 9% throughout this time. Running htop showed that `nvidia-powerd` was roasting the CPU. "Show: All processes" was checked. Choosing "Show: System Processes", `nvidia-powerd` was shown as taking up only 5% of the CPU. Maybe this is technically correct if only one core was running at 100% and 5% was an average across all core, but this isn't what interests the user. I was using System Monitor to find out what was causing the fan to stay on, and a process at 5% is easy to overlook and not suspect as the culprit. htop's output was more useful. In other instances (may post a screenshot later), the total memory of the running apps from the Applications tab seemed to be under 4GB, yet my 16GB system was thrashing the swap file. Whatever system components were using the other ~12GB, should be shown, ideally with an option to kill them. SOFTWARE/OS VERSIONS Tuxedo OS 22.04 2 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 461479] Backlight briefly flashes to full brightness on screen wake
https://bugs.kde.org/show_bug.cgi?id=461479 Dan Robinson changed: What|Removed |Added Platform|openSUSE|Fedora RPMs Product|kscreenlocker |Powerdevil Version|5.26.4 |5.27.3 Component|general |general --- Comment #3 from Dan Robinson --- Well remember how I said it wasn't happening? Thanks to the magic of inotifywait, I just confirmed that I'm not crazy, and my actual hardware backlight is flashing to full when I wake my display up to reveal the lock screen. It seems to only happen if I have "dim screen" set in the power saving settings with the screen blanking afterwards. If I turn that option off and just have the display turn off, it didn't happen. If anyone wants to confirm that it's happening, here's what I did: 1. Set your lock screen time and dim screen time to 1 minute, set your display off time to 2 minutes. 2. Open a terminal and (install inotify-tools if you haven't, then) run: # inotifywait -m -e modify /sys/class/backlight/intel_backlight/brightness | while read file event; do cat $file; done (obviously if your backlight isn't intel, change that part) 3. Wait 2 minutes, then wiggle your mouse and unlock your screen 4. You should see a big string of numbers going from 0, then very high, and then coming down to whatever your brightness was set to. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462673] Clipboard does not include items copied via copy/paste (CTRL+C or right click+copy)
https://bugs.kde.org/show_bug.cgi?id=462673 --- Comment #26 from Dan Duris --- (In reply to Nate Graham from comment #23) > Dan, does it temporarily fix the issue when you restart plasmashell by > running `systemctl restart --user plasma-plasmashell.service` in a terminal > window? It has actually stopped happening since some recent update. I will test it once I hit it again. -- You are receiving this mail because: You are watching all bug changes.
