[kde] [Bug 469349] Custom Shortcuts gobble "keyboard input" letter
https://bugs.kde.org/show_bug.cgi?id=469349
--- Comment #4 from Jaggz H. ---
I created them in the normal Settings -> Shortcuts -> Custom Shortcuts.
I created a New Global Shortcut -> Keyboard Input
Email address is like:
M:Y:E:M:A:I:L:Shift+2:G:M:A:I:L:.:C:O:M (that first 'm' never gets sent)
Trigger:
Meta+Ctrl+Shift+j (j for jaggz)
With the following information, from my testing, it seems it Might have
something to do with the modifier keys used in the trigger...
I have another keyboard input shortcut (created like normal, and assigned to a
single key on my keyboard; ie. no modifiers);
this shortcut sends out "^A^A" (I use it so a single key can toggle my tmux
panes). Thus, its entry in the shortcut's action area is:
Ctrl+A:Ctrl+A
When I use it I get an 'a' (letter) output into Konsole. Actually what it
sends out is the 'a' followed by a ^A.
So it seems the initial "Ctrl" in the shortcut action is being lost somehow.
Notice the first letter of those other macros is being lost.
But, if I use the keystroke again it works fine, even if I type normal things
in-between.
It'll keep working after that, until I use one of the Meta+Ctrl+Shift
shortcuts. If I use one of them, this single-key assigned to ^A^A puts out the
a^A again.
Another note: I made a new hotkey T:E:S:T, assigned to a single key on the
keyboard. It outputs fine. And the single key for ^A^A works after it too.
So, it does seem like something with the modifier keys in the other macros
might be related.
Also, they don't look weird in khotkeysrc:
[Data_4_12Triggers]
Comment=Simple_action
TriggersCount=1
[Data_4_12Triggers0]
Key=Meta+Ctrl+Shift+J
Type=SHORTCUT
Uuid={.uuid here.}
...
[Data_4_12Actions0]
DestinationWindow=0
Input=J:A:G:G:Z:.:H:Shift+2:G:M:A:I:L:.:C:O:M
Type=KEYBOARD_INPUT
...
[Data_4_35Actions0]
DestinationWindow=0
Input=T:E:S:T
Type=KEYBOARD_INPUT
So, it seems these modifier sequences somehow mess something up.
Last note: the email outputs (using modifiers) never work. They *always* skip
the first letter no matter what I've tried.
--
You are receiving this mail because:
You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 470504] New: Dolphin crashed when I use KDE partion manager to create volume system or modify partion table on a ndb device
https://bugs.kde.org/show_bug.cgi?id=470504 Bug ID: 470504 Summary: Dolphin crashed when I use KDE partion manager to create volume system or modify partion table on a ndb device Classification: Applications Product: dolphin Version: 23.04.1 Platform: Archlinux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: typeryougish...@163.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (23.04.1) Qt Version: 5.15.9 Frameworks Version: 5.106.0 Operating System: Linux 6.3.5-zen1-1-zen x86_64 Windowing System: X11 Distribution: "Arch Linux" DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: I use qemu-nbd to connect a raw file to /dev/nbd0. Then when I use KDE partion manager to modify partion tabe, Dolphin crashed. Before this time, it also crashed when using KDE partion manager to create volume system on the same device The crash can be reproduced sometimes. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x7f34ed884710 in Solid::Device::isValid() const () from /usr/lib/libKF5Solid.so.5 #5 0x7f34ede5594c in ?? () from /usr/lib/libKF5KIOFileWidgets.so.5 #6 0x7f34ede5d6fd in KFilePlacesModel::closestItem(QUrl const&) const () from /usr/lib/libKF5KIOFileWidgets.so.5 #7 0x7f34ede8931b in ?? () from /usr/lib/libKF5KIOFileWidgets.so.5 #8 0x7f34ede8edfe in ?? () from /usr/lib/libKF5KIOFileWidgets.so.5 #9 0x7f34ebccffe7 in ?? () from /usr/lib/libQt5Core.so.5 #10 0x7f34ebc567c3 in QAbstractItemModel::rowsRemoved(QModelIndex const&, int, int, QAbstractItemModel::QPrivateSignal) () from /usr/lib/libQt5Core.so.5 #11 0x7f34ebc56927 in QAbstractItemModel::endRemoveRows() () from /usr/lib/libQt5Core.so.5 #12 0x7f34ede59295 in ?? () from /usr/lib/libKF5KIOFileWidgets.so.5 #13 0x7f34ebccffe7 in ?? () from /usr/lib/libQt5Core.so.5 #14 0x7f34ed883f2a in Solid::DeviceNotifier::deviceRemoved(QString const&) () from /usr/lib/libKF5Solid.so.5 #15 0x7f34ebcd01a3 in ?? () from /usr/lib/libQt5Core.so.5 #16 0x7f34ed878d1a in ?? () from /usr/lib/libKF5Solid.so.5 #17 0x7f34ed8772c0 in ?? () from /usr/lib/libKF5Solid.so.5 #18 0x7f34ebcd01a3 in ?? () from /usr/lib/libQt5Core.so.5 #19 0x7f34ed87397a in ?? () from /usr/lib/libKF5Solid.so.5 #20 0x7f34ed874593 in ?? () from /usr/lib/libKF5Solid.so.5 #21 0x7f34ed0ba43e in ?? () from /usr/lib/libQt5DBus.so.5 #22 0x7f34ebcc2834 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #23 0x7f34ec97893f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #24 0x7f34ebc9ab18 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #25 0x7f34ebc9fa7b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQt5Core.so.5 #26 0x7f34ebce6088 in ?? () from /usr/lib/libQt5Core.so.5 #27 0x7f34e9b10981 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #28 0x7f34e9b6db39 in ?? () from /usr/lib/libglib-2.0.so.0 #29 0x7f34e9b0e032 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #30 0x7f34ebce9f0c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #31 0x7f34ebc99824 in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #32 0x7f34ebc9acc3 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #33 0x55868131bda8 in ?? () #34 0x7f34eb439850 in ?? () from /usr/lib/libc.so.6 #35 0x7f34eb43990a in __libc_start_main () from /usr/lib/libc.so.6 #36 0x55868131c565 in ?? () [Inferior 1 (process 48984) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 462931] "No metadata URIs for vendor directory" error seen in Discover for disabled fwupd repo
https://bugs.kde.org/show_bug.cgi?id=462931 Boba Fit changed: What|Removed |Added CC||boba_...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 126942] Kghostview can't show any overprint preview
https://bugs.kde.org/show_bug.cgi?id=126942 Bernard Gray changed: What|Removed |Added Version|0.15.2 |21.12.3 --- Comment #2 from Bernard Gray --- I have raised this request in the okular mailing list: https://mail.kde.org/pipermail/okular-devel/2023-May/044525.html Oliver Sander has indicated that (some level of) overprint support exists in poppler: > See for example the manpage of pdftops. Ref: https://mail.kde.org/pipermail/okular-devel/2023-May/044531.html They have directed me to raise an issue here - I will crosslink this bug back to the mailing list and see if it can get some movement :) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 126942] Kghostview can't show any overprint preview
https://bugs.kde.org/show_bug.cgi?id=126942 Bernard Gray changed: What|Removed |Added CC||bernard.g...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 421245] Add save tabs feature (like in Dolphin)
https://bugs.kde.org/show_bug.cgi?id=421245 --- Comment #10 from avlas --- (In reply to Stefano Crocco from comment #9) > (In reply to avlas from comment #8) > > (In reply to Stefano Crocco from comment #7) > > I guess that to reproduce the issue you probably need to: > > > > 1. check the option to restore tabs in settings > > 2. open some tabs > > 3. close konqueror > > 4. click on the email link > > > > Could you please try to reproduce following these steps? > > That's what I already tried. I checked again, with both my current user and > a new user and the results are the same I already described: a new window > with only the page corresponding to the link. I'll look again into this > issue during the weekend, but I really can't think of something leading to > the behavior you're describing. I see. I think you may also need to check the setting to open links in new tabs instead of in new windows. Can you try? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399913] Make drag drop, copy and paste work more transparently with desktop/filemanager
https://bugs.kde.org/show_bug.cgi?id=399913 --- Comment #7 from caulier.gil...@gmail.com --- >On my laptop it even freezes the whole system. I have to reboot!! It freezes ??? Seriously, i never seen that... What's your laptop OS exactly ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461427] Native Wayland apps appear blurry after switching off and on a display with scaling enabled
https://bugs.kde.org/show_bug.cgi?id=461427 Iyán Méndez Veiga changed: What|Removed |Added CC||m...@iyanmv.com --- Comment #6 from Iyán Méndez Veiga --- I can replicate this with a AMD GPU but not on my laptop with integrated Intel GPU. And it seems like all other reports also have AMD GPUs. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399913] Make drag drop, copy and paste work more transparently with desktop/filemanager
https://bugs.kde.org/show_bug.cgi?id=399913 --- Comment #6 from b...@bertenselena.net --- Hello Gilles, I checked on both my laptop and desktop. On both Drag & drop from Digikam to the desktop or to the filemanager does not work. On my laptop it even freezes the whole system. I have to reboot!! I also noticed both on the laptop and desktop that D&D between folders in Digikam itself doesn't work anymore for me. I get a tiny no-access sign when I drag a photo to a folder and the folder tree when I hover with my mouse over a folder. Strangely, copy-paste into one of the folders does work, so it is not a write-access issue. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 466149] On Xorg, Plasma's idea of the monitor configuration differs from xrandr's
https://bugs.kde.org/show_bug.cgi?id=466149 --- Comment #19 from zyf0330 --- (In reply to Tupac from comment #18) > (In reply to zyf0330 from comment #17) > > What is your `xrandr` output > > Screen 0: minimum 16 x 16, current 3532 x 1080, maximum 32767 x 32767 > XWAYLAND0 connected 1600x900+0+90 (normal left inverted right x axis y axis) > 380mm x 210mm >1600x900 74.89*+ >1152x864 74.82 >1024x768 74.90 >800x600 74.91 >640x480 74.77 >320x240 73.82 >1440x900 74.98 >1280x800 74.93 >720x480 74.51 >640x400 74.23 >320x200 73.70 >1368x768 74.90 >1280x720 74.78 >1024x576 74.80 >864x486 74.45 >720x400 74.23 >640x350 74.53 > XWAYLAND1 connected 1920x1080+1612+0 (normal left inverted right x axis y > axis) 530mm x 300mm >1920x1080 74.91*+ >1440x1080 74.92 >1400x1050 74.87 >1280x1024 74.90 >1280x960 74.86 >1152x864 74.82 >1024x768 74.90 >800x600 74.91 >640x480 74.77 >320x240 73.82 >1680x1050 74.89 >1440x900 74.98 >1280x800 74.93 >720x480 74.51 >640x400 74.23 >320x200 73.70 >1600x900 74.89 >1368x768 74.90 >1280x720 74.78 >1024x576 74.80 >864x486 74.45 >720x400 74.23 >640x350 74.53 It seems that, screen number is opposite in the Wayland to Xserver. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470342] digikam dont start
https://bugs.kde.org/show_bug.cgi?id=470342 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Portability-Runtime CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 466149] On Xorg, Plasma's idea of the monitor configuration differs from xrandr's
https://bugs.kde.org/show_bug.cgi?id=466149 --- Comment #18 from Tupac --- (In reply to zyf0330 from comment #17) > What is your `xrandr` output Screen 0: minimum 16 x 16, current 3532 x 1080, maximum 32767 x 32767 XWAYLAND0 connected 1600x900+0+90 (normal left inverted right x axis y axis) 380mm x 210mm 1600x900 74.89*+ 1152x864 74.82 1024x768 74.90 800x600 74.91 640x480 74.77 320x240 73.82 1440x900 74.98 1280x800 74.93 720x480 74.51 640x400 74.23 320x200 73.70 1368x768 74.90 1280x720 74.78 1024x576 74.80 864x486 74.45 720x400 74.23 640x350 74.53 XWAYLAND1 connected 1920x1080+1612+0 (normal left inverted right x axis y axis) 530mm x 300mm 1920x1080 74.91*+ 1440x1080 74.92 1400x1050 74.87 1280x1024 74.90 1280x960 74.86 1152x864 74.82 1024x768 74.90 800x600 74.91 640x480 74.77 320x240 73.82 1680x1050 74.89 1440x900 74.98 1280x800 74.93 720x480 74.51 640x400 74.23 320x200 73.70 1600x900 74.89 1368x768 74.90 1280x720 74.78 1024x576 74.80 864x486 74.45 720x400 74.23 640x350 74.53 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 452691] [Bluetooth - Bluedevil] PS4 / Dual Shock 4 Controller Crashed kded5
https://bugs.kde.org/show_bug.cgi?id=452691 --- Comment #10 from thegalacticv...@gmail.com --- (In reply to nekonexus from comment #9) > > Isn't it because you've set multiple aliases like "crash" and "segfault"? > > > > Searching those words with the search bar directs you to this bug report. > > That isn't an excuse. It very much is because all of us are trying to do the right thing by searching for existing bug reports instead of starting new threads. You shouldn't berate people for making basic mistakes, especially when said mistakes are a result of this site's unintuitive design. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470503] New: [nvidia] Screen corruption after changing theme
https://bugs.kde.org/show_bug.cgi?id=470503 Bug ID: 470503 Summary: [nvidia] Screen corruption after changing theme Classification: Plasma Product: kwin Version: 5.27.5 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: j...@devklog.net Target Milestone: --- SUMMARY When changing the global theme via system settings, say from Breeze to Breeze Dark, the screen becomes corrupted, rendering incorrect textures or compositing textures in the wrong place. STEPS TO REPRODUCE 1. Start a plasma wayland session 2. Change the global theme. OBSERVED RESULT Corrupt desktop compositing. EXPECTED RESULT Correct desktop compositing. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.3.5-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 32 × AMD Ryzen 9 7950X3D 16-Core Processor Memory: 62.5 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4090/PCIe/SSE2 Manufacturer: ASUS ADDITIONAL INFORMATION Linux: 6.3.5-arch1-1 Nvidia drivers: 530.41.03-15 Taking a screenshot with Spectacle does not show corruption, it is only on-screen. -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 469857] Kasts->Settings reports nothing
https://bugs.kde.org/show_bug.cgi?id=469857 --- Comment #2 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.
[plasmashell] [Bug 469849] Containment missing on login with laptop screen disabled and external screen as the only active one until plasmashell is restarted
https://bugs.kde.org/show_bug.cgi?id=469849 --- 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.
[dolphin] [Bug 469676] Dolphin not opening when called with arguments
https://bugs.kde.org/show_bug.cgi?id=469676 --- 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.
[kdenlive] [Bug 465247] Kdenlive (appimage) wont start on Linux Mint 20.3
https://bugs.kde.org/show_bug.cgi?id=465247 --- Comment #6 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469814] Rectangular region screenshot includes Spectacle window
https://bugs.kde.org/show_bug.cgi?id=469814 --- 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.
[k3b] [Bug 469268] k3b faild
https://bugs.kde.org/show_bug.cgi?id=469268 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 469865] Crash when exporting scans to PDF
https://bugs.kde.org/show_bug.cgi?id=469865 --- Comment #2 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 469888] Crash during screensharing
https://bugs.kde.org/show_bug.cgi?id=469888 --- 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.
[systemsettings] [Bug 469869] [regression] KCM_SDDM Crashes Utilizing over 100% CPU
https://bugs.kde.org/show_bug.cgi?id=469869 --- Comment #2 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.
[plasmashell] [Bug 441591] Switching user sometimes results in frozen UI
https://bugs.kde.org/show_bug.cgi?id=441591 --- 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.
[plasmashell] [Bug 429826] Plasma/OpenSuse Logout / Login crashing regularly
https://bugs.kde.org/show_bug.cgi?id=429826 --- Comment #2 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.
[plasmashell] [Bug 406690] ksmserver crashes when resuming from suspend, if kiosk mode is used
https://bugs.kde.org/show_bug.cgi?id=406690 --- Comment #2 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.
[plasmashell] [Bug 469228] Layout switcher doesn't work entirely
https://bugs.kde.org/show_bug.cgi?id=469228 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 469038] kde connect disconnects during presentations
https://bugs.kde.org/show_bug.cgi?id=469038 Bug Janitor Service changed: What|Removed |Added Resolution|BACKTRACE |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 464378] [Recorder] All artworks created from the same template ends into the same recorded directory
https://bugs.kde.org/show_bug.cgi?id=464378 --- Comment #2 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.
[plasmashell] [Bug 432697] Quick re-login causes ACPI ERRORs and a broken plasma session.
https://bugs.kde.org/show_bug.cgi?id=432697 --- 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.
[neon] [Bug 424565] Okteta uses dark text color on a dark background
https://bugs.kde.org/show_bug.cgi?id=424565 --- Comment #7 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.
[plasmashell] [Bug 376728] Global Menu does not reappear for windows on session restore because appmenu kded module isn't loaded yet by the time the app launches
https://bugs.kde.org/show_bug.cgi?id=376728 --- Comment #13 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 458446] Menus Start Showing behind Windows
https://bugs.kde.org/show_bug.cgi?id=458446 Pedro Rosado changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Target Milestone|--- |5 Resolution|WORKSFORME |--- Version|5.25.4 |5.27.5 Platform|Other |openSUSE --- Comment #6 from Pedro Rosado --- My apologies, I didn't receive the email asking for additional information. What information is needed? Please advise. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 470502] several blank tabs
https://bugs.kde.org/show_bug.cgi?id=470502 --- Comment #1 from ksso --- Created attachment 159382 --> https://bugs.kde.org/attachment.cgi?id=159382&action=edit the caption do not match with the width -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 470502] New: several blank tabs
https://bugs.kde.org/show_bug.cgi?id=470502 Bug ID: 470502 Summary: several blank tabs Classification: Applications Product: kdenlive Version: 22.12.3 Platform: Ubuntu OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: kep...@gmail.com Target Milestone: --- Created attachment 159381 --> https://bugs.kde.org/attachment.cgi?id=159381&action=edit some tabs work, some not SUMMARY *** in ubuntu 23.04 kdenlive show several tabs in blank *** STEPS TO REPRODUCE 1. install xubuntu 23.04 2. install kdenlive repository (22.12.3) 3. some problems with tabs in blank, resizing also 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.
[frameworks-kded] [Bug 452691] [Bluetooth - Bluedevil] PS4 / Dual Shock 4 Controller Crashed kded5
https://bugs.kde.org/show_bug.cgi?id=452691 --- Comment #9 from nekone...@protonmail.ch --- > Isn't it because you've set multiple aliases like "crash" and "segfault"? > > Searching those words with the search bar directs you to this bug report. That isn't an excuse. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 470501] New: Konsole moves off screen during monitor sleep
https://bugs.kde.org/show_bug.cgi?id=470501 Bug ID: 470501 Summary: Konsole moves off screen during monitor sleep Classification: Applications Product: konsole Version: 23.04.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: jeremiah.johns...@icloud.com Target Milestone: --- SUMMARY: Every time my single monitor system goes to sleep, the open konsole window moves off screen. To get it back on the only monitor I have plugged in I have to minimize and restore the window. STEPS TO REPRODUCE 1. Open konsole 2. Let monitor go to sleep 3. Wake system up OBSERVED RESULT konsole window is not on screen but is open EXPECTED RESULT konsole window is where it was when monitor went to sleep SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION konsole is the only application that behaves this way, no other apps. I have a single display using Wayland. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 470319] Add recent instruction sets to processor.h
https://bugs.kde.org/show_bug.cgi?id=470319 --- Comment #1 from 2wxsy5823...@opayq.com --- Since kinfocenter uses solid, if you view CPU information by Devices -> Device Viewer -> Processors -> Processor 0, you will see that AVX, AVX2, etc. will not be listed under "Supported Instruction Sets" even if your CPU supports them. It can only expose the short list of instruction sets provided by solid. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 468706] Color corrections behavior is either incorrect or misleading
https://bugs.kde.org/show_bug.cgi?id=468706 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Version Fixed In||23.08 Latest Commit||https://invent.kde.org/grap ||hics/gwenview/-/commit/5e6d ||1230d188b61d9b3293f1dba2b1c ||4d317efb1 --- Comment #2 from Nate Graham --- Git commit 5e6d1230d188b61d9b3293f1dba2b1c4d317efb1 by Nate Graham, on behalf of Adam Fontenot. Committed on 01/06/2023 at 01:39. Pushed by ngraham into branch 'master'. Fix color management settings The setting for disabling color management was incorrectly described, and also activated by default. The latter was an unintentional error in a previous commit. FIXED-IN: 23.08 M +4-4app/advancedconfigpage.ui M +1-1lib/cms/cmsprofile.cpp M +1-1lib/gwenviewconfig.kcfg https://invent.kde.org/graphics/gwenview/-/commit/5e6d1230d188b61d9b3293f1dba2b1c4d317efb1 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 462384] Palette editor missing catch for zero division
https://bugs.kde.org/show_bug.cgi?id=462384 vanyossi changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED CC||ghe...@gmail.com --- Comment #2 from vanyossi --- Since the MR is merged, let's mark this as fixed -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 470111] Bookmarks in Konsole "Broken" with Pasting Artifacts
https://bugs.kde.org/show_bug.cgi?id=470111 ninj...@gmail.com changed: What|Removed |Added CC||ninj...@gmail.com --- Comment #1 from ninj...@gmail.com --- Konsole needs to discard the current command line in case it's not empty, so it can then send the cd command to the shell. The way it does this is by sending an ASCII 03 character to the pseudo-terminal, which typically makes the tty line discipline generate and send an INT signal to the shell, which then discards the current command line. Some shells may display ^C while doing this (others don't). This was added as requested in https://bugs.kde.org/show_bug.cgi?id=46233 -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 468929] Kalendar crashes when tasks are edited
https://bugs.kde.org/show_bug.cgi?id=468929 --- Comment #2 from Beyley Thomas --- Created attachment 159380 --> https://bugs.kde.org/attachment.cgi?id=159380&action=edit New crash information added by DrKonqi kalendar (23.04.0) using Qt 5.15.9 Happen consistently every time i edit any task in Kalendar -- Backtrace (Reduced): #4 0x7fa3b1ba1250 in QDateTime::operator=(QDateTime const&) () at /usr/lib/libQt5Core.so.5 [...] #7 0x7fa3b1c46c41 in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () at /usr/lib/libQt5Core.so.5 [...] #10 0x7fa3b1c46c41 in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () at /usr/lib/libQt5Core.so.5 [...] #13 0x7fa3b1c46c41 in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () at /usr/lib/libQt5Core.so.5 [...] #16 0x7fa3b1c46c41 in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () at /usr/lib/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 468929] Kalendar crashes when tasks are edited
https://bugs.kde.org/show_bug.cgi?id=468929 Beyley Thomas changed: What|Removed |Added CC||ep1cm1n10n...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 463732] Print Dialog should remember PDF Options
https://bugs.kde.org/show_bug.cgi?id=463732 Nate Graham changed: What|Removed |Added Resolution|UPSTREAM|FIXED Version Fixed In||23.08 Latest Commit||https://invent.kde.org/grap ||hics/okular/-/commit/8afcf2 ||56a8efc176cc9d84f4681e64a51 ||44bdf1a --- Comment #11 from Nate Graham --- Git commit 8afcf256a8efc176cc9d84f4681e64a5144bdf1a by Nate Graham, on behalf of Martin Schnitkemper. Committed on 31/05/2023 at 23:51. Pushed by ngraham into branch 'master'. Make default PDF printing scale mode configurable Until now, some users have found it annoying when they want to print multiple documents in their original size and have to manually change the scaling mode before each print. This commit allows the user to select the default value so they won't have to change it before every print. FIXED-IN: 23.08 M +6-0generators/poppler/conf/pdfsettings.kcfg M +44 -1generators/poppler/conf/pdfsettingswidget.ui M +8-0generators/poppler/generator_pdf.cpp https://invent.kde.org/graphics/okular/-/commit/8afcf256a8efc176cc9d84f4681e64a5144bdf1a -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 470346] Out-of-bounds access in Screen::setSelectionEnd when selecting last line of scrolling text
https://bugs.kde.org/show_bug.cgi?id=470346 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/utilities/konsole/-/merge_requests/856 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 470232] Show package description on updates page
https://bugs.kde.org/show_bug.cgi?id=470232 --- Comment #3 from vaughan.m.johns...@protonmail.com --- (In reply to Nate Graham from comment #1) > Can you provide an annotated screenshot showing the exact page where you'd > like the description to be shown, and where on the page the description > should go? Hey Nate :-) thanks for responding; I just added the screenshot as you requested. I'm not sure how this would work with different package managers as besides a brief stint with Arch I've only been using apt in Debian. However that said my suggestion is to add a short description directly below the package title, perhaps with a 'more info' hyperlink next to the brief description text that either expands an additional long description text, or redirects to the URL of the package. To use the package libc6 as an example (https://packages.debian.org/bullseye/libc6), it would look something like the following: [title] libc6 [short description] GNU C Library: Shared libraries [url] more info [long description] Contains the standard libraries that are used by nearly all programs on the system. This package includes shared versions of the standard C library and the standard math library, as well as many others. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 470500] New: PolicyKit1 keeps asking for permission for most session based actions
https://bugs.kde.org/show_bug.cgi?id=470500 Bug ID: 470500 Summary: PolicyKit1 keeps asking for permission for most session based actions Classification: I don't know Product: kde Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: tonyspe...@gmail.com Target Milestone: --- Created attachment 159379 --> https://bugs.kde.org/attachment.cgi?id=159379&action=edit Screenshot of PolicyKit1 asking for permission SUMMARY After any of the recent updates, every time I want to shut down my pc, hibernate or similar, I get a message that system policies prevent editing custom network settings. I have attached a screenshot for this. Why does this happen, what could have caused it, and how do I fix it? STEPS TO REPRODUCE 1. Try setting your PC into hibbernate mode, or shut it down, or wake your pc up 2. Get the dialog as shown in my attachment OBSERVED RESULT A dialog keeps asking for my password EXPECTED RESULT No dialog negging me every now and then SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 5.19.0-42-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-6300HQ CPU @ 2.30GHz Memory: 23.3 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 530 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 470499] New: Wrong value is passed for the "frame_duration" option for `libopus`
https://bugs.kde.org/show_bug.cgi?id=470499 Bug ID: 470499 Summary: Wrong value is passed for the "frame_duration" option for `libopus` Classification: Applications Product: kdenlive Version: 23.04.1 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: rem...@tutanota.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Create a video 2. Try to render using SVT-AV1 (`libsvtav1`) as the Video encoding and `libopus` as the audio encoder OBSERVED RESULT Render failed. EXPECTED RESULT Render to complete successfully. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (latest updates) (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: 5.15.9+kde+r154-1 ADDITIONAL INFORMATION I have created a custom render preset using the SVT-AV1 encoder. I have bother tried from scratch and by copying the existing preset of AOM AV1 and just changing the video encoder. In both of the cases, I cannot render as it seems that a wrong value is passed for the option "frame_duration". I have tried to manually set the option in the "addition parameters" section but I get the same results. It is worth noting that I have the same exact problem in Shotcut so maybe what is used underline in both these editors causes the problem. Also, I'm able to find a work around, using the method [here](https://gitlab.com/AOMediaCodec/SVT-AV1/-/issues/1958). Yes, this issue was create from me and I found help. So another theory is that as the custom packages work, this may be a problem with the default packages of Arch Linux. But I wanted to post and find a solution because compiling so many programs in every release will just be a pain so this must be addressed cause if the later is the case, I will not be the only one that has/will have a problem and I/we/you need to talk with the team on Arch Linux to find a solution. The crass error message in more detail: ``` [libopus @ 0x7f3c74004080] Value 3.00 for parameter 'frame_duration' out of range [2.5 - 120] Svt[info]: --- Svt[info]: SVT [version]: SVT-AV1 Encoder Lib v1.1.0 Svt[info]: SVT [build] : GCC 12.1.0 64 bit Svt[info]: LIB Build date: Jul 28 2022 09:50:18 Svt[info]: --- [libsvtav1 @ 0x7f3c74001fc0] Error setting encoder parameters: bad parameter (0x80001005) [libopus @ 0x7f3c740035c0] Value 3.00 for parameter 'frame_duration' out of range [2.5 - 120] ``` -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 470232] Show package description on updates page
https://bugs.kde.org/show_bug.cgi?id=470232 --- Comment #2 from vaughan.m.johns...@protonmail.com --- Created attachment 159378 --> https://bugs.kde.org/attachment.cgi?id=159378&action=edit Annotated screenshot -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470394] Scrolling up on task manager task always maximizes window
https://bugs.kde.org/show_bug.cgi?id=470394 lig...@hotmail.com changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|NEEDSINFO |RESOLVED --- Comment #2 from lig...@hotmail.com --- My apologies. It is a problem with a plasmoid/widget/applet called "Mouse wheel Window Control". During troubleshooting i ran across https://bugs.kde.org/show_bug.cgi?id=388614 (Add possibility to Minimize/Restore windows with Mouse scroll on Task Manager). It seems this will not be added to official. Again, sorry for wasting time. -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 447905] When setting express button actions, keyboard shortcuts using META key cannot be set
https://bugs.kde.org/show_bug.cgi?id=447905 ian.h.chamberl...@gmail.com changed: What|Removed |Added CC||ian.h.chamberl...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470497] Compositor-provided V-Sync is active on fullscreen applications even when turned off in the settings
https://bugs.kde.org/show_bug.cgi?id=470497 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Nate Graham --- Can confirm. Looks like it actually isn't even wired up to anything internally. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 469825] Adwaita theme is scaled wrong in the preview
https://bugs.kde.org/show_bug.cgi?id=469825 Henning changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Henning --- The preview in the systemsettings lol. The section where you select the icons, there is a preview field where the icons are displayed. This seems to have been fixed, -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 470331] the shortcut 'alt + é' don't work in any app
https://bugs.kde.org/show_bug.cgi?id=470331 --- Comment #4 from El Mhadji Mohamed Abdelhake --- (In reply to Nate Graham from comment #3) > Thanks. If you're using X11, than this isn't a KDE issue. It could be > somewhere in xkb or the X server. If you're unsure how to proceed, I'd > recommend contacting your distro about it. thanks i will i t(In reply to Nate Graham from comment #3) > Thanks. If you're using X11, than this isn't a KDE issue. It could be > somewhere in xkb or the X server. If you're unsure how to proceed, I'd > recommend contacting your distro about it. thanks i will contact my distro -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 470100] cannot select and copy text on git log
https://bugs.kde.org/show_bug.cgi?id=470100 ninj...@gmail.com changed: What|Removed |Added CC||ninj...@gmail.com --- Comment #1 from ninj...@gmail.com --- In the "git log" example, the mouse pointer is shown as an arrow, while in the other examples it is shown as an I-beam(bar). This means the application enabled mouse-tracking mode, taking control of the mouse. You can still bypass the application handling of the mouse by holding the Shift key while pressing the mouse buttons. What's the value of the $LESS environment variable? "less" with the "--mouse" option enables mouse tracking mode to be able to react to the scroll-wheel and to set the # mark with a click (which you can then jump to with '# ). If you're not using "less" with the --mouse option, what's the value of the $GIT_PAGER and $PAGER environment variables? Have you configured core.pager or pager.log in git? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 470498] New: can't maximize window of kdenlive
https://bugs.kde.org/show_bug.cgi?id=470498 Bug ID: 470498 Summary: can't maximize window of kdenlive Classification: Applications Product: kdenlive Version: 22.12.3 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: kep...@gmail.com Target Milestone: --- Created attachment 159377 --> https://bugs.kde.org/attachment.cgi?id=159377&action=edit the bottom cant be accesed as can't maximize window SUMMARY *** can't maximize the window to see full options *** STEPS TO REPRODUCE 1. install kdenlive in xubuntu 2. try to maximize 3. OBSERVED RESULT can't maximize window EXPECTED RESULT maximize window SOFTWARE/OS VERSIONS kdenlive 22.12.3 xubuntu 23.04 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470497] New: Compositor-provided V-Sync is active on fullscreen applications even when turned off in the settings
https://bugs.kde.org/show_bug.cgi?id=470497 Bug ID: 470497 Summary: Compositor-provided V-Sync is active on fullscreen applications even when turned off in the settings Classification: Plasma Product: kwin Version: 5.27.5 Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: apri...@posteo.net Target Milestone: --- Created attachment 159376 --> https://bugs.kde.org/attachment.cgi?id=159376&action=edit Compositor option to disable V-Sync in fullscreen applications KWin as a Wayland compositor provides V-Sync over all screen content to prevent tearing. As high performance graphics applications like video games often provide their own V-Sync implementation the compositor-provided V-Sync should be disabled to avoid two V-Sync operations in a row and to give the application the option to disable V-Sync alltogether to favor latency over image quality. To achieve this behavior KWin has a checkbox in the System Settings under "Display and Monitor -> Compositor" called "Reduce latency by allowing screen tearing artifacts in fullscreen applications", so basically "Disable compositor V-Sync in fullscreen applications". Unfortunately this checkbox does nothing, as Nate Graham looked up in the code. Therefore currently applications in KWin Wayland are not able to run without forced V-Sync, which they should be able to. STEPS TO REPRODUCE 1. Go to the system settings "Display and Monitor -> Compositor" and test with the activated and deactivated check box "Reduce latency by allowing screen tearing artifacts in fullscreen applications" 2. Open different fullscreen applications which do not have internal V-Sync like "glxgears -fullscreen" OBSERVED RESULT I can not get fullscreen applications to tear, suggesting that KWin forces V-Sync itself, even if it should not. EXPECTED RESULT The applications should tear and KWin should not apply V-Sync leaving them the option to figure it out themselves. SOFTWARE/OS VERSIONS Linux: 6.3.4-arch1-1 (64-bit) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 15329] Save and remember positions of all windows
https://bugs.kde.org/show_bug.cgi?id=15329 --- Comment #83 from Eugene --- (In reply to Nate Graham from comment #82) > FWIW, as a workaround while this feature remains unimplemented, you should > be able to use Window Rules on Wayland to manually force windows to appear > where you want them. I would be very appreciate if you would show working window rules for Telegram window to always appear in upper right screen corner on Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 470376] kscreenlocker uses discrete GPU when integrated GPU is available
https://bugs.kde.org/show_bug.cgi?id=470376 --- Comment #2 from David Koppelman --- When a system is set up for what Nvidia calls prime render offload, applications by default will use the integrated GPU. In order to use the discrete GPU the application has to have certain environment variables set, usually __NV_PRIME_RENDER_OFFLOAD=1, though others need to be set for Vulkan applications. For details see Chapter 35 in the Nvidia driver readme: http://us.download.nvidia.com/XFree86/Linux-x86_64/530.41.03/README/primerenderoffload.html On my system I only want to use the discrete GPU for graphics intensive applications. I do that by starting these applications with a script that sets the environment variables before launching the application or by appropriate .gdbinit settings (if I'm debugging one of those applications). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469948] Update libaom from 3.6.0 to 3.6.1
https://bugs.kde.org/show_bug.cgi?id=469948 caulier.gil...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Version Fixed In||8.1.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 182912] Display of focus from photo
https://bugs.kde.org/show_bug.cgi?id=182912 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|DUPLICATE |FIXED Version Fixed In||8.1.0 --- Comment #2 from caulier.gil...@gmail.com --- Fixed with bug 138704 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 210909] Add image names in Light Table
https://bugs.kde.org/show_bug.cgi?id=210909 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|DUPLICATE |FIXED Version Fixed In||8.1.0 --- Comment #2 from caulier.gil...@gmail.com --- Fixed with bug 148572 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 470278] problem with USB-C / TB4 display / KVM switch
https://bugs.kde.org/show_bug.cgi?id=470278 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 249078] digikam should be able to show the available and/or used AF sensors
https://bugs.kde.org/show_bug.cgi?id=249078 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||8.1.0 Resolution|DUPLICATE |FIXED --- Comment #2 from caulier.gil...@gmail.com --- Fixed with bug 138704 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 456310] Keyboard volume control keys don't change the volume of the default sink
https://bugs.kde.org/show_bug.cgi?id=456310 --- Comment #7 from AT --- I keep experiencing weird stuff with pipewire and the selected device in the volume control, maybe it's related. Like opening a video with mpv, and it randomly choosing to play audio either from the first device in the list (currently muted and unselected), or the currently active/selected one with the radio button selection. I was originally opening and closing mpv multiple times over until I got audio, thinking it was an mpv problem, but then I found not getting audio was because of it randomly picking the muted&unselected device I've also discovered the hamburger menu's "Play all audio from this device" and "Record all audio from this device" which is confusing because clicking that does NOT change the radio button position. So what do the radio buttons to select a device actually do then? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470399] Event Calendar's calendar tooltip opens under cursor and moves away from cursor, closing itself
https://bugs.kde.org/show_bug.cgi?id=470399 Nate Graham changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED Summary|Plasmoid tooltip opens |Event Calendar's calendar |under cursor and moves away |tooltip opens under cursor |from cursor, closing itself |and moves away from cursor, ||closing itself CC||n...@kde.org, ||zrenf...@gmail.com --- Comment #1 from Nate Graham --- This is a bug in the tooltip implementation of that particular widget, yeah. Spawning in the corner is weird and it shouldn't do that. We don't wait for the animation cycle to complete to avoid making the fade-out take longer, which has annoyed people in the past. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469948] Update libaom from 3.6.0 to 3.6.1
https://bugs.kde.org/show_bug.cgi?id=469948 --- Comment #4 from caulier.gil...@gmail.com --- Git commit 233b33d970a64342e97ed2377f72f90852822713 by Gilles Caulier. Committed on 31/05/2023 at 20:22. Pushed by cgilles into branch 'master'. fix broken compile while updateing libaom M +2-1project/bundles/mxe/01-build-mxe.sh https://invent.kde.org/graphics/digikam/-/commit/233b33d970a64342e97ed2377f72f90852822713 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 470376] kscreenlocker uses discrete GPU when integrated GPU is available
https://bugs.kde.org/show_bug.cgi?id=470376 Nate Graham changed: What|Removed |Added Summary|kscreenlocker uses discrete |kscreenlocker uses discrete |GPU when integrated GPU is |GPU when integrated GPU is |available. |available CC||n...@kde.org --- Comment #1 from Nate Graham --- In general, how do you determine which GPU an app uses? I'm not very familiar with this type of hardware. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 470423] I can't take a screenshot with this software
https://bugs.kde.org/show_bug.cgi?id=470423 --- Comment #6 from matheusC.C --- (In reply to Noah Davis from comment #3) > I see this is a report caused by a message in version 22.12 that tells users > to report a bug whenever it appears. Unfortunately, all of the bug reports > generated from that message aren't helpful since Spectacle didn't provide > users with much information about the issue and the version that had the > message will no longer be getting updates. Please try version 23.04 to see > if your problem was fixed. I installed the snap version of spectacle and it didn't work, I'm going to migrate to flameshot, at least it's working. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 469277] Black screen after loging in my machine when external screen is attached
https://bugs.kde.org/show_bug.cgi?id=469277 --- Comment #12 from Ahmed --- Created attachment 159375 --> https://bugs.kde.org/attachment.cgi?id=159375&action=edit The output of running `kscreen-doctor -o` (when everything is not working) qt.qpa.xcb: could not connect to display qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. This application failed to start because no Qt platform plugin could be intialized. Reinstalling the application may fix this problem. Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb. Aborted (core dumped). -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 470331] the shortcut 'alt + é' don't work in any app
https://bugs.kde.org/show_bug.cgi?id=470331 Nate Graham changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |UPSTREAM --- Comment #3 from Nate Graham --- Thanks. If you're using X11, than this isn't a KDE issue. It could be somewhere in xkb or the X server. If you're unsure how to proceed, I'd recommend contacting your distro about it. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 470398] Add window borders to match the kwin theme
https://bugs.kde.org/show_bug.cgi?id=470398 --- Comment #2 from david <12david...@gmail.com> --- Oh that's unfortunate, thank you for the reply. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469948] Update libaom from 3.6.0 to 3.6.1
https://bugs.kde.org/show_bug.cgi?id=469948 --- Comment #3 from caulier.gil...@gmail.com --- Git commit 127febb20c6747d9c543db91049fb19c8df89584 by Gilles Caulier. Committed on 31/05/2023 at 20:11. Pushed by cgilles into branch 'master'. fix broken compilation while updating libaom M +3-1project/bundles/appimage/01-build-host.sh https://invent.kde.org/graphics/digikam/-/commit/127febb20c6747d9c543db91049fb19c8df89584 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 469277] Black screen after loging in my machine when external screen is attached
https://bugs.kde.org/show_bug.cgi?id=469277 Ahmed changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- --- Comment #11 from Ahmed --- I encountered the same issue today and yesterday. I have updated Kubuntu recently to 5.27.5. Pressing the power button does not suspend my machine, and unplugging the HDMI cable does not help either. I could go to the terminal by pressing alt+ctrl+f2, and after trying to execute `kscreen-doctor -o`, I got an error that I captured using my phone. I will upload it in my next comment. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 470331] the shortcut 'alt + é' don't work in any app
https://bugs.kde.org/show_bug.cgi?id=470331 --- Comment #2 from El Mhadji Mohamed Abdelhake --- (In reply to Nate Graham from comment #1) > If it's broken with those non-KDE apps, than this isn't a problem in any KDE > software unless you're using the Wayland session, in which case it might be > an issue in KWin. So are you using X11 or Wayland? to be honest you got a point when you said that i didn't try it the KDE-apps but even when i've try to set the shortcut in setting it didn't work at all (didn't even work when i added in setting like a custom shortcut for KRunner, when i try any other shortcut it work fine ),for your question about if i'm using X11 or Wayland i've type echo $XDG_SESSION_TYPE in terminal and i get x11(so i suppose that i'm using x11).thanks in advance for any help, i truly appreciate your help -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 15329] Save and remember positions of all windows
https://bugs.kde.org/show_bug.cgi?id=15329 --- Comment #82 from Nate Graham --- FWIW, as a workaround while this feature remains unimplemented, you should be able to use Window Rules on Wayland to manually force windows to appear where you want them. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449840] On X11, sometimes WindowHeap-based effects stop accepting keyboard input
https://bugs.kde.org/show_bug.cgi?id=449840 --- Comment #33 from t3n3t --- So the bug is still at large, will it ever be addressed or X11 users should just ditch Overview and Present Windows Kwin effects and wait till Wayland becomes actually viable? Also, just wondering, does this bug affect people with only one keyboard layout (I have two)? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 15329] Save and remember positions of all windows
https://bugs.kde.org/show_bug.cgi?id=15329 --- Comment #81 from Raman Gupta --- In https://bugs.kde.org/show_bug.cgi?id=470318#c1 Nate explained that X11 apps are allowed to save and restore their own window positions. So I'm guessing that this bug has been open for almost 23 years because this ceased to be an issue on X11, as every app implemented this on their own. However, Nate also explains in https://bugs.kde.org/show_bug.cgi?id=470318#c1 that on Wayland, apps are no longer allowed to restore their own window positions. This can be seen easily with Firefox. MOZ_DISABLE_WAYLAND=1 firefox Firefox running via XWayland is able to remember its own window position (though there is some visual jank as the windows position in the default spot, and then move to the remembered position). But when running firefox natively on Wayland, window positions are not remembered. Nate's comment in late 2020 was about purported progress in Wayland, but this is still not working in 2023. Now that Wayland will not allow apps to remember their own positions, I hope that renewed focus will be applied to this nearly 23 year old issue. For me, this is a showstopper issue for Wayland adoption, as I have many carefully positioned windows with browsers and IDEs and its a major pain to continually reposition Windows across every restart. -- You are receiving this mail because: You are watching all bug changes.
