[lattedock] [Bug 438440] Plasma applet popups show in wrong place or too large
https://bugs.kde.org/show_bug.cgi?id=438440 Jackson changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #3 from Jackson --- I just figured out the issue, it's not a bug but rather me screwing something up. I had set a window rule to make the Download New Plasma Widgets window always appear larger, but that actually affected all of the popup windows made by Latte Dock. I guess since certain popups couldn't be resized, they would just appear to be moved. Sorry about that, thanks for your help. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 438454] Scatter plots from R are not shown incorrectly
https://bugs.kde.org/show_bug.cgi?id=438454 --- Comment #18 from Yuri Chornoivan --- (In reply to Albert Astals Cid from comment #17) > (In reply to Yuri Chornoivan from comment #12) > > DejaVu Sans (dejavu-fonts package) should be enough. You can file a bug > > report against openSUSE package to include it as a dependence as proposed by > > Albert. > > This is not correct. Dejavu is not a correct replacement for ZapfDingbats. > > ZapfDingbats is a special font where A is not rendered as an A but as the > star of david, etc. It can be proven (e.g. using FontForge) that DejaVu Sans is a good replacement of ZapfDingbats as it contains dingbats part and is common in the distributions. The screenshot above (Mageia 8, fontconfig 2.13.93) is additional proof of the fact that it can be used to render the test file. The only problem is the font precedence. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438531] New: Cannot paste screenshots from Spectacle to Libre Office on Wayland session
https://bugs.kde.org/show_bug.cgi?id=438531 Bug ID: 438531 Summary: Cannot paste screenshots from Spectacle to Libre Office on Wayland session Product: kwin Version: 5.22.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: daant...@gmail.com Target Milestone: --- Created attachment 139273 --> https://bugs.kde.org/attachment.cgi?id=139273=edit Screen recording Cannot paste screenshots from Spectacle to Libre Office on Wayland session STEPS TO REPRODUCE 1. Open Libre Writer 2. Take a screenshot with Spectacle 3. Press "Copy to clipboard" 4. In Libre Writer, press "Ctrl-v", or right click and choose "Paste" OBSERVED RESULT The screenshot isn't pasted EXPECTED RESULT The screenshot appears on Libre Writer, like on X11 session SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux KDE Plasma Version: 5.22.0 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Also tested on a fresh user account. Pasting successes through Google Docs on Firefox 88 (ran via MOZ_ENABLE_WAYLAND=1). -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 435580] Incorrect balance of account
https://bugs.kde.org/show_bug.cgi?id=435580 --- Comment #4 from pa...@web.de --- As I was not able to reproduce the problem with a newly created user starting a skrooge file from scratch, I copied my existing skg-file to that new user. Although I see the same pattern there (first tab works, all tabs afterwords have incoorect balances for some transaction), the problem vanishes as soon as I save the skg-file with this new user. So it seems to be something configuration related and I guess I also need to copy all the configuration to the new user to be able to reproduce it. -- You are receiving this mail because: You are watching all bug changes.
[colord-kde] [Bug 433068] Shows "you need Gnome color management installed in order to calibrate devices"
https://bugs.kde.org/show_bug.cgi?id=433068 --- Comment #8 from 2wxsy5823...@opayq.com --- The developer said: [1] > This is not maintained, and does not work well. Since gcm-calibrate is no longer available starting from 3.35.90, perhaps KDE can remove the functionality? Additionally, the shared-color-targets [2] which is used by gcm-calibrate is unmaintained, and I guess you have to manually download the reference files if you are using a target recently purchased from Wolf Faust. This webpage [3] has instructions for scanner calibration in Linux. [1] https://gitlab.gnome.org/GNOME/gnome-color-manager/-/merge_requests/6/diffs?commit_id=5a1bf35e30ff689c727222fae1f31b0d4be4ae9d [2] https://github.com/hughsie/shared-color-targets [3] https://blog.simon-dreher.de/color-management.html -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437764] Shortcuts for apps/system apps when right clicking the on Kickoff button
https://bugs.kde.org/show_bug.cgi?id=437764 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 437809] Dock unhides if mouse is close to the perimeter
https://bugs.kde.org/show_bug.cgi?id=437809 --- Comment #14 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 411938] Segmentation fault at launch with Wayland
https://bugs.kde.org/show_bug.cgi?id=411938 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 435580] Incorrect balance of account
https://bugs.kde.org/show_bug.cgi?id=435580 --- Comment #3 from pa...@web.de --- Ok, it does not matter how you open the tab or which filter is active. It works correctly in the first transaction tab opened in the skrooge process. In all later opened transaction tabs the balance is sometimes calculated incorrectly (out-of-order), even if all transaction tabs have been closed inbetween. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 435485] Audio cracks on playback (windows)
https://bugs.kde.org/show_bug.cgi?id=435485 ays...@gmail.com changed: What|Removed |Added CC||ays...@gmail.com Version|20.12.3 |21.04.2 --- Comment #5 from ays...@gmail.com --- I think I am seeing the same issue - any playback, even scrubbing over even a blank timeline, produces audio crackling. Kdenlive 21.04.1, fresh install MLT 6.26.1 KDE Frameworks 5.82.0 Qt 5.15.2 ASRock X99 Extreme4 NVidia GeForce GTX 1070 Ti Intel Core i7-5820K I notice we both are using the same mobo; its audio is based on RealTek ALC1150. I have driver version 6.0.1.7926. May be a coincidence, but: Voicemeeter and Discord had a similar problem, and they developed a workaround where you give the audiodg.exe process (Windows Audio Device Graph Isolation) High priority and affinity to a single core. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 150685] Wish: Requesting added options in the "Include Information" print box
https://bugs.kde.org/show_bug.cgi?id=150685 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/pim/calendarsupport/-/merge_requests/12 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 438530] New: ./kdesrc-build --initial-setup adds invalid `complete` command to .zshrc
https://bugs.kde.org/show_bug.cgi?id=438530 Bug ID: 438530 Summary: ./kdesrc-build --initial-setup adds invalid `complete` command to .zshrc Product: kdesrc-build Version: Git Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: setup wizard Assignee: mp...@kde.org Reporter: skierp...@gmail.com Target Milestone: --- SUMMARY Following https://community.kde.org/Get_Involved/development#Set_up_kdesrc-build , I let `./kdesrc-build --initial-setup` make changes to my .zshrc. But when I ran source ~/.zshrc, it failed with "command not found: complete". STEPS TO REPRODUCE 1. Be using zsh (I'm using Fedora 34's zsh 5.8) 2. Follow steps to set up in https://community.kde.org/Get_Involved/development 3. Enter ./kdesrc-build --initial-setup , enter 'y' when it prompts "* Update your /home/spage/.zshrc? (y/N)" 4. Enter source ~/.zshrc OBSERVED RESULT home/spage/.zshrc:125: command not found: complete zsh has a different completion system to bash. EXPECTED RESULT I don't know. I spent some time with https://stackoverflow.com/questions/3249432/can-a-bash-tab-completion-script-be-used-in-zsh , but adding `bashcompinit` or `autoload bashcompinit` before the function _comp-kdesrc-run didn't help . SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 on Wayland -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 434954] Support firewalld zones
https://bugs.kde.org/show_bug.cgi?id=434954 Neal Gompa changed: What|Removed |Added CC||ngomp...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 438318] Some AMD gpu (lm-sensors-based?) sensors no longer available
https://bugs.kde.org/show_bug.cgi?id=438318 Maciej Stanczew changed: What|Removed |Added CC||maciej.stancze...@gmail.com --- Comment #2 from Maciej Stanczew --- Same for CPU sensors: k10temp module provides Tctl, Tdie and Tccd1 temperatures, but System Monitor shows only a single "Core x Current Temperature" sensor. Both k10temp and amdgpu are detected correctly under KSysGuard. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 438529] App won't fully quit on macOS
https://bugs.kde.org/show_bug.cgi?id=438529 Dawid Wróbel changed: What|Removed |Added Latest Commit||bed835a9bfac1983190ed78b28a ||05c638bc1dd46 Status|REPORTED|RESOLVED Version Fixed In||5.12 Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 438529] New: App won't fully quit on macOS
https://bugs.kde.org/show_bug.cgi?id=438529 Bug ID: 438529 Summary: App won't fully quit on macOS Product: kmymoney Version: 5.1.1 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: m...@dawidwrobel.com Target Milestone: --- SUMMARY Close the app and notice that KMM is still running and not responding. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 437314] CPU history graph is scaled to 100% * number of cores, but CPU table view columns are scaled to 100%
https://bugs.kde.org/show_bug.cgi?id=437314 Maciej Stanczew changed: What|Removed |Added CC||maciej.stancze...@gmail.com --- Comment #1 from Maciej Stanczew --- As I understand, it's because the lines are stacked by default -- so if e.g. 4 cores are working at 100%, then the stacked line will go to 400%. Unchecking "Stacked Charts" results in the scale being 0-100%. (Unless I misunderstand what "CPU table view columns" are.) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 194539] Gestures with mouse wheel
https://bugs.kde.org/show_bug.cgi?id=194539 qydwhotm...@gmail.com changed: What|Removed |Added CC||qydwhotm...@gmail.com Platform|Fedora RPMs |unspecified Version|5.20.3 |5.22.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 135097] Mouse Trails when using Mouse Gestures
https://bugs.kde.org/show_bug.cgi?id=135097 qydwhotm...@gmail.com changed: What|Removed |Added Version|5.21.4 |5.22.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 436627] Mouse gestures don't work in Wayland
https://bugs.kde.org/show_bug.cgi?id=436627 qydwhotm...@gmail.com changed: What|Removed |Added Version|5.21.5 |5.22.0 -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 435338] Krfb on Wayland doesn't accept remote keyboard input
https://bugs.kde.org/show_bug.cgi?id=435338 qydwhotm...@gmail.com changed: What|Removed |Added Version|20.12.3 |21.04.1 -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 437807] import audio file metadata
https://bugs.kde.org/show_bug.cgi?id=437807 --- Comment #7 from mark --- I did have the "recursive folder search" checked. I've even tried checking, unchecking, checking and still nothing happens. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438521] Move the icon and label from the center of the thumbnail
https://bugs.kde.org/show_bug.cgi?id=438521 David Edmundson changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #4 from David Edmundson --- Yes. It was an intentional change. https://invent.kde.org/plasma/kwin/-/merge_requests/868 We can't please everyone when it comes to visuals. Sorry. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 438382] after baloo indexes some files more than once you can't clean this up
https://bugs.kde.org/show_bug.cgi?id=438382 --- Comment #2 from skierpage --- (In reply to tagwerk19 from comment #1) Thanks for responding 珞. > (In reply to skierpage from comment #0) > > Some baloo searches return the same file numerous times. > ... > Baloo relies on the device number / inode internally, if a file appears with > a different ID, it's treated as a different file. Ding-ding, that's it. `baloosearch --id term` shows different IDs for the same path, e.g. % baloosearch --id FuelCellWorks 500d90803 /media/Windows/Users/spage/Documents/ECO.txt 5be200803 /media/Windows/Users/spage/Documents/ECO.txt 8546e0803 /media/Windows/Users/spage/Documents/ECO.txt ... > > Once this happens it seems impossible to clean up. > Yes, I have also noticed this. It seems that a file has to be "there" on > disc for "balooctl clear" to work and also (maybe?) the stored device number > / inode also has to match. It's worth following up. I filed bug 438527 , and may have spotted a logic error in `balooctl clear` . I filed enhancement bug 438528 to add a `balooctl remove [ID...]` subcommand. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437455] Plasma crashed on Wayland in QWaylandClientExtensionPrivate::handleRegistryGlobal() when enabling blur effect in Desktop Effects KCM
https://bugs.kde.org/show_bug.cgi?id=437455 --- Comment #13 from David Edmundson --- >with the KDE patch collection which should include the upstream fix This statement was wrong. It did not. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 438528] New: balooctl could use a remove subcommand to remove duplicate IDs
https://bugs.kde.org/show_bug.cgi?id=438528 Bug ID: 438528 Summary: balooctl could use a remove subcommand to remove duplicate IDs Product: frameworks-baloo Version: 5.82.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: balooctl Assignee: baloo-bugs-n...@kde.org Reporter: skierp...@gmail.com Target Milestone: --- SUMMARY It's possible to have multiple entries in Baloo's index for a file path due to the way it generates its internal IDs (see bug 438382). `baloosearch --id some terms` will show these IDs but you can't clear particular IDs. STEPS TO REPRODUCE 1. Get into a state where Baloo's index has multiple IDs for a file. This happens to me with files I often edit on a mounted NTFS partition which I told Baloo to index. 2. baloosearch for terms in this file, using its --id option 3. Try to remove the errant IDs with balooctl clear OBSERVED RESULT E.g. % baloosearch --id FuelCellWorks 500d90803 /media/Windows/Users/spage/Documents/ECO.txt 5be200803 /media/Windows/Users/spage/Documents/ECO.txt 8546e0803 /media/Windows/Users/spage/Documents/ECO.txt ... EXPECTED RESULT You should be able to clear particular IDs from Baloo's index. It would work like this: % balooctl remove 5be200803 nosuchid666 8546e0803 Removing ID 5be200803 from index. ID nosuchid666 not found in index. Removing ID 8546e0803 from index. 2 IDs removed from Baloo's index. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 on Wayland ADDITIONAL INFORMATION The logic in balooctl clear may be broken, bug 438527. If that were fixed, then you could repeatedly enter `balooctl clear /path/to/file` and eventually all the IDs would clear, and then you could `touch /path/to/file` and get Baloo to reindex. However, I think this would first remove the ID that matches the file on-disk, and it seems generally useful to have a remove [IDs] subcommand. Maybe removeID is a better subcommand name, but then you'd want arbitrary capitalization handling... "Rewrite it in Rust" -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 420416] Volume Applet Settings allows invalid characters and textbox expands
https://bugs.kde.org/show_bug.cgi?id=420416 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- Can reproduce on Plasma 5.22, Arch Linux. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437455] Plasma crashed on Wayland in QWaylandClientExtensionPrivate::handleRegistryGlobal() when enabling blur effect in Desktop Effects KCM
https://bugs.kde.org/show_bug.cgi?id=437455 --- Comment #12 from Nate Graham --- Why? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 410891] Add mountpoint to default disk label
https://bugs.kde.org/show_bug.cgi?id=410891 Ahmad Samir changed: What|Removed |Added CC||a.samir...@gmail.com --- Comment #4 from Ahmad Samir --- FWIW, the most robust solution is adding partition labels using any partition manager (e.g. gparted), that works across OS's ...etc, because it's a property of the filesystem not specific to an OS. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 438527] New: `balooctl clear` always prints "File(s) cleared" and never prints "File not found on filesystem or in DB"
https://bugs.kde.org/show_bug.cgi?id=438527 Bug ID: 438527 Summary: `balooctl clear` always prints "File(s) cleared" and never prints "File not found on filesystem or in DB" Product: frameworks-baloo Version: 5.82.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: balooctl Assignee: baloo-bugs-n...@kde.org Reporter: skierp...@gmail.com Target Milestone: --- SUMMARY balooctl clear's logic seems wrong. If you clear a file that has never existed, it prints "File(s) cleared" and never triggers its code that prints "File not found on filesystem or in DB" STEPS TO REPRODUCE 1. Enter `balooctl clear /never/had/this/file` 2. Enter `ls -lt $HOME/.local/share/baloo/index` 3. Look at baloo source code OBSERVED RESULT balooctl prints Could not stat file: /never/had/this/file File(s) cleared The modification time of Baloo's index doesn't change. EXPECTED RESULT balooctl clear has code to print "File not found on filesystem or in DB" but it doesn't run. balooctl should print "NN file(s) cleared" where NN is the count of files balooctl tried to clear from the index. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 on Wayland ADDITIONAL INFORMATION The "clear" handling in https://invent.kde.org/frameworks/baloo/-/blob/master/src/tools/balooctl/main.cpp (which seems more recent than Fedora 34's package) * assumes filePathToId() returning 0 means failure, but as I understand it the underlying stat64() call returns 0 on _success_! -1 means error. * always calls tr.removeDocument(id) for each argument even if it didn't locate an id. * always prints "File(s) cleared". Baloo's removeDocument() doesn't return a status, so it seems impossible to detect successful clearing. It would also be nice to print the ID (as shown by balooshow and baloosearch --id) of each file that was cleared in baloo's index, because of bug 438382 and similar. So the ideal output from % balooctl clear /never/had/this/file /path/to/file2 /now/gone/file3 would be File /never/had/this/file not found in filesystem or in index. Clearing /path/to/file2 with ID 5be200803 from index. File /now/gone/file3 with ID 3fef8fd03 not found in filesystem, clearing from index. 2 file(s) cleared from Baloo's index. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 438323] crash loading an appointment in KOrganizer from web in ICS format
https://bugs.kde.org/show_bug.cgi?id=438323 --- Comment #4 from gjditchfi...@acm.org --- (In reply to John Mc Gill from comment #3) > Created attachment 139255 [details] > attachment-4391-0.html Did you mean to attach an ICS file with comment #3? The attachment is just an e-mail reply. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 438509] Segfault in open window when opening a new window
https://bugs.kde.org/show_bug.cgi?id=438509 --- Comment #8 from Tcll --- well I didn't have gdb on my system, and there wasn't a release available for download (only a source package) so I found this portable program called Insight which bundled gdb in it's release... anyways, I did some probing and may have found a lead on something related to one of the plugins: KF5WindowSystemX11Plugin.so I had to extract kate from the appimage to get it to work, but the attached image (kate_debug.png) may hopefully provide more info the green line is the moment of the crash `rdi+0x968` is a solid address hopefully that relates to an existing pointer in the source -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 438509] Segfault in open window when opening a new window
https://bugs.kde.org/show_bug.cgi?id=438509 --- Comment #7 from Tcll --- Created attachment 139272 --> https://bugs.kde.org/attachment.cgi?id=139272=edit Insight-gdb moment of kate crash -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 438526] New: Scrollbar doesn't handle scroll events
https://bugs.kde.org/show_bug.cgi?id=438526 Bug ID: 438526 Summary: Scrollbar doesn't handle scroll events Product: frameworks-qqc2-desktop-style Version: 5.83.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: c...@carlschwan.eu CC: ahiems...@heimr.nl, k...@davidedmundson.co.uk, noaha...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. move mouse to scrollbar 2. scroll with the touchpad OBSERVED RESULT The ScrollablePage associated with the scrollbar doesn't scroll EXPECTED RESULT The ScrollablePage associated with the scrollbar scroll exactly like how it would work anywhere else on the page. SOFTWARE/OS VERSIONS openSUSE Tumbleweed KDE Frameworks Version: master Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 437807] import audio file metadata
https://bugs.kde.org/show_bug.cgi?id=437807 --- Comment #6 from Robby Stephenson --- Sorry to ask a basic question, but confirm you've got "Recursive folder search" checked in the import options? I just discovered that that checkbox has a bug in some aspects where the check is not respected, but I did want to ask -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438525] Setting the color of a sensor is very hard; no hover or focus decoration of any buttons.
https://bugs.kde.org/show_bug.cgi?id=438525 David Hurka changed: What|Removed |Added CC||david.hu...@mailbox.org --- Comment #1 from David Hurka --- Created attachment 139271 --> https://bugs.kde.org/attachment.cgi?id=139271=edit No hover decoration on buttons. My attachment was lost when submitting the bug. Now I created a new screenshot, and realized that color buttons which contain a non-default color have a permanent hover decoration. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438525] New: Setting the color of a sensor is very hard; no hover or focus decoration of any buttons.
https://bugs.kde.org/show_bug.cgi?id=438525 Bug ID: 438525 Summary: Setting the color of a sensor is very hard; no hover or focus decoration of any buttons. Product: plasmashell Version: 5.22.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: plasma-b...@kde.org Reporter: david.hu...@mailbox.org CC: ahiems...@heimr.nl, notm...@gmail.com Target Milestone: 1.0 SUMMARY As seen in https://bugsfiles.kde.org/attachment.cgi?id=139270 the default colors are nearly invisible. But it is almost impossible to figure out how to configure the color of a sensor. The sensors can be rearranged in the configuration dialog, but there isn’t any hover or focus highlight anywhere. The red cross of the delete button also doesn’t have any hover decoration, it only changes its gamma a little bit. The color button doesn’t even do that. In addition, this button is really tiny. This user interface is kind of button-in-button (in-graphics-area), which seems not correct to me. Traditionally, there was a KEditListWidget-like interface, where every possible user interaction is pretty clear. STEPS TO REPRODUCE 1. Open configuration dialog, page Sensor Details. 2. Move the mouse cursor over the sensors. OBSERVED RESULT Nothing. EXPECTED RESULT Button frames appear (auto raise), focus aura, or anything. SOFTWARE/OS VERSIONS System monitor Sensor 1.0 Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.0 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436359] Right click while dragging causes dropping
https://bugs.kde.org/show_bug.cgi?id=436359 Ahmad Samir changed: What|Removed |Added CC||a.samir...@gmail.com Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Ahmad Samir --- I agree with what was said here: https://github.com/linuxmint/nemo/issues/2508#issuecomment-733753073 I don't think there is anything we can do here. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438524] Bar Chart does not show axis ranges (but Horizontal Bars does)
https://bugs.kde.org/show_bug.cgi?id=438524 --- Comment #2 from David Hurka --- Created attachment 139270 --> https://bugs.kde.org/attachment.cgi?id=139270=edit Horizontal Bars display style -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438524] Bar Chart does not show axis ranges (but Horizontal Bars does)
https://bugs.kde.org/show_bug.cgi?id=438524 David Hurka changed: What|Removed |Added CC||david.hu...@mailbox.org --- Comment #1 from David Hurka --- Created attachment 139269 --> https://bugs.kde.org/attachment.cgi?id=139269=edit Bar Chart display style -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438524] New: Bar Chart does not show axis ranges (but Horizontal Bars does)
https://bugs.kde.org/show_bug.cgi?id=438524 Bug ID: 438524 Summary: Bar Chart does not show axis ranges (but Horizontal Bars does) Product: plasmashell Version: 5.22.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: plasma-b...@kde.org Reporter: david.hu...@mailbox.org CC: ahiems...@heimr.nl, notm...@gmail.com Target Milestone: 1.0 SUMMARY When using the Bar Chart display style, there is no way to tell the axis ranges. However, the Horizontal Bars display style, shows the axis ranges by giving them a background color. STEPS TO REPRODUCE 1. Put sensors in Bar Chart display style OBSERVED RESULT No way to tell whether the bar is full or only half full. EXPECTED RESULT The bar has a background color, so I can exactly see whether it is half full or only 40% full. SOFTWARE/OS VERSIONS System monitor Sensor 1.0 Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.0 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421700] Plasma crashed in QScreen::name()/ShellCorona::addOutput()/ShellCorona::load()/KActivities::Consumer::serviceStatusChanged on a Wayland session after I've switched from main
https://bugs.kde.org/show_bug.cgi?id=421700 David Edmundson changed: What|Removed |Added CC||mateoestradaramirez2001@gma ||il.com --- Comment #23 from David Edmundson --- *** Bug 438499 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438499] Getting Segmentation Faults Every Time I Log in.
https://bugs.kde.org/show_bug.cgi?id=438499 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 421700 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438523] New: Plasma crash after add network speed widget
https://bugs.kde.org/show_bug.cgi?id=438523 Bug ID: 438523 Summary: Plasma crash after add network speed widget Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: bait...@mailfence.com CC: plasma-b...@kde.org Target Milestone: 1.0 STEPS TO REPRODUCE 1. create a new user 2. Start a Plasma session on Wayland 3. Click on "add widget" and add "Network speed" widget. OBSERVED RESULT Plasma crash SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.22.80 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.3 Kernel Version: 5.4.0-74-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-4200U CPU @ 1.60GHz Memory: 9,6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4400 ADDITIONAL INFORMATION This bug affect only new users. Application: Plasma (plasmashell), signal: Segmentation fault [New LWP 9151] [New LWP 9069] [New LWP 9040] [New LWP 9041] [New LWP 9043] [New LWP 9112] [New LWP 9114] [New LWP 9115] [New LWP 8952] [New LWP 9022] [New LWP 9117] [New LWP 9113] [New LWP 9042] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/bin/plasmashell'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 [Current thread is 1 (Thread 0x7f9426dff700 (LWP 9151))] [Current thread is 1 (Thread 0x7f9426dff700 (LWP 9151))] Thread 13 (Thread 0x7f9465059700 (LWP 9042)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x561354e3d71c) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x561354e3d6c8, cond=0x561354e3d6f0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x561354e3d6f0, mutex=0x561354e3d6c8) at pthread_cond_wait.c:638 #3 0x7f9466755e6b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f9466755a6b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f946b79d609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f946c45b293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7f94467c0700 (LWP 9113)): #0 0x7f946c44eaff in __GI___poll (fds=0x7f9438018210, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f946ad6b36e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f946ad6b4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f946ca1cb22 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f946c9c0dcb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f946c7dabb2 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f946e3643ba in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f946c7dbd4c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f946b79d609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f946c45b293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7f943e28b700 (LWP 9117)): #0 0x7f946c44eaff in __GI___poll (fds=0x7f942c006550, nfds=1, timeout=3498563) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f946ad6b36e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f946ad6b4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f946ca1cb22 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f946c9c0dcb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f946c7dabb2 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f943e78207c in KCupsConnection::run() () from /lib/x86_64-linux-gnu/libkcupslib.so #7 0x7f946c7dbd4c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f946b79d609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f946c45b293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7f9467b59700 (LWP 9022)): #0 0x7f946c44eaff in __GI___poll (fds=0x7f9460005240, nfds=3, timeout=7611) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f946ad6b36e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f946ad6b4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f946ca1cb22 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f946c9c0dcb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f946c7dabb2 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6
[kwin] [Bug 437893] rendering problem on vulkan full-screen applications
https://bugs.kde.org/show_bug.cgi?id=437893 Zamundaaa changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/kwin/commit/19f92d731aca ||686b1365db9b032f5ca961f5be2 ||6 Resolution|--- |FIXED Version Fixed In||5.22.1 Status|ASSIGNED|RESOLVED --- Comment #11 from Zamundaaa --- Great! -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 435361] Graphical glitches (flashing) under wayland in kate
https://bugs.kde.org/show_bug.cgi?id=435361 David Edmundson changed: What|Removed |Added Assignee|kwin-bugs-n...@kde.org |kwrite-bugs-n...@kde.org Component|wayland-generic |general Version|5.21.3 |unspecified Product|kwin|kate Keywords||wayland --- Comment #11 from David Edmundson --- >This looks like a client buffer or damage related issue in kate or qtwayland. Does to me too, moving. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425250] Computer freezes Randomly
https://bugs.kde.org/show_bug.cgi?id=425250 David Edmundson changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REOPENED|NEEDSINFO --- Comment #8 from David Edmundson --- This does not have all the info requested -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427880] Font too small after installing Nvidia driver
https://bugs.kde.org/show_bug.cgi?id=427880 David Edmundson changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #14 from David Edmundson --- This is most definitely not a kwin bug, but I'll leave here till we can move it. Please include output of : xrdb -q |& grep -i dpi ~/.config/kdeglobals xrandr -q -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427880] Font too small after installing Nvidia driver
https://bugs.kde.org/show_bug.cgi?id=427880 David Edmundson changed: What|Removed |Added CC|aplatt...@nvidia.com, |k...@davidedmundson.co.uk |ekurzin...@nvidia.com | Severity|critical|normal --- Comment #13 from David Edmundson --- Please only tag the Nvidia devs after investigation proves them to be at fault. We don't want to abuse their time. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425250] Computer freezes Randomly
https://bugs.kde.org/show_bug.cgi?id=425250 David Edmundson changed: What|Removed |Added Severity|critical|normal -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 438447] Latte Dock Crashes on Startup
https://bugs.kde.org/show_bug.cgi?id=438447 --- Comment #4 from abhiroop.san...@gmail.com --- The crash happens because of the widgets in edna layout (https://store.kde.org/p/1417204/) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 438509] Segfault in open window when opening a new window
https://bugs.kde.org/show_bug.cgi?id=438509 --- Comment #6 from Christoph Cullmann --- Can you start kate inside gdb and attach then the backtrace you get with "bt" after the crash? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 426939] Kate sometimes crashes when showing previously-hidden menu bar
https://bugs.kde.org/show_bug.cgi?id=426939 Christoph Cullmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/util ||ities/kate/commit/3a5cd5698 ||1f76138fa80f6ecffede2abcfda ||b766 --- Comment #1 from Christoph Cullmann --- Git commit 3a5cd56981f76138fa80f6ecffede2abcfdab766 by Christoph Cullmann. Committed on 12/06/2021 at 21:33. Pushed by cullmann into branch 'master'. ensure to not crash on missing context menu contextMenu() is allowed to return a nullptr check for this to avoid crash on menubar hide/show see backtrace in related bug, nullptr as menu M +6-16 kate/katemainwindow.cpp M +0-3kate/katemainwindow.h M +6-12 kwrite/kwrite.cpp M +0-3kwrite/kwrite.h https://invent.kde.org/utilities/kate/commit/3a5cd56981f76138fa80f6ecffede2abcfdab766 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 438509] Segfault in open window when opening a new window
https://bugs.kde.org/show_bug.cgi?id=438509 --- Comment #5 from Tcll --- well, it's not libX11 just had a friend copy their libX11.so.6.3.0 and when I ran kate with that, the same segfault happened so now I'm starting to think something's not installed that libX11 needs that I don't have installed... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437406] drag-and-drop between Wayland and Xwayland apps fails
https://bugs.kde.org/show_bug.cgi?id=437406 --- Comment #13 from David Edmundson --- I said it fixes what was mentioned in the comment above, not the whole bug. I think there are still some issues left. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438521] Move the icon and label from the center of the thumbnail
https://bugs.kde.org/show_bug.cgi?id=438521 --- Comment #3 from popov895 --- Seriously? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 432325] kate scrollbar doesn't take into account line length
https://bugs.kde.org/show_bug.cgi?id=432325 Christoph Cullmann changed: What|Removed |Added CC||cullm...@kde.org Severity|normal |wishlist --- Comment #2 from Christoph Cullmann --- Yes, that is by design. One can keep this as some wish to alter this behavior, but this is unlikely to happen. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437455] Plasma crashed on Wayland in QWaylandClientExtensionPrivate::handleRegistryGlobal() when enabling blur effect in Desktop Effects KCM
https://bugs.kde.org/show_bug.cgi?id=437455 David Edmundson changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437455] Plasma crashed on Wayland in QWaylandClientExtensionPrivate::handleRegistryGlobal() when enabling blur effect in Desktop Effects KCM
https://bugs.kde.org/show_bug.cgi?id=437455 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #11 from David Edmundson --- > Re-opening. Re-closing. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438521] Move the icon and label from the center of the thumbnail
https://bugs.kde.org/show_bug.cgi?id=438521 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL CC||k...@davidedmundson.co.uk -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 418552] Random crashes on ppc64
https://bugs.kde.org/show_bug.cgi?id=418552 --- Comment #7 from Peter Piwowarski --- I should be able to set up another ppc64 system soon, I'll see what I can find out at that time. On Sat, Jun 12, 2021, 2:39 PM Christoph Cullmann wrote: > https://bugs.kde.org/show_bug.cgi?id=418552 > > Christoph Cullmann changed: > >What|Removed |Added > > > Status|REPORTED|NEEDSINFO > Resolution|--- |WAITINGFORINFO > CC||cullm...@kde.org > > --- Comment #6 from Christoph Cullmann --- > I looked a bit at the below backtrace again. > I see no real Kate specific parts. > If you can reproduce that with e.g. some recent released 21.04.x version, > please re-open. > Thanks! > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 419018] dolphin lags when there is a lot of mounted directory
https://bugs.kde.org/show_bug.cgi?id=419018 Ahmad Samir changed: What|Removed |Added CC||a.samir...@gmail.com --- Comment #4 from Ahmad Samir --- If you disable auto-completion in dolphin (right click in the location bar and from the menu select "text completion" -> none), does the location bar work as expected? The memory consumption issues, might be related to bug 398908, could you test again with KIO 5.83? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437893] rendering problem on vulkan full-screen applications
https://bugs.kde.org/show_bug.cgi?id=437893 --- Comment #10 from r.kunsc...@googlemail.com --- I meant in the git master. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 398908] MimeTypeFinderJob can use huge amounts of memory reading unnecessary data
https://bugs.kde.org/show_bug.cgi?id=398908 Ahmad Samir changed: What|Removed |Added CC||unkn...@skynet.be --- Comment #92 from Ahmad Samir --- *** Bug 427168 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 427168] Memory leak
https://bugs.kde.org/show_bug.cgi?id=427168 Ahmad Samir changed: What|Removed |Added CC||a.samir...@gmail.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Ahmad Samir --- Might be a duplicate of bug 398908; closing as such; feel free to reopen if you still see the same issue with KDE Frameworks 5.83 (which has been released today). *** This bug has been marked as a duplicate of bug 398908 *** -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 433173] KRunner does not remember history, the drop-down menu is non-functional
https://bugs.kde.org/show_bug.cgi?id=433173 --- Comment #37 from Knut Hildebrandt --- Here everything is fine. I recently upgraded to 21.04.1 and running Manjaro which comes with it's own theme. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438150] Port away from QWindow::requestActivate()
https://bugs.kde.org/show_bug.cgi?id=438150 --- Comment #2 from Ladislav Nesnera --- Done - https://invent.kde.org/plasma/plasma-phone-components/-/issues/95 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 426488] Large fonts incurs cursor movement lag
https://bugs.kde.org/show_bug.cgi?id=426488 --- Comment #7 from Björn Lindqvist --- (In reply to Christoph Cullmann from comment #6) > Sorry, if this really is an issue for you, you can try to report this > upstream to Qt, but in KTextEditor/Kate/... we can't improve the speed of > the text rendering operations. > > Or you might try the advice given below to use a smaller resolution. I wouldn't have reported it unless it was an issue for me so you didn't have to add the "really" qualifier. The suggested workarounds doesn't work as they make the whole screen blurry. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 398908] MimeTypeFinderJob can use huge amounts of memory reading unnecessary data
https://bugs.kde.org/show_bug.cgi?id=398908 --- Comment #91 from Paul --- *** Bug 436505 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436505] Opening large file through dolphin causes large increase in dolphin memory use
https://bugs.kde.org/show_bug.cgi?id=436505 Paul changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Paul --- *** This bug has been marked as a duplicate of bug 398908 *** -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 438516] Partition manager crashes after I selecek a removable USB device
https://bugs.kde.org/show_bug.cgi?id=438516 Andrius Štikonas changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Andrius Štikonas --- This is fixed in newer versions. And you shouldn't use version 4.1.0 because it has CVE reported against it: https://kde.org/info/security/advisory-20201017-1.txt *** This bug has been marked as a duplicate of bug 413418 *** -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 413418] KDE Partition Manager crashes when opening partition information on USB drive
https://bugs.kde.org/show_bug.cgi?id=413418 Andrius Štikonas changed: What|Removed |Added CC||cme...@pm.me --- Comment #28 from Andrius Štikonas --- *** Bug 438516 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412655] Tabbox uses wrong visualization when switching between Main and Alternative while holding a common Alt
https://bugs.kde.org/show_bug.cgi?id=412655 --- Comment #3 from andydecle...@gmail.com --- I've made a good demonstration video @ https://user-images.githubusercontent.com/1787385/121787725-de97fb80-cb95-11eb-914d-e219801fe8df.mp4 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 438522] New: App menu username text is black, should be white.
https://bugs.kde.org/show_bug.cgi?id=438522 Bug ID: 438522 Summary: App menu username text is black, should be white. Product: Breeze Version: 5.21.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: derocar...@bbsaili.com Target Milestone: --- Created attachment 139267 --> https://bugs.kde.org/attachment.cgi?id=139267=edit Result SUMMARY App menu username text is black, should be white. STEPS TO REPRODUCE Unknown could be after previewing various display and visual/layout options. OBSERVED RESULT See picture EXPECTED RESULT text should be white SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.12.8-1-MANJARO OS Type: 64-bit Graphics Platform: X11 Processors: 4 × Intel® Core™ i7-6600U CPU @ 2.60GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 520 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 438509] Segfault in open window when opening a new window
https://bugs.kde.org/show_bug.cgi?id=438509 --- Comment #4 from Tcll --- I won't deny it could be a Void Linux issue, since my old Void machine runs Blender 2.8+ at 1.5FPS, where this one runs it just fine (updated) and it seems like it specifically has to do with libX11... which funny enough is something I'm RE-ing the protocol of for a project of my own that manages /tmp/.X11-unix/X0 directly as a bi-directional named pipe for performance and compatibility reasons. but unfortunately, I wouldn't know how to tell you what functions or such specifically seem to be missing from my specific patch to where it could potentially be worked around as an exception... my experience with C is rather lacking due to there not being a decent FOSS IDE for it... (CLion is quite a big load to cover) ;) ... I could probably patch it manually, and then deal with any XBPS issues later if I can find a decent download >.> (no internet on the target machine) -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 433173] KRunner does not remember history, the drop-down menu is non-functional
https://bugs.kde.org/show_bug.cgi?id=433173
kakadu.hafan...@gmail.com changed:
What|Removed |Added
CC||kakadu.hafan...@gmail.com
--- Comment #36 from kakadu.hafan...@gmail.com ---
(In reply to Riccardo Robecchi from comment #24)
> Created attachment 136816 [details]
> RunCommand.qml
>
> (In reply to Alexander Lohnau from comment #19)
> > There we have it!
> >
> > Do you have a custom theme or sth. like that? In KRunner new API was added
> > and a property was added in QML to expose this. But it seems like that is
> > not found.
> >
> > Could you please provide the contend of
> > /usr/share/plasma/look-and-feel/org.kde.breath2.desktop/contents/runcommand/
> > RunCommand.qml and
> > /home/user/kde/usr/lib/x86_64-linux-gnu/qml/org/kde/milou/ResultsView.qml
> >
> > Also the version info provided from
> > >apt show milou
> > would be useful.
>
> I am using a custom theme on KDE Neon and this is the output when opening
> KRunner from the terminal:
> riccardo@Sleipnir ~ $ killall -9 krunner && krunner
> qt.svg: :377:374: Could not add child element to parent element
> because the types are incorrect.
> qt.svg: :378:126: Could not add child element to parent element
> because the types are incorrect.
> qt.svg: :379:126: Could not add child element to parent element
> because the types are incorrect.
> qt.svg: :379:385: Could not add child element to parent element
> because the types are incorrect.
> qt.svg: :380:125: Could not add child element to parent element
> because the types are incorrect.
> qt.svg: :381:124: Could not add child element to parent element
> because the types are incorrect.
> qt.svg: :382:125: Could not add child element to parent element
> because the types are incorrect.
> qt.svg: :383:125: Could not add child element to parent element
> because the types are incorrect.
> qt.svg: :384:125: Could not add child element to parent element
> because the types are incorrect.
> qt.svg: :384:371: Could not add child element to parent element
> because the types are incorrect.
> qt.svg: :384:619: Could not add child element to parent element
> because the types are incorrect.
> file:///home/riccardo/.local/share/plasma/look-and-feel/Adagio/contents/
> runcommand/RunCommand.qml:39:5: QML Connections: Implicitly defined onFoo
> properties in Connections are deprecated. Use this syntax instead: function
> onFoo() { ... }
> file:///home/riccardo/.local/share/plasma/look-and-feel/Adagio/contents/
> runcommand/RunCommand.qml:228: TypeError: Cannot call method 'slice' of
> undefined
>
> So it looks like the last two lines are where the problem is. I uploaded the
> file in question.
> Switching to another look & feel theme restores functionality (I chose
> Breeze Twilight, but I imagine any default theme would work just fine).
> While Knut is on Manjaro, I am on Neon.
I upgraded toady a few packages on Ubuntu hirsuite and the issue about krunner
+ `qt.svg: :409:130: Could not add child element to parent element
because the types are incorrect.` appeared.
➜ ~ cat /var/log/dpkg.log | grep "\ install\ "
2021-06-12 11:38:51 install libcurl3-gnutls:i386 7.74.0-1ubuntu2
2021-06-12 11:39:15 install libtbb2:i386 2020.3-1
2021-06-12 18:15:27 install dyalog-unicode-180:amd64 18.0.39712
2021-06-12 18:29:34 install qtbase5-dev:amd64 5.15.2+dfsg-5
2021-06-12 18:29:44 install libqt5gui5:amd64 5.14.2+dfsg-6 5.15.2+dfsg-5
2021-06-12 18:29:44 install libqt5opengl5:amd64 5.15.2+dfsg-5
2021-06-12 18:29:45 install libqt5opengl5-dev:amd64 5.15.2+dfsg-5
2021-06-12 18:29:45 install virtualbox-qt:amd64 6.1.16-dfsg-6~ubuntu1.20.10.1
6.1.18-dfsg-5
I observed it another machine too, but not on this one. It seems that some of
the packages I installed today introduce the issue.
Riccardo, did you manage to workaround it?
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-ktexteditor] [Bug 426488] Large fonts incurs cursor movement lag
https://bugs.kde.org/show_bug.cgi?id=426488 Christoph Cullmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #6 from Christoph Cullmann --- Sorry, if this really is an issue for you, you can try to report this upstream to Qt, but in KTextEditor/Kate/... we can't improve the speed of the text rendering operations. Or you might try the advice given below to use a smaller resolution. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 430049] session memory leak
https://bugs.kde.org/show_bug.cgi?id=430049 --- Comment #2 from Marcos Dione --- In fact no, I deleted the session and created a new one. So I think we can close this one. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438521] Move the icon and label from the center of the thumbnail
https://bugs.kde.org/show_bug.cgi?id=438521 --- Comment #2 from popov895 --- Created attachment 139266 --> https://bugs.kde.org/attachment.cgi?id=139266=edit Windows 10 Task View -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438521] Move the icon and label from the center of the thumbnail
https://bugs.kde.org/show_bug.cgi?id=438521 popov895 changed: What|Removed |Added CC||popov...@ukr.net -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438521] Move the icon and label from the center of the thumbnail
https://bugs.kde.org/show_bug.cgi?id=438521 --- Comment #1 from popov895 --- Created attachment 139265 --> https://bugs.kde.org/attachment.cgi?id=139265=edit GNOME Activities Overview -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438521] New: Move the icon and label from the center of the thumbnail
https://bugs.kde.org/show_bug.cgi?id=438521 Bug ID: 438521 Summary: Move the icon and label from the center of the thumbnail Product: kwin Version: 5.22.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-present-windows Assignee: kwin-bugs-n...@kde.org Reporter: popov...@ukr.net Target Milestone: --- Created attachment 139264 --> https://bugs.kde.org/attachment.cgi?id=139264=edit Present Windows SUMMARY After upgrading to Plasma 5.22, the icon and label are now displayed in the center of the thumbnail, which is illogical since they overlap the contents of the thumbnail and make it difficult to find the desired window. Please, see the attached image. Ideally, the icon and label should be displayed near the thumbnail, but not in it. As a last resort, they should be displayed at the edge of the thumbnail (for example, at the bottom or in the lower right corner), but not in the center. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210610 KDE Plasma Version: 5.22.0 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 357062] Dead keys do not work correctly in vi input mode
https://bugs.kde.org/show_bug.cgi?id=357062 --- Comment #4 from Christoph Cullmann --- *** Bug 396376 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 396376] while vi-mode is active, third keyboard level is not available in the command-line
https://bugs.kde.org/show_bug.cgi?id=396376 Christoph Cullmann changed: What|Removed |Added Resolution|--- |DUPLICATE CC||cullm...@kde.org Status|REPORTED|RESOLVED --- Comment #2 from Christoph Cullmann --- *** This bug has been marked as a duplicate of bug 357062 *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 332935] jump to mark doesn't work with dead keys keyboard
https://bugs.kde.org/show_bug.cgi?id=332935 Christoph Cullmann changed: What|Removed |Added CC||cullm...@kde.org Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #10 from Christoph Cullmann --- *** This bug has been marked as a duplicate of bug 357062 *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 357062] Dead keys do not work correctly in vi input mode
https://bugs.kde.org/show_bug.cgi?id=357062 Christoph Cullmann changed: What|Removed |Added CC||thiago.bauermann@kolabnow.c ||om --- Comment #3 from Christoph Cullmann --- *** Bug 332935 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 438520] New: Okular sometimes needs two attempts to get to the next bookmark
https://bugs.kde.org/show_bug.cgi?id=438520 Bug ID: 438520 Summary: Okular sometimes needs two attempts to get to the next bookmark Product: okular Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: tofailihas...@gmail.com Target Milestone: --- SUMMARY Okular allows the user to create multiple bookmarks in a PDF file by right-clicking then clicking `add Bookmark` from the menu. The user can navigate between bookmarks by right-clicking and choosing `Next Bookmark` or `Previous Bookmark` from the menu. However, with some bookmarks clicking `Next Bookmark` doesn't do anything, and I'll need to right-click then click it again for Okular to move to the next bookmark. STEPS TO REPRODUCE 1. Create multiple bookmarks in a PDF file 2. Cycle between bookmarks using right-click and `Previous/Next Bookmark`. OBSERVED RESULT Sometimes two attempts are needed to get to the next bookmark. EXPECTED RESULT One attempt would work. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE (available in About System) KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I had thought at first that I could be dragging the PDF a little with the mouse, causing the view to move by a tiny amount from the bookmark, then `Next Bookmark` would appear not to do anything because it only reverses the tiny deviation from the bookmark. However, the problem seems to appear consistently with certain bookmarks and not others, so I do not think this is the problem. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 438519] New: keep "OK" button of window to create a file with pasted contents greyed out until the user starts to type a file name
https://bugs.kde.org/show_bug.cgi?id=438519 Bug ID: 438519 Summary: keep "OK" button of window to create a file with pasted contents greyed out until the user starts to type a file name Product: dolphin Version: 21.04.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: bugsefor...@gmx.com CC: kfm-de...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. copy text 2. open Dolphin 3. press ctrl+v OBSERVED RESULT A window to create a file with pasted contents shows up. "OK" button is active despite file name field is empty, "File already exists" dialog appears when I click on it. EXPECTED RESULT keep "OK" greyed out until th user starts to type a file name. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: Plasma 5.22 KDE Frameworks Version: 5.82 Qt Version: Qt 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 436616] Kate 21.04.0 doesn't show Icons on Ubuntu 21.04
https://bugs.kde.org/show_bug.cgi?id=436616 Christoph Cullmann changed: What|Removed |Added Assignee|kwrite-bugs-n...@kde.org|neon-b...@kde.org Version|21.04.0 |unspecified Component|application |Snaps Product|kate|neon -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 438518] New: Adaptive automatic Y data range as separate option
https://bugs.kde.org/show_bug.cgi?id=438518 Bug ID: 438518 Summary: Adaptive automatic Y data range as separate option Product: plasma-systemmonitor Version: 5.22.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: watisthis...@outlook.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 139263 --> https://bugs.kde.org/attachment.cgi?id=139263=edit weird systemp and cpufan charts Would be nice to have the automatic adaptive range (like in the network line chart on History page or old ksysguard) as a third user-selectable option, in addition to the now-default automatic fixed range from a sensor and manual fixed range. -Some sensors seem to have the limits missing or incorrect and probably not all can be easily fixed. That results in some weird-looking graphs that require user action to be corrected. (Maybe automatic adaptation/range adjustment could be done when an actual value doesn't fit into the sensor limits, though that doesn't help if the limit is too large.) -User can then of course set a fixed manual range, but for that they need to know the maximum. Eg. I can't remember what's the max speed of my CPU fan without finding and googling its model number. Would be easier to just enable the adaptive range than guessing/googling. -I was quite okay with the adaptive range in ksysguard for sensors that usually vary within a smallish range compared to the total possible range. It kind of "zooms in" a bit. The extra 'empty space' on top isn't always necessary in my opinion. I might prefer adaptive range when it's more important to know how the value changes in relation to itself than what percentage it is of the absolute maximum. Might be also cool to have the manual fixed range with options for auto adaptation if value over/undershoots it; to zoom at a specific value range when possible. --- Just as an example of some buggy predefined min values, below is an excerpt from 'sensors' command, and a corresponding System Monitor screenshot is attached too. temp1 (SYS Temp) somehow has high value of 2C, so that overshoots a bit... fan2 (CPU Fan) chart doesn't really work. If I've understood right the fan min value is rather related to the monitoring chip resolution than the actual rpm that depends on the fan itself. Should fans be on adaptive scale by default? w83627dhg-isa-0a10 Adapter: ISA adapter Vcore: 1.40 V (min = +0.00 V, max = +1.74 V) in1: 1.82 V (min = +0.00 V, max = +0.07 V) ALARM AVCC: 3.25 V (min = +2.98 V, max = +3.63 V) +3.3V: 3.25 V (min = +2.98 V, max = +3.63 V) in4: 1.10 V (min = +1.02 V, max = +0.00 V) ALARM in5: 880.00 mV (min = +0.02 V, max = +0.00 V) ALARM in6: 1.56 V (min = +1.02 V, max = +0.00 V) ALARM 3VSB: 3.25 V (min = +2.98 V, max = +3.63 V) Vbat: 3.20 V (min = +2.70 V, max = +3.63 V) fan1: 0 RPM (min = 659 RPM, div = 128) ALARM fan2: 847 RPM (min = 21093 RPM, div = 8) ALARM fan3: 0 RPM (min = 1318 RPM, div = 128) ALARM fan4:4687 RPM (min = 168750 RPM, div = 8) ALARM fan5: 0 RPM (min = 10546 RPM, div = 128) ALARM temp1:+43.0°C (high = +2.0°C, hyst = +0.0°C) ALARM sensor = thermistor temp2:+29.0°C (high = +80.0°C, hyst = +75.0°C) sensor = CPU diode temp3:+63.0°C (high = +117.0°C, hyst = +117.0°C) sensor = thermistor cpu0_vid:+0.000 V intrusion0: ALARM -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438325] Adaptive transparency not working on wayland
https://bugs.kde.org/show_bug.cgi?id=438325 --- Comment #3 from Prasad Murthy --- The above said bug is present in X11 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 386825] unknown service type warnings for katepart.json
https://bugs.kde.org/show_bug.cgi?id=386825 Christoph Cullmann changed: What|Removed |Added Product|frameworks-ktexteditor |frameworks-kcoreaddons Component|general |general Assignee|kwrite-bugs-n...@kde.org|mp...@kde.org CC||cullm...@kde.org, ||kdelibs-b...@kde.org --- Comment #1 from Christoph Cullmann --- I have no real idea how to fix this. I think it is emitted by the desktop => json converter. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438325] Adaptive transparency not working on wayland
https://bugs.kde.org/show_bug.cgi?id=438325 Prasad Murthy changed: What|Removed |Added CC||phoenix_fire...@yahoo.com --- Comment #2 from Prasad Murthy --- Adaptive transparency for taskbar doesn't work when the compositor backend is OpenGL 2.0 or OpenGL 3.1. It works when the compositor backend is XRender. Application dashboard shows blur effect when using OpenGL backend but that doesn't work when using XRender backend. libopengl version is 1.3.2 Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.0 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.3 Kernel Version: 5.4.0-74-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-7400 CPU @ 3.00GHz Memory: 30.3 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 382405] vertical scrollbar occasionally not rendering properly
https://bugs.kde.org/show_bug.cgi?id=382405 Christoph Cullmann changed: What|Removed |Added CC||cullm...@kde.org Resolution|--- |WAITINGFORINFO Status|CONFIRMED |NEEDSINFO --- Comment #12 from Christoph Cullmann --- I could not reproduce this in a long time and have this always enabled. If one finds a way to reproduce this with recent versions, please provide some hints and reopen, thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420977] Double click on the window's menu icon does not close with Plastik theme
https://bugs.kde.org/show_bug.cgi?id=420977 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #5 from Patrick Silva --- Can reproduce with Arc theme from KDE Store and Plastik. Arch Linux, Plasma 5.22. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 415231] When code indexing is disabled, Kate's Project plugin has misleading error (points to kateproject, not config dialog)
https://bugs.kde.org/show_bug.cgi?id=415231 Christoph Cullmann changed: What|Removed |Added Version Fixed In||21.04.0 CC||cullm...@kde.org Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #5 from Christoph Cullmann --- In 21.04 this is fixed and you have there directly some button to enable indexing. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 418552] Random crashes on ppc64
https://bugs.kde.org/show_bug.cgi?id=418552 Christoph Cullmann changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||cullm...@kde.org --- Comment #6 from Christoph Cullmann --- I looked a bit at the below backtrace again. I see no real Kate specific parts. If you can reproduce that with e.g. some recent released 21.04.x version, please re-open. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438517] New: Plasma crash when change the screen layout (wayland)
https://bugs.kde.org/show_bug.cgi?id=438517 Bug ID: 438517 Summary: Plasma crash when change the screen layout (wayland) Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: bait...@mailfence.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY My notebook is connected with an external monitor. Plasma crash when change the screen layout. STEPS TO REPRODUCE 1. Add Widget -> Add "Display Configuration" 2. open "Display configuration" widget and select "Switch to Laptop screen" or "Switch to external screen" OBSERVED RESULT Plasma crash EXPECTED RESULT screen layout change without plasma crash SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.22.80 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.4.0-73-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-4200U CPU @ 1.60GHz Memory: 9,6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4400 ADDITIONAL INFORMATION Same bug in Kubuntu impish beta Application: Plasma (plasmashell), signal: Aborted [New LWP 11595] [New LWP 11607] [New LWP 11608] [New LWP 11609] [New LWP 11610] [New LWP 11643] [New LWP 11673] [New LWP 11674] [New LWP 11681] [New LWP 11687] [New LWP 11701] [New LWP 11702] [New LWP 11737] [New LWP 11738] [New LWP 11739] [New LWP 11740] [New LWP 11741] [New LWP 11742] [New LWP 11743] [New LWP 11744] [New LWP 11804] [New LWP 11806] [New LWP 11918] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f11a88bbaff in __GI___poll (fds=0x7ffcb4a0e9b8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f11a4ba2ec0 (LWP 11517))] Thread 24 (Thread 0x7f110faff700 (LWP 11918)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x56338ff6cf90) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x56338ff6cf40, cond=0x56338ff6cf68) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x56338ff6cf68, mutex=0x56338ff6cf40) at pthread_cond_wait.c:638 #3 0x7f11a8c4ed5b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f11aa894814 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f11aa894c89 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f11a8c48bec in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f11a7c0d609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f11a88c8293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 23 (Thread 0x7f116c8e2700 (LWP 11806)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x563389255114) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5633892550c0, cond=0x5633892550e8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5633892550e8, mutex=0x5633892550c0) at pthread_cond_wait.c:638 #3 0x7f11a8c4ed5b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f11aa894814 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f11aa894c89 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f11a8c48bec in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f11a7c0d609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f11a88c8293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 22 (Thread 0x7f111cd95700 (LWP 11804)): #0 0x7f11a88c85ce in epoll_wait (epfd=64, events=0x7f111cd948f0, maxevents=32, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30 #1 0x7f1180e66acb in ?? () from /usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-support.so #2 0x7f1180e594a4 in ?? () from /usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-support.so #3 0x7f1180eabe70 in ?? () from /lib/x86_64-linux-gnu/libpipewire-0.3.so.0 #4 0x7f11a7c0d609 in start_thread (arg=) at pthread_create.c:477 #5 0x7f11a88c8293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 21 (Thread 0x7f111d7fa700 (LWP 11744)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5633821443a4) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x563382144350, cond=0x563382144378) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x563382144378, mutex=0x563382144350) at pthread_cond_wait.c:638 #3 0x7f11a8c4ed5b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f1180afef40 in
[kate] [Bug 438509] Segfault in open window when opening a new window
https://bugs.kde.org/show_bug.cgi?id=438509 Christoph Cullmann changed: What|Removed |Added CC||cullm...@kde.org --- Comment #3 from Christoph Cullmann --- Hmm, unfortunately this output is not very helpful, but shows that it indeed does crash. Could this be an issue with the packaged version on Void Linux? -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 438095] Kate crashes trying to save text file
https://bugs.kde.org/show_bug.cgi?id=438095 Christoph Cullmann changed: What|Removed |Added Component|general |Thumbnails and previews Product|kate|kio-extras Assignee|kwrite-bugs-n...@kde.org|plasma-b...@kde.org CC||cullm...@kde.org --- Comment #3 from Christoph Cullmann --- Looks for me like some issue in the thumbnail io process. -- You are receiving this mail because: You are watching all bug changes.
