[kmail2] [Bug 425209] New: Kmail crash on quick click of 'Show mail' in notification
https://bugs.kde.org/show_bug.cgi?id=425209 Bug ID: 425209 Summary: Kmail crash on quick click of 'Show mail' in notification Product: kmail2 Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: kkremit...@gmail.com Target Milestone: --- Application: kmail (5.14.1 (20.04.0)) Qt Version: 5.14.2 Frameworks Version: 5.70.0 Operating System: Linux 5.7.0-2-amd64 x86_64 Distribution: Debian GNU/Linux bullseye/sid -- Information about the crash: - What I was doing when the application crashed: I got an email on a Gmail account. I have the 'New Mail Notifier' Kmail plugin set to 'Show Action Buttons'. When I have good reactions and click it almost immediately after receiving, I get a crash. - Custom settings of the application: - 'New Mail Notifier' plugin -> 'Show Action Buttons' - Kmail running in system tray already The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc5584d43c0 (LWP 98735))] Thread 45 (Thread 0x7fc4da8e4700 (LWP 135115)): #0 futex_abstimed_wait_cancelable (private=0, abstime=0x7fc4da8e2f70, clockid=-628216064, expected=0, futex_word=0x7fc4da8e30b8) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7fc4da8e2f70, clockid=-628216064, mutex=0x7fc4da8e3068, cond=0x7fc4da8e3090) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x7fc4da8e3090, mutex=0x7fc4da8e3068, abstime=0x7fc4da8e2f70) at pthread_cond_wait.c:656 #3 0x7fc56664f9ba in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0xacdf in () #5 0x1e217a35 in () #6 0xacbe in () #7 0x1e217e1d in () #8 0x in () Thread 44 (Thread 0x7fc4767fc700 (LWP 135112)): #0 __GI___libc_read (nbytes=16, buf=0x7fc4767fafd0, fd=29) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=29, buf=0x7fc4767fafd0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7fc56b9f3f4f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc56b9ac33e in g_main_context_check () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fc56b9ac792 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fc56b9ac90f in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fc56f10331b in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fc56f0ac4db in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fc56eed38de in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fc56eed4a01 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fc56c41bea7 in start_thread (arg=) at pthread_create.c:477 #11 0x7fc56eb77eaf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 43 (Thread 0x7fc477fff700 (LWP 135061)): #0 futex_abstimed_wait_cancelable (private=0, abstime=0x7fc477ffdf70, clockid=2013257472, expected=0, futex_word=0x7fc477ffe0b8) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7fc477ffdf70, clockid=2013257472, mutex=0x7fc477ffe068, cond=0x7fc477ffe090) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x7fc477ffe090, mutex=0x7fc477ffe068, abstime=0x7fc477ffdf70) at pthread_cond_wait.c:656 #3 0x7fc56664f9ba in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0xacdf in () #5 0x1e2592d3 in () #6 0xacbe in () #7 0x1e2592d3 in () #8 0x in () Thread 42 (Thread 0x7fc4d98e2700 (LWP 133080)): #0 futex_abstimed_wait_cancelable (private=0, abstime=0x7fc4d98e0f70, clockid=-645001472, expected=0, futex_word=0x7fc4d98e10b8) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7fc4d98e0f70, clockid=-645001472, mutex=0x7fc4d98e1068, cond=0x7fc4d98e1090) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x7fc4d98e1090, mutex=0x7fc4d98e1068, abstime=0x7fc4d98e0f70) at pthread_cond_wait.c:656 #3 0x7fc56664f9ba in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0xacdf in () #5 0x1e20f042 in () #6 0xacbe in () #7 0x1e20f812 in () #8 0x in () Thread 41 (Thread 0x7fc481e70700 (LWP 98851)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x7fc55e06bfb8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7fc55e06bf68, cond=0x7fc55e06bf90) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x7fc55e06bf90, mutex=0x7fc55e06bf68) at
[frameworks-kio] [Bug 424990] Tab key changes focus from field with Automatic and Short Automatic completion rather than completing current path
https://bugs.kde.org/show_bug.cgi?id=424990 --- Comment #4 from Thomas Carmichael --- I left a comment on Bug 424991 since I think there would be more usability issues for that one. For this one however, I would expect that the idea of a second press of the Tab key would complete the faded completion text and then in the absence of additional completion, the focus should move out of the field. Using the Steps to Reproduce example path, this would mean that using '/usr/share/plasma/plasmoids/org' for Automatic completion, the path would become '/usr/share/plasma/plasmoids/org.kde.desktopcontainment' and pressing Tab after that would move the focus. For Short Automatic completion I'd expect the path to be '/usr/share/plasma/plasmoids/org.kde.' and then pressing Tab would again, move the focus. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 424991] Using Ctrl+L to edit the path and pressing the Tab key moves focus from the field
https://bugs.kde.org/show_bug.cgi?id=424991 --- Comment #2 from Thomas Carmichael --- I'd think that the first press of the Tab key would complete the path and a subsequent press of the Tab key would move the focus away from the text field. I will admit from doing a quick test right now that I could foresee an issue with this approach when the focus is moved back into the editable location bar by pressing Shift+Tab. Currently, moving the focus out with Tab and back in by Shift+Tab selects the text of the location and I think it would be a usability issue if someone had to repeatedly double-Tab to move focus back out again. My main aim for something here is being able to start editing the path from the keyboard, keeping close to the home row, however it's probably easier to adapt to using F6 for this, which I also now realise leaves the cursor at the end of the path. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 424990] Tab key changes focus from field with Automatic and Short Automatic completion rather than completing current path
https://bugs.kde.org/show_bug.cgi?id=424990 --- Comment #3 from Nate Graham --- I think my question is the same for both, though: if the tab key is changed to trigger autocompletion rather than moving the keyboard focus, then how would do you move the keyboard focus using the keyboard? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 424990] Tab key changes focus from field with Automatic and Short Automatic completion rather than completing current path
https://bugs.kde.org/show_bug.cgi?id=424990 --- Comment #2 from Thomas Carmichael --- This differs from Bug 424991 in that it's related to the Tab key behaviour as it relates to the Automatic/Short Automatic completion and after looking at the issue reporting page (https://community.kde.org/Get_Involved/Issue_Reporting#One_issue_per_Bugzilla_ticket) I realised that the issues seemed different enough that they should be separated. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424701] Caligraphy does not work properly it makes a lot of circular shapes and it becomes useless
https://bugs.kde.org/show_bug.cgi?id=424701 --- 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.
[krita] [Bug 423718] Krita does not open, Event 1000, Application Error
https://bugs.kde.org/show_bug.cgi?id=423718 --- 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.
[krita] [Bug 424632] No drawing until after 1 inch on Huion
https://bugs.kde.org/show_bug.cgi?id=424632 --- 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.
[krita] [Bug 423593] pen lag huion HS610
https://bugs.kde.org/show_bug.cgi?id=423593 --- 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.
[kate] [Bug 424110] Search function is extremely slow
https://bugs.kde.org/show_bug.cgi?id=424110 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.
[plasmashell] [Bug 397785] Pinned apps should be hidden if application is opened on ANY desktop
https://bugs.kde.org/show_bug.cgi?id=397785 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.
[elisa] [Bug 424621] Não carrega lista de músicas
https://bugs.kde.org/show_bug.cgi?id=424621 --- 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.
[krita] [Bug 423475] Krita crases on close the application after an export to png or jpg
https://bugs.kde.org/show_bug.cgi?id=423475 --- 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.
[krita] [Bug 423876] Project crashes when ever I try to open it
https://bugs.kde.org/show_bug.cgi?id=423876 --- Comment #21 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.
[krunner] [Bug 425180] krunner dictionary doesn't work
https://bugs.kde.org/show_bug.cgi?id=425180 --- Comment #3 from Michael K. --- Thanks Nate, then I'll have to wait until Leap 15.3. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384006] Panel icons flickers
https://bugs.kde.org/show_bug.cgi?id=384006 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #19 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 424275] Stylus input (applepen) stop drawing after first stroke
https://bugs.kde.org/show_bug.cgi?id=424275 --- 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 403200] Not changes windows some titmes
https://bugs.kde.org/show_bug.cgi?id=403200 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.
[krita] [Bug 423710] Crashes after I save
https://bugs.kde.org/show_bug.cgi?id=423710 --- Comment #16 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 395611] Off-by-few pixels in task previews
https://bugs.kde.org/show_bug.cgi?id=395611 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #7 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.
[plasmashell] [Bug 404450] Request: Display Windows from a different Monitor than current
https://bugs.kde.org/show_bug.cgi?id=404450 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 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 424319] Modifier shortcut keys stop working
https://bugs.kde.org/show_bug.cgi?id=424319 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 425208] New: Import of .gnucash failed Skrooge 2.22.1 Flatpak
https://bugs.kde.org/show_bug.cgi?id=425208 Bug ID: 425208 Summary: Import of .gnucash failed Skrooge 2.22.1 Flatpak Product: skrooge Version: 2.22.0 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: guillaume.deb...@gmail.com Reporter: kaga...@gmail.com CC: steph...@mankowski.fr Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Save gnucash file in xml format gnucash version 4.1 Flatpack 2. Import in Skrooge 3. OBSERVED RESULT [ERR-5]: Import of file named 'file:///sysroot/home/kamalakar/Documents/test.gnucash' failed EXPECTED RESULT Import successful SOFTWARE/OS VERSIONS Endless OS 3.8.4 (available in About System) ADDITIONAL INFORMATION gnucash file size 1.7 MB could not be attached. I can mail it if required -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 425111] UHD Resolution on HDMI / On TV's with ~ 43" or more
https://bugs.kde.org/show_bug.cgi?id=425111 --- Comment #8 from blackcrack --- Created attachment 130777 --> https://bugs.kde.org/attachment.cgi?id=130777=edit Nvidia-Settings/Configuration in WinNT 2 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 425111] UHD Resolution on HDMI / On TV's with ~ 43" or more
https://bugs.kde.org/show_bug.cgi?id=425111 blackcrack changed: What|Removed |Added Assignee|kscreen-bugs-n...@kde.org |blackcr...@blackysgate.de --- Comment #7 from blackcrack --- Created attachment 130776 --> https://bugs.kde.org/attachment.cgi?id=130776=edit Nvidia-Settings/Configuration in WinNT and the Result at the whole is, you can not install Plasma-releated Distributions on a UHD Screen, because KDE want make his own thing, use the wrong resolution and the UHD-TV get a black screen. i have here the possibility to use a 4096x2160 resolution with 60Htz and is native Possible be also => Look Picture, but this is a thing of nouveau Driver.. but the nouveau driver works of the nativ resolution, but Plasma Hardware- recognition , discovery, identification to not works well on hdmi + UHD Resolution, because because the information simply does not exist in kde hardware recognition. And therewith it is impossible to install a Linux-Distribution on a Computer with a hdmi - UHD Screen. All exit Linux-Distributions.. with KDE/Plasma -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421098] Speed control of brush properties has an impractically large 'Fast' value.
https://bugs.kde.org/show_bug.cgi?id=421098 tomtomtomreportin...@gmail.com changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421098] Speed control of brush properties has an impractically large 'Fast' value.
https://bugs.kde.org/show_bug.cgi?id=421098 tomtomtomreportin...@gmail.com changed: What|Removed |Added CC||tomtomtomreportingin@gmail. ||com --- Comment #1 from tomtomtomreportin...@gmail.com --- Created attachment 130775 --> https://bugs.kde.org/attachment.cgi?id=130775=edit A speed curve for reproducing the issue I can vouch for the impracticality of the current value. How I reproduce it is setting up the speed curve as demonstrated in my attachment. This makes it so that only dabs done above the 50% threshold will be shown. If you try making strokes yourself using this curve, you will find it absurdly impractical to reach above even 50% of the max speed value. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 425176] Zoom On Hover cannot be disabled
https://bugs.kde.org/show_bug.cgi?id=425176 --- Comment #4 from Drew --- I don't understand what you mean by "maintain." I have no expectation that someone is going to fix 0.9.11 and re-release it as the same version number, if that's what you're implying. The standard practice would be to release bug fixes with incremental patch numbers 0.9.12, 0.9.13, etc. I also don't understand why you marked this as FIXED. Did you commit a fix? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 425204] Installer of neon unstable 20.04 creates a passwordless user account without administrator privileges
https://bugs.kde.org/show_bug.cgi?id=425204 Eric Adams changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||esa1...@gmail.com --- Comment #1 from Eric Adams --- I can confirm this behavior with the same ISO file. I was able to perform a recovery boot, add a password for my user as well as adding it to the sudo group. Once I rebooted everything else seems to be working. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425190] Improve scaling of the desktop
https://bugs.kde.org/show_bug.cgi?id=425190 --- Comment #15 from Claudius Ellsel --- (In reply to Nate Graham from comment #14) > David, I think Claudius is using the term "scaling" as a user understands > the term, not as a KWin developer understands the term. Looking at the > attachments, clearly there are differences in the different ways that images > can be scaled up. Knowing that fractional scaling downscales from a doubled > pixel-perfect version, it might be interesting to repeat the tests with > downscaled images. Ah, I see my mistake now. Roman Gilg already pointed that out, but I did not understand it then. I just assumed it would be scaled up. Downscaling obviously is the better approach to implementation, since no information has to be interpolated, so that makes sense. This renders the different algorithm comparisons I posted rather pointless. However, I read the the NoHalo algorithms were actually developed for downscaling in particular and that blurriness can also happen when scaling down. So the general idea that there might be better algorithms still seems to be valid. -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 399919] Calligra aborts signal andproduces error on closing
https://bugs.kde.org/show_bug.cgi?id=399919 --- Comment #4 from taekyung@cryptolab.co.kr --- Created attachment 130774 --> https://bugs.kde.org/attachment.cgi?id=130774=edit New crash information added by DrKonqi calligrawords (3.2.1) using Qt 5.15.0 - What I was doing when the application crashed: Calligra words crashes when I close the application. -- Backtrace (Reduced): #6 0x7f513862c86a in __gnu_cxx::__verbose_terminate_handler () at /build/gcc/src/gcc/libstdc++-v3/libsupc++/vterminate.cc:95 #7 0x7f5138638d8a in __cxxabiv1::__terminate (handler=) at /build/gcc/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:48 #8 0x7f5138638df7 in std::terminate () at /build/gcc/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:58 #9 0x7f5138639b55 in __cxxabiv1::__cxa_pure_virtual () at /build/gcc/src/gcc/libstdc++-v3/libsupc++/pure.cc:50 [...] #11 0x7f5138e6516f in QWidget::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 399919] Calligra aborts signal andproduces error on closing
https://bugs.kde.org/show_bug.cgi?id=399919 taekyung@cryptolab.co.kr changed: What|Removed |Added CC||taekyung@cryptolab.co.k ||r -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 418708] Settings shows double entry for flatpak flathub
https://bugs.kde.org/show_bug.cgi?id=418708 Aleix Pol changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #8 from Aleix Pol --- Maybe you copied some text from the internet into your shell? In any case, closing as Discover's behaviour is correct. If you think it might have been Discover, we can look into addressing it. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 424862] Error messages should respect plasma language
https://bugs.kde.org/show_bug.cgi?id=424862 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #4 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/discover/-/merge_requests/22 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 424862] Error messages should respect plasma language
https://bugs.kde.org/show_bug.cgi?id=424862 --- Comment #5 from Aleix Pol --- Please test. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 411830] [packagekit-alpm] Cannot cancel installation
https://bugs.kde.org/show_bug.cgi?id=411830 Aleix Pol changed: What|Removed |Added Resolution|--- |UPSTREAM Status|CONFIRMED |RESOLVED --- Comment #2 from Aleix Pol --- It is indeed an issue in alpm's backend in PackageKit. Feel free to take it there https://github.com/hughsie/PackageKit I've been looking into it and it reports cancellability for some parts so you will actually see the button flashing at times. Of course this is not acceptable but we can't also extrapolate much information from it, if the backend claims it's not possible. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 419648] Discover is unable to update plasma addons and even crashes
https://bugs.kde.org/show_bug.cgi?id=419648 --- Comment #7 from Aleix Pol --- This is super weird. I can't reproduce and the backtrace doesn't really bring any information. Maybe you could bring the rest of the threads? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 425111] UHD Resolution on HDMI / On TV's with ~ 43" or more
https://bugs.kde.org/show_bug.cgi?id=425111 Nate Graham changed: What|Removed |Added Version|unspecified |5.19.4 Assignee|notm...@gmail.com |kscreen-bugs-n...@kde.org Product|frameworks-plasma |KScreen Component|libplasma |common -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424829] Crash when undoing/redoing while using Colorize Mask
https://bugs.kde.org/show_bug.cgi?id=424829 --- Comment #4 from tomtomtomreportin...@gmail.com --- I wouldn't think it's a CPU issue. I have an i3 Haswell while my friend has a 2nd generation Ryzen. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425124] On the scratchpad, brush presets utilizing the speed sensor often aren't drawn accurately
https://bugs.kde.org/show_bug.cgi?id=425124 --- Comment #2 from tomtomtomreportin...@gmail.com --- (In reply to Ahab Greybeard from comment #1) > It does look like the detected speed on the scratchpad is noticably higher > than on the canvas. > It's difficult to quantify this because it's difficult to manually draw at > any given speed, to repeat a particular speed or even know what the speed is. > > In addition, I believe that the detected speed signal is scaled too low and > requires inconveniently high speeds to cover the full range of the transfer > curve. > This has been noted in: > https://bugs.kde.org/show_bug.cgi?id=421098 Thanks for posting your report, I was unaware of this exact behavior, but it did feel like something was fishy. As you also note in your report, "the Speed is proportional to 'canvases per second'", which I think is likely to be related to this issue. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kuserfeedback] [Bug 425114] Always show the "View previously submitted data..." link
https://bugs.kde.org/show_bug.cgi?id=425114 Nate Graham changed: What|Removed |Added Latest Commit||https://invent.kde.org/libr ||aries/kuserfeedback/commit/ ||ffecbf6eadaa83f1a088a4276f3 ||ac0afcdedfdda Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #4 from Nate Graham --- Git commit ffecbf6eadaa83f1a088a4276f3ac0afcdedfdda by Nate Graham. Committed on 10/08/2020 at 17:08. Pushed by ngraham into branch 'master'. Always show the "View previously submitted data..." link We enable and disable it as needed now, rather than hiding and showing it. This should make it more obvious to the user that such a feature exists even when they haven't turned on data collection. M +2-2src/provider/widgets/feedbackconfigwidget.cpp https://invent.kde.org/libraries/kuserfeedback/commit/ffecbf6eadaa83f1a088a4276f3ac0afcdedfdda -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 425117] Combine "Halt" and "Continue" button
https://bugs.kde.org/show_bug.cgi?id=425117 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/util ||ities/print-manager/-/commi ||t/f9787b13b8dbd5673cc4e0590 ||ed8d59bb922cb71 Status|CONFIRMED |RESOLVED Version Fixed In||20.12.0 --- Comment #2 from Nate Graham --- Fixed with https://invent.kde.org/utilities/print-manager/-/commit/f9787b13b8dbd5673cc4e0590ed8d59bb922cb71! -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 425207] New: Can't see queue and library at the same time
https://bugs.kde.org/show_bug.cgi?id=425207 Bug ID: 425207 Summary: Can't see queue and library at the same time Product: juk Version: 19.12 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: whee...@kde.org Reporter: cardinalidi...@gmail.com CC: mp...@kde.org Target Milestone: --- I can only choose either: wouldn't it be possible to have a small box inside the window where I can drag the songs to and where I can keep a costant eye on what's next? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423952] [Wayland] Firefox's tab overflow menu is too short
https://bugs.kde.org/show_bug.cgi?id=423952 --- Comment #9 from David Edmundson --- Firefox... or gtk. But the log does seems to rule out kwin at this stage. -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 180078] Cannot Defer Playlist Scan at Start
https://bugs.kde.org/show_bug.cgi?id=180078 lupccs changed: What|Removed |Added CC||cardinalidi...@gmail.com Version|3.2 |19.12 --- Comment #4 from lupccs --- Eleven years later and we still have that problem, at least on kubuntu 20.04 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423952] [Wayland] Firefox's tab overflow menu is too short
https://bugs.kde.org/show_bug.cgi?id=423952 --- Comment #8 from Nate Graham --- I have no idea. It's really frustrating to submit Wayland bugs because it seems impossible to know who's at fault for an issue like this. I gather you're saying that it's Firefox's fault? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 425192] Screens overlap on Wayland when scaling is fractional
https://bugs.kde.org/show_bug.cgi?id=425192 Kyrylo Bohdanenko changed: What|Removed |Added CC||kirill.bogdane...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423952] [Wayland] Firefox's tab overflow menu is too short
https://bugs.kde.org/show_bug.cgi?id=423952 David Edmundson changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REOPENED|RESOLVED --- Comment #7 from David Edmundson --- Your log shows the client asked for it to be 208 pixels tall. So what is kwin doing wrong? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425127] Uneven margins between all 4 sides
https://bugs.kde.org/show_bug.cgi?id=425127 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED Ever confirmed|0 |1 --- Comment #10 from Nate Graham --- Thanks, that's helpful! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 421131] Wayland: cursor lags under heavy CPU load
https://bugs.kde.org/show_bug.cgi?id=421131 --- Comment #3 from Nate Graham --- How does one find out that information? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425127] Uneven margins between all 4 sides
https://bugs.kde.org/show_bug.cgi?id=425127 --- Comment #9 from wg9rffujwz8y2...@airmail.cc --- for ((i=1; i<=9000; i++)); do echo -n "01"; done; -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423952] [Wayland] Firefox's tab overflow menu is too short
https://bugs.kde.org/show_bug.cgi?id=423952 Nate Graham changed: What|Removed |Added Resolution|NOT A BUG |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #6 from Nate Graham --- What? Does the screenshot not adequately depict the problem that the popup doesn't become as tall as the parent window? If the resolution in the screenshot is low, that's Spectacle not being able to do hidpi properly on Wayland. Nothing to do with the bug at hand. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425127] Uneven margins between all 4 sides
https://bugs.kde.org/show_bug.cgi?id=425127 --- Comment #8 from wg9rffujwz8y2...@airmail.cc --- I just took these screenshots in a live Kubuntu 20.04 virtual machine with default settings. The margins are not equal if you compare top/bottom with left/right. To better visualize them you can imagine that each monospaced character has a box around it, that's their real size. And maybe the margins are what's outside the sum of all of them? It's probably not like that in the code at all but I don't know how else to describe it. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425127] Uneven margins between all 4 sides
https://bugs.kde.org/show_bug.cgi?id=425127 --- Comment #7 from wg9rffujwz8y2...@airmail.cc --- Created attachment 130773 --> https://bugs.kde.org/attachment.cgi?id=130773=edit 7 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425127] Uneven margins between all 4 sides
https://bugs.kde.org/show_bug.cgi?id=425127 --- Comment #6 from wg9rffujwz8y2...@airmail.cc --- Created attachment 130772 --> https://bugs.kde.org/attachment.cgi?id=130772=edit 6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423952] [Wayland] Firefox's tab overflow menu is too short
https://bugs.kde.org/show_bug.cgi?id=423952 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #5 from David Edmundson --- [3687561.559] -> xdg_positioner@73.set_size(308, 288) [3687561.575] -> xdg_positioner@73.set_anchor_rect(1461, 59, 28, 28) [3687561.601] -> xdg_positioner@73.set_offset(20, -6) [3687561.615] -> xdg_positioner@73.set_anchor(2) [3687561.624] -> xdg_positioner@73.set_gravity(6) [3687561.632] -> xdg_positioner@73.set_constraint_adjustment(51) [3687561.642] -> xdg_wm_base@23.get_xdg_surface(new id xdg_surface@74, wl_surface@70) To me that pictures looks ~308x208? If it's not, please reopen, -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425127] Uneven margins between all 4 sides
https://bugs.kde.org/show_bug.cgi?id=425127 --- Comment #2 from wg9rffujwz8y2...@airmail.cc --- Created attachment 130768 --> https://bugs.kde.org/attachment.cgi?id=130768=edit 2 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425127] Uneven margins between all 4 sides
https://bugs.kde.org/show_bug.cgi?id=425127 --- Comment #4 from wg9rffujwz8y2...@airmail.cc --- Created attachment 130770 --> https://bugs.kde.org/attachment.cgi?id=130770=edit 4 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425127] Uneven margins between all 4 sides
https://bugs.kde.org/show_bug.cgi?id=425127 --- Comment #3 from wg9rffujwz8y2...@airmail.cc --- Created attachment 130769 --> https://bugs.kde.org/attachment.cgi?id=130769=edit 3 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425127] Uneven margins between all 4 sides
https://bugs.kde.org/show_bug.cgi?id=425127 --- Comment #5 from wg9rffujwz8y2...@airmail.cc --- Created attachment 130771 --> https://bugs.kde.org/attachment.cgi?id=130771=edit 5 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416584] libs-image-kis_colorize_mask_test (Failed)
https://bugs.kde.org/show_bug.cgi?id=416584 Dmitry Kazakov changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/88aa1a2bd ||9d04dbb3e6cc3468de8ba81f502 ||4427 Resolution|--- |FIXED --- Comment #1 from Dmitry Kazakov --- Git commit 88aa1a2bd9d04dbb3e6cc3468de8ba81f5024427 by Dmitry Kazakov. Committed on 10/08/2020 at 22:48. Pushed by dkazakov into branch 'krita/4.3'. Fix first redo() after paint device color space conversion There is a bug in all versions of Krita since November, 5th 2019. BUG === 1) Change image color space from RGBA to GrayA. 2) Undo with Ctrl+Z 3) Redo with Ctrl+Shift+Z The image looks as if the color space has changed back to GrayA, but it is not so. Only the color space of the projection has changed to GrayA, the layers are still in RGBA. It can be seen by the state of Advanced Color Selector (it shows colors instead of shades of gray) and in layers' properties. WORKAROUND == 1) Press Undo (Ctrl+Z) and Redo (Ctrl+Shift+Z) again. The image will enter the correct state. All further undo/redo operations for this particular action will be executed correctly. TECHNICAL DETAILS = The bug was called by commit e39e6379564b5f6c4c72960a6e1ee3ca7716d5bd, which caused DeviceChangeColorSpaceCommand to skip the first redo of the operation, which was not in its design. The bug has been caught by KisColorizeMaskTest. CC:kimages...@kde.org M +1-1libs/command/kis_command_utils.cpp M +15 -15 libs/image/kis_paint_device_data.h https://invent.kde.org/graphics/krita/commit/88aa1a2bd9d04dbb3e6cc3468de8ba81f5024427 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 425148] okular import of old embedded annotations does not import the original create/modify time stamp
https://bugs.kde.org/show_bug.cgi?id=425148 --- Comment #8 from Albert Astals Cid --- (In reply to jprorama from comment #7) > I'm running into an issue with polkit-qt-1. Just don't build polkit-qt-1, it's not needed for what you want to test. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425206] New: The Stable Aug 10 appimage has improperly working Watercolour brush presets
https://bugs.kde.org/show_bug.cgi?id=425206 Bug ID: 425206 Summary: The Stable Aug 10 appimage has improperly working Watercolour brush presets Product: krita Version: nightly build (please specify the git hash!) Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: ahab.greybe...@hotmail.co.uk Target Milestone: --- SUMMARY In the latest 4.3.1 alpha appimage (git 040ab1a), the watercolour brush presets have their on-canvas outline as a square and many do not paint well. The same presets, if saved as new presets, work fine in the 4.3.0 appimage. The 5.0.0 prealpha shows the same behaviour. I believe that this is not related to: https://bugs.kde.org/show_bug.cgi?id=423359 Turning layer visibility on/off and Save/re-Open show no change. Turning canvas graphics acceleration on/off shows no changes (except that the brush outline is purple instead of black with cga off but this seems to be a new thing for all preset outlines). STEPS TO REPRODUCE 1. Run 4.3.0 and note the appearance and behaviour of the Watercolour brush presets. Especially observe j)_WaterC_Basic_Round-Fringe_02 and j)_WaterC_Flat_Big-Grain_Tilt as examples. 2. Repeat Step 1. but running the 4.3.1 alpha appimage. 3. Save new presets for j)_WaterC_Basic_Round-Fringe_02 and j)_WaterC_Flat_Big-Grain_Tilt 4. Run 4.3.0 and check the new saved watercolour brush presets. OBSERVED RESULT 1. They look good and they work (but some need a stylus rather than a mouse). 2a. Most have a square brush outline but use the same/correct brush tip as in 4.3.0 and they paint in black. not the selected colour. 2b. j)_WaterC_Basic_Round-Fringe_02 and j)_WaterC_Flat_Big-Grain_Tilt do not paint well but have the same/correct brush tip as in 4.3.0 4. The new saved watercolour presets behave well. EXPECTED RESULT Those brush presets should work as they do in 4.3.0. SOFTWARE/OS VERSIONS Krita Version: 4.3.1-alpha (git 040ab1a) Languages: en_GB, en, en, en_GB, en Hidpi: false Qt Version (compiled): 5.12.9 Version (loaded): 5.12.9 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 4.19.0-10-amd64 Pretty Productname: Debian GNU/Linux 10 (buster) Product Type: debian Product Version: 10 Desktop: MATE OpenGL Info Vendor: "NVIDIA Corporation" Renderer: "GeForce GTX 750 Ti/PCIe/SSE2" Version: "4.6.0 NVIDIA 440.100" Shading language: "4.60 NVIDIA" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format:QSurfaceFormat(version 4.6, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Version: 4.6 Supports deprecated functions true is OpenGL ES: false QPA OpenGL Detection Info supportsDesktopGL: true supportsOpenGLES: true isQtPreferOpenGLES: false ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425124] On the scratchpad, brush presets utilizing the speed sensor often aren't drawn accurately
https://bugs.kde.org/show_bug.cgi?id=425124 Ahab Greybeard changed: What|Removed |Added CC||ahab.greybe...@hotmail.co.u ||k Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Ahab Greybeard --- It does look like the detected speed on the scratchpad is noticably higher than on the canvas. It's difficult to quantify this because it's difficult to manually draw at any given speed, to repeat a particular speed or even know what the speed is. In addition, I believe that the detected speed signal is scaled too low and requires inconveniently high speeds to cover the full range of the transfer curve. This has been noted in: https://bugs.kde.org/show_bug.cgi?id=421098 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425190] Improve scaling of the desktop
https://bugs.kde.org/show_bug.cgi?id=425190 --- Comment #14 from Nate Graham --- David, I think Claudius is using the term "scaling" as a user understands the term, not as a KWin developer understands the term. Looking at the attachments, clearly there are differences in the different ways that images can be scaled up. Knowing that fractional scaling downscales from a doubled pixel-perfect version, it might be interesting to repeat the tests with downscaled images. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 425148] okular import of old embedded annotations does not import the original create/modify time stamp
https://bugs.kde.org/show_bug.cgi?id=425148 --- Comment #7 from jpror...@gmail.com --- (In reply to Albert Astals Cid from comment #6) > > To be fair we support upgrading from such old versions, one could argue that > the annotation timestamp being changed is even correct since now it's inside > the PDF and previously wasn't, but i guess one could argue that this is a > technicality and that the annotation was really added in the past to the > users point of view. Being the user, I naturally favor the second interpretation. ;) In that line of thinking, the annotation is a data object created by the user. That it was once stored in an an okular xml file and is now stored in the pdf itself is really of little importance to the user. It's the data that I created that I care about. In the current implementation, it's not just the timestamp that I would lose. Since the new annotation element is created by me, I'm the owner, the old object may in fact have a different owner listed in the xml. That owner information is also lost by not migrating the metadata and this seems a even more significant than the time stamp. Thanks for the additional thoughts and support in working on the migration. I'm still in the process of getting a pristine okular to build in my build env so that I can test out the proposed fix with my data. At the moment, most of the build dependencies succeed (78/84). I'm running into an issue with polkit-qt-1. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 425205] KMail crashes on first start after Tumbleweed dist-upgrade
https://bugs.kde.org/show_bug.cgi?id=425205 Peter Huyoff changed: What|Removed |Added CC||peter.huy...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 425188] Okular crashes opening PDFs from other apps
https://bugs.kde.org/show_bug.cgi?id=425188 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org --- Comment #4 from Albert Astals Cid --- This is a duplicate, as far as i remember someone else was having this QScreen crash -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 425148] okular import of old embedded annotations does not import the original create/modify time stamp
https://bugs.kde.org/show_bug.cgi?id=425148 --- Comment #6 from Albert Astals Cid --- (In reply to David Hurka from comment #4) > (In reply to Albert Astals Cid from comment #1) > > Sure, valid issue, but at this point how many people are left using such old > > versions that this is actually an issue we want to spend time fixing? > > Yes, I think we should support upgrading from such old versions. At least > when the fix does not require structural changes in Okular. The submitted MR > 239 looks promising to me, although it doesn’t pass tests right now. To be fair we support upgrading from such old versions, one could argue that the annotation timestamp being changed is even correct since now it's inside the PDF and previously wasn't, but i guess one could argue that this is a technicality and that the annotation was really added in the past to the users point of view. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416589] libs-image-kis_update_scheduler_test (Child aborted)
https://bugs.kde.org/show_bug.cgi?id=416589 Dmitry Kazakov changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/39252d9cb ||65a036e4e29444c77c09a2755ee ||f47a --- Comment #1 from Dmitry Kazakov --- Git commit 39252d9cb65a036e4e29444c77c09a2755eef47a by Dmitry Kazakov. Committed on 10/08/2020 at 21:47. Pushed by dkazakov into branch 'krita/4.3'. Unbreak KisUpdateSchedulerTest Looks like it has been fixed in the meantime. Both Windows and Linux builds run fine now. M +1-6libs/image/tests/CMakeLists.txt https://invent.kde.org/graphics/krita/commit/39252d9cb65a036e4e29444c77c09a2755eef47a -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 425188] Okular crashes opening PDFs from other apps
https://bugs.kde.org/show_bug.cgi?id=425188 --- Comment #3 from David Hurka --- Now my theory is that it will crash when you enable tabs and open a file from File -> Open. Right? (Settings -> Configure Okular -> General -> Open new files in tabs) QScroller appears to access screen() of PageView although it hasn’t been shown yet. I think there was another bug much like this some weeks ago, don’t remember which. Can you try to install the debugging symbols and generate a new backtrace? If that works, it could make our job easier. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 425205] New: KMail crashes on first start after Tumbleweed dist-upgrade
https://bugs.kde.org/show_bug.cgi?id=425205 Bug ID: 425205 Summary: KMail crashes on first start after Tumbleweed dist-upgrade Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: peter.huy...@gmx.de Target Milestone: --- Application: akonadiserver (5.14.3 (20.04.3)) Qt Version: 5.15.0 Frameworks Version: 5.72.0 Operating System: Linux 5.7.11-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - Unusual behavior I noticed: After the latest dist-upgrade plasma-desktop doesn`t come up. (Maybe the proprietary nvidia drivers not compile and nouveau has problems with plasma) KMail runs up in fullscreen but akonadi crashes. After restarting it, KMail runs properly. The crash can be reproduced sometimes. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault [KCrash Handler] #4 0x7fd8834cb9de in std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x7fd83080) at /usr/include/c++/10/bits/atomic_base.h:420 #5 QAtomicOps::loadRelaxed (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239 #6 QBasicAtomicInteger::loadRelaxed (this=0x7fd83080) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:107 #7 QtPrivate::RefCount::deref (this=0x7fd83080) at ../../include/QtCore/../../src/corelib/tools/qrefcount.h:66 #8 QString::operator= (this=this@entry=0x7fd830465088, other=...) at text/qstring.cpp:2395 #9 0x55b6267d7864 in Akonadi::Server::ItemRetrievalManager::retrievalJobFinished (this=0x55b62785bd20, request=0x7fd830465070, errorMsg=...) at /usr/src/debug/akonadi-server-20.04.3-1.1.x86_64/src/server/storage/itemretrievalmanager.cpp:176 #10 0x7fd88365f0f6 in QtPrivate::QSlotObjectBase::call (a=0x7fd87d5778b0, r=0x55b62785bd20, this=0x7fd868008130) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #11 doActivate (sender=0x7fd87802e7c0, signal_index=3, argv=argv@entry=0x7fd87d5778b0) at kernel/qobject.cpp:3886 #12 0x7fd883658450 in QMetaObject::activate (sender=sender@entry=0x7fd87802e7c0, m=m@entry=0x55b626899000 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fd87d5778b0) at kernel/qobject.cpp:3946 #13 0x55b6267d9378 in Akonadi::Server::AbstractItemRetrievalJob::requestCompleted (_t2=..., _t1=, this=0x7fd87802e7c0) at /usr/src/debug/akonadi-server-20.04.3-1.1.x86_64/build/src/server/libakonadiserver_autogen/5XLNPBDXWK/moc_itemretrievaljob.cpp:136 #14 Akonadi::Server::ItemRetrievalJob::callFinished (this=0x7fd87802e7c0, watcher=) at /usr/src/debug/akonadi-server-20.04.3-1.1.x86_64/src/server/storage/itemretrievaljob.cpp:78 #15 0x7fd88365f0f6 in QtPrivate::QSlotObjectBase::call (a=0x7fd87d577a00, r=0x7fd87802e7c0, this=0x7fd8680084c0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #16 doActivate (sender=0x7fd868005380, signal_index=3, argv=argv@entry=0x7fd87d577a00) at kernel/qobject.cpp:3886 #17 0x7fd883658450 in QMetaObject::activate (sender=, m=m@entry=0x7fd8839de5e0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fd87d577a00) at kernel/qobject.cpp:3946 #18 0x7fd8839beabf in QDBusPendingCallWatcher::finished (this=, _t1=) at .moc/moc_qdbuspendingcall.cpp:158 #19 0x7fd883654b41 in QObject::event (this=0x7fd868005380, e=0x55b62785fda0) at kernel/qobject.cpp:1314 #20 0x7fd883628bef in doNotify (event=0x55b62785fda0, receiver=0x7fd868005380) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:116 #21 QCoreApplication::notify (event=, receiver=, this=) at kernel/qcoreapplication.cpp:1137 #22 QCoreApplication::notifyInternal2 (receiver=0x7fd868005380, event=0x55b62785fda0) at kernel/qcoreapplication.cpp:1061 #23 0x7fd88362b641 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x55b627825c20) at kernel/qcoreapplication.cpp:1815 #24 0x7fd8836809d3 in postEventSourceDispatch (s=0x7fd8680047b0) at kernel/qeventdispatcher_glib.cpp:277 #25 0x7fd8819bd2b7 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #26 0x7fd8819bd638 in ?? () from /usr/lib64/libglib-2.0.so.0 #27 0x7fd8819bd6ef in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #28 0x7fd88368005f in QEventDispatcherGlib::processEvents (this=0x7fd868000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #29 0x7fd8836275db in QEventLoop::exec (this=this@entry=0x7fd87d577da0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #30 0x7fd88344973e in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #31 0x7fd88344a871 in
[krita] [Bug 416582] libs-image-kis_selection_test (Failed)
https://bugs.kde.org/show_bug.cgi?id=416582 Dmitry Kazakov changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||dimul...@gmail.com Resolution|--- |FIXED --- Comment #1 from Dmitry Kazakov --- KisSelectionTest has been unbroken in 6f283ca981fd8ecf3e85ba2fd8859e75e0670b80 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416586] libs-image-kis_async_merger_test (Failed)
https://bugs.kde.org/show_bug.cgi?id=416586 Dmitry Kazakov changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||dimul...@gmail.com Resolution|--- |FIXED --- Comment #1 from Dmitry Kazakov --- Async merger has been unbroken in 47fdcd94e4e06422271beee74a7db4937acb9484 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416602] libs-ui-kis_animation_frame_cache_test (Child aborted)
https://bugs.kde.org/show_bug.cgi?id=416602 Dmitry Kazakov changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/9f9ee7438 ||6dc169860032821beccbb29fbc7 ||9aa1 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Dmitry Kazakov --- Git commit 9f9ee74386dc169860032821beccbb29fbc79aa1 by Dmitry Kazakov. Committed on 10/08/2020 at 21:36. Pushed by dkazakov into branch 'krita/4.3'. Fix and unbreak KisAnimationFrameCacheTest M +25 -7libs/ui/opengl/kis_opengl_image_textures.cpp M +3-1libs/ui/opengl/kis_opengl_image_textures.h M +1-6libs/ui/tests/CMakeLists.txt M +17 -3libs/ui/tests/kis_animation_frame_cache_test.cpp M +7-0libs/ui/tests/kis_animation_frame_cache_test.h https://invent.kde.org/graphics/krita/commit/9f9ee74386dc169860032821beccbb29fbc79aa1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416603] libs-ui-kis_derived_resources_test (Child aborted)
https://bugs.kde.org/show_bug.cgi?id=416603 Dmitry Kazakov changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/8ea2e8b7b ||72fdb475f52936c917920b2df02 ||f0cf Resolution|--- |FIXED --- Comment #1 from Dmitry Kazakov --- Git commit 8ea2e8b7b72fdb475f52936c917920b2df02f0cf by Dmitry Kazakov. Committed on 10/08/2020 at 20:10. Pushed by dkazakov into branch 'krita/4.3'. Fix and unbreak KisDerivedResourcesTest M +1-6libs/ui/tests/CMakeLists.txt M +8-23 libs/ui/tests/kis_derived_resources_test.cpp https://invent.kde.org/graphics/krita/commit/8ea2e8b7b72fdb475f52936c917920b2df02f0cf -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 425196] Removing KMyMoney Focus Auto Inputs Transaction Amount
https://bugs.kde.org/show_bug.cgi?id=425196 jesse changed: What|Removed |Added CC||jvap...@yahoo.com --- Comment #1 from jesse --- Can I +1 this? :) This happens to me also when bouncing between ledgers. I go to see check one Credit card and come back to my bank and the amount has been entered. It can get confusing as sometimes, the date is also an older date (maybe I had to enter a previous transaction) and now there is a transaction out there with the wrong amount and wrong date.. lol -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 425204] New: Installer of neon unstable 20.04 creates a passwordless user account without administrator privileges
https://bugs.kde.org/show_bug.cgi?id=425204 Bug ID: 425204 Summary: Installer of neon unstable 20.04 creates a passwordless user account without administrator privileges Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Live/Install images Assignee: neon-b...@kde.org Reporter: bugsefor...@gmx.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Today I installed neon unstable based on ubuntu 20.04 and I can't start plasma with the password typed during install process. I can start plasma without a password but User kcm indicates that I'm using a default user account and I can't do anything that requires administrator privileges. I have downloaded neon-unstable-20200810-1849.iso -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425190] Improve scaling of the desktop
https://bugs.kde.org/show_bug.cgi?id=425190 --- Comment #13 from David Edmundson --- I said the specific thing in your screenshot shouldn't be upscaled. If fractional scaling was applied that could result in a downscale of the original client texture. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425151] Some times there is shadows, some times don't
https://bugs.kde.org/show_bug.cgi?id=425151 --- Comment #4 from viniciusbr --- Ok. I did it. Let's test. If it back again I return here. Many thanks -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 425194] Discover crash if we open a .deb file from firefox (without saving the file)
https://bugs.kde.org/show_bug.cgi?id=425194 Nate Graham changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||n...@kde.org --- Comment #1 from Nate Graham --- Cannot reproduce with Discover from git master using the .deb or .rpm packages available at https://www.dropbox.com/install-linux. Can you provide a link to the .deb file that made Discover crash, and let us know if it happens to you for the one at https://www.dropbox.com/install-linux? -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 425180] krunner dictionary doesn't work
https://bugs.kde.org/show_bug.cgi?id=425180 Nate Graham changed: What|Removed |Added CC||n...@kde.org --- Comment #2 from Nate Graham --- I think this was only fixed just recently, in which case using Plasma 5.18 might cause you to not have the fix. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 425187] An application explorer Discover crash
https://bugs.kde.org/show_bug.cgi?id=425187 Nate Graham changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||n...@kde.org Resolution|--- |WAITINGFORINFO --- Comment #1 from Nate Graham --- I think you forgot to put information in the bug report. :) Please see https://community.kde.org/Get_Involved/Issue_Reporting to learn how to file bug reports. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 425192] Screens overlap on Wayland when scaling is fractional
https://bugs.kde.org/show_bug.cgi?id=425192 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 425188] Okular crashes opening PDFs from other apps
https://bugs.kde.org/show_bug.cgi?id=425188 Nate Graham changed: What|Removed |Added CC||n...@kde.org --- Comment #2 from Nate Graham --- Thread 1 (Thread 0x7f5185bb1800 (LWP 12569)): [KCrash Handler] #6 0x7f5189924ea4 in QScreen::size() const () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #7 0x7f5189925071 in QScreen::physicalDotsPerInchY() const () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #8 0x7f518a2b6d96 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7f518a2b9f9c in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7f518a2bb48f in QScroller::scrollTo(QPointF const&, int) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 # That's odd. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 425184] Big glitch on screenshot in moment doing screenshot
https://bugs.kde.org/show_bug.cgi?id=425184 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 425185] Display Configuration allows to replicate screen for turned off screen
https://bugs.kde.org/show_bug.cgi?id=425185 Nate Graham changed: What|Removed |Added CC||n...@kde.org, ||plasma-b...@kde.org Component|general |kcm_kscreen Assignee|plasma-b...@kde.org |kscreen-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425191] Allow folder creation on desktop via F10 shortcut
https://bugs.kde.org/show_bug.cgi?id=425191 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Keywords||junior-jobs Status|REPORTED|CONFIRMED Severity|normal |wishlist CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kdenetwork-filesharing] [Bug 425203] New: If guest access to Samba shares is globally disabled, either warn the user ahead of time or prompt to turn it on
https://bugs.kde.org/show_bug.cgi?id=425203 Bug ID: 425203 Summary: If guest access to Samba shares is globally disabled, either warn the user ahead of time or prompt to turn it on Product: kdenetwork-filesharing Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: n...@kde.org Reporter: n...@kde.org Target Milestone: --- On openSUSE, apparently guest access for Samba shares is globally disabled by default. As a result, if you attempt to enable guest access for a samba share you're creating, it will currently just fail silently. With https://invent.kde.org/network/kdenetwork-filesharing/-/merge_requests/2 applied, you will see an appropriate though still fairly cryptic error message: net usershare add: guest_ok=y requested but the "usershare allow guests" parameter is not enabled by this server. This is much better than nothing, but it would be even better if it could warn you ahead of time, potentially even inline, when you click on the checkbox to enable guest access. For bonus points, it could even prompt you to turn on guest access globally, which as far as I can tell involves the following change to smb.conf: diff samba_working.conf samba_broken.conf 15c15 < usershare allow guests = Yes --- > usershare allow guests = No -- You are receiving this mail because: You are watching all bug changes.
[kdenetwork-filesharing] [Bug 425203] If guest access to Samba shares is globally disabled, either warn the user ahead of time or prompt to turn it on
https://bugs.kde.org/show_bug.cgi?id=425203 Nate Graham changed: What|Removed |Added CC||fab...@ritter-vogt.de, ||sit...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kdenetwork-filesharing] [Bug 425202] If Samba shares are globally disabled, either warn the user ahead of time or prompt to turn it on
https://bugs.kde.org/show_bug.cgi?id=425202 Nate Graham changed: What|Removed |Added CC||fab...@ritter-vogt.de, ||sit...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kdenetwork-filesharing] [Bug 425202] New: If Samba shares are globally disabled, either warn the user ahead of time or prompt to turn it on
https://bugs.kde.org/show_bug.cgi?id=425202 Bug ID: 425202 Summary: If Samba shares are globally disabled, either warn the user ahead of time or prompt to turn it on Product: kdenetwork-filesharing Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: n...@kde.org Reporter: n...@kde.org Target Milestone: --- On openSUSE, apparently Samba sharing is globally disabled by default. As a result, if you attempt to create a Samba share, it will currently just fail silently. With https://invent.kde.org/network/kdenetwork-filesharing/-/merge_requests/2 applied, you will at least see a fairly cryptic error message: net usershare add: usershares are currently disabled This is much better than nothing, but it would be even better if it could warn you ahead of time, potentially even inline, when you click on the checkbox to share a folder. For bonus points, it could even prompt you to enable samba shares globally, which as far as I can tell involves the following change to smb.conf: diff samba_working.conf samba_broken.conf 17c17,19 < usershare max shares = 100 --- > ldap admin dn = > wins server = > wins support = No -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 425176] Zoom On Hover cannot be disabled
https://bugs.kde.org/show_bug.cgi?id=425176 Michail Vourlakos changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #3 from Michail Vourlakos --- pretty simple, it is not maintained because I don't maintain it. If you find someone else to maintain it feel free to inform me. I develop only git, master version nowadays. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 425201] Tor Browser can no longer be started using "start-tor-browser.desktop"
https://bugs.kde.org/show_bug.cgi?id=425201 --- Comment #1 from Christoph Feck --- #!/usr/bin/env ./Browser/execdesktop # # This file is a self-modifying .desktop file that can be run from the shell. # It preserves arguments and environment for the start-tor-browser script. # # Run './start-tor-browser.desktop --help' to display the full set of options. # # When invoked from the shell, this file must always be in a Tor Browser root # directory. When run from the file manager or desktop GUI, it is relocatable. # # After first invocation, it will update itself with the absolute path to the # current TBB location, to support relocation of this .desktop file for GUI # invocation. You can also add Tor Browser to your desktop's application menu # by running './start-tor-browser.desktop --register-app' # # If you use --register-app, and then relocate your TBB directory, Tor Browser # will no longer launch from your desktop's app launcher/dock. However, if you # re-run --register-app from inside that new directory, the script # will correct the absolute paths and re-register itself. # # This file will also still function if the path changes when TBB is used as a # portable app, so long as it is run directly from that new directory, either # via the shell or via the file manager. [Desktop Entry] Type=Application Name=Tor Browser GenericName=Web Browser Comment=Tor Browser is +1 for privacy and −1 for mass surveillance Categories=Network;WebBrowser;Security; Exec=sh -c '"/home/USER/TorBrowser/Browser/start-tor-browser" --detach || ([ ! -x "/home/USER/TorBrowser/Browser/start-tor-browser" ] && "$(dirname "$*")"/Browser/start-tor-browser --detach)' dummy %k X-TorBrowser-ExecShell=./Browser/start-tor-browser --detach Icon=/home/USER/TorBrowser/Browser/browser/chrome/icons/default/default128.png StartupWMClass=Tor Browser -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 425201] New: Tor Browser can no longer be started using "start-tor-browser.desktop"
https://bugs.kde.org/show_bug.cgi?id=425201 Bug ID: 425201 Summary: Tor Browser can no longer be started using "start-tor-browser.desktop" Product: frameworks-kio Version: 5.73.0 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kio-bugs-n...@kde.org Reporter: cf...@kde.org CC: kdelibs-b...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. Download Tor Browser Bundle, unpack where filesystem has 'exec' permission 2. Navigate into its "Browser" folder, and click "start-tor-browser" (without .desktop); this will cause the paths in the parent folder's .desktop file to get updated 3. Exit Tor Browser and/or its network setup 4. Go back to parent folder, and click "start-tor-browser.desktop" 5. Click "Execute" on "What do you want to do with this executable file?" dialog OBSERVED RESULT Nothing happens EXPECTED RESULT Tor Browser appears SOFTWARE/OS VERSIONS KDE Plasma Version: 5.19.80 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION This worked with earlier frameworks versions. Adding the start-tor-browser.desktop file in next comment for reference, it assumes the Tor Browser was unpacked into "/home/USER/TorBrowser" folder. -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 425200] Add [year] to album tag
https://bugs.kde.org/show_bug.cgi?id=425200
--- Comment #1 from Urs Fleisch ---
You can do this with menu function "File/Import from Tags...". In the same way
as the predefined example "Track Number to Title" you can define a new Format
"Year to Album" with Source "[%{year}] %{album}" and Extraction "%{album}(.*)".
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 422726] [Wayland] The shutdown / logout widget does not respond on first click
https://bugs.kde.org/show_bug.cgi?id=422726 --- Comment #8 from Andrey --- (In reply to tromzy from comment #3) > Actually it's not a Wayland-specific problem, since it also happens on X11 > on my machine. Is it still happens? Shall we remove "Wayland" from title/flags? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 424986] "New Tab" session menu does not work
https://bugs.kde.org/show_bug.cgi?id=424986 --- Comment #3 from Christoph Feck --- I updated to f4bf8a42 and the issue is still reproducible using the steps from comment 0. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 425111] UHD Resolution on HDMI / On TV's with ~ 43" or more
https://bugs.kde.org/show_bug.cgi?id=425111 blackcrack changed: What|Removed |Added Resolution|UPSTREAM|--- Status|RESOLVED|REPORTED --- Comment #6 from blackcrack --- well, Gnomedesktop and other Desktop works well.. but KDE/Plasma not with nouveau drivers.. what's there wring ? Because only Plasma works not.. i be to less programmer for know directly what's goes on.. but once do i know.. Plasma have a Problem, other WM's not.. so it's easy to say it's a nouveau problem, no, on other Desktops works it.. best regards Blacky -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 390875] Plasma Widgets from KDE Store can not be uninstalled via Widget Explorer
https://bugs.kde.org/show_bug.cgi?id=390875 Alexander Lohnau changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #7 from Alexander Lohnau --- Without having any specific plan on how to implement this let me propose an alternative concept: When deleting an entry we move the file on disk to a temporary location and write in a variable that we can restore this entry. This variable in only in memory, meaning that when we restart the session we can't restore the entry. And whenever we start a new session we clean the temporary location. This way we make the behavior more predictable(the 60 seconds seem pretty random IMO) and ensure that the operation executed by the user gets applied. And we also avoid the case where a user is customizing and cleaning up the plasma config and thinks that they have all the time of the world to restore the entry. This can be even more confusing considering that the entry is not immediately removed from the KNS list of installed entries. This happened to me when I was really new to KDE ;-) -- You are receiving this mail because: You are watching all bug changes.
