[systemsettings] [Bug 489177] New: Screen dims then locks when playing steam or battle net games
https://bugs.kde.org/show_bug.cgi?id=489177 Bug ID: 489177 Summary: Screen dims then locks when playing steam or battle net games Classification: Applications Product: systemsettings Version: git-stable-Plasma/6.1 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: kcm_screenlocker Assignee: plasma-b...@kde.org Reporter: capone6...@yahoo.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE 1. Play D4 for more then 15min 2. Play Division 2 to for same time 3. Play with controller OBSERVED RESULT Screen Dims Screen Turns off Screen Locks EXPECTED RESULT Not to dim while playing SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 6.1 (available in About System) KDE Plasma Version: 6.1 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Seems to not register as active while using a controller and locks the screen -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 487772] New: Doing multiple operations no longer uses previously calculated value as the first value in the calculation.
https://bugs.kde.org/show_bug.cgi?id=487772 Bug ID: 487772 Summary: Doing multiple operations no longer uses previously calculated value as the first value in the calculation. Classification: Applications Product: kcalc Version: 24.05.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: evan.te...@gmail.com Reporter: n...@nschoonover.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE 1. Perform any operation, such as 2 + 2 2. Do another operation on the previously calculated value, such as + 2, without manually entering the previously calculated value. 3. OBSERVED RESULT The previously calculated value is not carried over to the new operation. Doing the above will result in 2, rather than carrying over the 4 from the previous operation and adding up to 6. EXPECTED RESULT KCalc should take the previously calculated value and allow you to keep operating on that value without it needing to be manually reentered. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 484682] Since 6.0.3, global shortcuts do not persist settings across sessions and behave erratically
https://bugs.kde.org/show_bug.cgi?id=484682 Nicholas Kinney changed: What|Removed |Added CC||kinneyan...@gmail.com --- Comment #16 from Nicholas Kinney --- (In reply to bugreporter42 from comment #15) > (In reply to bugreporter42 from comment #14) > > Me too. Global shortcuts initially work, but after a reboot they likely > > disappear/stop working. > > That's been broken since Arch switched to Plasma 6. Definitely not correct, I have set my archive to the day before 6.0.3 launched and confirmed the behavior was not present before the upgrade. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 484884] Overriden default shortcuts stop working after relogin
https://bugs.kde.org/show_bug.cgi?id=484884 --- Comment #7 from Nicholas Kinney --- (In reply to Nicholas Kinney from comment #6) > (In reply to Dmitrii Chermnykh from comment #5) > > (In reply to Nicholas Kinney from comment #3) > > > (In reply to Dmitrii Chermnykh from comment #1) > > > > It's probably a NixOS packaging issue > > > > > > I'm experiencing the same issue on the latest stable arch release > > > > Does the problem reproduce for you if you wipe ~/.cache directory? > > This did solve the problem Actually, some of the shortcuts are still broken, it just changed which ones are affected. For example, I have a shortcut to capture a region of the screen with meta+shift+s, which appears to have a default binding in spectacle and is being overwritten. My override for the terminal shortcut ctrl+shift+t does work with terminator instead of konsole now after removing the .cache entries. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 484884] Overriden default shortcuts stop working after relogin
https://bugs.kde.org/show_bug.cgi?id=484884 --- Comment #6 from Nicholas Kinney --- (In reply to Dmitrii Chermnykh from comment #5) > (In reply to Nicholas Kinney from comment #3) > > (In reply to Dmitrii Chermnykh from comment #1) > > > It's probably a NixOS packaging issue > > > > I'm experiencing the same issue on the latest stable arch release > > Does the problem reproduce for you if you wipe ~/.cache directory? This did solve the problem -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 484884] Overriden default shortcuts stop working after relogin
https://bugs.kde.org/show_bug.cgi?id=484884 Nicholas Kinney changed: What|Removed |Added CC||kinneyan...@gmail.com --- Comment #3 from Nicholas Kinney --- (In reply to Dmitrii Chermnykh from comment #1) > It's probably a NixOS packaging issue I'm experiencing the same issue on the latest stable arch release -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 481195] New: SDDM password field does not submit when the Enter key is pressed
https://bugs.kde.org/show_bug.cgi?id=481195 Bug ID: 481195 Summary: SDDM password field does not submit when the Enter key is pressed Classification: I don't know Product: kde Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: k...@nicholasjestrada.aleeas.com Target Milestone: --- SUMMARY SDDM password field does not submit when the Enter key is pressed. Might be a duplicate of https://bugs.kde.org/show_bug.cgi?id=478875 Not sure, because that one mentions X11 and the virtual keyboard specifically, neither of which apply to my setup. STEPS TO REPRODUCE 1. Restart computer 2. Type in password 3. Press [Enter] OBSERVED RESULT Does not log in or try to submit the password EXPECTED RESULT Submits the password Operating System: KDE neon Unstable Edition KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.1 Kernel Version: 6.5.0-17-generic (64-bit) Graphics Platform: Wayland Processors: 4 × AMD Ryzen 3 3200U with Radeon Vega Mobile Gfx Memory: 13.6 GiB of RAM Graphics Processor: AMD Radeon Vega 3 Graphics Manufacturer: MOTILE Product Name: M141 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 474464] Preview Shifts All Windows
https://bugs.kde.org/show_bug.cgi?id=474464 Nicholas Kinney changed: What|Removed |Added Resolution|WORKSFORME |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 474464] Preview Shifts All Windows
https://bugs.kde.org/show_bug.cgi?id=474464 --- Comment #8 from Nicholas Kinney --- (In reply to Nicholas Kinney from comment #7) > (In reply to Nicholas Kinney from comment #6) > > (In reply to Nate Graham from comment #3) > > > Thanks. Is your global scale set to 100%, or something else? > > > > > > Does the same problem happen on Wayland too? > > > > My global scale is at 125%, I have not tried with Wayland, but if needed I > > can see what happens. > > The issue does not appear to persist when running wayland, even with wayland > configured to also use a 125% scaling. Disabling global scaling on x11 does appear to resolve the issue as well -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 474464] Preview Shifts All Windows
https://bugs.kde.org/show_bug.cgi?id=474464 --- Comment #7 from Nicholas Kinney --- (In reply to Nicholas Kinney from comment #6) > (In reply to Nate Graham from comment #3) > > Thanks. Is your global scale set to 100%, or something else? > > > > Does the same problem happen on Wayland too? > > My global scale is at 125%, I have not tried with Wayland, but if needed I > can see what happens. The issue does not appear to persist when running wayland, even with wayland configured to also use a 125% scaling. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 474464] Preview Shifts All Windows
https://bugs.kde.org/show_bug.cgi?id=474464 --- Comment #6 from Nicholas Kinney --- (In reply to Nate Graham from comment #3) > Thanks. Is your global scale set to 100%, or something else? > > Does the same problem happen on Wayland too? My global scale is at 125%, I have not tried with Wayland, but if needed I can see what happens. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 477817] Need to save the login credentials for Mediawiki export persistent
https://bugs.kde.org/show_bug.cgi?id=477817 nicholas changed: What|Removed |Added Summary|Need to save the login |Need to save the login |credentials for Mediawikit |credentials for Mediawiki |export persistent |export persistent -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 477817] New: Need to save the login credentials for Mediawikit export persistent
https://bugs.kde.org/show_bug.cgi?id=477817 Bug ID: 477817 Summary: Need to save the login credentials for Mediawikit export persistent Classification: Applications Product: digikam Version: 8.1.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: wishlist Priority: NOR Component: Plugin-WebService-MediaWiki Assignee: digikam-bugs-n...@kde.org Reporter: ijnicho...@yahoo.com Target Milestone: --- As of now the pluging for Mediawikit does not save the login credentials within Digikam. This is a pain. When ever, I want to upload pictures, I have to enter the login and password. This is not needed. Can you please provide an option to save the login credentials, so that repetitive login/password entries can be avoided. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 474464] Preview Shifts All Windows
https://bugs.kde.org/show_bug.cgi?id=474464 --- Comment #2 from Nicholas Kinney --- (In reply to Nate Graham from comment #1) > Can you describe your screen setup, GPU hardware, and mention whether you're > using X11 or Wayland? Three monitors bottom justified, 1920x1080 on the left, 2560x1440 in the middle, and another 1920x1080 on the right. Running x11 with a 7900xtx with Mesa 23.1.6-arch1.4. Running kernel 6.4.12-arch1-1. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 474464] New: Preview Shifts All Windows
https://bugs.kde.org/show_bug.cgi?id=474464 Bug ID: 474464 Summary: Preview Shifts All Windows Classification: Applications Product: Spectacle Version: 23.08.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: kinneyan...@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY *** Entering the screenshot preview interface (which I reach through a shortcut that runs spectacle -rbnceo /tmp/screenshot.png ) causes every window to shift, attempting to select a region for the screenshot will now be inaccurate because the region is taken from the actual position of the windows and not the shifted positions. *** STEPS TO REPRODUCE 1. Hit Screenshot OBSERVED RESULT All windows shift in preview EXPECTED RESULT Windows should remain in their actual location on the desktop SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Problem was resolved by downgrading the version I had installed last (23.08.0-1) kde-cli-tools 5.27.7-1 kde-gtk-config 5.27.7-1 kdeclarative 5.109.0-1 kdeconnect 23.08.0-1 kdecoration 5.27.7-1 kded 5.109.0-1 kdelibs4support 5.109.0-1 kdeplasma-addons 5.27.7-1 kdesu 5.109.0-1 libblockdev 2.28-4 polkit-kde-agent 5.27.7-1 qt5-base 5.15.10+kde+r155-1 qt5-declarative 5.15.10+kde+r31-1 qt5-location 5.15.10+kde+r4-2 qt5-multimedia 5.15.10+kde+r3-1 qt5-quickcontrols2 5.15.10+kde+r6-1 qt5-speech 5.15.10+kde+r1-1 qt5-svg 5.15.10+kde+r8-1 qt5-tools 5.15.10+kde+r3-2 qt5-wayland 5.15.10+kde+r57-1 qt5-webchannel 5.15.10+kde+r3-1 xdg-desktop-portal-kde 5.27.7-1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471810] New: Waydroid decorations don't paint background properly
https://bugs.kde.org/show_bug.cgi?id=471810 Bug ID: 471810 Summary: Waydroid decorations don't paint background properly Classification: Plasma Product: kwin Version: 5.27.6 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: vano...@gmail.com Target Milestone: --- Created attachment 160011 --> https://bugs.kde.org/attachment.cgi?id=160011=edit Image showing the issues described above SUMMARY When running waydroid in multi-window mode, the decorations don't paint properly under kwin. The action buttons (close, maximise, minimise) are drawn, but no background is drawn. Shadows suggest that the window is being drawn smaller than expected: the outer edge of the shadow around the titlebar matches the outer edge of the rest of the window's content. (See attached image!) STEPS TO REPRODUCE 1. Install waydroid, and enable multi-window mode ( waydroid prop set persist.waydroid.multi_windows true ) 2. Run an android app. If necessary, switch to multi-window mode by pressing the F11 key 3. Note the corruption in the header. OBSERVED RESULT Titlebar area has no background drawn. EXPECTED RESULT Background should be a solid colour, as it is under mutter. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Kernel Version: 6.3.8-200.fc38.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz Memory: 11.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 458266] When ktorrent is closed and a torrent file is opened it is no being added to ktorrent
https://bugs.kde.org/show_bug.cgi?id=458266 Nicholas Redgrave changed: What|Removed |Added CC||ba...@bologrew.net --- Comment #2 from Nicholas Redgrave --- Still present in version 22.12.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465740] If a floating tile is split nether splits can be deleted
https://bugs.kde.org/show_bug.cgi?id=465740 --- Comment #1 from Nicholas Omann --- Sorry for the quick comment but I have more information from testing. I did confirm same behavior when vertical is done instead and it's not just delete all the buttons for the split tile close the layout editor. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465740] New: If a floating tile is split nether splits can be deleted
https://bugs.kde.org/show_bug.cgi?id=465740 Bug ID: 465740 Summary: If a floating tile is split nether splits can be deleted Classification: Plasma Product: kwin Version: 5.27.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Custom Tiling Assignee: kwin-bugs-n...@kde.org Reporter: alphaclus...@linux.com CC: notm...@gmail.com Target Milestone: --- SUMMARY If you happen to split (in my case i had done it horizontally) a floating tile clicking delete on either split tile will close the layout designer rather then delete the split. STEPS TO REPRODUCE 1. Add a floating tile 2. Split Horizontally 3. Press Delete OBSERVED RESULT Tiling layout manager closes. EXPECTED RESULT Split tile that delete was clicked on should be deleted. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 450855] Upower Not suspending
https://bugs.kde.org/show_bug.cgi?id=450855 --- Comment #2 from Nicholas --- thank you! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 450855] New: Upower Not suspending
https://bugs.kde.org/show_bug.cgi?id=450855 Bug ID: 450855 Summary: Upower Not suspending Product: kde Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: trovianflip...@gmail.com Target Milestone: --- I was experimenting with using Howdy for some facial recognition unlocks, but somewhere along the line, I realized that my computer stopped suspending/locking when the lid was closed! I uninstalled howdy, and it went back to normal, and investigating `systemd-inhibit` the only difference was that suspend worked when `UPower` was not present. However, I removed howdy, and now `Upower` is still there, but it is listed as a dependency of kio, so I can't remove it. STEPS TO REPRODUCE 1. Install howdy 2. reboot 3. Check if upower shows up with `systemd-inhibit` 4. If it is, close lid of laptop 5. Open lid, and computer screen goes straight to desktop without any waiting. OBSERVED RESULT Screen doesn't lock or suspend EXPECTED RESULT It used to lock and suspend just fine. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.11-arch1-1 (64-bit) Graphics Platform: X11 Processors: 8 × AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx Memory: 14.6 GiB of RAM Graphics Processor: AMD Radeon Vega 8 Graphics -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 446729] Crashes with error: The Wayland connection broke. Did the Wayland compositor die?
https://bugs.kde.org/show_bug.cgi?id=446729 Nicholas Eckardt changed: What|Removed |Added CC||necka...@gmail.com --- Comment #3 from Nicholas Eckardt --- I'm also experiencing this bug. I initially used digikam 7.1.0 using SQLite. I attempted to run digiKam-7.5.0-x86-64.appimage, however I encountered https://bugs.kde.org/show_bug.cgi?id=427906 My OS is Debian 11, I'm also using sway. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 450018] New: Konsole tabs-from-file adds extra unwanted tab
https://bugs.kde.org/show_bug.cgi?id=450018 Bug ID: 450018 Summary: Konsole tabs-from-file adds extra unwanted tab Product: konsole Version: 21.08.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: tabbar Assignee: konsole-de...@kde.org Reporter: ba...@bologrew.net Target Milestone: --- Created attachment 146584 --> https://bugs.kde.org/attachment.cgi?id=146584=edit script for konsole tabs-from-file test SUMMARY *** When running konsole with "tabs-from-file" option, new konsole window has requested tabs plus an additional unwanted one. *** STEPS TO REPRODUCE 1. Run attached script or use: konsole --tabs-from-file ./konsoletabstest.txt with the following lines in the "konsoletabstest.txt" file: title: .local;; workdir: ~/.local;; profile: "Default" title: .config;; workdir: ~/.config;; profile: "Default" OBSERVED RESULT New konsole window with three tabs - two correct and one unwanted extra. EXPECTED RESULT New konsole window with two tabs. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 35 KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.5-200.fc35.x86_64 (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 450015] New: KDialog progress bar doesn't go to 100%
https://bugs.kde.org/show_bug.cgi?id=450015 Bug ID: 450015 Summary: KDialog progress bar doesn't go to 100% Product: kdialog Version: 21.08.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: br...@frogmouth.net Reporter: ba...@bologrew.net Target Milestone: --- Created attachment 146582 --> https://bugs.kde.org/attachment.cgi?id=146582=edit KDialog progress test script SUMMARY *** KDialog progress bar never shows a full bar and "100%" indication. *** STEPS TO REPRODUCE 1. Run attached script in a konsole window. OBSERVED RESULT Progress bar goes up to 66% and shows "66%" in text and then goes blank. EXPECTED RESULT Progress bar becomes full and shows "100%" in text. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 35 KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.5-200.fc35.x86_64 (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION The konsole window scrolls because qdbus emits carriage returns during the script. That can be fixed with liberal use of "> /dev/null" but it is annoying. The example uses two different methods of setting the progress bar value: qdbus $dbusRef Set "" value 1 and qdbus $dbusRef value 1 The first comes from the "Shell Scripting with KDE Dialogs" page at: https://develop.kde.org/deploy/kdialog/ and the second style is from the "progressdemo" example in the KDialog source repository "tests" directory. I do not know which style is best or whether there is any difference between the two. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 449901] Virtual Desktop Pager Resizes on Activity Change
https://bugs.kde.org/show_bug.cgi?id=449901 --- Comment #1 from Nicholas --- Apparently, that video might not work, so this is a link to an mp4. https://cdn.discordapp.com/attachments/691014970225197107/941128238086885396/example.mp4 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 449901] New: Virtual Desktop Pager Resizes on Activity Change
https://bugs.kde.org/show_bug.cgi?id=449901 Bug ID: 449901 Summary: Virtual Desktop Pager Resizes on Activity Change Product: kde Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: trovianflip...@gmail.com Target Milestone: --- Created attachment 146511 --> https://bugs.kde.org/attachment.cgi?id=146511=edit a brief video of the problem STEPS TO REPRODUCE 1. Make several vertical virtual desktops 2. Make a Pager widget on the desktop 3. Make the Widget tall and skinny 4. Switch to another activity, then come back OBSERVED RESULT The pager expands horizontally and is much larger than how it was set. EXPECTED RESULT That the widget would not change size. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.7-arch1-1 (64-bit) Graphics Platform: X11 Processors: 8 × AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx Memory: 14.6 GiB of RAM Graphics Processor: AMD Radeon Vega 8 Graphics -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 449619] Widgets not working properly on second activity
https://bugs.kde.org/show_bug.cgi?id=449619 Nicholas changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #5 from Nicholas --- After several incidental reboots, I tried again, and it worked. I think I just had to replace the old ones. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449541] Quick tile action via shortcut de-maximizes the window without tiling as a first action
https://bugs.kde.org/show_bug.cgi?id=449541 --- Comment #13 from Nicholas Serrano <2019nicho...@gmail.com> --- (In reply to Vlad Zahorodnii from comment #11) > As a workaround, select "No Borders" border size in system settings. I > believe it should fix the issue when using Sierra Breeze Enhanced This indeed works as a workaround, thanks for the tip -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449541] Quick tile action via shortcut de-maximizes the window without tiling as a first action
https://bugs.kde.org/show_bug.cgi?id=449541 --- Comment #10 from Nicholas Serrano <2019nicho...@gmail.com> --- I see. Thanks for looking into the issue and asking the right questions as I hadn't provided much info initially. I'll keep an eye on the mr and update this report/open a new one if I run into any issues after updating kwin to a version that should have the fix. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449541] Quick tile action via shortcut de-maximizes the window without tiling as a first action
https://bugs.kde.org/show_bug.cgi?id=449541 --- Comment #7 from Nicholas Serrano <2019nicho...@gmail.com> --- Ah I was typing up/recording a way to reproduce but saw your message. I was using Sierra Breeze Enhanced Window Decorations and after switching to Breeze the bugged behavior went away. It does seem associated with decorated windows when using that specific Window decoration theme. I assume I should open a bug report with the creator of Sierra Breeze Enhanced. (https://github.com/kupiqu/SierraBreezeEnhanced) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449541] Quick tile action via shortcut de-maximizes the window without tiling as a first action
https://bugs.kde.org/show_bug.cgi?id=449541 --- Comment #4 from Nicholas Serrano <2019nicho...@gmail.com> --- Just updated to the following: KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.5-200.fc35.x86_64 (64-bit) Using https://copr.fedorainfracloud.org/coprs/zawertun/kde/ I'm still running into this issue however have noticed that it does not affect gtk applications, for example the "Problem Reporting" app on Fedora, or rnote from flathub. Should I expect to have seen different behavior in 5.24 or have those fixes not been pushed to a release yet. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 449619] Widgets not working properly on second activity
https://bugs.kde.org/show_bug.cgi?id=449619 Nicholas changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- Ever confirmed|0 |1 --- Comment #4 from Nicholas --- (In reply to Nate Graham from comment #3) > This regression should be already fixed in Plasma 5.24. It got worse. I updated to 5.24 this morning (the 8th) and this evening, My desktops were all reset (the backgrounds were the default and all the widgets were gone, ALL desktops have the same unresponsive widgets as shown in the "not working" image. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 449619] Widgets not working properly on second activity
https://bugs.kde.org/show_bug.cgi?id=449619 Nicholas changed: What|Removed |Added Version Fixed In|5.24| -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 449741] New: Archiver crash
https://bugs.kde.org/show_bug.cgi?id=449741 Bug ID: 449741 Summary: Archiver crash Product: Akonadi Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Archive Mail Agent Assignee: kdepim-b...@kde.org Reporter: ba...@bologrew.net Target Milestone: --- Application: akonadi_archivemail_agent (5.18.3 (21.08.3)) Qt Version: 5.15.2 Frameworks Version: 5.90.0 Operating System: Linux 5.16.5-200.fc35.x86_64 x86_64 Windowing System: X11 Distribution: Fedora Linux 35 (KDE Plasma) DrKonqi: 5.23.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I had just defined three archiving events for my inbox, sent mail and received mail folders. I have several identities and one of them puts its sent mail into a different folder - or it would but whatever I call that folder gets automatically renamed to "sent-mail". I ended up with two "sent-mail" folders and the only why I could tell them apart was to change the icon on one of them and then I made it a sub-folder of the original "sent-mail". This may be a factor in the archiving failure. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: akonadi_archivemail_agent (akonadi_archivemail_agent), signal: Segmentation fault [KCrash Handler] #4 0x7f090c01b636 in QUrlPrivate::appendPath(QString&, QUrlTwoFlags, QUrlPrivate::Section) const () at /lib64/libQt5Core.so.5 #5 0x7f090c014fbd in QUrl::path(QFlags) const () at /lib64/libQt5Core.so.5 #6 0x55d911381bfd in ArchiveMailInfo::dirArchive(bool&) const [clone .constprop.0] () #7 0x55d911384018 in ArchiveJob::execute() () #8 0x7f090d016ca9 in MailCommon::JobScheduler::slotRunNextJob() () at /lib64/libKF5MailCommon.so.5 #9 0x7f090c0e23e9 in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #10 0x7f090c0e568e in QTimer::timeout(QTimer::QPrivateSignal) () at /lib64/libQt5Core.so.5 #11 0x7f090c0d8edf in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #12 0x7f090c5dc443 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #13 0x7f090c0ae7d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #14 0x7f090c0feea3 in QTimerInfoList::activateTimers() () at /lib64/libQt5Core.so.5 #15 0x7f090c0ff7ac in timerSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5 #16 0x7f0908f9d05f in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #17 0x7f0908ff22a8 in g_main_context_iterate.constprop () at /lib64/libglib-2.0.so.0 #18 0x7f0908f9a853 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #19 0x7f090c0ffbb8 in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #20 0x7f090c0ad1e2 in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #21 0x7f090c0b5724 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #22 0x55d91137f68c in main () [Inferior 1 (process 1784) detached] Possible duplicates by query: bug 425786, bug 424232, bug 415991, bug 410345, bug 383859. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 449619] Widgets not working properly on second activity
https://bugs.kde.org/show_bug.cgi?id=449619 --- Comment #2 from Nicholas --- Created attachment 146275 --> https://bugs.kde.org/attachment.cgi?id=146275=edit An image of the widgets working fine on original activity -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 449619] Widgets not working properly on second activity
https://bugs.kde.org/show_bug.cgi?id=449619 --- Comment #1 from Nicholas --- I do not know if this is an issue with the unstable branch specifically or also the stable version because I have not used activities before I switched to the unstable branch -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 449619] New: Widgets not working properly on second activity
https://bugs.kde.org/show_bug.cgi?id=449619 Bug ID: 449619 Summary: Widgets not working properly on second activity Product: kde Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: trovianflip...@gmail.com Target Milestone: --- Created attachment 146274 --> https://bugs.kde.org/attachment.cgi?id=146274=edit showing system information widgets not working and pager without icons SUMMARY STEPS TO REPRODUCE 1. Create any system monitor or pager widget on desktop on primary activity 2. Create second activity 3. Create another system monitor or pager widget on the new activity OBSERVED RESULT All of the system information widgets (total cpu usage, individual core usage, memory usage, network usage, etc. Anything that you can right click and see "Open System Monitor") are blank, and pager doesn't show program icon. EXPECTED RESULT That all widgets would work and appear the same on all activities. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.90 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.5-arch1-1 (64-bit) Graphics Platform: X11 Processors: 8 × AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx Memory: 14.6 GiB of RAM Graphics Processor: AMD Radeon Vega 8 Graphics ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449541] Quick tile action via shortcut de-maximizes the window without tiling as a first action
https://bugs.kde.org/show_bug.cgi?id=449541 --- Comment #2 from Nicholas Serrano <2019nicho...@gmail.com> --- Currently using Wayland, I can confirm that when I switch to X11 the bugged behavior goes away so this is Wayland specific -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 329136] Quick Tiling shortcuts always toggle tiling, regardless whether the current tiling state matches the shortcut
https://bugs.kde.org/show_bug.cgi?id=329136 Nicholas Serrano <2019nicho...@gmail.com> changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=449541 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449541] New: Quick tile action via shortcut de-maximizes the window without tiling as a first action
https://bugs.kde.org/show_bug.cgi?id=449541 Bug ID: 449541 Summary: Quick tile action via shortcut de-maximizes the window without tiling as a first action Product: kwin Version: 5.23.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: 2019nicho...@gmail.com Target Milestone: --- SUMMARY Using a quick tile action via shortcut on a window that is currently maximized causes it to de-maximize without tiling. A subsequent quick tile action tiles as expected. EXPECTED RESULT Using a quick tile action via shortcut on a window that is currently maximized will tile it immediately. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Linux 35 (available in About System) KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 376104] Quick tile window to any screen edge or corner de-maximizes the window without tiling as a first action since plasma 5.9.0
https://bugs.kde.org/show_bug.cgi?id=376104 Nicholas Serrano <2019nicho...@gmail.com> changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=449541 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 376104] Quick tile window to any screen edge or corner de-maximizes the window without tiling as a first action since plasma 5.9.0
https://bugs.kde.org/show_bug.cgi?id=376104 Nicholas Serrano <2019nicho...@gmail.com> changed: What|Removed |Added Status|RESOLVED|REOPENED CC||2019nicho...@gmail.com Resolution|FIXED |--- --- Comment #30 from Nicholas Serrano <2019nicho...@gmail.com> --- Currently using Fedora 35 and it seems this bugged behavior has returned at some point. Using a keybind to quick tile a currently maximized window causes the window to unmaximize but not tile as desired until a subsequent quick tile bind is pressed. Has anyone else run into this issue? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 437964] See crash report in attachment.
https://bugs.kde.org/show_bug.cgi?id=437964 --- Comment #1 from Nicholas E. Haniotis --- attached (correction because of bad 'c' key). -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 437964] New: See crash report in attachment.
https://bugs.kde.org/show_bug.cgi?id=437964 Bug ID: 437964 Summary: See crash report in attachment. Product: Akonadi Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: akonadiconsole Assignee: kdepim-b...@kde.org Reporter: elot...@yahoo.com Target Milestone: --- Created attachment 138928 --> https://bugs.kde.org/attachment.cgi?id=138928=edit Crash report. SUMMARY STEPS TO REPRODUCE 1. N/A. 2. N/A. 3. N/A. OBSERVED RESULT Crash Indicator during bootup of KDE. Plasma running in Linux Mint 20.1 EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I think the crash report attahed should have the rest of the information. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436156] No Emoji Support in Notifications and Panel Task Manager
https://bugs.kde.org/show_bug.cgi?id=436156 --- Comment #8 from Nicholas --- I'm on Fedora here - bug reported upstream at https://bugzilla.redhat.com/show_bug.cgi?id=1954359 Perhaps @Chromer can report it to Arch> -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436156] No Emoji Support in Notifications and Panel Task Manager
https://bugs.kde.org/show_bug.cgi?id=436156 --- Comment #6 from Nicholas --- (In reply to Antonio Rojas from comment #4) > Does it work in other Qt applications? Doesn't work in kwrite either. Adding the fontconfig settings from https://gist.github.com/charveey/091b11ea554436d15c7fffcf01129a8a *does* fix the issue, at least here on Fedora 34. Thanks for the pointer, Nate. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436156] No Emoji Support in Notifications and Panel Task Manager
https://bugs.kde.org/show_bug.cgi?id=436156 --- Comment #3 from Nicholas --- This is on: Fedora 34 KDE Frameworks 5.80.0 Qt 5.15.2 (built against 5.15.2) The wayland windowing system Plasma: 5.21.4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436156] No Emoji Support in Notifications and Panel Task Manager
https://bugs.kde.org/show_bug.cgi?id=436156 Nicholas changed: What|Removed |Added CC||vano...@gmail.com --- Comment #2 from Nicholas --- Here, some emoji's show as line art, others simply show the "blank rectangle(s)". For instance, notify-send "" doesn't work. Ideally, it'd also be great to have these show as full colour emojis - and not simply line-art. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 433503] Falkon hangs and takes stops the OS from working
https://bugs.kde.org/show_bug.cgi?id=433503 --- Comment #2 from Nicholas --- @Juraj thanks for your reply, I appreciate that you don't have my laptop, what logs would be most helpful? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 434088] Removing user with auto-login enabled causes failure to show SDDM on reboot
https://bugs.kde.org/show_bug.cgi?id=434088 --- Comment #5 from Nicholas Estrada --- (In reply to Nate Graham from comment #4) > SDDM could handle it better for sure, but also the users KCM could take the > initiative to reset this automatically when a user is deleted. No need for a > listener, I think. > > Nicholas, can you also file an SDDM bug report at > https://github.com/valve-project/tasks/issues/ to request better fallback > behavior? Thanks! Will do -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 434088] Removing user with auto-login enabled causes failure to show SDDM on reboot
https://bugs.kde.org/show_bug.cgi?id=434088 --- Comment #2 from Nicholas Estrada --- (In reply to David Redondo from comment #1) > Isn't that a sddm issue? I don't think so. System Settings should set auto-login to false when the account that it's set on is deleted. Its failure to do so led to the bug. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 433887] Dock offset changes when compositor is suspended
https://bugs.kde.org/show_bug.cgi?id=433887 --- Comment #8 from Nicholas Serrano <2019nicho...@gmail.com> --- Perfect, tried out the latest commits and can confirm this is resolved now. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 434088] New: Removing user with auto-login enabled causes failure to show SDDM on reboot
https://bugs.kde.org/show_bug.cgi?id=434088 Bug ID: 434088 Summary: Removing user with auto-login enabled causes failure to show SDDM on reboot Product: systemsettings Version: 5.18.5 Platform: Neon Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: 116ni...@gmail.com Target Milestone: --- SUMMARY Removing a secondary user that has auto-login enabled will make the admin user auto-login enabled. This causes a black screen with cursor and inability to do anything in that TTY on reboot. STEPS TO REPRODUCE 1. Add a new user with auto-login enabled 2. Reboot. This will log you in as that new user 3. Switch users to admin 4. Delete the new user. 5. Reboot. OBSERVED RESULT On reboot, a black screen shows up with a cursor and that's it. EXPECTED RESULT SDDM will show up like normal and nothing will auto-login. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.18.5 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.72.0 Qt Version: 5.14.2 Kernel Version: 5.3.0-28-generic OS Type: 64-bit ADDITIONAL INFORMATION To fix this issue: 1. Use Crl+Alt+F2 to open a new TTY 2. Log in and run `startx` 3. Go to the SDDM settings in System Settings and uncheck the auto-login option 4. Reboot -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 433887] Dock offset changes when compositor is suspended
https://bugs.kde.org/show_bug.cgi?id=433887 --- Comment #5 from Nicholas Serrano <2019nicho...@gmail.com> --- Just built Latte from git with the latest fix. It seems now when compositing is suspended the affected dock just disappears. The other docks without an offset stay visible however the offset one only shows up with compositing enabled. Thanks for looking into this! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 433887] Dock offset changes when compositor is suspended
https://bugs.kde.org/show_bug.cgi?id=433887 --- Comment #3 from Nicholas Serrano <2019nicho...@gmail.com> --- Created attachment 136439 --> https://bugs.kde.org/attachment.cgi?id=136439=edit Latte layout file -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 433887] Dock offset changes when compositor is suspended
https://bugs.kde.org/show_bug.cgi?id=433887 --- Comment #1 from Nicholas Serrano <2019nicho...@gmail.com> --- Seems there was an issue with the attached video so here is a link: https://streamable.com/c60ro2 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 433887] New: Dock offset changes when compositor is suspended
https://bugs.kde.org/show_bug.cgi?id=433887 Bug ID: 433887 Summary: Dock offset changes when compositor is suspended Product: lattedock Version: git (master) Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: 2019nicho...@gmail.com Target Milestone: --- Created attachment 136333 --> https://bugs.kde.org/attachment.cgi?id=136333=edit Dock offset changing when toggling compositing SUMMARY When the compositor is suspended, the offset distance of the dock changes. STEPS TO REPRODUCE 1. Change dock maximum length to 75% 2. Set Offset to 4% 3. Compare distance to edge of the screen before compositing is suspended and after OBSERVED RESULT Compositing effects are disabled and dock changes position. EXPECTED RESULT Compositing effects are disabled and dock stays in place. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Bedrock Linux 0.7.20beta2 Poki, Debian Testing stratum (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I've attached a video to help visualize what I'm talking about. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 433503] New: Falkon hangs and takes stops the OS from working
https://bugs.kde.org/show_bug.cgi?id=433503 Bug ID: 433503 Summary: Falkon hangs and takes stops the OS from working Product: Falkon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: nicho...@nshiell.com Target Milestone: --- SUMMARY Browser hangs,renders the whole system unresponsive STEPS TO REPRODUCE 1. Goto https://coronavirus.data.gov.uk/details/interactive-map 2. Goto https://coronavirus.data.gov.uk/details/interactive-map in a new tab 3. Goto https://coronavirus.data.gov.uk/details/interactive-map in a new tab 4. Drag the map around 5. Put the browser under more load OBSERVED RESULT The whole OS stops working, can't use Ctrl+Alt+F3 to get to a TTY EXPECTED RESULT Either work and not break or provide a message saying the page is unresponsive, don't crash the whole system SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.10 (available in About System) KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION This is on a new laptop Dell i7-1165G7 - This laptop model number is certified by Cannonical The laptop has around 16gb of memory It is running a resonably vanilla fresh install of Kubuntu If Falkon can't run, then it shouldn't take down my whole OS, so there may be 2 issues, one: Falkon has some issue with memory, second: nothing catches the situation -- You are receiving this mail because: You are watching all bug changes.
[kcachegrind] [Bug 424078] dprof2calltree cannot be distributed with a GPL-2 work
https://bugs.kde.org/show_bug.cgi?id=424078 --- Comment #1 from Nicholas D Steeves --- Also, the license of dprof2calltree is in violation of https://community.kde.org/Policies/Licensing_Policy Thanks to nicolas17 in irc://#debian-qt-...@oftc.net -- You are receiving this mail because: You are watching all bug changes.
[kcachegrind] [Bug 424078] New: dprof2calltree cannot be distributed with a GPL-2 work
https://bugs.kde.org/show_bug.cgi?id=424078 Bug ID: 424078 Summary: dprof2calltree cannot be distributed with a GPL-2 work Product: kcachegrind Version: unspecified Platform: unspecified OS: All Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: josef.weidendor...@gmx.de Reporter: nstee...@gmail.com Target Milestone: --- converters/dprof2calltree is © 2004 OmniTI Computer Consulting Unfortunately its BSD-4-like (with problematic advertising clause) has the following issue: * All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by OmniTI Computer Consulting. * Neither name of the company nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. I'm not 100% certain that bundling dprof2calltree with kcachegrind constitutes a "product[s] derived from this software", because I'm also of the opinion that bundling != derivation, but it seems like a lawyer might argue the it does. So kcachegrind and any distributions' package would also need written persmission from OmniTI Computer Consulting. Metadata, such as a package description (deb, rpm, etc.) or possibly even converters/README can be argued to be advertising materials. If the package description appears in an "App store" like Discover then I think it would be considered advertising. Thus, mentioning features provided by dprof2calltree in any user-facing way appears to require written permission from OmniTI Computer Consulting. Given how this requirements is more restrictive than the GPL-2, it looks like dprof2calltree cannot be distributed with a GPL-2 work. Disclaimer, this is not legal advice, but legal advice should be sought if kcachegrind is to continue to distribute dprof2calltree. Thanks, Nicholas -- You are receiving this mail because: You are watching all bug changes.
[kcachegrind] [Bug 424077] New: hotshot2calltree should be dropped (Python 2 EOL)
https://bugs.kde.org/show_bug.cgi?id=424077 Bug ID: 424077 Summary: hotshot2calltree should be dropped (Python 2 EOL) Product: kcachegrind Version: unspecified Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: josef.weidendor...@gmx.de Reporter: nstee...@gmail.com Target Milestone: --- Hotshot does not have a Python 3 equivalent, and Python 2 is EOL thus hotshot2calltree should be dropped. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936783 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 377131] Audio files with colon in name are silently ignored by rendering
https://bugs.kde.org/show_bug.cgi?id=377131 Samuel Nicholas changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #8 from Samuel Nicholas --- Apologies for delay, tested with Arch linux extra/kdenlive 20.04.2 Can confirm that the rendered output contained video from files with a colon in the filename. -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 422191] New: [ABI break] 20.04 and 20.04.1 have renamed symbols and needs and ABI bump
https://bugs.kde.org/show_bug.cgi?id=422191 Bug ID: 422191 Summary: [ABI break] 20.04 and 20.04.1 have renamed symbols and needs and ABI bump Product: KAccounts Version: 20.04 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kde-telepathy-b...@kde.org Reporter: nstee...@gmail.com Target Milestone: --- Hi! Thank you for maintaining KAccounts, and particularly for the recent fixes for Google's changes. When importing the latest version (20.04 at that time, later 20.04.1) I noticed that many symbols appeared to have been renamed, eg: - _ZN16KAccountsDPlugin11qt_metacallEN11QMetaObject4CallEiPPv@Base 0.0 + _ZN13AccountsModel11qt_metacallEN11QMetaObject4CallEiPPv@Base 4:20.04.0 P.S. The trailing version is a Debian (and derivatives)-specific version used for mappings between upstream symbols and Debian package versions. Please bump ABI for 20.04.2, and I'll package it as soon as it's ready. If you're interested in the Debian side of the discussion, it happened here: https://salsa.debian.org/qt-kde-team/kde/kaccounts-integration/-/merge_requests/3#note_168563 Thank you, Nicholas -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 422143] New: I wanted to burn an image and an error message popped up(F.Y.I. I'm not a software developer).
https://bugs.kde.org/show_bug.cgi?id=422143 Bug ID: 422143 Summary: I wanted to burn an image and an error message popped up(F.Y.I. I'm not a software developer). Product: k3b Version: 17.12.3 Platform: Mint (Debian based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Burning/Hardware Assignee: k...@kde.org Reporter: elot...@yahoo.com CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- Created attachment 128845 --> https://bugs.kde.org/attachment.cgi?id=128845=edit K3b bug report SUMMARY An error message pops up (see attachment). -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 306352] 100% cpu usage when waking up from suspend or switching between x servers, might be caused by kglobalaccel
https://bugs.kde.org/show_bug.cgi?id=306352 Nicholas changed: What|Removed |Added CC||nicho...@nshiell.com --- Comment #9 from Nicholas --- This bug may have not been fixed OR re-appeared As well as seeing this issue when plugging in a USB device I have 100% CPU usage when waking from suspend as the bug description says. Removing my ~/.Xmodmap prevented me from seeing this issue. Using up-to-date Plasma 5 on KDE NEON on 20.04 LTS base Please see here: https://forum.kde.org/viewtopic.php?f=309=165873=432142#p432142 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 419928] Kmail crashes and continues to immediately crash when reopened permanently when "Local Folders" is deleted from sidebar
https://bugs.kde.org/show_bug.cgi?id=419928 --- Comment #1 from Nicholas Estrada <116ni...@gmail.com> --- I was able to get kmail to open again by opening Akonadi Console and reconfiguring "Local Folders" from there. I still think this is a bug and THERE SHOULD BE A WAY TO NOT HAVE LOCAL FOLDERS CLUTTERING UP THE SIDEBAR without it killing the entire application. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 419928] New: Kmail crashes and continues to immediately crash when reopened permanently when "Local Folders" is deleted from sidebar
https://bugs.kde.org/show_bug.cgi?id=419928 Bug ID: 419928 Summary: Kmail crashes and continues to immediately crash when reopened permanently when "Local Folders" is deleted from sidebar Product: kmail2 Version: 5.13.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: folders Assignee: kdepim-b...@kde.org Reporter: 116ni...@gmail.com Target Milestone: --- Created attachment 127434 --> https://bugs.kde.org/attachment.cgi?id=127434=edit Screenshot of error dialog SUMMARY Title says it all. Kmail immediately crashed when I deleted "Local Folders" from the sidebar (because for me it's useless), and now every time I open it, it immediately crashes. STEPS TO REPRODUCE 1. Open Kmail. 2. Delete "Local Folders" by right-clicking and then selecting "Delete" (or "Remove" I can't remember which and I can't reopen kmail to check now) 3. Suffer forever. OBSERVED RESULT Kmail crashes and becomes unopenable. An error dialog appears instead of kmail. Error message: "The Email program encountered a fatal error and will terminate now. The error was: Failed to fetch the resource collection." EXPECTED RESULT Not that. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.18 User Edition KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.14.1 Kernel Version: 5.3.0-46-generic ADDITIONAL INFORMATION "The Email program encountered a fatal error and will terminate now. The error was: Failed to fetch the resource collection." -- You are receiving this mail because: You are watching all bug changes.
[parley] [Bug 418639] Compose key input not working
https://bugs.kde.org/show_bug.cgi?id=418639 --- Comment #1 from Nicholas --- Please note that I since realised I had both the snap parley app as well as the .deb from apt installed. The problem I reported is only happening in the snap version of the app. I removed the snap and am able to use compose key in the .deb package from the Ubuntu repository. -- You are receiving this mail because: You are watching all bug changes.
[parley] [Bug 418639] New: Compose key input not working
https://bugs.kde.org/show_bug.cgi?id=418639 Bug ID: 418639 Summary: Compose key input not working Product: parley Version: 19.12 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: parley-bugs-n...@kde.org Reporter: nicho...@nitric.co.za Target Milestone: --- I am unable to type Portuguese characters such as á or ç using compose key. Compose key works in other apps. I use Unity on Ubuntu but in effort to resolve this problem i installed Plasma via kubuntu-desktop package and went in to the KDE settings to set the compose key to caps lock, same as I have it set in Unity I noticed when I run the KDE settings from Unity the keyboard is not one of the input devices but it is there when doing from a Plasma session. Compose key does work in other KDE apps such as Konqueror, whether running in Unity or Plasma. Compose key does not work in Parley regardless of whether run in a Unity or Plasma session. STEPS TO REPRODUCE 1. in Parley lesson, try to answer question containing accented character, eg: "básico" OBSERVED RESULT the compose key has no effect: i try to type básico but i get b'asico EXPECTED RESULT básico! SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 19.10 Package: kubuntu-desktop, Version: 1.387 (available in About System) Package: kde-plasma-desktop, Version: 5:104ubuntu1 KDE Frameworks 5.67.0 Qt 5.14.1 (built against 5.13.2) ADDITIONAL INFORMATION I love Parley it's exactly what I've been looking for! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416202] Unable to load file by starting Krita while running an instance in single application mode
https://bugs.kde.org/show_bug.cgi?id=416202 --- Comment #3 from Nicholas LaPointe --- Ah, this is probably an important finding: If I let Krita fully load and then try to load a document by "krita ./document.kra", it won't load it. However, if I don't have any instance of Krita running, and then I run "krita ./document.kra & krita ./document.kra & krita ./document.kra & krita ./document.kra", an instance of Krita will open with four documents. I can load a document while the splash screen is up, but it seems like it stops working correctly once a main window exists. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416202] Unable to load file by starting Krita while running an instance in single application mode
https://bugs.kde.org/show_bug.cgi?id=416202 --- Comment #2 from Nicholas LaPointe --- I tested more carefully today, but still got the same result. This time, I made two builds -- one at 4c715c4c9470b9a454413cd9002ace514abc7ee1 (fix for bug #415794) and one at b4c44d395a7debd33c4bc1d9de52dcd556980a9a (its parent commit). Other than disabling PyQt by editing a CMakeLists.txt file (I don't have the right version installed), they were clean builds. I also cleared the config between tests. The second build (pre-fix) worked as expected, but the other one did not. The krita/4.2 branch also has this issue for me (it has the #415794 fix in commit 8db82515ce132c1190597aae1aa1f80f841dd5af). Version information in case it is relevant: Krita Version: 4.3.0-prealpha (git 4c715c4) Languages: en_US, en Hidpi: true Qt Version (compiled): 5.13.2 Version (loaded): 5.13.2 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 4.15.0-74-generic Pretty Productname: Ubuntu 18.04.3 LTS Product Type: ubuntu Product Version: 18.04 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416202] New: Unable to load file by starting Krita while running an instance in single application mode
https://bugs.kde.org/show_bug.cgi?id=416202
Bug ID: 416202
Summary: Unable to load file by starting Krita while running an
instance in single application mode
Product: krita
Version: git master
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: General
Assignee: krita-bugs-n...@kde.org
Reporter: nicholaslapoin...@gmail.com
Target Milestone: ---
When the "Allow only one instance of Krita" option is set and an instance of
Krita is already running, trying to load a document by the likes of "krita
./document.kra" will do nothing.
This seems to be a regression caused by the resolution of bug #415794.
The following patch fixes this by reintroducing a chunk that was removed in
4c715c4c9470b9a454413cd9002ace514abc7ee1.
I chose to submit this as bug rather than a patch because I have not properly
tested if it will make bug #415794 happen again and I don't have a clear
understanding of what this change does at the moment, but I can commit it if
desired.
diff --git a/libs/ui/KisApplication.cpp b/libs/ui/KisApplication.cpp
index 4d94ee428f..8b0bfc4676 100644
--- a/libs/ui/KisApplication.cpp
+++ b/libs/ui/KisApplication.cpp
@@ -696,6 +696,10 @@ void KisApplication::remoteArguments(QByteArray message,
QObject *socket)
// check if we have any mainwindow
KisMainWindow *mw = qobject_cast(qApp->activeWindow());
+if (!mw) {
+mw = KisPart::instance()->mainWindows().first();
+}
+
if (!mw) {
d->earlyRemoteArguments << message;
return;
--
You are receiving this mail because:
You are watching all bug changes.
[Akonadi] [Bug 416016] Akonadi can no longer start : /run/user/1000/akonadi problem
https://bugs.kde.org/show_bug.cgi?id=416016 Nicholas Istre changed: What|Removed |Added CC||nickis...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 --- Comment #95 from Nicholas Sushkin --- Google is disabling password access altogether I got the following email yesterday: From: The G Suite Team Beginning June 15, 2020, non-Google apps that use only a password to access Google accounts will no longer be supported. Starting February 15, 2021, G Suite accounts will only allow access to apps using OAuth. Password-based access will no longer be supported. Dear Administrator, We're constantly working to improve the security of your organization's Google accounts. As part of this effort, and in consideration of the current threat landscape, we'll be turning off access to less secure apps (LSA) — non-Google apps that can access your Google account with only a username and password, without requiring any additional verification steps. Access through only a username and password makes your account more vulnerable to hijacking attempts. Moving forward, only apps that support a more modern and secure access method called OAuth will be able to access your G Suite account. Access to LSAs will be turned off in two stages: June 15, 2020 - Users who try to connect to an LSA for the first time will no longer be able to do so. This includes third-party apps that allow password-only access to Google calendars, contacts, and email via protocols such as CalDAV, CardDAV and IMAP. Users who have connected to LSAs prior to this date will be able to continue using them until usage of all LSAs is turned off. February 15, 2021 - Access to LSAs will be turned off for all G Suite accounts. What do I need to do? To continue using a specific app with your G Suite accounts, users in your organization must switch to a more secure type of access called OAuth. This connection method allows apps to access accounts with a digital key instead of requiring a user to reveal their username and password. We recommend that you share the user instructions (included below) with individuals in your organization to help them make the necessary changes. Alternatively, if your organization is using custom tools, you can ask the developer of the tool to update it to use OAuth. Developer instructions are also included below. MDM configuration If your organization uses a mobile device management (MDM) provider to configure CalDAV, CardDAV, and Exchange ActiveSync (Google Sync) profiles, these services will be phased out according to the timeline below: June 15, 2020 - MDM push of IMAP, CalDAV, CardDAV, and Exchange ActiveSync (Google Sync) will no longer work for new users. February 15, 2021 - MDM push of IMAP, CalDAV, CardDAV, and Exchange ActiveSync (Google Sync) will no longer work for existing users. Admins will need to push a Google Account using their MDM provider, which will re-add their Google accounts to iOS devices using OAuth. Other less secure apps For any other LSA, ask the developer of the app you are using to start supporting OAuth. If you use other apps on iOS or MacOS that access your G Suite account information through only a password, most access issues can be resolved by removing then re-adding your account. When you add it back, make sure to select Google as the account type to automatically use OAuth. Scanners and other devices No change is required for scanners or other devices using simple mail transfer protocol (SMTP) or LSAs to send emails. If you replace your device, look for one that sends email using OAuth. User instructions If you are using an app that accesses your Google account with only a username and password, take one of the following actions to switch to a more secure method and continue to access your email, calendar, or contacts. If you do not take one of the following actions, when LSA access is discontinued after February 15, 2021, you will begin receiving an error message that your username-password combination is incorrect. Email If you are using stand-alone Outlook 2016 or earlier, move to Office 365 (a web-based version of Outlook) or Outlook 2019, both of which support OAuth access. Alternatively you can use G Suite Sync for Microsoft Outlook. If you are using Thunderbird or another email client, re-add your Google Account and configure it to use IMAP with OAuth. If you are using the mail app on iOS or MacOS, or Outlook for Mac, and use only a password to login, you'll need to remove and re-add your account. When you add it back, select “sign in with Google” to automatically use OAuth. Mac OS iOS mail app view Mac OS mail app view iOS Calendar If you use CalDAV to give an app or device access to your calendar, switch to a method that supports OAuth. We recommend the Google Calendar app [Web/iOS/Android] as the most secure app to use with your G Suite account. If your G Suite account is linked to the calendar app in iOS or MacOS and uses only a password
[kdevelop] [Bug 414551] New: Crahes thru ChromeOS
https://bugs.kde.org/show_bug.cgi?id=414551 Bug ID: 414551 Summary: Crahes thru ChromeOS Product: kdevelop Version: 5.3.1 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: a...@grokalex.com Target Milestone: --- Application: kdevelop (5.3.1) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 4.19.79-07511-ge32b3719f26b aarch64 Distribution: Debian GNU/Linux 10 (buster) -- Information about the crash: - Unusual behavior I noticed: Via term vs Via OS, thru Debian Buster - Custom settings of the application: https://GitLab.com/parcha/atlas The crash can be reproduced every time. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x710a0e9a10 (LWP 594))] Thread 22 (Thread 0x709effcfa0 (LWP 763)): #0 0x007111509800 in futex_wait_cancelable (private=0, expected=0, futex_word=0x62c5de9308) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x007111509800 in __pthread_cond_wait_common (abstime=0x0, mutex=0x62c5de92b0, cond=0x62c5de92e0) at pthread_cond_wait.c:502 #2 0x007111509800 in __pthread_cond_wait (cond=0x62c5de92e0, mutex=0x62c5de92b0) at pthread_cond_wait.c:655 #3 0x00711441bf04 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/aarch64-linux-gnu/libQt5Core.so.5 #4 0x007110b271b0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/aarch64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x007110b2bcc4 in () at /usr/lib/aarch64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x007110b260dc in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/aarch64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x007110b2bd28 in () at /usr/lib/aarch64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x007110b260dc in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/aarch64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x007110b2bd28 in () at /usr/lib/aarch64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x007110b260dc in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/aarch64-linux-gnu/libKF5ThreadWeaver.so.5 #11 0x007110b2bd28 in () at /usr/lib/aarch64-linux-gnu/libKF5ThreadWeaver.so.5 #12 0x007110b260dc in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/aarch64-linux-gnu/libKF5ThreadWeaver.so.5 #13 0x007110b2bd28 in () at /usr/lib/aarch64-linux-gnu/libKF5ThreadWeaver.so.5 #14 0x007110b260dc in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/aarch64-linux-gnu/libKF5ThreadWeaver.so.5 #15 0x007110b2bd28 in () at /usr/lib/aarch64-linux-gnu/libKF5ThreadWeaver.so.5 #16 0x007110b260dc in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/aarch64-linux-gnu/libKF5ThreadWeaver.so.5 #17 0x007110b2bd28 in () at /usr/lib/aarch64-linux-gnu/libKF5ThreadWeaver.so.5 #18 0x007110b260dc in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/aarch64-linux-gnu/libKF5ThreadWeaver.so.5 #19 0x007110b2bd28 in () at /usr/lib/aarch64-linux-gnu/libKF5ThreadWeaver.so.5 #20 0x007110b260dc in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/aarch64-linux-gnu/libKF5ThreadWeaver.so.5 #21 0x007110b2bd28 in () at /usr/lib/aarch64-linux-gnu/libKF5ThreadWeaver.so.5 #22 0x007110b260dc in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/aarch64-linux-gnu/libKF5ThreadWeaver.so.5 #23 0x007110b2bd28 in () at /usr/lib/aarch64-linux-gnu/libKF5ThreadWeaver.so.5 #24 0x007110b260dc in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/aarch64-linux-gnu/libKF5ThreadWeaver.so.5 #25 0x007110b2bd28 in () at /usr/lib/aarch64-linux-gnu/libKF5ThreadWeaver.so.5 #26 0x007110b260dc in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/aarch64-linux-gnu/libKF5ThreadWeaver.so.5 #27 0x007110b2bd28 in () at /usr/lib/aarch64-linux-gnu/libKF5ThreadWeaver.so.5 #28 0x007110b260dc in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/aarch64-linux-gnu/libKF5ThreadWeaver.so.5 #29 0x007110b2bd28 in () at /usr/lib/aarch64-linux-gnu/libKF5ThreadWeaver.so.5 #30 0x007110b260dc in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/aarch64-linux-gnu/libKF5ThreadWeaver.so.5 #31 0x007110b29500 in ThreadWeaver::Thread::run() () at /usr/lib/aarch64-linux-gnu/libKF5ThreadWeaver.so.5 #32 0x00711441b444 in () at
[kwin] [Bug 411906] Panel widgets and menus are too high when panel on auto-hide
https://bugs.kde.org/show_bug.cgi?id=411906 --- Comment #3 from Nicholas Estrada <116ni...@gmail.com> --- *normal menus -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411906] Panel widgets and menus are too high when panel on auto-hide
https://bugs.kde.org/show_bug.cgi?id=411906 --- Comment #2 from Nicholas Estrada <116ni...@gmail.com> --- Created attachment 122648 --> https://bugs.kde.org/attachment.cgi?id=122648=edit See the problem 2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411906] Panel widgets and menus are too high when panel on auto-hide
https://bugs.kde.org/show_bug.cgi?id=411906 --- Comment #1 from Nicholas Estrada <116ni...@gmail.com> --- Created attachment 122647 --> https://bugs.kde.org/attachment.cgi?id=122647=edit See the problem -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411906] New: Panel widgets and menus are too high when panel on auto-hide
https://bugs.kde.org/show_bug.cgi?id=411906 Bug ID: 411906 Summary: Panel widgets and menus are too high when panel on auto-hide Product: kwin Version: 5.16.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: 116ni...@gmail.com Target Milestone: --- SUMMARY Panel widgets and menus like the system tray popups and application menu draw too high on the screen when the panel is on auto-hide. STEPS TO REPRODUCE 1. put panel on autohide 2. reboot computer 3. OBSERVED RESULT see screenshots EXPECTED RESULT normal men ADDITIONAL INFORMATION The problem seems to go away after setting the panel to Always Visible and then back again to Auto Hide. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 411576] New: Kmail crashes on logout using
https://bugs.kde.org/show_bug.cgi?id=411576 Bug ID: 411576 Summary: Kmail crashes on logout using Product: kmail2 Version: 5.12.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: 116ni...@gmail.com Target Milestone: --- Kmail crashes and shows a bug report window when logging out. I've tried getting the info from the window, but it finishes logging out in about 10 - 20 seconds before I can finish the report. Reproducible: Every single time I log out, shut down, or restart using the applet in the Application Menu. -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 411392] New: In Kopete 1.13 "View History" action is gone from menu and toolbars
https://bugs.kde.org/show_bug.cgi?id=411392 Bug ID: 411392 Summary: In Kopete 1.13 "View History" action is gone from menu and toolbars Product: kopete Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: History Plugin Assignee: kopete-bugs-n...@kde.org Reporter: nsush...@sushkins.net Target Milestone: --- SUMMARY After upgrading to Kopete 1.13, "View History" menu has disappeared. I can still view history via keyboard shortcut Ctrl-H, but the action is not available in any toolbar or menu and does not appear in "Available actions" in Configure Toolbars. Kopete Handbook specifies that View History should be in the Edit menu STEPS TO REPRODUCE 1. In Settings/Configure, Plugins, enable History plugin 2. Click Edit menu, list menu items 3. Click Settings/Configure Toolbars 4. Browser "Available actions:" list, there is no "View History" action OBSERVED RESULT In Edit menu there is no "View History" menu item In "Available actions", there is no "View History" action EXPECTED RESULT In Edit menu there should be "View History" menu item In "Available actions", there should be "View History" action SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 19.04 (available in About System) KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION Operating System: Kubuntu 19.04 KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 Kernel Version: 5.0.0-25-generic OS Type: 64-bit Processors: 2 × Intel® Core™ i7-3520M CPU @ 2.90GHz Memory: 9.8 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411124] New: Merge Group on invisible group layer crashes krita
https://bugs.kde.org/show_bug.cgi?id=411124 Bug ID: 411124 Summary: Merge Group on invisible group layer crashes krita Product: krita Version: 4.2.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: captains...@gmail.com Target Milestone: --- If a group layer with any sublayers is set to invisible and "Merge Group" is selected from the right-click menu on that group in the layers docker, Krita crashes. STEPS TO REPRODUCE 1. Create a new image 2. Create a group layer and add at least one layer to it (or right-click an existing layer -> Group -> Quick Group) 3. Make that group layer invisible by clicking its eye icon in the layers docker 4. Right-click that group layer and click "Merge Group" OBSERVED RESULT Krita crashes immediately. EXPECTED RESULT Either the group should be merged and remain invisible, a message should appear saying this action makes little sense, or "Merge Group" should be greyed out if the user shouldn't be doing that in that situation in the first place. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kernel 4.15.0-58-generic (via Ubuntu) (available in About System) KDE Plasma Version: 5.12.8 KDE Frameworks Version: 5.47.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION With some additional testing, I've seen this NOT crash a few times with the exact same inputs. I'd put it at around a 95% crash rate, though. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 Nicholas Sushkin changed: What|Removed |Added CC||nsush...@sushkins.net --- Comment #53 from Nicholas Sushkin --- (In reply to Daniel Vrátil from comment #50) > I've now did the necessary changes and filed a request to have the login > enabled again. Hi, Daniel, Are you expecting that Google will notify when your request has been processed? I am still seeing "Sign in with Google temporarily disabled for this app" when Akonadi is trying to log into my MFA enabled GMail account. Thanks -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 410396] New: "Date"s given as 07/02/2106 06:28 - way in the future.
https://bugs.kde.org/show_bug.cgi?id=410396 Bug ID: 410396 Summary: "Date"s given as 07/02/2106 06:28 - way in the future. Product: akregator Version: 5.10.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: throw-kdeb...@mgn.org.uk Target Milestone: --- SUMMARY "Date"s given as 07/02/2106 06:28 - way in the future. STEPS TO REPRODUCE 1. Subscribe to http://rss.acast.com/rhlstp or https://rss.acast.com/insidethecomedian OBSERVED RESULT For certain articles "Date"s are given as "07/02/2106 06:28". These seem to actually be sometime in the past, some are from 2015. EXPECTED RESULT "Date" to be sometime in the past. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION Acast is the common element. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 410394] New: Unread shown as -1 articles.
https://bugs.kde.org/show_bug.cgi?id=410394 Bug ID: 410394 Summary: Unread shown as -1 articles. Product: akregator Version: 5.10.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: throw-kdeb...@mgn.org.uk Target Milestone: --- SUMMARY Unread Feeds given as -1 STEPS TO REPRODUCE 1. Subscribe to http://www.radiolab.org/feeds/podcast/ 2. Wait OBSERVED RESULT "Unread" given as -1. "Total" given as 35. EXPECTED RESULT "Unread" given as 0. "Total" given as 35. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION This is the only feed I have that does this. The "Unread" of -1 propagates upwards to "All Feeds". -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408225] Canvas itself becomes transparent with transparent pixels, showing what is behind the Krita window
https://bugs.kde.org/show_bug.cgi?id=408225 --- Comment #7 from Nicholas Killewald --- Looks like it's fixed in 4.2.1. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408225] Canvas itself becomes transparent with transparent pixels, showing what is behind the Krita window
https://bugs.kde.org/show_bug.cgi?id=408225 --- Comment #3 from Nicholas Killewald --- Sure, here's the output: OpenGL Info Vendor: "NVIDIA Corporation" Renderer: "GeForce GTX 970/PCIe/SSE2" Version: "4.6.0 NVIDIA 390.116" 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::SwapBehavior(DoubleBuffer), swapInterval 0, profile QSurfaceFormat::OpenGLContextProfile(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::SwapBehavior(DoubleBuffer), swapInterval 0, profile QSurfaceFormat::OpenGLContextProfile(CompatibilityProfile)) Version: 4.6 Supports deprecated functions true is OpenGL ES: false QPA OpenGL Detection Info supportsDesktopGL: true supportsOpenGLES: true isQtPreferOpenGLES: false == log == Supported renderers: QFlags(0x2|0x4) Surface format preference list: * QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 0, profile QSurfaceFormat::OpenGLContextProfile(CompatibilityProfile)) QSurfaceFormat::RenderableType(OpenGL) * QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 0, profile QSurfaceFormat::OpenGLContextProfile(CompatibilityProfile)) QSurfaceFormat::RenderableType(OpenGLES) Probing format... QSurfaceFormat::RenderableType(OpenGL) Found format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 0, profile QSurfaceFormat::OpenGLContextProfile(CompatibilityProfile)) QSurfaceFormat::RenderableType(OpenGL) == end log == SESSION: 31 May 2019 20:35:49 -0700. Executing /usr/bin/krita WARNING: This file contains information about your system and the images you have been working with. If you have problems with Krita, the Krita developers might ask you to share this file with them. The information in this file is not shared automatically with the Krita developers in any way. You can disable logging to this file in Krita's Configure Krita Dialog. Please review the contents of this file before sharing this file with anyone. Krita Version: 4.2.0 Languages: en_US Hidpi: false Qt Version (compiled): 5.9.5 Version (loaded): 5.9.5 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 4.15.0-50-generic Pretty Productname: Ubuntu 18.04.2 LTS Product Type: ubuntu Product Version: 18.04 Hardware Information GPU Acceleration: auto Memory: 32131 Mb Number of Cores: 8 Swap Location: /tmp 31 May 2019 20:35:57 -0700: Closing. OpenGL Info Vendor: "NVIDIA Corporation" Renderer: "GeForce GTX 970/PCIe/SSE2" Version: "4.6.0 NVIDIA 390.116" 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::SwapBehavior(DoubleBuffer), swapInterval 0, profile QSurfaceFormat::OpenGLContextProfile(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::SwapBehavior(DoubleBuffer), swapInterval 0, profile QSurfaceFormat::OpenGLContextProfile(CompatibilityProfile)) Version: 4.6 Supports deprecated functions true is OpenGL ES: false QPA OpenGL Detection Info supportsDesktopGL: true supportsOpenGLES: true isQtPreferOpenGLES: false == log == Supported renderers: QFlags(0x2|0x4) Surface format preference list: * QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, sam
[krita] [Bug 408225] New: Canvas itself becomes transparent with transparent pixels, showing what is behind the Krita window
https://bugs.kde.org/show_bug.cgi?id=408225
Bug ID: 408225
Summary: Canvas itself becomes transparent with transparent
pixels, showing what is behind the Krita window
Product: krita
Version: 4.2.0
Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: OpenGL Canvas
Assignee: krita-bugs-n...@kde.org
Reporter: captains...@gmail.com
Target Milestone: ---
Created attachment 120509
--> https://bugs.kde.org/attachment.cgi?id=120509=edit
Screenshot showing issue; note the desktop visible through the transparent
orange areas
Any pixels that are transparent and show the canvas (that is, show the
checkerboard "transparent" pattern and would have an alpha of less than 1.0 if
ultimately exported) seem to be showing what's behind the Krita window itself.
That is, the desktop (or whatever else is there) becomes visible through the
transparent areas.
I stumbled across this when I noticed the antialiased edges of black Bezier
curve vectors didn't look black on-screen. When I zoomed in, I saw the default
Kubuntu wallpaper peeking out through the enlarged, transparent pixels. I
tried it with other transparencies, and sure enough, they all showed my desktop
behind the transparent areas.
Curiously, if there's no pixel data at all in a given region (or the pixels are
completely transparent), that area is NOT transparent to the desktop, and just
the plain checkerboard is visible.
If I turn off Canvas Graphics Acceleration in the settings, the problem goes
away, leading me to believe this is something to do with OpenGL.
STEPS TO REPRODUCE
1. Create a new image.
2. Draw a filled, opaque square by whatever means you wish.
3. Set the layer on which the square is to anything less than 100% Opacity.
OBSERVED RESULT
The desktop is visible through the transparent square and the transparency
checkerboard.
EXPECTED RESULT
Only the checkerboard should be visible through the transparent square; the
Krita canvas itself should not be transparent.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 18.04, running Linux 4.15.0-50-generic from Ubuntu
packages
(available in About System)
KDE Plasma Version: 5.12.7
KDE Frameworks Version: 5.47.0
Qt Version: 5.9.5
ADDITIONAL INFORMATION
This problem shows up on both my desktop and my laptop. The desktop has a
GeForce GTX 970, and the laptop has the mobile version of same. Both are
running the same version of Kubuntu with the same KDE Plasma, Frameworks,
Krita, and Qt versions.
In the attached screenshot, you can see a diagonal yellow line from the default
Kubuntu 18.04 wallpaper behind the transparent orange area ("Curtains Fore" in
the layer list, currently set to 34% opacity for demonstration), as well as the
icons for Inkscape and GKrellM in a folder widget on the desktop. Areas with
no pixel data just show the checkerboard.
--
You are receiving this mail because:
You are watching all bug changes.
[kdenlive] [Bug 406792] Kdenlive crashes when trying to load pre-last-update project
https://bugs.kde.org/show_bug.cgi?id=406792 --- Comment #4 from Nicholas Estrada <116ni...@gmail.com> --- Created attachment 119758 --> https://bugs.kde.org/attachment.cgi?id=119758=edit Kdenlive project causing crash Kdenlive project causing crash -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 406792] New: Kdenlive crashes when trying to load pre-last-update project
https://bugs.kde.org/show_bug.cgi?id=406792 Bug ID: 406792 Summary: Kdenlive crashes when trying to load pre-last-update project Product: kdenlive Version: 19.04.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: 116ni...@gmail.com Target Milestone: --- Kdenlive crashes immediately when I try to open a project that I was working on a week ago before the 19.04 update. I was leery of updating because I thought this might happen, but I decided to do it anyway and revert if needed. However, the worst is what happened. As soon as I try to open this project, it dies completely and I get the "Program Crashed" dialog. Everything else seems to work just fine. New projects seem to save just fine. Opening these new projects also seems to work just fine. The new update just broke compatibility with old projects. Bug report output below: -- Application: Kdenlive (kdenlive), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb0a3426980 (LWP 8354))] Thread 68 (Thread 0x7fafb0ff9700 (LWP 8435)): #0 0x7fb09a4bdbf9 in __GI___poll (fds=0x7faf580062e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fb092045539 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb09204564c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb09b3b615b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fb09b35764a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fb09b17f41a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fb09cb721c6 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fb09b180bc2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fb096df56db in start_thread (arg=0x7fafb0ff9700) at pthread_create.c:463 #9 0x7fb09a4ca88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 67 (Thread 0x7fafb3fff700 (LWP 8434)): #0 0x7fb096dfb9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7fb048092044) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fb096dfb9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7fb0480920a8, cond=0x7fb048092018) at pthread_cond_wait.c:502 #2 0x7fb096dfb9f3 in __pthread_cond_wait (cond=0x7fb048092018, mutex=0x7fb0480920a8) at pthread_cond_wait.c:655 #3 0x7fb067bb0ede in () at /usr/lib/x86_64-linux-gnu/libavcodec.so.57 #4 0x7fb096df56db in start_thread (arg=0x7fafb3fff700) at pthread_create.c:463 #5 0x7fb09a4ca88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 66 (Thread 0x7fafb8ff9700 (LWP 8433)): #0 0x7fb096dfb9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7fb048091e94) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fb096dfb9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7fb048091ef8, cond=0x7fb048091e68) at pthread_cond_wait.c:502 #2 0x7fb096dfb9f3 in __pthread_cond_wait (cond=0x7fb048091e68, mutex=0x7fb048091ef8) at pthread_cond_wait.c:655 #3 0x7fb067bb0ede in () at /usr/lib/x86_64-linux-gnu/libavcodec.so.57 #4 0x7fb096df56db in start_thread (arg=0x7fafb8ff9700) at pthread_create.c:463 #5 0x7fb09a4ca88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 65 (Thread 0x7fafb97fa700 (LWP 8432)): #0 0x7fb096dfb9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7fb048091ce4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fb096dfb9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7fb048091d48, cond=0x7fb048091cb8) at pthread_cond_wait.c:502 #2 0x7fb096dfb9f3 in __pthread_cond_wait (cond=0x7fb048091cb8, mutex=0x7fb048091d48) at pthread_cond_wait.c:655 #3 0x7fb067bb0ede in () at /usr/lib/x86_64-linux-gnu/libavcodec.so.57 #4 0x7fb096df56db in start_thread (arg=0x7fafb97fa700) at pthread_create.c:463 #5 0x7fb09a4ca88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 64 (Thread 0x7fafb9ffb700 (LWP 8431)): #0 0x7fb096dfb9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7fb048091b34) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fb096dfb9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7fb048091b98, cond=0x7fb048091b08) at pthread_cond_wait.c:502 #2 0x7fb096dfb9f3 in __pthread_cond_wait (cond=0x7fb048091b08, mutex=0x7fb048091b98) at pthread_cond_wait.c:655 #3 0x7fb067bb0ede in () at /usr/lib/x86_64-linux-gnu/libavcodec.so.57 #4 0x7fb096df56db in start_thread (arg=0x7fafb9ffb700)
[kdevelop] [Bug 387347] kdev-xdebug missing current-step row indicator [remote debugging]
https://bugs.kde.org/show_bug.cgi?id=387347 Nicholas changed: What|Removed |Added CC||nicho...@nshiell.com --- Comment #9 from Nicholas --- I may have the same issue, where the debugging works - but the GUI doesn't show the line with remote debugging. I worked around my issue by adding trailing slashes to the paths in the directory map i.e. /var/www/html => /home/nicholas/someProject to /var/www/html/ => /home/nicholas/someProject/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 267277] configurable delay for autohide/show of panels
https://bugs.kde.org/show_bug.cgi?id=267277 Nicholas Istre changed: What|Removed |Added CC||nickis...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400174] New: let's generate a manpage for kdeconnect-cli!
https://bugs.kde.org/show_bug.cgi?id=400174 Bug ID: 400174 Summary: let's generate a manpage for kdeconnect-cli! Product: kdeconnect Version: 1.3.1 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: nstee...@gmail.com Target Milestone: --- Hi Albert, Nico, and possibly other maintainers, Debian has an English language manpage for kdeconnect-cli in troff format: https://salsa.debian.org/qt-kde-team/extras/kdeconnect/blob/master/debian/kdeconnect-cli.1 This last summer I noticed that it was four years out of date https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900710 I really don't like working with troff, internationalisation is obviously non-existent, and updates are currently a manual affair. It would also be really nice if they could be generated from existing strings and PO files as part of the release process! Would you please point me documentation or put me in touch with someone who would know how KDE/Plasma Desktop applications conventionally handle internationalised manpages? Warm regards, Nicholas -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 377131] Audio files with colon in name are silently ignored by rendering
https://bugs.kde.org/show_bug.cgi?id=377131 --- Comment #5 from Samuel Nicholas --- I'll test as soon as I can, which may be a few weeks, sorry. If someone else beats me to it OK. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 359517] Can't extend onto second screen in VMWare
https://bugs.kde.org/show_bug.cgi?id=359517 --- Comment #1 from Nicholas --- I'm sorry but I no longer have access to the VMWare installation to advise on this bug anymore -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 396850] Incorrect RFC822 timezone parsing in mail Date field
https://bugs.kde.org/show_bug.cgi?id=396850 --- Comment #1 from Nicholas Sushkin --- Created attachment 114119 --> https://bugs.kde.org/attachment.cgi?id=114119=edit email message whose date is displaying incorrectly -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 396850] New: Incorrect RFC822 timezone parsing in mail Date field
https://bugs.kde.org/show_bug.cgi?id=396850
Bug ID: 396850
Summary: Incorrect RFC822 timezone parsing in mail Date field
Product: kmail2
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: message list
Assignee: kdepim-b...@kde.org
Reporter: nsush...@sushkins.net
Target Milestone: ---
I received an email with Date header in the following format:
Date: Wed, 25 Jul 2018 10:55:49 CDT
In message list and message view, the email date is displayed as 6:55 AM. I am
in in US Eastern time zone. The proper date in EDT is 11:55 AM.
I looked at all other messages whose date is displayed correctly and their date
header has timezone in ("+" / "-") 4DIGIT format. Is it possible kmail2 has
parsing issues with timezone specified as CDT? After all, "Wed, 25 Jul 2018
10:55:49 +" is 6:55AM EDT.
RFC 822 allows CDT as a time zone, see
https://tools.ietf.org/html/rfc822#section-5.1
This is Ubuntu 16.04.5 LTS, KMail 5.1.3
--
You are receiving this mail because:
You are watching all bug changes.
[kio-gdrive] [Bug 396262] [PATCH] Provide screenshot in Appstream metadata
https://bugs.kde.org/show_bug.cgi?id=396262 --- Comment #4 from Nicholas D Steeves --- Hi Elvis and Nate, Ben, the/a KDE sysadmin replied to my inquiry and we sorted things out. Patch submitted for review on Phabricator. Nate, I would have also added you for review of the patch, but it seems you were not available in the query reviewers box. Cheers, Nicholas -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 396262] [PATCH] Provide screenshot in Appstream metadata
https://bugs.kde.org/show_bug.cgi?id=396262 --- Comment #3 from Nicholas D Steeves --- Hi Elvis and Nate, Well, it seems my email address was already registered with KDE Identity (strange), so I'm unable to use it to apply for an account with Phabricator. I send an email to sysad...@kde.org because I don't have a record (nor memory) of ever signing up for this account. While waiting to hear back from sysadmin, would providing a git remote be sufficiently convenient to merge this trivial patch? I prefer to avoid web things when possible. Cheers, Nicholas -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 396263] New: Please add translation tag to appdata.xml
https://bugs.kde.org/show_bug.cgi?id=396263 Bug ID: 396263 Summary: Please add translation tag to appdata.xml Product: kio-gdrive Version: unspecified Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: nstee...@gmail.com Target Milestone: --- This one is optional, and very much wishlist. https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-translation I'm guessing this should probably be KIO GDrive because this package seems to use gettext ( `Messages.sh:$XGETTEXT $(find . -name "*.cpp") -o $podir/kio5_gdrive.pot` ). but maybe it's org.kde.kio_gdrive ? Sorry I can't yet be of more help on this one, Nicholas -- You are receiving this mail because: You are watching all bug changes.
