[plasmashell] [Bug 453766] New: When using application menu on Wayland the keyboard navigation doesn't work for submenus.
https://bugs.kde.org/show_bug.cgi?id=453766 Bug ID: 453766 Summary: When using application menu on Wayland the keyboard navigation doesn't work for submenus. Product: plasmashell Version: 5.24.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: plasma-b...@kde.org Reporter: milos.radivojevic...@gmail.com Target Milestone: 1.0 SUMMARY When using Application Menu on Wayland the keyboard navigation doesn't work for sub menus. STEPS TO REPRODUCE 1. Press SUPER key to open the Application Menu on Wayland session 2. Press UP on keyboard to go on some submenu category, it opens up on the right 3. Pressing RIGHT on keyboard doesn't focus the submenu like it would on X11, pressing UP and DOWN just continues opening the main menu categories OBSERVED RESULT Submenus don't become active when navigating with keyboard EXPECTED RESULT The focus should move to the submenu and the UP/DOWN presses should scroll inside it, not the parent menu SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453386] Multi/hybrid GPU double copy
https://bugs.kde.org/show_bug.cgi?id=453386 --- Comment #12 from ctj9...@cardkurd.com --- Would double copy be affected by direct scanout? I attempted using Sway and an application running fullscreen with direct scanout would not be affected by performance loss. However, only Weston supports direct scanout with an application that is windowed (not fullscreen). -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 451790] System Monitor Sensor breaks WeatherWidget-2 from the KDE store on KDE Framework 5.92
https://bugs.kde.org/show_bug.cgi?id=451790 Nate Graham changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 411462] On X11, Plasma dialogs (applet popups, OSDs, notifications) should not be movable, maximizable, or minimizable, or tilable
https://bugs.kde.org/show_bug.cgi?id=411462 Nate Graham changed: What|Removed |Added Status|CONFIRMED |ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453188] Krita crashes instantly upon attempting to flatten layers
https://bugs.kde.org/show_bug.cgi?id=453188 --- 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.
[frameworks-kwayland] [Bug 453124] VSCodium consistently crashes Plasmashell with SIGSEGV
https://bugs.kde.org/show_bug.cgi?id=453124 --- Comment #5 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.
[Heaptrack] [Bug 453120] Heaptrack Aaarch64 crashes with dbus assertion
https://bugs.kde.org/show_bug.cgi?id=453120 --- Comment #4 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.
[kwin] [Bug 445454] programs usually open on a different screen
https://bugs.kde.org/show_bug.cgi?id=445454 --- Comment #9 from David Chmelik --- Created attachment 148819 --> https://bugs.kde.org/attachment.cgi?id=148819=edit screenshot screenshot -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445454] programs usually open on a different screen
https://bugs.kde.org/show_bug.cgi?id=445454 --- Comment #8 from David Chmelik --- Perhaps I should use forum more(?) because this is probably working but settings weren't updated (Slackware doesn't make their own default settings but this isn't new KDE installation)... you partly-described two areas of this screen (named differently than you said) so I'm showing you what I have. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445454] programs usually open on a different screen
https://bugs.kde.org/show_bug.cgi?id=445454 --- Comment #7 from David Chmelik --- Created attachment 148818 --> https://bugs.kde.org/attachment.cgi?id=148818=edit screenshot screenshot -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 453534] kcalc process always takes nearly 100% of a CPU thread when it's running
https://bugs.kde.org/show_bug.cgi?id=453534 david.p.war...@gmail.com changed: What|Removed |Added CC||david.p.war...@gmail.com --- Comment #1 from david.p.war...@gmail.com --- I'm seeing this with 22.04.1 (environment: Fedora 36, KDE Plasma 5.24.5, KDE Frameworks 5.93.0, Qt 5.15.3, Kernel 5.17.6, X11). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 453765] New: Not using set cursor theme and not displaying the one selected.
https://bugs.kde.org/show_bug.cgi?id=453765 Bug ID: 453765 Summary: Not using set cursor theme and not displaying the one selected. Product: systemsettings Version: 5.24.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_cursortheme Assignee: plasma-b...@kde.org Reporter: chicobello1...@gmail.com Target Milestone: --- SUMMARY *** Not using the cursor theme you manually set on x11, but on wayland it works. and doesnt show the ones you have installed. *** STEPS TO REPRODUCE 1. Just install a cursor theme and change ir OBSERVED RESULT Defaults to default kde cursor theme EXPECTED RESULT Use the one you selected -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 453764] Plasma doesn't ask confirmation to delete a note when using its contextual menu "Delete" option
https://bugs.kde.org/show_bug.cgi?id=453764 --- Comment #1 from zocsfxljsgpmiua...@protonmail.com --- Sorry, I was referring to the Trash button icon on the bottom of the note on my first comment, but that one actually asks for confirmation. The one who doesn't is on the contextual menu. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 453764] Plasma doesn't ask confirmation to delete a note when using its contextual menu "Delete" option
https://bugs.kde.org/show_bug.cgi?id=453764 zocsfxljsgpmiua...@protonmail.com changed: What|Removed |Added Summary|Plasma doesn't ask |Plasma doesn't ask |confirmation to delete a|confirmation to delete a |note when using its "trash" |note when using its |button |contextual menu "Delete" ||option -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 453764] New: Plasma doesn't ask confirmation to delete a note when using its "trash" button
https://bugs.kde.org/show_bug.cgi?id=453764 Bug ID: 453764 Summary: Plasma doesn't ask confirmation to delete a note when using its "trash" button Product: kdeplasma-addons Version: 5.24.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: notes Assignee: plasma-b...@kde.org Reporter: zocsfxljsgpmiua...@protonmail.com Target Milestone: --- SUMMARY This behavior is different that the one of the other methods to delete a widget. I think this is actually the only widget with a embedded delete button so maybe that's why? ADDITIONAL INFORMATION I actually lost a (pretty large) note by clicking the trash button by accident, fortunately the actual files where the notes are saved are not deleted when its widget is, so I managed to recovered it. Maybe this risk makes the bug a bit more important to fix? :) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 453748] Single-instance app that's already running is not raised when activated from global launch shortcut
https://bugs.kde.org/show_bug.cgi?id=453748 Aleix Pol changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Aleix Pol --- - kstart5 should just forward the token. - getting a token for kglobalaccel should work, I'll see if we can make it the least dirty. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 426499] Draggable area not clearly signposted/misleading highlighting
https://bugs.kde.org/show_bug.cgi?id=426499 --- Comment #11 from Andrey --- Thanks for replies. (In reply to Joe Dight from comment #10) > I can't see if the lighter/darker split also exists on hover, when > no selection has been made. > If it does (or is made obvious somehow else) the bug is definitely fixed. No, it doesn't. It wasn't clear from the report so I didn't pay much attention to hover. However, in previous version I cut off the hover highlight: https://invent.kde.org/utilities/ark/-/merge_requests/115#note_447960 It doesn't look in-style with recent selection highlights though as I tend to keep full-row selection. I'll see if similar color split can be implemented for hover highlight too. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 434764] iconv_open causes ld.so v2.28 and later to execute optimised strncmp which confuses memcheck
https://bugs.kde.org/show_bug.cgi?id=434764 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #5 from Mark Wielaard --- commit 947388eb043ea1c44b37df94046e1eee790ad776 (HEAD -> master) Author: Mike Crowe Date: Mon Sep 9 14:16:16 2019 +0100 Intercept strncmp for glibc ld.so v2.28+ In glibc 5aad5f617892e75d91d4c8fb7594ff35b610c042 (first released in v2.28) a call to strncmp was added to dl-load.c:is_dst. This causes valgrind to complain about glibc's highly-optimised strncmp performing sixteen-byte reads on short strings in ld.so. Let's intercept strncmp in ld.so too so we use valgrind's simple version to avoid this problem. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 449857] Lockscreen window does not get focus by default on X11
https://bugs.kde.org/show_bug.cgi?id=449857 Erik changed: What|Removed |Added CC||eeco...@qirx.org --- Comment #57 from Erik --- Others in this thread pointed out the piece of code that is responsible (/usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml:231), which makes a lot of sense: > visible: opacity > 0 > enabled: visible Set visible to true if the it is not transparent. Enable when visible. This seems to be introduced in https://invent.kde.org/plasma/plasma-workspace/-/commit/c4a3a4e5b974fb309a6da61252b2b830d2d90683 with comment: > // changing enabled will toggle if an item can have activeFocus, which > otherwise > //keeps the text cursor blinking even when invisble I however changed `enabled: visible` to `enabled: true` and (as expected) this restored the behavior for me. I do not see any evidence of a blinking cursor. I don't have any understanding of versioning or policy. I am on Kubuntu 20.04 and there are no updates in the Updates tab of Discover. The kinfocenter tells me I am on version 5.18.8 for the KDE Plasma. It would be nice (at least for other people who did not yet find this thread) to update the line, but as I said, I am not sure if the policy allows such a change -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #65 from Natalie Clarius --- I just tried it out with restoring from a manually saved session instead of previous session and I'm getting the same behavior. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 434764] iconv_open causes ld.so v2.28 and later to execute optimised strncmp which confuses memcheck
https://bugs.kde.org/show_bug.cgi?id=434764
Mark Wielaard changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED|CONFIRMED
--- Comment #4 from Mark Wielaard ---
On some systems the default suppression would have caught this.
Specifically this one in glibc-2.X.supp.in:
{
dl-hack4-64bit-addr-1
Memcheck:Addr8
obj:*/lib*/ld-@GLIBC_VERSION@*.so*
obj:*/lib*/ld-@GLIBC_VERSION@*.so*
obj:*/lib*/ld-@GLIBC_VERSION@*.so*
}
But this doesn't match anymore since glibc 2.34 which changed the (in-memory)
paths of the glibc library names.
The paths were updated for some, but not all suppressions, see:
commit a1364805fc74b5690f763033c0c9b43f27613572
Author: Mark Wielaard
Date: Fri Jul 16 15:47:08 2021 -0400
Update helgrind and drd suppression libc and libpthread paths in glibc 2.34
[...]
The same could be done for the glibc-2.X.supp.in file, but hasn't
yet because it looks like most suppressions in that file are obsolete.
Instead of fixing up those suppressions I think it is better to go with Mike's
intercepts.
I tried on arm64, armhf, s390x and ppc64le. None would trigger an issue (and
none had suppressions).
--
You are receiving this mail because:
You are watching all bug changes.
[juk] [Bug 453761] Juk Crash, if application is opened using media from unmounted partition [before mount]
https://bugs.kde.org/show_bug.cgi?id=453761 Charlie Ramirez Animation Studios MX changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=453763 -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 453763] Juk Starts or Shows Volume 0% as a giant Negative Number tending to infinity
https://bugs.kde.org/show_bug.cgi?id=453763 Charlie Ramirez Animation Studios MX changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=453761 -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 453763] Juk Starts or Shows Volume 0% as a giant Negative Number tending to infinity
https://bugs.kde.org/show_bug.cgi?id=453763 --- Comment #1 from Charlie Ramirez Animation Studios MX --- Created attachment 148817 --> https://bugs.kde.org/attachment.cgi?id=148817=edit Screenshot showing volume set to -2 147 483 648 percent in slide Bar the occurrence of the event seems to be somewhat random, since sometimes when changing the song the already adjusted volume value returns to the giant negative -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 450547] Logout doesn't work: Cannot find '.logout' in object /KSMServer at org.kde.ksmserver
https://bugs.kde.org/show_bug.cgi?id=450547 --- Comment #11 from Lyubomir --- Created attachment 148816 --> https://bugs.kde.org/attachment.cgi?id=148816=edit dbus-monitor-pcap.txt -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 450547] Logout doesn't work: Cannot find '.logout' in object /KSMServer at org.kde.ksmserver
https://bugs.kde.org/show_bug.cgi?id=450547 --- Comment #10 from Lyubomir --- Created attachment 148815 --> https://bugs.kde.org/attachment.cgi?id=148815=edit system.pcap -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 450547] Logout doesn't work: Cannot find '.logout' in object /KSMServer at org.kde.ksmserver
https://bugs.kde.org/show_bug.cgi?id=450547 --- Comment #9 from Lyubomir --- Created attachment 148814 --> https://bugs.kde.org/attachment.cgi?id=148814=edit session.pcap -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 450547] Logout doesn't work: Cannot find '.logout' in object /KSMServer at org.kde.ksmserver
https://bugs.kde.org/show_bug.cgi?id=450547 Lyubomir changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REPORTED --- Comment #8 from Lyubomir --- Happened again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display (no wallpaper, can't get a context menu on right-click)
https://bugs.kde.org/show_bug.cgi?id=353975 --- Comment #162 from Nate Graham --- I'm glad to hear the desktop issues are fixed for you! Let's get another bug report for the crash, please. -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 453763] New: Juk Starts or Shows Volume 0% as a giant Negative Number tending to infinity
https://bugs.kde.org/show_bug.cgi?id=453763 Bug ID: 453763 Summary: Juk Starts or Shows Volume 0% as a giant Negative Number tending to infinity Product: juk Version: 21.12.3 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: whee...@kde.org Reporter: todo.ciencia.y.electron...@gmail.com CC: mp...@kde.org Target Milestone: --- Created attachment 148813 --> https://bugs.kde.org/attachment.cgi?id=148813=edit Screenshot showing volume set to -2 147 483 648 percent SUMMARY *** Using the default installation of Debian 11 and default settings. When opening Juk on many occasions the volume is set as a giant negative number that needs to be raised manually with the slider. *** STEPS TO REPRODUCE 1. Open Juk normaly. 2. You should notice that the volume is muted; click or hover over the speaker icon, you will notice that the volume is set to negative (see attached). Sometimes the negative figure will also be displayed both at the bottom of the slider or just on hover 3. Increase the volume by sliding the bar (at the first touch with the click the number will return to zero and it will work normally if you try to increase the volume with the key shortcuts, only the negative number will be reduced, being too large does not produce changes) OBSERVED RESULT I don't know if the volume is usually set by default to 0 and has to be adjusted whenever juk is started, that is part of the problem, although it can be patch-corrected by simply clicking on the slider, the value should not drop to negatives, leaving keyboard shortcuts not working as a result EXPECTED RESULT The volume should remain at a "theoretical" zero or based on the last time it was used?. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Operating System: Debian GNU/Linux KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.17.0-1-amd64 (64-bit) Graphics Platform: X11 Processors: 8 × AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx Memory: 13.6 GiB of RAM Graphics Processor: AMD Radeon Vega 8 Graphics ADDITIONAL INFORMATION It is unknown if the bug could be related to the crash if juk is booted with media from an unmounted drive. https://bugs.kde.org/show_bug.cgi?id=453761 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 453762] Long lines break C code highlighting
https://bugs.kde.org/show_bug.cgi?id=453762 --- Comment #3 from Alexander Wilms --- Created attachment 148812 --> https://bugs.kde.org/attachment.cgi?id=148812=edit Screenshot of the minimal example -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 453762] Long lines break C code highlighting
https://bugs.kde.org/show_bug.cgi?id=453762 --- Comment #2 from Alexander Wilms --- Created attachment 148811 --> https://bugs.kde.org/attachment.cgi?id=148811=edit Minimal example -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 453762] Long lines break C code highlighting
https://bugs.kde.org/show_bug.cgi?id=453762 --- Comment #1 from Alexander Wilms --- Created attachment 148810 --> https://bugs.kde.org/attachment.cgi?id=148810=edit Code after obfuscating it three times -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 453762] New: Long lines break C code highlighting
https://bugs.kde.org/show_bug.cgi?id=453762 Bug ID: 453762 Summary: Long lines break C code highlighting Product: kate Version: 22.04.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: part Assignee: kwrite-bugs-n...@kde.org Reporter: f.alexander.wi...@gmail.com Target Milestone: --- Created attachment 148809 --> https://bugs.kde.org/attachment.cgi?id=148809=edit Initial Code SUMMARY The code highlighting stops working when a file contains lines longer than 5360 characters STEPS TO REPRODUCE 1. Open minimal_example.c in Kate 2. Observe the broken code highlighting or 1. Go to https://picheta.me/obfuscator, select "Generic FizzBuzz" and click "Obfuscate" 2. Copy obfuscated code, paste it into the editor on the left and click "Obfuscate" 3. Copy obfuscated code, paste it into the editor on the left and click "Obfuscate" once more 4. Copy obfuscated code, paste it into Kate and save it as a C file 5. Observe the broken code highlighting OBSERVED RESULT In the first few lines after a newline, the hexadecimal integers are highlighted in yellow, afterwards they are no longer highlighted. EXPECTED RESULT The highlighting should be consistent. After saving and opening the file, the following warning message is shown: "The file generic_fizzbuzz_obfuscated_thrice.c was opened and contained line slonger than the configured Line Length Limit (10,000 characters). The longest of those lines was 10,313 characters long" Clicking on "Temporarily raise limit and reload file" does not fix the highlighting. However, adding a newline somewhere in the sum of hex values results in the highlighting being applied properly after the newline. I know this is a niche case, but maybe the bug report is helpful anyway. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220427 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display (no wallpaper, can't get a context menu on right-click)
https://bugs.kde.org/show_bug.cgi?id=353975 --- Comment #161 from gene c --- Forgot to say (sorry for being obvious) -but the fact that it crashes when being woken up after things go to sleep - suggests that this is perhaps case (i) -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 453761] Juk Crash, if application is opened using media from unmounted partition [before mount]
https://bugs.kde.org/show_bug.cgi?id=453761 --- Comment #1 from Charlie Ramirez Animation Studios MX --- Created attachment 148808 --> https://bugs.kde.org/attachment.cgi?id=148808=edit kde error Handler Screen after crash -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display (no wallpaper, can't get a context menu on right-click)
https://bugs.kde.org/show_bug.cgi?id=353975 --- Comment #160 from gene c --- Since restarting plasmashell always "fixed" the desktop I don't think your test validates that anything is fixed. I suppose there are 2 possibilities: (i) If the crash is a result of the "fix" and now crashes instead then bug is not fixed. (ii) Crash is unrelated, so cannot tell if the bug is fixed or not yet (bad build, new bug, etc). Either way, until it stops crashing we cannot tell which of the 2 is happening. Has anyone else managed to get git master fully built with all deps updated etc and test it? -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 453761] New: Juk Crash, if application is opened using media from unmounted partition [before mount]
https://bugs.kde.org/show_bug.cgi?id=453761 Bug ID: 453761 Summary: Juk Crash, if application is opened using media from unmounted partition [before mount] Product: juk Version: 21.12.3 Platform: Debian testing OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: whee...@kde.org Reporter: todo.ciencia.y.electron...@gmail.com CC: mp...@kde.org Target Milestone: --- Created attachment 148807 --> https://bugs.kde.org/attachment.cgi?id=148807=edit KCrash Handler Generated Backtrace SUMMARY *** Using Juk Defaults in Debian 11 With Testing Repositories. Juk usually opens by default on startup [Function expected correct]. and remains in the background until the user needs it. -If Juke is configured to Read media or use a default music folder from a secondary Drive or unmounted partition, Juk will boot normally but will not show the playlist, If the source drive is mounted while juk is already open , at the time of scanning or pressing the play button the program will close suddenly, launching the error reporting wizard. If Juk is opened again (already with the media drive mounted) it will operate normally. And the playlist visible from the beginning *** -Inverse trace generated by the assistant is attached. But apparently not useful. STEPS TO REPRODUCE 1. Using a default installation of juk on debian 11 start it. 2. Open the Juk folder settings and configure a Media Folder as a single folder located on a secondary disk or Partition that is not mounted by default when booting debian, save changes and scan. [play some music, juk should work fine so far] 3. Reboot or shutdown Debian. (it doesn't matter if Juk is closed or stays in the background). Upon reboot, open an instance of juk [the partition or drive configured as source should not be mounted at this point yet]. 4. With juk open (as is), mount the drive with the media folder and hit the play button or try scanning the folder. [Juk should close and pop up a notification to generate a crash report]. OBSERVED RESULT The report assistant will only tell you that the generated backtrace is useless. or it lacks data to generate a report, or it must be done manually. giving the option to close or restart Juk. If Juk is rebooted (remember the media drive is already mounted now). juke will show the list of songs and work normally EXPECTED RESULT juk should not hang when mounting media and trying to play if media is not mounted before juk starts. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.17.0-1-amd64 (64-bit) Graphics Platform: X11 Processors: 8 × AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx Memory: 13.6 GiB of RAM Graphics Processor: AMD Radeon Vega 8 Graphics ADDITIONAL INFORMATION Probably unrelated, the media partition is on NTFS (Dualboot System -Windows). reason why it is not usually mounted by default on boot. -Inverse trace generated by the assistant is attached. -there is a secondary bug where juk in the same version, starts with the volume at 0% [But displayed as a volume number too large or tending to infinity, which must be manually raised in the frontend to return to zero or desired level and operate normally, I will open a separate Bug for this. ] -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 447900] Scaling Broken on Windows
https://bugs.kde.org/show_bug.cgi?id=447900 chrisjba...@hotmail.com changed: What|Removed |Added CC||chrisjba...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 346937] Toolbox buttons and labels do not scale correctly - unusable for non standard dpi settings
https://bugs.kde.org/show_bug.cgi?id=346937 chrisjba...@hotmail.com changed: What|Removed |Added CC||chrisjba...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[kscd] [Bug 120533] accomodate high DPI, making all display text fit
https://bugs.kde.org/show_bug.cgi?id=120533 chrisjba...@hotmail.com changed: What|Removed |Added CC||chrisjba...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 453121] calender can't connect to nextcloud
https://bugs.kde.org/show_bug.cgi?id=453121 --- Comment #9 from gjditchfi...@acm.org --- (In reply to m.eik michalke from comment #8) > i doubt that's the issue, at least im running with let's encrypt certs. > rather i suspect apache's TLS configuration could be causing this. can > anyone suggest how to best debug this, e.g. getting some informative logs of > the communication with the nextcloud server to get a hint what's going > wrong? the server itself doesn't log any errors; it hardly logged anything, > actually, as if it doesn't even get a request. I think you could use wireshark-qt to spy on the communication. I haven't found any hints about getting Qt to log more detail about the connection; maybe a Qt forum could help. -- You are receiving this mail because: You are watching all bug changes.
[kblocks] [Bug 453736] Game stops at 20k points
https://bugs.kde.org/show_bug.cgi?id=453736 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org --- Comment #1 from Albert Astals Cid --- Do you get a crash dialog? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display (no wallpaper, can't get a context menu on right-click)
https://bugs.kde.org/show_bug.cgi?id=353975 Jacek Wieczorek changed: What|Removed |Added CC||mrj...@gmail.com --- Comment #159 from Jacek Wieczorek --- I've just built and tried the newest Plasma from git. It seems to be consistently crashing on login and whenever my screens go to sleep for a while (doesn't happen when I wake them up relatively quickly). Good thing is that so far, after each crash Plasma has been able to restart and recover without messing up wallpapers and the desktop layout. Does this behavior deserve its own bug report? -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 453121] calender can't connect to nextcloud
https://bugs.kde.org/show_bug.cgi?id=453121 --- Comment #8 from m.eik michalke --- (In reply to gjditchfield from comment #7) > My second wild guess is that Qt and your browser use different > configurations; > Chrome uses a different SSL library, for instance. that would explain why access via browser is possible. > My third is that the Nextcloud CalDAV server is using a really old > certificate that could be > upgraded, but I'm way outside my knowledge. i doubt that's the issue, at least im running with let's encrypt certs. rather i suspect apache's TLS configuration could be causing this. can anyone suggest how to best debug this, e.g. getting some informative logs of the communication with the nextcloud server to get a hint what's going wrong? the server itself doesn't log any errors; it hardly logged anything, actually, as if it doesn't even get a request. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 449166] Dragging items in Dolphin makes them look shaky when using Breeze cursors
https://bugs.kde.org/show_bug.cgi?id=449166 --- Comment #23 from Michael D --- "fliggering" = "flickering" -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 449166] Dragging items in Dolphin makes them look shaky when using Breeze cursors
https://bugs.kde.org/show_bug.cgi?id=449166 --- Comment #22 from Michael D --- Same--the bug disappears using Adwaita cursors. However, I do get other weird fliggering from drag n' drop with non-Breeze cursors: sometimes when I drag a file to a folder (e.g. trash) in Places it causes flickering outside of the window near the Places folder I dragged to. Not always reproducible, but not hard to reproduce. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446753] Enable the Overview effect by default
https://bugs.kde.org/show_bug.cgi?id=446753 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/kwin/commit/9ff137f5cb4c ||d7cc54c2d454f3d28efa60d8aed ||6 Version Fixed In||5.25 Status|CONFIRMED |RESOLVED --- Comment #1 from Nate Graham --- Git commit 9ff137f5cb4cd7cc54c2d454f3d28efa60d8aed6 by Nate Graham. Committed on 13/05/2022 at 19:42. Pushed by ngraham into branch 'master'. effects/overview: enable it by default Overview is quite polished now, enough that we have a default touchpad gesture that opens it by default. It's time to move it out of public beta and enable it by default, and this commit does that. FIXED-IN: 5.25 M +1-1src/effects/overview/metadata.json https://invent.kde.org/plasma/kwin/commit/9ff137f5cb4cd7cc54c2d454f3d28efa60d8aed6 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 453617] Add "Ignore face" button for unrecongised faces in thumbnail view
https://bugs.kde.org/show_bug.cgi?id=453617 Maik Qualmann changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/digikam/commit/c0e7698 ||0c714b4a7b4e61dd735e798c3b6 ||28d2e6 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Version Fixed In||7.7.0 --- Comment #4 from Maik Qualmann --- Git commit c0e76980c714b4a7b4e61dd735e798c3b628d2e6 by Maik Qualmann. Committed on 13/05/2022 at 19:56. Pushed by mqualmann into branch 'qt5-maintenance'. uniform and new icon to ignore faces FIXED-IN: 7.7.0 M +2-1NEWS M +3-3core/utilities/facemanagement/widgets/assignnamewidget.cpp M +4-2core/utilities/facemanagement/widgets/assignnamewidget_p.cpp M +2-2core/utilities/facemanagement/widgets/assignnamewidget_p.h https://invent.kde.org/graphics/digikam/commit/c0e76980c714b4a7b4e61dd735e798c3b628d2e6 -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 453760] Use three windows when pasting text.
https://bugs.kde.org/show_bug.cgi?id=453760 chrisjba...@hotmail.com changed: What|Removed |Added CC||chrisjba...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 453760] New: Use three windows when pasting text.
https://bugs.kde.org/show_bug.cgi?id=453760 Bug ID: 453760 Summary: Use three windows when pasting text. Product: kdiff3 Version: 1.9.5 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: reeves...@gmail.com Reporter: chrisjba...@hotmail.com Target Milestone: --- SUMMARY *** Unable to do a 3-way comparison with pasted text. *** STEPS TO REPRODUCE 1. Open kdiff3 and click Cancel to avoid opening any files. 2. Paste contents in A side and B side. 3. Try to paste contents in C side; fail. There is no C window. OBSERVED RESULT If I have the menu item Window > Show Window C checked, I should be able to see window C, even if I'm pasting in text. EXPECTED RESULT I have no way of seeing or interacting with window C. SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION This apparently isn't new: - https://sourceforge.net/p/kdiff3/feature-requests/128/ - https://sourceforge.net/p/kdiff3/feature-requests/127/ -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 451486] md5sums of krita-5.0.2.dmg in https://download.kde.org/stable/krita/5.0.2/md5sum.txt is wrong
https://bugs.kde.org/show_bug.cgi?id=451486 Ben Cooksley changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #10 from Ben Cooksley --- Given the content of the md5sum.txt file was both inaccurate and was served from mirrors rather than directly by us i've now removed the 5.0.2 and 5.0.5 versions of those files. Please use the mirrorlist/md5/sha1/sha256 special links as noted below for retrieving a sum that can be used to validate your download. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 453759] New: KSyntaxHighlighting does not build with a C++20 compiler on Windows
https://bugs.kde.org/show_bug.cgi?id=453759 Bug ID: 453759 Summary: KSyntaxHighlighting does not build with a C++20 compiler on Windows Product: frameworks-syntax-highlighting Version: 5.93.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: critical Priority: NOR Component: framework Assignee: kwrite-bugs-n...@kde.org Reporter: nicolas.arnaudcor...@gmail.com Target Milestone: --- SUMMARY KSyntaxHighlighting does not compile with Visual Studio 2022 and C++20. (You need a C++20 compiler that support the new format standard library feature) STEPS TO REPRODUCE 1. Compile KSyntaxHighlighting with Visual Studio 2022 in C++20 mode... OBSERVED RESULT Thousands of errors like that: ``` C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.29.30133\include\chrono(4595): error C2760: syntax error: unexpected token 'identifier', expected 'type specifier' C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.29.30133\include\chrono(4622): error C3646: '_Alignment': unknown override specifier C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.29.30133\include\chrono(4629): note: see reference to class template instantiation 'std::_Chrono_format_specs<_CharT>' being compiled C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.29.30133\include\chrono(4622): error C2059: syntax error: '=' C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.29.30133\include\chrono(4622): error C2653: '_Fmt_align': is not a class or namespace name ``` EXPECTED RESULT It builds ;) ADDITIONAL INFORMATION The problem comes from the generation of headers with ecm_generate_headers. One of the header is "Format", which will be mixed up with the standard library one "format". Obviously, this error does not happen on Linux. I see 2 ways to fix it: - complex: change the generated header to something else than Format (may impact other projects) - easy: don't call ecm_generate_headers on Windows, or at least add a way to not do it with a CMake variable Maybe there's another one, I don't know. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 453475] KDE Connect kdeconnect add run commands causes immediate crash
https://bugs.kde.org/show_bug.cgi?id=453475 --- Comment #2 from Jeff Tratt --- It's working now. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441556] Race condition between automounted disks and any run-on-login scripts or apps that use them
https://bugs.kde.org/show_bug.cgi?id=441556 --- Comment #5 from Jinu --- (In reply to empyreal from comment #2) > Sorry. I'll explain. Open qbittorrent. Have some torrents seeding from > mounted NTFS disk. Turn off or reboot PC. Linux starts and qbittorrent > starts. qbittorrent shows errors instead starting seeding. It looks that > qbittoerrent starts before mount. Hi, any update on resolving this bug/issue? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 453758] Okular fails to render some mathematical symbols in PDF
https://bugs.kde.org/show_bug.cgi?id=453758 --- Comment #3 from Corentin Poupry --- I forgot to mention that the renderer is Poppler 22.05.0 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 453758] Okular fails to render some mathematical symbols in PDF
https://bugs.kde.org/show_bug.cgi?id=453758 --- Comment #2 from Corentin Poupry --- Created attachment 148806 --> https://bugs.kde.org/attachment.cgi?id=148806=edit With Firefox viewer -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 453758] Okular fails to render some mathematical symbols in PDF
https://bugs.kde.org/show_bug.cgi?id=453758 --- Comment #1 from Corentin Poupry --- Created attachment 148805 --> https://bugs.kde.org/attachment.cgi?id=148805=edit With Okular -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 453751] kwin_wayland crash when starting plasmashell from the Overview effect search field
https://bugs.kde.org/show_bug.cgi?id=453751 --- Comment #1 from Alexander Lohnau --- No idea why this crashes, the stacktrace looks Qt-internal. I did not experience any crash recently, though I do not use Arch which is the distro that the other bug reporter uses too. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 453758] New: Okular fails to render some mathematical symbols in PDF
https://bugs.kde.org/show_bug.cgi?id=453758 Bug ID: 453758 Summary: Okular fails to render some mathematical symbols in PDF Product: okular Version: 22.04.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: pouprycorenti...@gmail.com Target Milestone: --- SUMMARY Okular does not correctly render some mathematical symbols in some PDFs I use as a student. I found a reference to a similar bug here https://bugs.freedesktop.org/show_bug.cgi?id=32237 I can't provide the PDF here for copyright reasons, but I could send it to a developer STEPS TO REPRODUCE 1. Open the PDF 2. Note that some symbols are missing OBSERVED RESULT Some symbols are missing and make the document uninterpretable EXPECTED RESULT The document symbols should be interpretable SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.17.5-arch1-1 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-7700 CPU @ 3.60GHz Memory: 15.6 Gio of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453757] New: If you use the tool briefly: move on the canvas, zoom in, keyboard and mouse, respectively, they are disabled.
https://bugs.kde.org/show_bug.cgi?id=453757 Bug ID: 453757 Summary: If you use the tool briefly: move on the canvas, zoom in, keyboard and mouse, respectively, they are disabled. Product: krita Version: 5.0.6 Platform: unspecified OS: Microsoft Windows Status: REPORTED Severity: minor Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: kiber-nicho...@yandex.ru Target Milestone: --- When you use the mouse to zoom in on the canvas, the space bar on the keyboard to move across the canvas just stops working after a while. The same thing happens with the "Shift" key to zoom in and out of the brush. I have to press any other key to make it work. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 417615] Option to disable kdeconnect
https://bugs.kde.org/show_bug.cgi?id=417615 Marcus Sundman changed: What|Removed |Added CC||sund...@iki.fi -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 452903] KDE Connect crashes when opening module settings
https://bugs.kde.org/show_bug.cgi?id=452903 Colin J Thomson changed: What|Removed |Added CC|colin.thom...@g6avk.co.uk | -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453756] New: Location bar resets after several seconds when typing
https://bugs.kde.org/show_bug.cgi?id=453756 Bug ID: 453756 Summary: Location bar resets after several seconds when typing Product: dolphin Version: 21.12.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: bars: location Assignee: dolphin-bugs-n...@kde.org Reporter: tracy.p...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY When typing a location in the location bar, the contents of the bar will reset to the current directory after several seconds. This doesn't happen every time, but it is very common. STEPS TO REPRODUCE 1. Open dolphin. 2. Press CTRL+L. 3. Begin typing an address, e.g. /home/... OBSERVED RESULT The location shown in the address bar will reset to the current directory, losing what was typed. EXPECTED RESULT The typed location should not be overwritten. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 22.04 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION I saw this bug mentioned on 2022-01-11: https://www.reddit.com/r/kde/comments/s1m2sx/dolphin_location_navigation_refreshes/ -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 453755] New: KWrite crashed after pressing apply in Settings --> Open/Save --> Advanced
https://bugs.kde.org/show_bug.cgi?id=453755 Bug ID: 453755 Summary: KWrite crashed after pressing apply in Settings --> Open/Save --> Advanced Product: kate Version: 22.04.1 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: kwrite Assignee: kwrite-bugs-n...@kde.org Reporter: joa...@eiworth.net Target Milestone: --- Application: kwrite (22.04.1) Qt Version: 5.15.3 Frameworks Version: 5.93.0 Operating System: Linux 5.17.0-5.2-liquorix-amd64 x86_64 Windowing System: X11 Distribution: KDE neon User - 5.24 DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I was trying to configure the same restore-after-crash behavior as e.g. notepad++, i.e. complete session restore with all open files, manually saved or not so I first enabled Auto Save, applied change, switched to Advanced and tried to configure backup file for both local and remote files. I left default and applied and CRASH. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KWrite (kwrite), signal: Segmentation fault [New LWP 66337] [New LWP 66338] [New LWP 66339] [New LWP 66340] [New LWP 66341] [New LWP 66342] [New LWP 66343] [New LWP 66344] [New LWP 66345] [New LWP 66346] [New LWP 66347] [New LWP 66348] [New LWP 66349] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f9500a0899f in __GI___poll (fds=0x7ffe684189b8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7f94fc2499c0 (LWP 66335))] Thread 14 (Thread 0x7f94cdffb700 (LWP 66349)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5608866b9518) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5608866b94c8, cond=0x5608866b94f0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5608866b94f0, mutex=0x5608866b94c8) at pthread_cond_wait.c:647 #3 0x7f94f2647e0b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f94f2647b5b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f94ff2b8609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f9500a15133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 13 (Thread 0x7f94ce7fc700 (LWP 66348)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5608866b9518) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5608866b94c8, cond=0x5608866b94f0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5608866b94f0, mutex=0x5608866b94c8) at pthread_cond_wait.c:647 #3 0x7f94f2647e0b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f94f2647b5b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f94ff2b8609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f9500a15133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 12 (Thread 0x7f94ceffd700 (LWP 66347)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5608866b9518) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5608866b94c8, cond=0x5608866b94f0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5608866b94f0, mutex=0x5608866b94c8) at pthread_cond_wait.c:647 #3 0x7f94f2647e0b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f94f2647b5b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f94ff2b8609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f9500a15133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7f94cf7fe700 (LWP 66346)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5608866b9518) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5608866b94c8, cond=0x5608866b94f0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5608866b94f0, mutex=0x5608866b94c8) at pthread_cond_wait.c:647 #3 0x7f94f2647e0b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f94f2647b5b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f94ff2b8609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f9500a15133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7f94c700 (LWP 66345)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5608866b8fa8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5608866b8f58, cond=0x5608866b8f80) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5608866b8f80, mutex=0x5608866b8f58)
[kwin] [Bug 446753] Enable the Overview effect by default
https://bugs.kde.org/show_bug.cgi?id=446753 Bug 446753 depends on bug 445930, which changed state. Bug 445930 Summary: Does not appear as an option in the Task Manager settings https://bugs.kde.org/show_bug.cgi?id=445930 What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445930] Does not appear as an option in the Task Manager settings
https://bugs.kde.org/show_bug.cgi?id=445930 Nate Graham changed: What|Removed |Added Status|CONFIRMED |RESOLVED Version Fixed In||5.25 Resolution|--- |FIXED --- Comment #1 from Nate Graham --- This has been done for 5.25. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453668] Windows moved and window sizes are squashed when unplug-replugging screen
https://bugs.kde.org/show_bug.cgi?id=453668 --- Comment #2 from Andreas Aardal Hanssen --- (In reply to Nate Graham from comment #1) > Is this on X11 or Wayland? Does it affect all windows, or only windows of > some KDE apps? X11 and applies to all apps that don't have explicit size saved. My terminal windows remains unaffected. Very easy to reproduce... firefox fex, or Qt Creator, resize manually to approx 90% of size of screen both dimensions, window on the primary screen. Turn off the secondary screen, and the window immediately resizes to approx 30% height (width is unchanged). I think it has to do with the vertical resolution being different on the two screens maybe... -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 453754] New: Krusader crashes when trying to open (any) file in viewer
https://bugs.kde.org/show_bug.cgi?id=453754
Bug ID: 453754
Summary: Krusader crashes when trying to open (any) file in
viewer
Product: krusader
Version: unspecified
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: krusader-bugs-n...@kde.org
Reporter: tbp...@gmx.de
CC: krusader-bugs-n...@kde.org
Target Milestone: ---
Application: krusader (2.7.2 "Peace of Mind")
Qt Version: 5.15.2
Frameworks Version: 5.93.0
Operating System: Linux 5.17.5-1-default x86_64
Windowing System: X11
Distribution: openSUSE Tumbleweed
DrKonqi: 5.24.5 [KCrashBackend]
-- Information about the crash:
- What I was doing when the application crashed:
I've been starting Krusader normally, then I selected a file and pressed F3 to
view it's contents.
After pressing the key Krusader quits immediately. Instead, pressing F4 on the
same file to start the editor works fine.
I'm using Krusader's internal viewer / editor. The error is reproducable every
time and occurs no matter which type of file I want to view. There's no
difference in behaviour between pressing F3/F4 or selecting view/edit from the
File-Menu.
The crash can be reproduced every time.
-- Backtrace:
Application: Krusader (krusader), signal: Aborted
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#7 0x7f3f7cb7a1e3 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
#8 0x7f3f7cb2a306 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#9 0x7f3f7cb13813 in __GI_abort () at abort.c:79
#10 0x7f3f7ce96ad5 in __gnu_cxx::__verbose_terminate_handler () at
../../../../libstdc++-v3/libsupc++/vterminate.cc:95
#11 0x7f3f7cea1fcc in __cxxabiv1::__terminate (handler=) at
../../../../libstdc++-v3/libsupc++/eh_terminate.cc:48
#12 0x7f3f7cea2037 in std::terminate () at
../../../../libstdc++-v3/libsupc++/eh_terminate.cc:58
#13 0x7f3f7cea2d65 in __cxxabiv1::__cxa_pure_virtual () at
../../../../libstdc++-v3/libsupc++/pure.cc:50
#14 0x7f3f7d327f95 in QObject::setProperty (this=this@entry=0x562db5370b90,
name=name@entry=0x7f3f6c7bf629 "isSingleFolder", value=...) at
kernel/qobject.cpp:4031
#15 0x7f3f6c7932cd in Kerfuffle::LoadJob::onFinished (this=0x562db63e43d0,
result=) at
/usr/src/debug/ark-22.04.0-1.1.x86_64/kerfuffle/jobs.cpp:270
#16 0x7f3f7d31f28e in QObject::event (this=0x562db63e43d0,
e=0x7f3f5c004600) at kernel/qobject.cpp:1314
#17 0x7f3f7decfb0f in QApplicationPrivate::notify_helper (this=, receiver=0x562db63e43d0, e=0x7f3f5c004600) at
kernel/qapplication.cpp:3632
#18 0x7f3f7d2f2b5a in QCoreApplication::notifyInternal2
(receiver=0x562db63e43d0, event=0x7f3f5c004600) at
kernel/qcoreapplication.cpp:1064
#19 0x7f3f7d2f5b97 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x562db4c079a0) at
kernel/qcoreapplication.cpp:1821
#20 0x7f3f7d34ac33 in postEventSourceDispatch (s=s@entry=0x562db4d25a90) at
kernel/qeventdispatcher_glib.cpp:277
#21 0x7f3f7b89d122 in g_main_dispatch (context=0x7f3f74005010) at
../glib/gmain.c:3417
#22 g_main_context_dispatch (context=0x7f3f74005010) at ../glib/gmain.c:4135
#23 0x7f3f7b89d4b8 in g_main_context_iterate
(context=context@entry=0x7f3f74005010, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4211
#24 0x7f3f7b89d56f in g_main_context_iteration (context=0x7f3f74005010,
may_block=1) at ../glib/gmain.c:4276
#25 0x7f3f7d34a2b4 in QEventDispatcherGlib::processEvents
(this=0x562db4d2bb80, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#26 0x7f3f7d2f155b in QEventLoop::exec (this=this@entry=0x7ffd666073e0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#27 0x7f3f7d2f9820 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#28 0x7f3f7d74361c in QGuiApplication::exec () at
kernel/qguiapplication.cpp:1867
#29 0x7f3f7decfa85 in QApplication::exec () at kernel/qapplication.cpp:2824
#30 0x562db48c4d22 in main (argc=, argv=) at
/usr/src/debug/krusader-2.7.2-1.18.x86_64/krusader/main.cpp:316
[Inferior 1 (process 7063) detached]
Possible duplicates by query: bug 419428, bug 364706, bug 352150, bug 347564,
bug 340455.
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 453752] Effects Settings from XDG_CONFIG_DIRS are discarded when user clicks on [Defaults]
https://bugs.kde.org/show_bug.cgi?id=453752 Michael Mikowski changed: What|Removed |Added Summary|Effects Settings from |Effects Settings from |XDG_CONFIG_DIRS are discard |XDG_CONFIG_DIRS are |when user clicks on |discarded when user clicks |[Defaults] |on [Defaults] -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 453752] Effects Settings from XDG_CONFIG_DIRS are discard when user clicks on [Defaults]
https://bugs.kde.org/show_bug.cgi?id=453752 Michael Mikowski changed: What|Removed |Added Summary|Effects Settings do |Effects Settings from ||XDG_CONFIG_DIRS are discard ||when user clicks on ||[Defaults] -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453642] Multiple monitors reset configuration and mirror screens after sleep
https://bugs.kde.org/show_bug.cgi?id=453642 --- Comment #1 from Isaac --- I think an additional point that might be causing this bug is that both monitors are identified as "DP_FREESYNC 1" in the Display Configuration settings tab. They are identically named, and I think this is breaking the configuration upon waking. An additional point: The bug is not present when the system goes to sleep, only when the monitors are turned off for power savings. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453746] Crash when exporting lossy JPEG XL
https://bugs.kde.org/show_bug.cgi?id=453746 --- Comment #5 from Alvin Wong --- Ah, I found the trigger: "Low resolution DC" was set to "512x512 + 64x64" (must've changed that some time when scrolling). Other options are default. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445224] Short date format preview not visible on Time page
https://bugs.kde.org/show_bug.cgi?id=445224 --- Comment #14 from Ahmad Samir --- OK, thanks for the feedback. -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 453455] KBibTeX 0.9.90 won't start after I updated to Ubuntu 22.04
https://bugs.kde.org/show_bug.cgi?id=453455 --- Comment #3 from Raymond Wan --- Thank you for reporting the original problem, hakonanes! Out of desperation (as I need to use it), I even tried kbibtex for Ubuntu 21.10 (version 0.9.90-1) and Ubuntu 20.04 (0.8.1-1ubuntu5). I needed to install kbibtex, kbibtex-data, and icu. As kbibtex has other dependencies, I didn't think this could work. But I wasn't asked for other dependencies. However, it crashed in exactly the same way (i.e., segmentation fault), even though I have used kbibtex on Ubuntu 21.10 and Ubuntu 20.04 before. This was surprising and, unfortunately, I don't know what this means... Just thought I'd mention this so that you won't waste time trying this. -- You are receiving this mail because: You are watching all bug changes.
[policykit-kde-agent-1] [Bug 453494] Polkit, Wayland, password dialog should open centered above application, if possible, or at least centered on screen like in X11
https://bugs.kde.org/show_bug.cgi?id=453494 --- Comment #7 from kde@grau.net --- If it works like you describe it, then I don't think it has a parent window set in X11, either. At least for me, in X11 it always centers on the screen and is not displayed centered above in the application window, requesting the authentication. If I understand the way the integration of the polkit window works correctly, the requesting application asks for the authentication to performed via dbus. Therefore the polkit window is running in a separate process and doesn't have any information about the windows of the calling application. Hence, polkit cannot easily set the parent window. Imagine a command run on the commandline in konsole requesting authorization, for example "pamac" in Manjaro. That command doesn't even have any windows. If this command requests authorization, polkit would have to figure out that the command is run from within konsole and then find out, which of the Konsole windows it's run from. As this is quite complicated to get right and would probably require a lot of information passed on dbus between the applications and polkit, it's probably easier for polkit to just open the window centered on the screen. As I have only one screen, I wouldn't even know if polkit manages to display the window on the correct screen. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 453716] Kate sometimes crashes when closing a tab in a split view
https://bugs.kde.org/show_bug.cgi?id=453716 Waqar Ahmed changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/util ||ities/kate/commit/7b249cfeb ||4402679b96f3d363573820d431b ||ca29 --- Comment #2 from Waqar Ahmed --- Git commit 7b249cfeb4402679b96f3d363573820d431bca29 by Waqar Ahmed. Committed on 13/05/2022 at 06:42. Pushed by cullmann into branch 'master'. Fix tab closing with multiple viewspaces Sometimes a viewspace has only view available but multiple docs (and tabs for those docs). M +22 -5apps/lib/kateviewspace.cpp https://invent.kde.org/utilities/kate/commit/7b249cfeb4402679b96f3d363573820d431bca29 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 453753] New: Akonadi crashes when opening KMail
https://bugs.kde.org/show_bug.cgi?id=453753 Bug ID: 453753 Summary: Akonadi crashes when opening KMail Product: Akonadi Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: devuran...@gmx.net Target Milestone: --- Application: akonadiserver (5.20.0 (22.04.0)) Qt Version: 5.15.3 Frameworks Version: 5.93.0 Operating System: Linux 5.17.7-gentoo-dist x86_64 Windowing System: Wayland Distribution: "Gentoo Base System release 2.8" DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: When I open KMail, it tries to start Akonadi, which immediately crashes. This is reproducible every time I open KMail. The crash can be reproduced every time. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault [KCrash Handler] #4 0x565000140274 in Akonadi::Server::SchemaVersion::generation (this=this@entry=0x7fb6a5bdc850) at /usr/include/qt5/QtCore/qshareddata.h:82 #5 0x5650001f97ba in Akonadi::Server::NotificationSubscriber::NotificationSubscriber (this=this@entry=0x7fb6983186f0, manager=manager@entry=0x565000581070, socketDescriptor=socketDescriptor@entry=163) at /usr/include/qt5/QtCore/qsharedpointer_impl.h:307 #6 0x5650001f61bf in Akonadi::Server::NotificationManager::registerConnection (this=0x565000581070, socketDescriptor=163) at /tmp/portage/kde-apps/akonadi-22.04.0/work/akonadi-22.04.0/src/server/notificationmanager.cpp:87 #7 0x7fb6aae63d16 in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5 #8 0x7fb6aae38415 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #9 0x7fb6aae3bab5 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQt5Core.so.5 #10 0x7fb6aae8ab73 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /usr/lib64/libQt5Core.so.5 #11 0x7fb6a935d60b in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #12 0x7fb6a935d8c8 in ?? () from /usr/lib64/libglib-2.0.so.0 #13 0x7fb6a935d97f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #14 0x7fb6aae8a604 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #15 0x7fb6aae36e3b in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #16 0x7fb6aac817aa in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #17 0x7fb6aac82949 in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #18 0x7fb6aa808f5a in ?? () from /usr/lib64/libc.so.6 #19 0x7fb6aa88e6fc in ?? () from /usr/lib64/libc.so.6 Thread 2 (Thread 0x7fb6a6aa6640 (LWP 19369) "QDBusConnection"): #1 0x7fb6aa8541a9 in clock_gettime () from /usr/lib64/libc.so.6 #2 0x7fb6aae89ec1 in qt_gettime() () from /usr/lib64/libQt5Core.so.5 #3 0x7fb6aae88809 in QTimerInfoList::updateCurrentTime() () from /usr/lib64/libQt5Core.so.5 #4 0x7fb6aae88c85 in QTimerInfoList::timerWait(timespec&) () from /usr/lib64/libQt5Core.so.5 #5 0x7fb6aae8a8de in timerSourcePrepare(_GSource*, int*) () from /usr/lib64/libQt5Core.so.5 #6 0x7fb6a935cd4b in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #7 0x7fb6a935d783 in ?? () from /usr/lib64/libglib-2.0.so.0 #8 0x7fb6a935d97f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #9 0x7fb6aae8a68e in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #10 0x7fb6aae36e3b in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #11 0x7fb6aac817aa in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #12 0x7fb6ab173537 in QDBusConnectionManager::run() () from /usr/lib64/libQt5DBus.so.5 #13 0x7fb6aac82949 in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #14 0x7fb6aa808f5a in ?? () from /usr/lib64/libc.so.6 #15 0x7fb6aa88e6fc in ?? () from /usr/lib64/libc.so.6 Thread 1 (Thread 0x7fb6a6ed8cc0 (LWP 19362) "akonadiserver"): #1 0x7fb6aa808624 in pthread_cond_timedwait () from /usr/lib64/libc.so.6 #2 0x7fb6aac882a5 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib64/libQt5Core.so.5 #3 0x7fb6aac82681 in QThread::wait(QDeadlineTimer) () from /usr/lib64/libQt5Core.so.5 #4 0x7fb6aac8149c in QThread::wait(unsigned long) () from /usr/lib64/libQt5Core.so.5 #5 0x565000223a40 in Akonadi::Server::AkThread::quitThread (this=this@entry=0x565000581070) at /tmp/portage/kde-apps/akonadi-22.04.0/work/akonadi-22.04.0/src/server/akthread.cpp:55 #6 0x5650001f527e in Akonadi::Server::NotificationManager::~NotificationManager (this=0x565000581070, __in_chrg=) at
[systemsettings] [Bug 453752] New: Effects Settings do
https://bugs.kde.org/show_bug.cgi?id=453752 Bug ID: 453752 Summary: Effects Settings do Product: systemsettings Version: 5.24.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kwin_effects Assignee: kwin-bugs-n...@kde.org Reporter: z_mikow...@yahoo.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY *** Click on Defaults in `kcmshell5 kcm_kwin_effects` results in apparently hard-coded defaults, not those defined in the `kf5-config --path config` hierarchy. *** STEPS TO REPRODUCE 1. Install Kubuntu 22.04 2. Edit `/usr/share/kubuntu-default-settings/kf5-settings` to include the following: [Plugins] wobblywindowsEnabled=true 3. Log out and back in. Open `kcmshell5 kcm_kwin_effects` and notice that wobbly windows are indeed enabled (this is not default on stock KDE). 4. Click on the [Defaults] button in the GUI. OBSERVED RESULT The wobbly window option erased and there is no simple or easy way for the user to recover the intent from the config path. EXPECTED RESULT I think that clicking on [Defaults] should honor the `kf5-config --path config` so that, for example, Kubuntu defaults can be recovered. Alternately, there may be a system-default vs. KDE defaults option, maybe with a pulldown button so as to not further clutter the interface. The preferred default should be the config path so as to retain the distribution or vendor intent IMO. SOFTWARE/OS VERSIONS Windows: no macOS: no Linux/KDE Plasma: Kubuntu 22.04 (available in About System) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION We see similar behavior with kglobalshortcutsrc. However, in this case, these don't even get APPLIED during run. KDE apparently inserts a .config/kdedefaults directory in the config path after changes to the settings, which is also inserted into the xdg-config path before any system paths. There may be some overlap there. I am at your service to provide additional testing and assistance. Just let me know if there is any way I can help to get this resolved. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453746] Crash when exporting lossy JPEG XL
https://bugs.kde.org/show_bug.cgi?id=453746 Alvin Wong changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Alvin Wong --- It crashes on a blank new 8-bit A4 300dpi document. Note that this crash is an abort from JXL_CHECK, not actually from an illegal instruction within actual code. If you want to know it's a Kaby Lake i5-7300U (Surface Pro 5). -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 453697] kwin_wayland crashed when trying to start plasmashell from the Overview effect search field
https://bugs.kde.org/show_bug.cgi?id=453697 --- Comment #4 from Lyubomir --- Done -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 453741] Lock screen is broken
https://bugs.kde.org/show_bug.cgi?id=453741 --- Comment #10 from giuseppe --- Created attachment 148804 --> https://bugs.kde.org/attachment.cgi?id=148804=edit coredumpctl after i run the command from bash instead of fish I thought backtrace was the output when I tried to run the lock screen from bash. Instead it should be the coredumpctl. This one seems longer of 40 lines indeed. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 453751] New: kwin_wayland crash when starting plasmashell from the Overview effect search field
https://bugs.kde.org/show_bug.cgi?id=453751 Bug ID: 453751 Summary: kwin_wayland crash when starting plasmashell from the Overview effect search field Product: krunner Version: 5.24.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.loh...@gmx.de Reporter: liubomi...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY Same as https://bugs.kde.org/show_bug.cgi?id=453697#c3 but with different stacktrace. OBSERVED RESULT (gdb) backtrace #0 0x7f9c85140405 in QExplicitlySharedDataPointer::operator!() const (this=, this=) at ../../include/QtCore/../../src/corelib/tools/qshareddata.h:231 #1 QJsonObject::valueImpl(QStringView) const (key=..., this=) at serialization/qjsonobject.cpp:371 #2 QJsonObject::value(QStringView) const (this=0x2d323465342d344c, key=...) at serialization/qjsonobject.cpp:353 #3 0x7f9c851406dd in QJsonObject::operator[](QStringView) const (key=..., this=) at ../../include/QtCore/../../src/corelib/serialization/qjsonobject.h:102 #4 QJsonObject::operator[](QString const&) const (this=, key=...) at serialization/qjsonobject.cpp:393 #5 0x7f9c8616cc50 in KPluginMetaData::rootObject() const (this=) at /usr/src/debug/kcoreaddons-5.93.0/src/lib/plugin/kpluginmetadata.cpp:351 #6 0x7f9c8616d10b in KPluginMetaData::pluginId() const (this=0x2d323465342d344c) at /usr/src/debug/kcoreaddons-5.93.0/src/lib/plugin/kpluginmetadata.cpp:473 #7 0x7f9c86169b5e in KPluginMetaData::isValid() const (this=0x2d323465342d344c) at /usr/src/debug/kcoreaddons-5.93.0/src/lib/plugin/kpluginmetadata.cpp:341 #8 0x7f9c4867aadd in Plasma::AbstractRunner::name() const (this=0x55fc39cf0b60) at /usr/src/debug/krunner-5.93.0/src/abstractrunner.cpp:336 #9 0x7f9c48686b7a in Plasma::DefaultRunnerPolicy::free(QSharedPointer) (this=0x7f9c486a2100 , job=...) at /usr/src/debug/krunner-5.93.0/src/runnerjobs.cpp:98 #10 0x7f9c4864fcce in ThreadWeaver::Private::Job_Private::freeQueuePolicyResources(QSharedPointer) (this=0x55fc39487650, job=...) at /usr/src/debug/threadweaver-5.93.0/src/job_p.cpp:30 #11 0x7f9c48653185 in ThreadWeaver::Job::defaultEnd(QSharedPointer const&, ThreadWeaver::Thread*) (this=, job=...) at /usr/src/debug/threadweaver-5.93.0/src/job.cpp:125 #12 0x7f9c486530f7 in ThreadWeaver::Job::execute(QSharedPointer const&, ThreadWeaver::Thread*) (this=, self=..., th=0x55fc394c4cd0) at /usr/src/debug/threadweaver-5.93.0/src/job.cpp:79 #13 0x7f9c48656dd9 in ThreadWeaver::Thread::run() (this=0x55fc394c4cd0) at /usr/src/debug/threadweaver-5.93.0/src/thread.cpp:98 #14 0x7f9c84f338cc in QThreadPrivate::start(void*) (arg=0x55fc394c4cd0) at thread/qthread_unix.cpp:331 #15 0x7f9c847503dd in start_thread () at /usr/lib/libc.so.6 #16 0x7f9c847d52c4 in clone () at /usr/lib/libc.so.6 SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.17.5-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz Memory: 7,6 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[policykit-kde-agent-1] [Bug 453494] Polkit, Wayland, password dialog should open centered above application, if possible, or at least centered on screen like in X11
https://bugs.kde.org/show_bug.cgi?id=453494 --- Comment #6 from Nate Graham --- It must not be getting a parent window set properly on Wayland somehow. That's how this works on X11; child windows are always centered in their parent windows. And that works on Wayland too as long as the parent window is properly set. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453730] Thread 1 "plasmashell" received signal SIGSEGV, Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=453730
--- Comment #3 from Marcos Gutiérrez Alonso ---
(In reply to Nate Graham from comment #2)
> Unfortunately the backtrace is incomplete and missing debug symbols for the
> following lines that we need to figure out exactly what's going wrong:
>
> > #4 0x7ff30404bbef in () at
> > /usr/lib/qt/plugins/plasma/applets/org.kde.plasma.private.systemtray.so
>
> Could you please install debug symbols for Plasma and the kiconthemes
> framework, reproduce the crash, and attach a new symbolicated backtrace? See
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports
>
> Thanks!
(This is my first time reporting a bug with a backtrace, please be patient)
After installing `debuginfod`, I restarted and got another crash. This time is
not the same error I think.
This is the backtrace (from gdb I run `bt full`):
```
Core was generated by `/usr/bin/plasmashell'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x7f110f49534c in __pthread_kill_implementation () from
/usr/lib/libc.so.6
[Current thread is 1 (Thread 0x7f110abb7540 (LWP 46271))]
(gdb)
(gdb) c
The program is not being run.
(gdb) bt full
#0 0x7f110f49534c in __pthread_kill_implementation () at
/usr/lib/libc.so.6
#1 0x7f110f4484b8 in raise () at /usr/lib/libc.so.6
#2 0x7f7aa384 in KCrash::defaultCrashHandler(int) (sig=11) at
/usr/src/debug/kcrash-5.93.0/src/kcrash.cpp:609
data =
{ = {_vptr.MetadataWriter = 0x7f7ad8b8
}, argv = {_M_elems = {0x0, 0x7f7ab0c1
"--platform", 0x55d477e95b98 "wayland", 0x7f7ab0de "--appname",
0x55d475b896f0 "plasmashell", 0x7f7ab0f7 "--apppath", 0x55d475b89630
"/usr/bin", 0x7f7ab104 "--signal", 0x7fffdb1715e6 "11", 0x7f7ab112
"--pid", 0x7fffdb1715f0 "46271", 0x7f7ab118 "--appversion", 0x55d4760df478
"5.24.5", 0x7f7ab125 "--programname", 0x55d4760a76e8 "Plasma",
0x7f7ab133 "--bugaddress", 0x55d4760a81b8 "sub...@bugs.kde.org",
0x7f7ab14e "--startupid", 0x55d4796a4798 "0", 0x7f7ab162 "--restarted",
0x0 }}, argc = 20, m_writer = 0x7fffdb171720}
platformName = {d = 0x55d477e95b80}
about =
argv = 0x7fffdb171618
ini =
{ = {_vptr.MetadataWriter = 0x7f7ad8e8
}, writable = false, fd = 95, iniLine
= {_M_elems = "restarted=true\n\0...@bugs.kde.org\n", '\000' }}
sigtxt = "11\000\000\000\000\000\000\000"
pidtxt = "46271\000\000\000\000\000\000\000\000\000\360?\000\000\000"
startupId = {d = 0x55d4796a4780}
argc =
crashRecursionCounter = 2
#3 0x7f110f448560 in () at /usr/lib/libc.so.6
#4 0x7f11100484d4 in QColor::operator=(QColor const&) () at
/usr/lib/libQt5Gui.so.5
#5 0x7f110f3d9b74 in KIconColors::KIconColors(QPalette const&)
(this=, palette=..., this=, palette=) at /usr/src/debug/kiconthemes-5.93.0/src/kiconcolors.cpp:101
d = 0x55d47984d9c0
#6 0x7f110f3e954b in KIconLoader::setCustomPalette(QPalette const&)
(this=0x7f110f3ff0d0 <(anonymous
namespace)::Q_QGS_globalIconLoader::innerFunction()::holder>, palette=...)
at /usr/src/debug/kiconthemes-5.93.0/src/kiconloader.cpp:1834
#7 0x7f10cc6da27e in QIconSource::pixmap(QSize const&)
(this=0x55d477be87c0, size=...) at
/usr/src/debug/plasma-framework-5.93.0/src/declarativeimports/core/iconitem.cpp:96
result =
#8 0x7f10cc6dff5e in IconItem::loadPixmap() (this=0x55d47700dd50) at
/usr/src/debug/plasma-framework-5.93.0/src/declarativeimports/core/iconitem.cpp:713
size = -619240880
result =
animated =
#9 0x7f3c606d in QQuickWindowPrivate::polishItems()
(this=0x7f10fc001d20) at
/usr/src/debug/qtdeclarative/src/quick/items/qquickwindow.cpp:393
item = 0x55d47700dd50
itemPrivate =
itemsRemaining = 1
polishLoopDetector = {itemsToPolish = ,
numPolishLoopsInSequence = 0}
#10 0x7f37f463 in
QSGThreadedRenderLoop::polishAndSync(QSGThreadedRenderLoop::Window*, bool)
(this=0x55d476866ab0, w=0x55d477118360, inExpose=)
at
/usr/src/debug/qtdeclarative/src/quick/scenegraph/qsgthreadedrenderloop.cpp:1577
window = 0x55d476d77ca0
timer = {t1 = -9223372036854775808, t2 = -9223372036854775808}
polishTime = 0
waitTime = 0
syncTime = 0
profileFrames = false
d =
#11 0x7f3d1784 in QQuickWindow::event(QEvent*) (this=0x55d476d77ca0,
e=0x7fffdb1725c0) at
/usr/src/debug/qtdeclarative/src/quick/items/qquickwindow.cpp:1857
d = 0x7f10fc001d20
#12 0x7f11107182c6 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#13 0x7f110fac25aa in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x55d476d77ca0, event=0x7fffdb1725c0) at
kernel/qcoreapplication.cpp:1064
selfRequired = true
result = false
cbdata = {0x55d476d77ca0, 0x7fffdb1725c0, 0x7fffdb17256f}
d =
threadData
[kdeconnect] [Bug 453750] KDE connect + LibreOffice Impress: Laserpointer function of presentation module is not shown on beamer
https://bugs.kde.org/show_bug.cgi?id=453750 --- Comment #1 from BOF --- I'll add some images once I get to it if needed. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 453750] New: KDE connect + LibreOffice Impress: Laserpointer function of presentation module is not shown on beamer
https://bugs.kde.org/show_bug.cgi?id=453750 Bug ID: 453750 Summary: KDE connect + LibreOffice Impress: Laserpointer function of presentation module is not shown on beamer Product: kdeconnect Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: bugs_kde_org.5.k...@spamgourmet.com Target Milestone: --- SUMMARY I tested a presentation on my laptop using KDE neon, LibreOffice Impress and KDE connect. When I tested the presentation on my laptop, the laserpointer worked. When I connected the laptop to the beamer via an HDMI cable the laserpointer did not show up on the slides. STEPS TO REPRODUCE 1. Run a presentation using LibreOffice Impress and KDE connect 2. Start the presentation in the presentation mode (only the slide is shown on the beamer, not your entire screen. Not sure how this mode is officially called) 3. Use the laser pointer OBSERVED RESULT The laserpointer is not shown on the slide on the beamer, but only on the slide on the laptop screen. So it's not like you don't see the laser pointer at all, but you only see it in the slide that is on the laptop screen. EXPECTED RESULT The laserpointer function's ring of death is also visible on the slide that is displayed by the beamer since this is the more important one. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.24 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.13.0-41-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Memory: 30.8 GiB of RAM Graphics Processor: AMD RENOIR Version: 7.3.3.2 / LibreOffice Community Build ID: d1d0ea68f081ee2800a922cac8f79445e4603348 CPU threads: 16; OS: Linux 5.13; UI render: default; VCL: gtk3 Locale: de-AT (de_AT.UTF-8); UI: de-DE Flatpak Calc: threaded -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453749] Do not re-arrange windows' positions immediately
https://bugs.kde.org/show_bug.cgi?id=453749 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453749] New: Do not re-arrange windows' positions immediately
https://bugs.kde.org/show_bug.cgi?id=453749 Bug ID: 453749 Summary: Do not re-arrange windows' positions immediately Product: kwin Version: 5.24.5 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: effects-overview Assignee: kwin-bugs-n...@kde.org Reporter: pos...@posteo.eu Target Milestone: --- SUMMARY Closing a window from a set of displayed windows, make all windows re-arrange so that they best fit the available space. This happens automatically and instantly. However, it makes it hard to keep an overview since it's hard to track the windows movement, especially when there are many windows opened (like > 5). It would be therefore helpful if the window would not re-arrange instantly or would arrange just slower, so it becomes easier to find the next window to work with. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445224] Short date format preview not visible on Time page
https://bugs.kde.org/show_bug.cgi?id=445224 --- Comment #13 from hanyo...@protonmail.com --- The short format is added back in the new Region & Language KCM: https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1147 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445224] Short date format preview not visible on Time page
https://bugs.kde.org/show_bug.cgi?id=445224 --- Comment #12 from Ahmad Samir --- Ping. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453713] Dragged and dropped image onto itself in Firefox stays as a preview with the cursor
https://bugs.kde.org/show_bug.cgi?id=453713 postix changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #2 from postix --- (In reply to Nate Graham from comment #1) > Cannot reproduce; works for me on that website with Firefox 100.0 in native > Wayland mode and git master KDE stuff. Let me re-check when I'm on 5.25 :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453720] Firefox: Search panel flickers on mouse hover instead of showing tooltips
https://bugs.kde.org/show_bug.cgi?id=453720 postix changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|RESOLVED --- Comment #3 from postix --- (In reply to Nate Graham from comment #2) > Cannot reproduce; works for me on that website with Firefox 100.0 in native > Wayland mode and git master KDE stuff. Let me re-check when I'm on 5.25 :) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 428043] Crash in KActionCollection::removeAssociatedWidget() when I typed "exit" in Dolphin's terminal panel
https://bugs.kde.org/show_bug.cgi?id=428043 Ahmad Samir changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||a.samir...@gmail.com --- Comment #2 from Ahmad Samir --- Does this still happen or was it a one-time crash? -- You are receiving this mail because: You are watching all bug changes.
[policykit-kde-agent-1] [Bug 453494] Polkit, Wayland, password dialog should open centered above application, if possible, or at least centered on screen like in X11
https://bugs.kde.org/show_bug.cgi?id=453494 --- Comment #5 from kde@grau.net --- I'm wondering who is actually responsible for the placement. As the centering works on X11, is this something kwin_wayland is responsible for, or is that something polkit must take care of? -- You are receiving this mail because: You are watching all bug changes.
[policykit-kde-agent-1] [Bug 453494] Polkit, Wayland, password dialog should open centered above application, if possible, or at least centered on screen like in X11
https://bugs.kde.org/show_bug.cgi?id=453494 kde@grau.net changed: What|Removed |Added Status|REOPENED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[policykit-kde-agent-1] [Bug 453494] Polkit, Wayland, password dialog should open centered above application, if possible, or at least centered on screen like in X11
https://bugs.kde.org/show_bug.cgi?id=453494 kde@grau.net changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #4 from kde@grau.net --- Hmm, that's weird, I'll reopen then. For me it previously only displayed the window centered, when there was no free space left on the desktop that the window would fit in. After upgrading to 5.24.5 the dialog is always centered, no matter where the window of the application requesting the authorization is located. It also doesn't matter how much free space is available on my desktop, either. I tried it a couple of times now, using pamac to install new software, changing root files with kate, ... The window is always centered on wayland now. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 427975] unable to select files with strange filenames
https://bugs.kde.org/show_bug.cgi?id=427975 Ahmad Samir changed: What|Removed |Added CC||a.samir...@gmail.com Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from Ahmad Samir --- Creating a file named e.g. "results.2020-10-16T13:21:40-21-1.emf", I can open that file in Kate and the open file dialog can open it. Do you still see this issue? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453721] Pinned Snap app not recognized in task manager after app update
https://bugs.kde.org/show_bug.cgi?id=453721 --- Comment #2 from 4ero...@gmail.com --- (In reply to Nate Graham from comment #1) > It seems like the path got recorded with the version number in it, rather > than using the "current" symlink. Yap. "Who" sets this ? Snap ? KDE ? Plasma ? Kinda lost here ;) -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 426499] Draggable area not clearly signposted/misleading highlighting
https://bugs.kde.org/show_bug.cgi?id=426499 --- Comment #10 from Joe Dight --- (In reply to Andrey from comment #8) > Here is how it looks like: > https://invent.kde.org/utilities/ark/-/merge_requests/115#note_447931 > > There are different opinions if it actually fixes the bug. > I would love to know what OP thinks about it. I can't see if the lighter/darker split also exists on hover, when no selection has been made. If it does (or is made obvious somehow else) the bug is definitely fixed. Otherwise it's more nebulous, because you still can't tell where to drag before you've made a selection. But maybe that would be a new bug? Sadly, the SUMMARY is rather broader than the STEPS TO REPRODUCE, which is where the uncertainty arises I think. -- You are receiving this mail because: You are watching all bug changes.
