[kwin] [Bug 433493] Cannot move windows across desktops using KWin shortcuts while the window is being dragged
https://bugs.kde.org/show_bug.cgi?id=433493 --- Comment #2 from Evan --- Yes, if you are NOT holding/dragging a window, then the desktop will switch as expected. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433501] kwin_wayland crashes occasionally
https://bugs.kde.org/show_bug.cgi?id=433501 --- Comment #6 from Nate Graham --- I don't know, sorry. :( Maybe someone more knowledgeable than me can help you. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433493] Cannot move windows across desktops using KWin shortcuts while the window is being dragged
https://bugs.kde.org/show_bug.cgi?id=433493 Nate Graham changed: What|Removed |Added Summary|[wayland] Cannot Drag |Cannot move windows across |Windows Across Desktops in |desktops using KWin |5.21 Wayland using KWin |shortcuts while the window |Shortcuts |is being dragged Keywords||regression CC||n...@kde.org --- Comment #1 from Nate Graham --- But it works if you don't drag the window while hitting the relevant keyboard shortcut right? -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 408070] Type error in logic.js
https://bugs.kde.org/show_bug.cgi?id=408070 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED CC||n...@kde.org Resolution|--- |FIXED --- Comment #1 from Nate Graham --- This looks to have been fixed at some point. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433501] kwin_wayland crashes occasionally
https://bugs.kde.org/show_bug.cgi?id=433501 --- Comment #5 from 32299...@gmail.com --- I have tried running the above, and after installing debug symbols and running bt, I cannot seem to get it to say anything except "no stack". What am I doing wrong? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433489] Memory leak in plasmashell when switching desktop
https://bugs.kde.org/show_bug.cgi?id=433489 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433486] Set multi-monitor mode to "Unify outputs", disconnect external monitor, turn it off and reconnect it: Plasma crashes.
https://bugs.kde.org/show_bug.cgi?id=433486 Nate Graham changed: What|Removed |Added Keywords||wayland CC||n...@kde.org --- Comment #1 from Nate Graham --- #4 0x7fef02ed1fcf in QtWaylandClient::QWaylandWindow::setVisible(bool) (visible=true, this=0x563408edd970) at qwaylandwindow.cpp:432 #5 QtWaylandClient::QWaylandWindow::setVisible(bool) (this=0x563408edd970, visible=) at qwaylandwindow.cpp:419 #6 0x7fef053919fb in QWindowPrivate::setVisible(bool) (this=0x56340109dbd0, visible=) at kernel/qwindow.cpp:408 #7 0x5633fda5b2db in ShellCorona::addOutput(QScreen*) (this=0x5633ff78ad20, screen=) at ./shell/shellcorona.cpp:1235 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 433476] When only one device is present, show its full name
https://bugs.kde.org/show_bug.cgi?id=433476 Nate Graham changed: What|Removed |Added Keywords||usability CC||n...@kde.org --- Comment #1 from Nate Graham --- Hmm, this was an intentional change made a year or two ago to simplify the presentation for the common case where you only have one device. We figured that there was no reason at all to show the full name when you only ever have one device (it was irrelevant information), and for people who periodically attach and detach devices, this is a manual action so they would know which device was in use. Part of the problem with always showing the name is that some device names are really ugly. Your device may say "USB DAC" but one of my devices is named "sof-hda-dsp Speaker + Headphones". I don't want to see that all the time. I know that hover only actions is sub-optimal, but maybe we could display the full name on hover when only one device is attached. What do you think? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354802] Desktop Icon position gets scrambled sometimes on reboot.
https://bugs.kde.org/show_bug.cgi?id=354802 --- Comment #156 from Nick Stefanov --- The weirdness continues: https://i.imgur.com/FEQyA9C.png Something is so screwed up... -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433115] Global Scaling Options Seems to "lower" resolution unlike old "force font DPI"; consider re-adding it as an option
https://bugs.kde.org/show_bug.cgi?id=433115 --- Comment #14 from Dimitris Giannos --- If that's more convenient for everyone.. then yes. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433475] Margin separators are not "visible" or easy to identify
https://bugs.kde.org/show_bug.cgi?id=433475 Nate Graham changed: What|Removed |Added Keywords||usability Status|REPORTED|CONFIRMED CC||n...@kde.org, ||niccolo.venera...@gmail.com Ever confirmed|0 |1 --- Comment #1 from Nate Graham --- Yeah I agree. It's probably fine that Margins Separator applets are invisible during normal use, but while the panel is being edited, their invisibility makes them hard to notice, and therefore it's not visually obvious why the thickness of the blue line is being changed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384782] Allow manually re-ordering tray icons
https://bugs.kde.org/show_bug.cgi?id=384782 Nate Graham changed: What|Removed |Added CC||overlord.jarrard@protonmail ||.com --- Comment #10 from Nate Graham --- *** Bug 433474 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433474] Enable moving of tray-icon entries in a custom order
https://bugs.kde.org/show_bug.cgi?id=433474 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||n...@kde.org --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 384782 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433471] Cover Switch and Flip Switch animations works unreliably after upgrade to Plasma 5.21
https://bugs.kde.org/show_bug.cgi?id=433471 Nate Graham changed: What|Removed |Added Component|effects-various |tabbox Summary|Cover switch animation |Cover Switch and Flip |works unreliably after |Switch animations works |upgrade to Plasma 5.21 |unreliably after upgrade to ||Plasma 5.21 --- Comment #2 from Nate Graham --- Looks like Flip Switch is affected too. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433471] Cover switch animation works unreliably after upgrade to Plasma 5.21
https://bugs.kde.org/show_bug.cgi?id=433471 Nate Graham changed: What|Removed |Added Keywords||regression Status|REPORTED|CONFIRMED CC||n...@kde.org Ever confirmed|0 |1 --- Comment #1 from Nate Graham --- Can confirm. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 433503] New: Falkon hangs and takes stops the OS from working
https://bugs.kde.org/show_bug.cgi?id=433503 Bug ID: 433503 Summary: Falkon hangs and takes stops the OS from working Product: Falkon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: nicho...@nshiell.com Target Milestone: --- SUMMARY Browser hangs,renders the whole system unresponsive STEPS TO REPRODUCE 1. Goto https://coronavirus.data.gov.uk/details/interactive-map 2. Goto https://coronavirus.data.gov.uk/details/interactive-map in a new tab 3. Goto https://coronavirus.data.gov.uk/details/interactive-map in a new tab 4. Drag the map around 5. Put the browser under more load OBSERVED RESULT The whole OS stops working, can't use Ctrl+Alt+F3 to get to a TTY EXPECTED RESULT Either work and not break or provide a message saying the page is unresponsive, don't crash the whole system SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.10 (available in About System) KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION This is on a new laptop Dell i7-1165G7 - This laptop model number is certified by Cannonical The laptop has around 16gb of memory It is running a resonably vanilla fresh install of Kubuntu If Falkon can't run, then it shouldn't take down my whole OS, so there may be 2 issues, one: Falkon has some issue with memory, second: nothing catches the situation -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433501] kwin_wayland crashes occasionally
https://bugs.kde.org/show_bug.cgi?id=433501 --- Comment #4 from Nate Graham --- you would need to invoke it like this: gdb --args kwin_wayland --wayland_fd 4 --xwayland /usr/libexec/startplasma-waylandsession [path to coredump file] -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433501] kwin_wayland crashes occasionally
https://bugs.kde.org/show_bug.cgi?id=433501 --- Comment #3 from 32299...@gmail.com --- I tried doing the above with a decompressed core dump, and it did not work, and ended with (gdb) bt #0 0x7f2474f9dbd0 in ?? () Backtrace stopped: Cannot access memory at address 0x7ffc4820e640 How would I analyze the core dumps in a way that will give useful results? The core dump also had the following in it: Failed to read a valid object file image from memory. Core was generated by `kwin_wayland --wayland_fd 4 --xwayland /usr/libexec/startplasma-waylandsession'. Program terminated with signal SIGSEGV, Segmentation fault. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 390147] Units::roundToIconSize returns incorrect result for SizeSmallMedium when screen scaling >= 2
https://bugs.kde.org/show_bug.cgi?id=390147 soredake changed: What|Removed |Added CC||ndrzj1...@relay.firefox.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 422567] Make everything in KRunner a little bit bigger to increase the speed of interaction
https://bugs.kde.org/show_bug.cgi?id=422567 soredake changed: What|Removed |Added CC||ndrzj1...@relay.firefox.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 433496] Im not an artist but all I have to say is that everything just turns black for me when I create or open a canvas
https://bugs.kde.org/show_bug.cgi?id=433496 --- Comment #3 from danylesp...@gmail.com --- Forgot to say that it dose not show bugs no errors or failures On Tue, 23 Feb 2021, 9:45 pm DAN LESPOIR, wrote: > I am not used to using email > > > I use my laptop I have integrated graphics and a Nvidia Graphics hard > Geforce mx110 but I mainly use my integrated but using changing between the > two has no difference and going to an older version works for some reason I > dont know if I'm doing g something wrong as I have little experience with > krita > > On Tue, 23 Feb 2021, 8:20 pm Halla Rempt, > wrote: > >> https://bugs.kde.org/show_bug.cgi?id=433496 >> >> Halla Rempt changed: >> >>What|Removed |Added >> >> >>Severity|major |normal >>Platform|Compiled Sources|Microsoft Windows >> Resolution|--- |WAITINGFORINFO >> CC||ha...@valdyas.org >> Status|REPORTED|NEEDSINFO >> >> --- Comment #1 from Halla Rempt --- >> Please provide the contents of >> >> help->system information for bug reports >> help->krita log for bug reports. >> >> Please explain what you mean with "I tried to change GPU" >> >> -- >> You are receiving this mail because: >> You reported the bug. > > -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 433498] Solution for fix krita maximize problem.
https://bugs.kde.org/show_bug.cgi?id=433498 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com --- Comment #1 from Tiar --- Hi, bugzilla is not a place to share workarounds and solutions for issues regarding Krita on a specific system. Please share them on krita-artists.org instead. if it turns out that a lot of people have the issue and this solution works for them, it can even be added to the manual. But this website is specifically for problems in Krita's code (development-oriented, not user-oriented). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 433496] Im not an artist but all I have to say is that everything just turns black for me when I create or open a canvas
https://bugs.kde.org/show_bug.cgi?id=433496 --- Comment #2 from danylesp...@gmail.com --- I am not used to using email I use my laptop I have integrated graphics and a Nvidia Graphics hard Geforce mx110 but I mainly use my integrated but using changing between the two has no difference and going to an older version works for some reason I dont know if I'm doing g something wrong as I have little experience with krita On Tue, 23 Feb 2021, 8:20 pm Halla Rempt, wrote: > https://bugs.kde.org/show_bug.cgi?id=433496 > > Halla Rempt changed: > >What|Removed |Added > > >Severity|major |normal >Platform|Compiled Sources|Microsoft Windows > Resolution|--- |WAITINGFORINFO > CC||ha...@valdyas.org > Status|REPORTED|NEEDSINFO > > --- Comment #1 from Halla Rempt --- > Please provide the contents of > > help->system information for bug reports > help->krita log for bug reports. > > Please explain what you mean with "I tried to change GPU" > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 388787] Support for C++17 new/delete
https://bugs.kde.org/show_bug.cgi?id=388787 Paul Floyd changed: What|Removed |Added Attachment #131600|0 |1 is obsolete|| --- Comment #10 from Paul Floyd --- Created attachment 136085 --> https://bugs.kde.org/attachment.cgi?id=136085=edit Update after feedback from Mark I think all items have been addressed except mismatch detection. I'd prefer open another bugzilla item for that. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433054] impossible unlock screen after upgrade to plasma 5.21
https://bugs.kde.org/show_bug.cgi?id=433054 Nate Graham changed: What|Removed |Added CC||tobi.goerg...@gmail.com --- Comment #28 from Nate Graham --- *** Bug 433495 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433495] Screen locker doesn't react to keyboard input when connected via receiver
https://bugs.kde.org/show_bug.cgi?id=433495 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||n...@kde.org --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 433054 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433501] kwin_wayland crashes occasionally
https://bugs.kde.org/show_bug.cgi?id=433501 Nate Graham changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||n...@kde.org Resolution|--- |WAITINGFORINFO --- Comment #2 from Nate Graham --- That's the whole core file, not the backtrace. You'll need to put it through gdb and run `bt` to get the backtrace itself. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432517] VLC launched from Dolphin doesn't close properly if there's certain widget
https://bugs.kde.org/show_bug.cgi?id=432517 Nate Graham changed: What|Removed |Added URL||https://gitlab.freedesktop. ||org/mesa/mesa/-/issues/116 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433490] Startup sound does not play with systemd startup enabled
https://bugs.kde.org/show_bug.cgi?id=433490 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433269] Blurry fractional scaling
https://bugs.kde.org/show_bug.cgi?id=433269 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=433115 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433115] Global Scaling Options Seems to "lower" resolution unlike old "force font DPI"; consider re-adding it as an option
https://bugs.kde.org/show_bug.cgi?id=433115 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=433269 --- Comment #13 from Nate Graham --- So basically you want to work around 433269. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 427038] Subwoofer speaker makes odd noise during sound check
https://bugs.kde.org/show_bug.cgi?id=427038 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REOPENED|NEEDSINFO --- Comment #5 from Nate Graham --- If you re-open a bug, please explain why. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433255] keyboard hotkeys not working after 5.21 update
https://bugs.kde.org/show_bug.cgi?id=433255 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |DUPLICATE Status|NEEDSINFO |RESOLVED --- Comment #3 from Nate Graham --- Ahh, so this was yet more fallout from Bug 431923. The ACPI stuff looks like it's happening at a deeper level than any of our software. Possibly the kernel. *** This bug has been marked as a duplicate of bug 431923 *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 431923] Keeping arrow keys pressed does nothing
https://bugs.kde.org/show_bug.cgi?id=431923 Nate Graham changed: What|Removed |Added CC||flyingwaf...@pm.me --- Comment #14 from Nate Graham --- *** Bug 433255 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 411189] Valgrind does not support POWER9 "DARN" RNG instructions
https://bugs.kde.org/show_bug.cgi?id=411189 Will Schmidt changed: What|Removed |Added CC||c...@us.ibm.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433502] Clipped error notice: There are two actions (New Tab, New Tab) that want to use the same shortcut (Ctrl+T). This is most probably a bug. Please report it in bugs.kde.org
https://bugs.kde.org/show_bug.cgi?id=433502 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||n...@kde.org --- Comment #2 from Nate Graham --- *** This bug has been marked as a duplicate of bug 398324 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 398324] Dophin has ambiguous shortcuts
https://bugs.kde.org/show_bug.cgi?id=398324 --- Comment #15 from Nate Graham --- *** Bug 433502 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433502] Clipped error notice: There are two actions (New Tab, New Tab) that want to use the same shortcut (Ctrl+T). This is most probably a bug. Please report it in bugs.kde.org
https://bugs.kde.org/show_bug.cgi?id=433502 --- Comment #1 from PvL --- There are two actions (New Tab, New Tab) that want to use the same shortcut (Ctrl+T). This is most probably a bug. Please report it in bugs.kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433501] kwin_wayland crashes occasionally
https://bugs.kde.org/show_bug.cgi?id=433501 --- Comment #1 from 32299...@gmail.com --- Unfortunately the core dump is too big to upload here, so I uploaded it to google drive. https://drive.google.com/file/d/1Vs-XbMT9UGxqZ7Hg-K9tzVjp90P8IVxJ/view?usp=sharing -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433499] Clipped error notice: There are two actions (New Tab, New Tab) that want to use the same shortcut (Ctrl+T). This is most probably a bug. Please report it in bugs.kde.org
https://bugs.kde.org/show_bug.cgi?id=433499 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 398324 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 398324] Dophin has ambiguous shortcuts
https://bugs.kde.org/show_bug.cgi?id=398324 Nate Graham changed: What|Removed |Added CC||sms.paul@gmail.com --- Comment #14 from Nate Graham --- *** Bug 433499 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 433500] DRD regtest faulures when libstdc++ and libgcc debuginfo are installed
https://bugs.kde.org/show_bug.cgi?id=433500 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr Assignee|jsew...@acm.org |m...@klomp.org -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433502] New: Clipped error notice: There are two actions (New Tab, New Tab) that want to use the same shortcut (Ctrl+T). This is most probably a bug. Please report it in bugs.kde.org
https://bugs.kde.org/show_bug.cgi?id=433502 Bug ID: 433502 Summary: Clipped error notice: There are two actions (New Tab, New Tab) that want to use the same shortcut (Ctrl+T). This is most probably a bug. Please report it in bugs.kde.org Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: sms.paul@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Component not listed see summary ver 18.08.0 Could also be related to error from Konqueror(v5.0.97) on some not all desktop launchers:"KDEInit could not launch 'konsole': Could not open library 'libkdeinit5_konsole'. Cannot load library libkdeinit5_konsole: (libkdeinit5_konsole: cannot open shared object file: No such file or directory) " SUMMARY STEPS TO REPRODUCE 1. Click on launcher 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433501] New: kwin_wayland crashes occasionally
https://bugs.kde.org/show_bug.cgi?id=433501 Bug ID: 433501 Summary: kwin_wayland crashes occasionally Product: kwin Version: 5.21.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: 32299...@gmail.com Target Milestone: --- SUMMARY occasionally, kwin_wayland crashes, bringing down the whole session and forcing one to restart. STEPS TO REPRODUCE 1. Use computer for a long while 2. After a time, kwin_wayland will crash and take down the whole session 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79 Qt Version: 5.15.2 ADDITIONAL INFORMATION I am running KDE from the zawertun/kde COPR. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 433500] New: DRD regtest faulures when libstdc++ and libgcc debuginfo are installed
https://bugs.kde.org/show_bug.cgi?id=433500 Bug ID: 433500 Summary: DRD regtest faulures when libstdc++ and libgcc debuginfo are installed Product: valgrind Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: pjfl...@wanadoo.fr Target Milestone: --- Valgrind compiled from git HEAD on Fedora 33 with gcc (GCC) 10.2.1 20201125 (Red Hat 10.2.1-9) If the following 2 packages are installed libstdc++-debuginfo.x86_64 libgcc-debuginfo.x86_64 then the following list of 14 DRD regression tests fail drd/tests/annotate_ignore_read (stderr) drd/tests/annotate_order_1 (stderr) drd/tests/annotate_order_2 (stderr) drd/tests/annotate_order_3 (stderr) drd/tests/annotate_smart_pointer (stderr) drd/tests/annotate_smart_pointer2(stderr) drd/tests/annotate_spinlock (stderr) drd/tests/annotate_static(stderr) drd/tests/bug322621 (stderr) drd/tests/concurrent_close (stderr) drd/tests/dlopen (stderr) drd/tests/pth_cancel_locked (stderr) drd/tests/pth_cleanup_handler(stderr) drd/tests/sem_wait (stderr) An example diff is paulf> cat annotate_ignore_read.stderr.diff --- annotate_ignore_read.stderr.exp 2017-11-11 10:43:44.152186306 +0100 +++ annotate_ignore_read.stderr.out 2021-02-23 16:57:25.402041732 +0100 @@ -1,4 +1,26 @@ + +parse DIE(readdwarf3.c:4085): confused by: + <3><55f9a2>: Abbrev Number: 64 (DW_TAG_subrange_type) + DW_AT_upper_bound : 2147483647 + DW_AT_name: (indirect string, offset: 0x): positive___XDLU_1__2147483647 + DW_AT_type: 0x + DW_AT_artificial : 1 +parse_type_DIE: +WARNING: Serious error when reading debug info +When reading debug info from /usr/lib64/libstdc++.so.6.0.28: +confused by the above DIE + +parse DIE(readdwarf3.c:4085): confused by: + <3><87da9>: Abbrev Number: 64 (DW_TAG_subrange_type) + DW_AT_upper_bound : 2147483647 + DW_AT_name: (indirect string, offset: 0x): positive___XDLU_1__2147483647 + DW_AT_type: 0x + DW_AT_artificial : 1 +parse_type_DIE: +WARNING: Serious error when reading debug info +When reading debug info from /usr/lib64/libgcc_s-10-20201125.so.1: +confused by the above DIE FLAGS [phb=1, fm=0] test69: negative GLOB=30 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433499] New: Clipped error notice: There are two actions (New Tab, New Tab) that want to use the same shortcut (Ctrl+T). This is most probably a bug. Please report it in bugs.kde.org
https://bugs.kde.org/show_bug.cgi?id=433499 Bug ID: 433499 Summary: Clipped error notice: There are two actions (New Tab, New Tab) that want to use the same shortcut (Ctrl+T). This is most probably a bug. Please report it in bugs.kde.org Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: sms.paul@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Component not listed see summary ver 18.08.0 SUMMARY STEPS TO REPRODUCE 1. Click on launcher 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 433096] Line Chart move too far ahead at the beginning and does not read value correctly
https://bugs.kde.org/show_bug.cgi?id=433096 --- Comment #3 from Andy Great --- (In reply to David Redondo from comment #2) > The legend thing was indeed a bug that was fixed. > > The fill behavior of the chart is intentional, it was the other way around > before. Alright, thanks for clarification. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 433498] Solution for fix krita maximize problem.
https://bugs.kde.org/show_bug.cgi?id=433498 Halla Rempt changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED CC||ha...@valdyas.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 433498] New: Solution for fix krita maximize problem.
https://bugs.kde.org/show_bug.cgi?id=433498 Bug ID: 433498 Summary: Solution for fix krita maximize problem. Product: krita Version: 4.4.2 Platform: Snap OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Resize/Scale Image/Layer Assignee: krita-bugs-n...@kde.org Reporter: ptawia...@gmail.com Target Milestone: --- SUMMARY This is the solution that worked for me on fixing krita not showing or allowing maximize for its window. STEPS TO REPRODUCE 1. Install krita snap package from snap store. 2. Run krita after installation. 3. When krita is fully loaded, check to see if maximize button is present. 4. If maximize button is present click to maximize. 5. If maximize button is not present, double click on title bar to maximize. OBSERVED RESULT For screens with limited area for krita to display its full window content, if maximize button show after first load, it disappears immediately when you try clicking on it. If no maximize button is present, double clicking on title bar does not maximize window. Like I said, this happens only when screen area is not enough to display full content of krita's window. SOLUTION 1. Open krita window. 2. Select view from the menu bar. 3. Remove tick from show status bar. This will immediately show maximize button or allow you to maximize window by double clicking on title bar. 4. To trick krita into allowing window maximization with status option ticked, select settings from the menu bar and chose reset krita configurations. 5. Select OK from the dialogue box that appears, then go back to view in the menu bar and place tick by show status bar. 6. Close krita window. 7. Open krita and you will still have button for maximize. NB: If you have messed up original krita windows parameters by manual resizing and you want to have the fresh look of krita back, then head over to your home folder and show hidden files/folders, open snap folder and delete the krita folder (that contains user configuration for krita). Then follow the steps in the solution as listed above. The deleted krita folder would be restored on next launch, only this time, with factory settings. SOFTWARE/OS VERSIONS Pop OS 20.04 LTS ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 430678] Allow to only enable specific external images
https://bugs.kde.org/show_bug.cgi?id=430678 --- Comment #6 from xdmx --- You are awesome, thank you! -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 433497] New: report upper bits of wait(2) status as undefined if `WIFSIGNALED(status)` is true
https://bugs.kde.org/show_bug.cgi?id=433497
Bug ID: 433497
Summary: report upper bits of wait(2) status as undefined if
`WIFSIGNALED(status)` is true
Product: valgrind
Version: unspecified
Platform: RedHat RPMs
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: memcheck
Assignee: jsew...@acm.org
Reporter: god...@gmail.com
Target Milestone: ---
SUMMARY
When a user program calls `wait()` where `status` is a variable, and if
the child process terminated with a signal, then a program should use the
`WIFSIGNALED` and `WTERMSIG` macros to extract the value of the signal that led
to its termination.
An erroneous program might instead compare status to a signal value, e.g. `if
(status == SIGFPE)`. However, the correct comparison should be `if
(WTERMSIG(status) == SIGFPE)` which is equivalent to `if (status & 07f ==
SIGFPE)` on (at least) CentOS 8 with its kernel + libc.
valgrind (wishlist here) could have custom logic that determines that the upper
bits in the status word returned from wait are undefined iff the lower 7 bits
are non-zero, which should flag the access as invalid reads. As is, it seems
to assume all bits are valid, despite the fact that the upper bits are
undefined.
This is of course custom to the specific version of Linux/libc that encodes the
wait status in this way, and may differ on other systems.
STEPS TO REPRODUCE
Compile and run this program:
#include
#include
#include
#include
#include
int
main()
{
if (fork() == 0) {
abort();
} else {
int status;
wait();
if (status == SIGABRT) // this line should be flagged
printf("Child aborted\n");
}
}
OBSERVED RESULT
No message.
EXPECTED RESULT
Conditional jump or move depends on uninitialised value.
SOFTWARE/OS VERSIONS
CentOS 8, valgrind 3.16
ADDITIONAL INFORMATION
This is obviously a wish for a corner case, but I'm wondering how much custom
logic there is for system calls. (I think ioctl()'s are another case but in the
opposite direction.)
--
You are receiving this mail because:
You are watching all bug changes.
[Breeze] [Bug 430944] LineEdits cannot be vertically aligned with ScrollViews with the new double-ringed focus highlight
https://bugs.kde.org/show_bug.cgi?id=430944 --- Comment #7 from Milian Wolff --- Indeed, to get a consistent look you have to either apply this style to *all* frames - otherwise things are bound to look odd one way or another. The only alternative is indeed growing inwards as @phd is suggesting. I personally also agree that ideally the corresponding change gets reverted from breeze until a proper solution is found. The current status quo is broken and has indeed a high potential for confusing novice developers into trying to workaround the alignment issues manually. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433306] Strange walk through windows behaviour
https://bugs.kde.org/show_bug.cgi?id=433306 Nate Graham changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 433037] Avatar does not preserve transparency in source image
https://bugs.kde.org/show_bug.cgi?id=433037 --- Comment #10 from Nate Graham --- Oops, forgot to move it. Thanks for doing so. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 433454] Clock on the locked screen
https://bugs.kde.org/show_bug.cgi?id=433454 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #4 from Nate Graham --- Ah, so you want the entire lock screen background to be a clock. I see, thanks. The lock screen accepts wallpaper plugins, so you or somebody else could create a wallpaper plugin that displays a giant clock and post it to store.kde.org, and then you could download it and use that on the lock screen to have what you want. This is the intended method for users to customize their lock screen. There are already a lot of nice wallpaper plugins available there. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 431707] setting new latency option to balance or other options even more in favor of latency causes frame drops in gaming on Wayland
https://bugs.kde.org/show_bug.cgi?id=431707 --- Comment #30 from Zamundaaa --- Turns out you haven't actually been using direct scanout because of what I assume to be a Wine bug. See (and test) https://invent.kde.org/plasma/kwin/-/merge_requests/728 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 433496] Im not an artist but all I have to say is that everything just turns black for me when I create or open a canvas
https://bugs.kde.org/show_bug.cgi?id=433496 Halla Rempt changed: What|Removed |Added Severity|major |normal Platform|Compiled Sources|Microsoft Windows Resolution|--- |WAITINGFORINFO CC||ha...@valdyas.org Status|REPORTED|NEEDSINFO --- Comment #1 from Halla Rempt --- Please provide the contents of help->system information for bug reports help->krita log for bug reports. Please explain what you mean with "I tried to change GPU" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 431446] Blinking panels and window contents not refreshing
https://bugs.kde.org/show_bug.cgi?id=431446 --- Comment #11 from vindicator --- Nope. KWIN_USE_BUFFER_AGE=0 didn't make any difference. I'm still in a flickering environment and can only see any updates in this browser tab if I max/restore this window. * $ KWIN_USE_BUFFER_AGE=0 kwin_x11 --replace & [1] 141797 kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5079:46: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5081:48: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5083:48: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5087:47: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5089:46: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5097:48: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5101:46: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5103:46: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5107:45: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: /usr/share/X11/locale/en_US.UTF-8/Compose:5110:46: this compose sequence is a duplicate of another; skipping line kwin_xkbcommon: XKB: Couldn't process include statement for 'us(\0)' kwin_xkbcommon: XKB: Abandoning symbols file "(unnamed)" kwin_xkbcommon: XKB: Failed to compile xkb_symbols kwin_xkbcommon: XKB: Failed to compile keymap kwin_core: XCB error: 10 (BadAccess), sequence: 2833, resource id: 308, major code: 142 (Composite), minor code: 2 (RedirectSubwindows) * * [ 69857.600] (II) intel(0): Modeline "1400x1050"x0.0 101.00 1400 1448 1480 1560 1050 1053 1057 1080 +hsync -vsync (64.7 kHz e) [ 70761.139] (EE) event3 - AT Translated Set 2 keyboard: client bug: event processing lagging behind by 23ms, your system is too slow [ 72240.460] (EE) intel(0): Failed to submit rendering commands (Bad address), disabling acceleration. [ 72385.800] (EE) event4 - Logitech M510: client bug: event processing lagging behind by 22ms, your system is too slow [ 72389.905] (EE) event4 - Logitech M510: client bug: event processing lagging behind by 15ms, your system is too slow [ 72566.569] (EE) event4 - Logitech M510: client bug: event processing lagging behind by 24ms, your system is too slow * With that "intel" error again, something is most definitely up with the driver I think. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 426770] pageStack.replace plays animation
https://bugs.kde.org/show_bug.cgi?id=426770 link...@testrun.org changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #5 from link...@testrun.org --- I can't test attached example with latest Kirigami because qmlscene from repositories does not run with it, but the bug remains in https://git.sr.ht/~link2xt/kdeltachat: every time chat is opened, an animation is played. With https://invent.kde.org/frameworks/kirigami/-/merge_requests/234 it works correctly. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 433459] Plasma Vault doesn't work with cryfs 0.11.0 (git version)
https://bugs.kde.org/show_bug.cgi?id=433459 Nate Graham changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |UPSTREAM Latest Commit||https://github.com/cryfs/cr ||yfs/commit/c6a69ae36bdfed8b ||274f1a608de11f0c0445407a --- Comment #2 from Nate Graham --- Fixed in cryfs with https://github.com/cryfs/cryfs/commit/c6a69ae36bdfed8b274f1a608de11f0c0445407a -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 431446] Blinking panels and window contents not refreshing
https://bugs.kde.org/show_bug.cgi?id=431446
vindicator changed:
What|Removed |Added
CC||nroycea+...@gmail.com
--- Comment #10 from vindicator ---
I think I have this issue as well, but I'm on 5.21.0.
I don't think I've experienced this "level" of an issue before and this is the
first time it's happened since I updated this past weekend.
My "normal" rendering issue comes from when I have "OpenGL" set as the
compositor.
Not immediately, but over time, I'll encounter rendering issues with video
playback that stutters/jitters/skips.
My "workaround" is simply to use "XRender" which is what I had done previously
(and it is still using xrender).
I'll also put out that that simply switching between OpenGL versions in the
compositor list sets things back on track... for awhile.
I am using X11. (I've learned my lesson with Wayland)
You stated that "restarting plasmashell" ("--replace"?) fixed it for you, but
not for me.
I also did a "replace" for kwin, but still no success.
While konsole rendered keystrokes just fine, no such luck with typing in Chrome
address bar.
One abnormal oddity that was probably leading up to the breakage (or letting me
know something was amiss before it all broke down) was while watching recorded
tv in kodi, there was some small/minor skippage (even though I was still using
xrender).
The only action I could take was CTRL-ALT-DEL my way to "logout".
Xorg:
"[ 68637.069] (EE) intel(0): Failed to submit rendering commands (Bad address),
disabling acceleration."
I don't know what time that was in relation to uptime.
Journalctl: (time which the clock stopped rendering was 09:07:##)
*
Feb 23 09:08:46 computerName plasmashell[1441]:
file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/main.qml:464:
TypeError: Cannot read property 'length' of undefined
Feb 23 09:07:57 computerName kwin_x11[1404]: qt.qpa.xcb: QXcbConnection: XCB
error: 9 (BadDrawable), sequence: 63014, resource id: 15333177, major code: 14
(GetGeometry), minor code: 0
Feb 23 09:07:57 computerName kwin_x11[1404]: qt.qpa.xcb: QXcbConnection: XCB
error: 3 (BadWindow), sequence: 63013, resource id: 15333177, major code: 3
(GetWindowAttributes), minor code: 0
Feb 23 09:07:55 computerName kwin_x11[1404]: qt.qpa.xcb: QXcbConnection: XCB
error: 9 (BadDrawable), sequence: 62514, resource id: 15333173, major code: 14
(GetGeometry), minor code: 0
Feb 23 09:07:55 computerName kwin_x11[1404]: qt.qpa.xcb: QXcbConnection: XCB
error: 3 (BadWindow), sequence: 62513, resource id: 15333173, major code: 3
(GetWindowAttributes), minor code: 0
Feb 23 09:05:06 computerName plasmashell[1441]:
file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15:
QML QQuickItem: Binding loop detected for property "height"
*
If it happens again, THEN I'll give "KWIN_USE_BUFFER_AGE=0" a try. This may
just be a one-off for me.
I don't know if you'll still see this, but it just happened while I went to
another tab to look at other bugs. I'm going to try to save this.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 433306] Strange walk through windows behaviour
https://bugs.kde.org/show_bug.cgi?id=433306 --- Comment #2 from Duns --- Uhm ... no, I don't think so. This bug is regardless from windows minimization or not. And it begins only 7/8 days ago or so. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422948] Startup sound does not play; system muted until after login
https://bugs.kde.org/show_bug.cgi?id=422948 --- Comment #80 from jmdkde --- All is ok for me ! Operating System: Arch Linux KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.10.16-arch1-1 OS Type: 64-bit Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 2600X Six-Core Processor Memory: 15.6 Gio of RAM Graphics Processor: GeForce GTX 1650 SUPER/PCIe/SSE2 Le mar. 23 févr. 2021 à 15:46, phd a écrit : > https://bugs.kde.org/show_bug.cgi?id=422948 > > phd changed: > >What|Removed |Added > > >See Also|| > https://bugs.kde.org/show_b >||ug.cgi?id=433490 > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 433454] Clock on the locked screen
https://bugs.kde.org/show_bug.cgi?id=433454 Dmitri Koulikoff changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Dmitri Koulikoff --- No, I mean the real old clock as on the picture. The option to *show* the clock works. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 430889] ssl certificate always requested in localhost
https://bugs.kde.org/show_bug.cgi?id=430889 --- Comment #2 from Duns --- nobody answers? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 433454] Clock on the locked screen
https://bugs.kde.org/show_bug.cgi?id=433454 --- Comment #2 from Dmitri Koulikoff --- Created attachment 136083 --> https://bugs.kde.org/attachment.cgi?id=136083=edit Clock screen lock Clock as screen lock -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 433496] New: Im not an artist but all I have to say is that everything just turns black for me when I create or open a canvas
https://bugs.kde.org/show_bug.cgi?id=433496 Bug ID: 433496 Summary: Im not an artist but all I have to say is that everything just turns black for me when I create or open a canvas Product: krita Version: 4.4.3-beta1 Platform: Compiled Sources OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: danylesp...@gmail.com Target Milestone: --- My screen turns black when a canvas is open and I just updated to 4.4.2 I tried to take a Screen shot but its turn to normal the second I do. if this is only for me I tried to change GPU but it still happens -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 433037] Avatar does not preserve transparency in source image
https://bugs.kde.org/show_bug.cgi?id=433037 --- Comment #9 from Mikel Johnson --- I think we'd wanna change the default to maintain consistency -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 433452] Power management ignores sleep and screen locking suppression
https://bugs.kde.org/show_bug.cgi?id=433452 Kai Uwe Broulik changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #5 from Kai Uwe Broulik --- Oh, I think I know what's going on: KScreenLocker asks PowerDevil for inhibitions and PowerDevil just sends them all out, no matter if they are screen or suspend. I guess that needs to be split. I've wanted to do that for a while so Battery Monitor can also show that in more detail. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 433037] Avatar does not preserve transparency in source image
https://bugs.kde.org/show_bug.cgi?id=433037 Mikel Johnson changed: What|Removed |Added Component|Application Launcher|general |(Kickoff) | Assignee|k...@davidedmundson.co.uk|notm...@gmail.com Version|5.21.0 |Master Product|plasmashell |frameworks-kirigami -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 433452] Power management ignores sleep and screen locking suppression
https://bugs.kde.org/show_bug.cgi?id=433452 --- Comment #4 from Wyatt Childers --- (In reply to Kai Uwe Broulik from comment #3) > Why should the screen not turn off when playing *music*? The bug I see here > is that the screen does not lock even though the screen turns off. See my second comment :) > It may be the case that this should actually be filed against the screen > locker. > I'm unsure if there is a specific kind of power suppression that should > suppress > sleep but not screen off -- if so, this is definitely an issue there instead. Testing quickly with a video in Firefox, the screen does not turn off. So I'm guessing it is the case that there is some way of differentiating? In which case this should probably be moved? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 411189] Valgrind does not support POWER9 "DARN" RNG instructions
https://bugs.kde.org/show_bug.cgi?id=411189 Will Schmidt changed: What|Removed |Added CC||will_schm...@vnet.ibm.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433495] New: Screen locker doesn't react to keyboard input when connected via receiver
https://bugs.kde.org/show_bug.cgi?id=433495 Bug ID: 433495 Summary: Screen locker doesn't react to keyboard input when connected via receiver Product: kwin Version: 5.21.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: platform-x11-standalone Assignee: kwin-bugs-n...@kde.org Reporter: tobi.goerg...@gmail.com Target Milestone: --- SUMMARY When the screen is locked automatically while receiver + TV are turned off, the lock screen is freezed at the time the TV + receiver is turned on again. Entering the password works though, but there's no text field shown. The mouse cursor is visible and movable. A video is available here, showing the issue: https://youtu.be/HSTeyBRhTys STEPS TO REPRODUCE 1. Connect PC to receiver 2. Set automatic screen locker 3. Turn off TV + receiver 4. Wait until screen is locked 5. Turn on TV + receiver 6. Observe OBSERVED RESULT The lock screen is freezed EXPECTED RESULT The lock screen is not freezed, reacts to user input, shows text field and updates time SOFTWARE/OS VERSIONS Windows: macOS: Operating System: openSUSE Tumbleweed 20210220 KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.10.16-1-default OS Type: 64-bit Graphics Platform: X11 Processors: 8 × AMD Ryzen 5 2400G with Radeon Vega Graphics Memory: 5.7 GiB of RAM Graphics Processor: AMD Radeon™ Vega 11 Graphics ADDITIONAL INFORMATION If there's any way to take a log of it, I'd like to. A video is available here: https://youtu.be/HSTeyBRhTys -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377799] Plasmashell crash due to invalid receiver in posted event
https://bugs.kde.org/show_bug.cgi?id=377799 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #4 from Nate Graham --- Ok cool, thanks! -- You are receiving this mail because: You are watching all bug changes.
[policykit-kde-agent-1] [Bug 433374] PolicyKit doesn't show the user whose password it's requesting when there is only one administrator account and you're not using it
https://bugs.kde.org/show_bug.cgi?id=433374 Nate Graham changed: What|Removed |Added Summary|PolicyKit doesn't show the |PolicyKit doesn't show the |user it ask for a password |user whose password it's |for |requesting when there is ||only one administrator ||account and you're not ||using it Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- Keywords||usability --- Comment #5 from Nate Graham --- Thanks, that makes sense. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 433494] New: No power off or restart within the 90 second timeout
https://bugs.kde.org/show_bug.cgi?id=433494 Bug ID: 433494 Summary: No power off or restart within the 90 second timeout Product: ksmserver Version: 5.20.5 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: marco.a...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- When logged, in I choose from the Menu "Leave -> Shutdown/Restart" but to get the system shutdown/restarted it takes about 90 seconds (which is the timeout configured in systemd or such). If I use "Leave -> Logout" and then hit shutdown/restart from sddm login screen I can logout in a couple of seconds and shutdown in a couple more (less than 10 seconds from clicking Logout to power-off/restart including my clicking in sddm). I have disabled restore previous session in KDE settings as I red this could cause issues with no joy. STEPS TO REPRODUCE 1. Log in to a session 2. Click "Leave -> shutdown" or "Leave -> restart" OBSERVED RESULT I get logged out straight away and see the console messages that were printed at start up for about 90 seconds (which is the timeout configured in systemd or such) then the system is powered off/restarted. EXPECTED RESULT I get logged out straight away and see the system powered off/restarted in a few seconds. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Debian bullseye - kernel 5.10.0-3-amd64 Using wayland. Using sddm as login manager. Used 'journalctl -rb -1' to check what happens at shutdown but can't see anything wrong or holding up shutdown process. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433307] Have the same corner radius for all 4 window corners
https://bugs.kde.org/show_bug.cgi?id=433307 --- Comment #6 from Nate Graham --- Yes, when a window is tiled, maximized, or full screen, we would not round the corners. In fact we already do this for the top corners. So we would continue to do that for the rounded bottom corners too. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 411189] Valgrind does not support POWER9 "DARN" RNG instructions
https://bugs.kde.org/show_bug.cgi?id=411189 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #3 from Mark Wielaard --- This doesn't solve this bug, DARN is still not implemented, but now valgrind will not advertise DARN is available so programs should not use it when running under valgrind. commit ea98cccb4d50a8740708507c4c72cfb1e6c88e38 Author: Mark Wielaard Date: Tue Feb 23 16:19:26 2021 +0100 Filter out unsupported instructions from HWCAP2 on powerpc. Valgrind currently doesn't support the DARN random number instruction and the SCV syscall instruction. Filter them out of HWCAP2 so glibc and applications don't try to use them when running under valgrind. Also suppress printing a log message for scv instructions in the instruction stream. Reported by: Florian Weimer DARN bug: https://bugs.kde.org/show_bug.cgi?id=411189 SCV bug: https://bugs.kde.org/show_bug.cgi?id=431157 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 431157] PPC_FEATURE2_SCV needs to be masked in AT_HWCAP2
https://bugs.kde.org/show_bug.cgi?id=431157 --- Comment #17 from Mark Wielaard --- For now I have pushed this commit: commit ea98cccb4d50a8740708507c4c72cfb1e6c88e38 Author: Mark Wielaard Date: Tue Feb 23 16:19:26 2021 +0100 Filter out unsupported instructions from HWCAP2 on powerpc. Valgrind currently doesn't support the DARN random number instruction and the SCV syscall instruction. Filter them out of HWCAP2 so glibc and applications don't try to use them when running under valgrind. Also suppress printing a log message for scv instructions in the instruction stream. Reported by: Florian Weimer DARN bug: https://bugs.kde.org/show_bug.cgi?id=411189 SCV bug: https://bugs.kde.org/show_bug.cgi?id=431157 When SCV is implemented it can be added to HWCAPS2 again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433037] Avatar does not preserve transparency in source image
https://bugs.kde.org/show_bug.cgi?id=433037 --- Comment #8 from Nate Graham --- background.color: is not a valid public property. color: is a public property, but overriding that to be transparent impacts the appearance of the auto-generated image, which is not desired. I cannot find a way to use the existing API to preserve transparency for non-auto-generated backgrounds. without impacting the auto-generated ones. Moving back to Kirigami. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432517] VLC launched from Dolphin doesn't close properly if there's certain widget
https://bugs.kde.org/show_bug.cgi?id=432517 --- Comment #4 from David --- Turns out in the end it's a bug with mesa, not KDE or QT: https://gitlab.freedesktop.org/mesa/mesa/-/issues/116 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433493] New: [wayland] Cannot Drag Windows Across Desktops in 5.21 Wayland using KWin Shortcuts
https://bugs.kde.org/show_bug.cgi?id=433493
Bug ID: 433493
Summary: [wayland] Cannot Drag Windows Across Desktops in 5.21
Wayland using KWin Shortcuts
Product: kwin
Version: 5.21.0
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: wayland-generic
Assignee: kwin-bugs-n...@kde.org
Reporter: evanmol...@gmail.com
Target Milestone: ---
SUMMARY
In wayland on 5.21, you cannot drag a window to another desktop using KWin
shortcuts to switch the desktop. The shortcuts don't work while holding a
window, but function fine if you aren't.
Shortcut located at:
Settings -> Workspace -> Shortcuts -> System Services -> KWin -> "Switch One
Desktop to the Right"
STEPS TO REPRODUCE
1. Bind Switch One Desktop to the Right to any key, I use Meta+Tab.
2. Next, try to "drag" a window to a different desktop by holding a window and
then hitting the next-desktop key.
3. When you press your "Switch One Desktop to the Right" key, nothing will
happen if you are holding a window. If you are not holding a window, then the
desktop will switch as expected.
OBSERVED RESULT
Switch-Desktop shortcut keys do not work while holding/dragging a window in
Wayland. The key functions as expected otherwise.
EXPECTED RESULT
Switch Desktop shortcut keys should switch to your next desktop while dragging
a window, allowing you to drag a window to a different desktop.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch
KDE Plasma Version: 5.21.0
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2
ADDITIONAL INFORMATION
GPU: Radeon RX 590
Two monitors: {1920x1080@60hz-Left, 2560x1440@144hz-Right}
--
You are receiving this mail because:
You are watching all bug changes.
[plasma-systemmonitor] [Bug 433096] Line Chart move too far ahead at the beginning and does not read value correctly
https://bugs.kde.org/show_bug.cgi?id=433096 David Redondo changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED CC||k...@david-redondo.de --- Comment #2 from David Redondo --- The legend thing was indeed a bug that was fixed. The fill behavior of the chart is intentional, it was the other way around before. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433037] Avatar does not preserve transparency in source image
https://bugs.kde.org/show_bug.cgi?id=433037 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Severity|normal |minor -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433037] Avatar does not preserve transparency in source image
https://bugs.kde.org/show_bug.cgi?id=433037 Nate Graham changed: What|Removed |Added Resolution|INTENTIONAL |--- Status|RESOLVED|REPORTED Component|general |Application Launcher ||(Kickoff) Assignee|notm...@gmail.com |k...@davidedmundson.co.uk Ever confirmed|1 |0 Version|Master |5.21.0 Product|frameworks-kirigami |plasmashell --- Comment #7 from Nate Graham --- Thanks. Moving back to Kickoff. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 433492] New: Audio track defective after changes
https://bugs.kde.org/show_bug.cgi?id=433492 Bug ID: 433492 Summary: Audio track defective after changes Product: kdenlive Version: 20.12.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: gerd.mun...@bigpond.com Target Milestone: --- Created attachment 136082 --> https://bugs.kde.org/attachment.cgi?id=136082=edit Screenshot of faulty clips in track SUMMARY Bits of the audio track are missing except for some and some markings where there had been audio clips STEPS TO REPRODUCE 1. An audio mp3 file was loaded into project bin 2. The audio clip was introduced into audio track 3. The clip in the audio track was cut up and bits of it were distributed to match the video clips 4.The project was saved and closed 5. The audio mp3 file was edited by adding additional content. 6. When the project was restarted again most of the bits of clips in the audio track had vanished with just vertical markers remaining where the bits had been before. OBSERVED RESULT Where there had been audio clips before nothing but markers of the beginning and end remained EXPECTED RESULT The audio track should have been the same as before cahnging the audio file. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Leap 15.2/5.18.6 (available in About System) KDE Plasma Version: 5.18.6 KDE Frameworks Version: 5.71.0 Qt Version: 5.12.7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdeclarative] [Bug 417636] Title rows of QML KCMs fade in and out, but others don't
https://bugs.kde.org/show_bug.cgi?id=417636 Nate Graham changed: What|Removed |Added Summary|Titles of QML KCMs fade in |Title rows of QML KCMs fade |and out, but others don't |in and out, but others ||don't Severity|minor |normal Status|REOPENED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 433491] New: Crash when open start menu
https://bugs.kde.org/show_bug.cgi?id=433491 Bug ID: 433491 Summary: Crash when open start menu Product: konqueror Version: 5.0.97 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: 526512...@qq.com Target Milestone: --- Application: konqueror (5.0.97) Qt Version: 5.12.8 Frameworks Version: 5.68.0 Operating System: Linux 5.4.0-65-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.04.2 LTS -- Information about the crash: - What I was doing when the application crashed: click start ,click konqueror in favorite sheet - Unusual behavior I noticed: prompt me how to open bookmarks:/ . then click third button, it crash. - Custom settings of the application: no The crash can be reproduced every time. -- Backtrace: Application: Konqueror (konqueror), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8db2e4e000 (LWP 9472))] Thread 22 (Thread 0x7f8d1f7fe700 (LWP 9518)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7f8d1f7fdb60, clockid=, expected=0, futex_word=0x7f8d1f7fdca8) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7f8d1f7fdb60, clockid=, mutex=0x7f8d1f7fdc58, cond=0x7f8d1f7fdc80) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x7f8d1f7fdc80, mutex=0x7f8d1f7fdc58, abstime=0x7f8d1f7fdb60) at pthread_cond_wait.c:656 #3 0x7f8d837f9b2e in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f8d837fa51f in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f8d837fa615 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f8d837bbda6 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f8d837be939 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f8d837beef8 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f8d837fcb63 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f8db587c609 in start_thread (arg=) at pthread_create.c:477 #11 0x7f8db9009293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 21 (Thread 0x7f8d1700 (LWP 9504)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x7f8d1fffecb8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f8d1fffec68, cond=0x7f8d1fffec90) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x7f8d1fffec90, mutex=0x7f8d1fffec68) at pthread_cond_wait.c:638 #3 0x7f8d837f9a5e in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f8d837fa530 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f8d837fa5d3 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f8d837bbdb8 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f8d837bec48 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f8d837befb8 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f8d837fcb63 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f8db587c609 in start_thread (arg=) at pthread_create.c:477 #11 0x7f8db9009293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 20 (Thread 0x7f8d5cff9700 (LWP 9503)): #0 __lll_lock_wait_private (futex=0x7f8db90d54b0 <_IO_stdfile_2_lock>) at ./lowlevellock.c:35 #1 0x7f8db8f641f6 in buffered_vfprintf (s=s@entry=0x7f8db90d35c0 <_IO_2_1_stderr_>, format=format@entry=0x7f8d97bd7258 "[%s] %s\n", args=args@entry=0x7f8d5cff85b0, mode_flags=mode_flags@entry=2) at vfprintf-internal.c:2381 #2 0x7f8db8f60ea4 in __vfprintf_internal (s=0x7f8db90d35c0 <_IO_2_1_stderr_>, format=0x7f8d97bd7258 "[%s] %s\n", ap=ap@entry=0x7f8d5cff85b0, mode_flags=2) at vfprintf-internal.c:1346 #3 0x7f8db90181b3 in ___fprintf_chk (fp=, flag=, format=) at fprintf_chk.c:33 #4 0x7f8d97bbdb36 in event_logv_ () from /lib/x86_64-linux-gnu/libevent-2.1.so.7 #5 0x7f8d97bbdd09 in event_warn () from /lib/x86_64-linux-gnu/libevent-2.1.so.7 #6 0x7f8d97bbf768 in ?? () from /lib/x86_64-linux-gnu/libevent-2.1.so.7 #7 0x7f8d97bb5625 in event_base_loop () from /lib/x86_64-linux-gnu/libevent-2.1.so.7 #8 0x7f8d83800318 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f8d83799e9f in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f8d837c47e1 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #11 0x7f8d837fcb63 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #12 0x7f8db587c609 in start_thread (arg=) at pthread_create.c:477 #13 0x7f8db9009293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread
[frameworks-kdeclarative] [Bug 417636] Titles of QML KCMs fade in and out, but others don't
https://bugs.kde.org/show_bug.cgi?id=417636 Nate Graham changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #8 from Nate Graham --- Oh no, sorry. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 433445] Autostarted applications show incorrect application name
https://bugs.kde.org/show_bug.cgi?id=433445 --- Comment #2 from Isaac Wismer --- I have 247.3, so it looks like that commit should fix it in 248. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422948] Startup sound does not play; system muted until after login
https://bugs.kde.org/show_bug.cgi?id=422948 phd changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=433490 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433490] Startup sound does not play with systemd startup enabled
https://bugs.kde.org/show_bug.cgi?id=433490 phd changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=422948 CC||p...@phd.re -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 347920] Edge sharpening for circle brush tip (watercolor-like effect)
https://bugs.kde.org/show_bug.cgi?id=347920 Helge Hielscher changed: What|Removed |Added CC||hhielsc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 357493] Remember color history after reopening a document
https://bugs.kde.org/show_bug.cgi?id=357493 Helge Hielscher changed: What|Removed |Added CC||hhielsc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 343531] Krita can't select colours outside of sRGB because of dodgy colour selector design.
https://bugs.kde.org/show_bug.cgi?id=343531 Helge Hielscher changed: What|Removed |Added CC||hhielsc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 433459] Plasma Vault doesn't work with cryfs 0.11.0 (git version)
https://bugs.kde.org/show_bug.cgi?id=433459 Nate Graham changed: What|Removed |Added Severity|normal |critical CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361706] [NTRIG] Krita does not recognize a right click performed by Surface Pen while on canvas
https://bugs.kde.org/show_bug.cgi?id=361706 Helge Hielscher changed: What|Removed |Added CC||hhielsc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 224523] Read metadata from PDF file
https://bugs.kde.org/show_bug.cgi?id=224523 Helge Hielscher changed: What|Removed |Added CC||hhielsc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 360541] HiDPI option in Qt also scales the canvas widget
https://bugs.kde.org/show_bug.cgi?id=360541 Helge Hielscher changed: What|Removed |Added CC||hhielsc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 122812] Scanning interface from within Krita
https://bugs.kde.org/show_bug.cgi?id=122812 Helge Hielscher changed: What|Removed |Added CC||hhielsc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
