[NeoChat] [Bug 467512] New: Room information sidebar isn't scrollable
https://bugs.kde.org/show_bug.cgi?id=467512 Bug ID: 467512 Summary: Room information sidebar isn't scrollable Classification: Applications Product: NeoChat Version: 23.01.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: saganomi...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Created attachment 157382 --> https://bugs.kde.org/attachment.cgi?id=157382&action=edit screenshot of ipsum text overflowing sidebar SUMMARY Room topic in Room information sidebar can go off-screen if too long and the element is not scrollable. STEPS TO REPRODUCE 1. Make a room 2. Set the room topic to something long OBSERVED RESULT Room topic text overflows out of view EXPECTED RESULT There should be a scroll-bar to view the rest of the text SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro (available in About System) KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 485989] New: Rescaled video exports in slightly wrong resolution
https://bugs.kde.org/show_bug.cgi?id=485989 Bug ID: 485989 Summary: Rescaled video exports in slightly wrong resolution Classification: Applications Product: kdenlive Version: 23.08.2 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: notnullnotv...@gmail.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. Open a project with a timeline resolution of 3840x2160 2. Go to Project->Render 3. Check "Rescale: Enabled" checkbox and set rescaled resolution to 1280x720 4. Render to file OBSERVED RESULT The rendered video is 1278x718 pixels instead of 1280x720 pixels. SOFTWARE/OS VERSIONS Windows 10 ADDITIONAL INFORMATION A video rendered from a project with a timeline resolution of 1280x720 has the correct resolution. It's seems to only be scaling the output that causes the issue. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 458488] New: View > Show Canvas Only exits fullscreen on Mac when green button used
ion (config option): false Hardware Information GPU Acceleration: auto Memory: 16384 Mb Number of Cores: 8 Swap Location: /private/var/folders/fn/68vtz98s1jzglybrpt5c2pscgn/T Built for: sse4.1 Base instruction set: sse4.1 Supported instruction sets: sse4.2 sse4.1 ssse3 sse3 sse2 Current Settings Current Swap Location: /private/var/folders/fn/68vtz98s1jzglybrpt5c2pscgn/T Current Swap Location writable: true Undo Enabled: true Undo Stack Limit: 200 Use OpenGL: true Use OpenGL Texture Buffer: true Disable Vector Optimizations: false Disable AVX Optimizations: false Canvas State: OPENGL_SUCCESS Autosave Interval: 420 Use Backup Files: true Number of Backups Kept: 1 Backup File Suffix: ~ Backup Location: Same Folder as the File Backup Location writable: false Use Win8 Pointer Input: false Use RightMiddleTabletButton Workaround: false Levels of Detail Enabled: false Use Zip64: false Display Information Number of screens: 1 Screen: 0 Name: Color LCD Depth: 24 Scale: 2 Physical DPI110.5 Logical DPI72 Physical Size: 331.005, 206.878 Position: 0, 0 Resolution in pixels: 1440x900 Manufacturer: Model: Refresh Rate: 60 - ==== SESSION: 29 Aug 2022 13:27:14 -0700. Executing /Applications/krita.app/Contents/MacOS/krita Krita Version: 5.1.0, Qt version compiled: 5.12.12, loaded: 5.12.12. Process ID: 29706 -- -- -- -- -- -- -- -- 29 Aug 2022 13:27:14 -0700: Style: macintosh. Available styles: macintosh, Windows, Fusion 29 Aug 2022 13:27:19 -0700: Creating database from scratch (database didn't exist, new schema version: 0.0.17). 29 Aug 2022 13:28:56 -0700: Importing image/png to application/x-krita. Location: /Users/miles/Downloads/unstable/unknown.png. Real location: /Users/miles/Downloads/unstable/unknown.png. Batchmode: 0 29 Aug 2022 13:28:56 -0700: Loaded image from image/png. Size: 640 * 880 pixels, 1 dpi. Color model: 8-bit integer/channel RGB/Alpha (sRGB-elle-V2-srgbtrc.icc). Layers: 2 29 Aug 2022 13:37:08 -0700: CLOSING SESSION SESSION: 29 Aug 2022 13:38:05 -0700. Executing /Applications/krita.app/Contents/MacOS/krita Krita Version: 5.1.0, Qt version compiled: 5.12.12, loaded: 5.12.12. Process ID: 29791 -- -- -- -- -- -- -- -- 29 Aug 2022 13:38:05 -0700: Style: macintosh. Available styles: macintosh, Windows, Fusion 29 Aug 2022 13:38:07 -0700: Database is up to date. Version: 0.0.17, created by Krita 5.1.0, at Mon Aug 29 13:27:19 2022 29 Aug 2022 13:38:34 -0700: Importing application/x-krita to application/x-krita. Location: /Applications/krita.app/Contents/share/krita/templates/comics/.source/BD-EuroTemplate.kra. Real location: /Applications/krita.app/Contents/share/krita/templates/comics/.source/BD-EuroTemplate.kra. Batchmode: 0 29 Aug 2022 13:38:34 -0700: Loaded image from application/x-krita. Size: 2480 * 3508 pixels, 4.16667 dpi. Color model: 8-bit integer/channel RGB/Alpha (sRGB built-in). Layers: 8 29 Aug 2022 13:38:58 -0700: Importing application/x-krita to application/x-krita. Location: /Applications/krita.app/Contents/share/krita/templates/animation/.source/Anim-Jp-EN.kra. Real location: /Applications/krita.app/Contents/share/krita/templates/animation/.source/Anim-Jp-EN.kra. Batchmode: 0 29 Aug 2022 13:38:58 -0700: Loaded image from application/x-krita. Size: 1756 * 1240 pixels, 4.16667 dpi. Color model: 8-bit integer/channel RGB/Alpha (sRGB-elle-V2-srgbtrc.icc). Layers: 39 29 Aug 2022 13:39:44 -0700: Importing application/x-krita to application/x-krita. Location: /Applications/krita.app/Contents/share/krita/templates/texture/.source/Texture1024x10248bitsrgb.kra. Real location: /Applications/krita.app/Contents/share/krita/templates/texture/.source/Texture1024x10248bitsrgb.kra. Batchmode: 0 29 Aug 2022 13:39:44 -0700: Loaded image from application/x-krita. Size: 1024 * 1024 pixels, 1.38889 dpi. Color model: 8-bit integer/channel RGB/Alpha (sRGB built-in). Layers: 3 - -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 458489] New: View > Show Canvas Only automatically enters fullscreen, causing lag on Mac
https://bugs.kde.org/show_bug.cgi?id=458489 Bug ID: 458489 Summary: View > Show Canvas Only automatically enters fullscreen, causing lag on Mac Product: krita Version: 5.1.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: treefrog...@gmail.com Target Milestone: --- SUMMARY Entering and exiting fullscreen on Mac systems is a heavy, laggy operation. My previous bug report addressed a flaw in the implementation of the current design, but I believe the design itself is flawed. Toggling fullscreen mode and toggling the palettes are separate concerns, and I believe they should be treated as such in this case. The use case of hiding all palettes while keeping the window as a window is a real thing. Currently the only way to arrive at such a combination of modes (fullscreen off, canvas-only on) is to enter canvas-only, and then exit fullscreen, which is just exploiting a glitch in the implementation. I propose totally decoupling the two modes. Simple, independent toggles for each. No automatic magic. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420927] quick tile is very hard to trigger on multi monitor middle edge
https://bugs.kde.org/show_bug.cgi?id=420927 Miles Roberts changed: What|Removed |Added CC||d...@milesroberts.net --- Comment #1 from Miles Roberts --- I have this issue too. There is no option to set the distance at which the window tiles and the default distance is too small to reliable do half and quarter-tiling when using multiple monitors. Other Windows managers, such as XFWM4 let the user set the distance from the edge of the screen where the tiling can occur and KWIN should introduce the same functionality. -- You are receiving this mail because: You are watching all bug changes.
[plasma-mobile] [Bug 459116] New: Bemenu does not work with onscreen keyboard
https://bugs.kde.org/show_bug.cgi?id=459116 Bug ID: 459116 Summary: Bemenu does not work with onscreen keyboard Product: plasma-mobile Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Shell Assignee: plasma-mobile-bugs-n...@kde.org Reporter: m...@milesalan.com Target Milestone: --- SUMMARY On plasma-mobile, after launching bemenu, the onscreen keyboard does not appear, and if manually launched via button or via dbus it's impossible to type into the bemenu prompt. STEPS TO REPRODUCE 1. Open Terminal on plasma mobile 2. Launch bemenu by typing: `seq 1 10 | bemenu -l 10` OBSERVED RESULT Onscreen keyboard does not launch, and if manually launched through button or qdbus (`qdbus org.kde.KWin /VirtualKeyboard org.kde.kwin.VirtualKeyboard.active true`), the keyboard does not focus bemenu and it's impossible to type into the bemenu prompt. EXPECTED RESULT The onscreen keyboard should focus bemenu and be able to type into bemenu's prompt. This is the behavior on other mobile environments such as Phosh. SOFTWARE/OS VERSIONS Linux/KDE Plasma: PmOS edge / Alpine Linux KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION Is there someway via dbus or otherwise to make the OSK focus to the bemenu overlay? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420889] Shift+scroll wheel behavior broke
https://bugs.kde.org/show_bug.cgi?id=420889 Miles Krell changed: What|Removed |Added CC||k...@mileskrell.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421989] New: Do not disturb end dates use unusual capitalization and some read awkwardly
https://bugs.kde.org/show_bug.cgi?id=421989
Bug ID: 421989
Summary: Do not disturb end dates use unusual capitalization
and some read awkwardly
Product: plasmashell
Version: 5.18.5
Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Notifications
Assignee: k...@privat.broulik.de
Reporter: k...@mileskrell.com
CC: plasma-b...@kde.org
Target Milestone: 1.0
SUMMARY
When do not disturb is turned on, the text displayed for the end date uses
unusual capitalization and sometimes reads awkwardly.
STEPS TO REPRODUCE
1. Turn on do not disturb for any length of time (other than "until turned
off").
2. Observe the label stating the do not disturb end date.
OBSERVED RESULT
The labels that each option ("for 1 hour", "for 4 hours", etc.) produces are as
follows at the time of writing:
- Until Today, 11:54 AM
- Until Today, 2:54 PM
- Until Today, 8:00 PM
- Until Tomorrow, 6:00 AM
- Until In two days, 6:00 AM
EXPECTED RESULT
I wouldn't expect:
- the second word of the labels to be capitalized
- the wording "until in [X] days", since it sounds unnatural. I would suggest
"until [X] days from now"
- the inclusion of the word "today" (because when one says e.g. "until 5:00
PM", the "today" is already implied)
Example after making these three changes:
- Until 11:54 AM
- Until 2:54 PM
- Until 8:00 PM
- Until tomorrow, 6:00 AM
- Until two days from now, 6:00 AM
SOFTWARE/OS VERSIONS
OS: Kubuntu 20.04
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 421989] Do not disturb end dates use unusual capitalization and some read awkwardly
https://bugs.kde.org/show_bug.cgi?id=421989 --- Comment #1 from Miles Krell --- Created attachment 128730 --> https://bugs.kde.org/attachment.cgi?id=128730&action=edit screenshot showing do not disturb end date of "Until In two days, 6:00 AM" -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 377555] New: 'The package kit daemon has crashed' upon searching in discover
https://bugs.kde.org/show_bug.cgi?id=377555 Bug ID: 377555 Summary: 'The package kit daemon has crashed' upon searching in discover Product: Discover Version: 5.9.3 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: davenpor...@outlook.com Target Milestone: --- I just installed KDE Neon freshly over a convoluted Ubuntu system. Everything works fine except when I try to install applications via discover, the software center. I open the application and it all works fine, however once I start typing in the search box and results start appearing I see a little semi-opaque box near the bottom of the app saying 'The Packagekit daemon has crashed' If I then click anywhere on the app it closes the application, with the box saying 'discover has closed unexpectedly. I've reinstalled the application through the command 'apt-get --reinstall install discover' though I may have got that wrong. Any tips on what I should do would be appreciated. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471160] New: Scrolling horizontally and vertically on a grid pager work in an unexpected way
https://bugs.kde.org/show_bug.cgi?id=471160 Bug ID: 471160 Summary: Scrolling horizontally and vertically on a grid pager work in an unexpected way Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: openSUSE OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Pager Assignee: plasma-b...@kde.org Reporter: milesbh...@linux.com CC: h...@kde.org Target Milestone: 1.0 Created attachment 159747 --> https://bugs.kde.org/attachment.cgi?id=159747&action=edit Example of grid pager SUMMARY Scrolling horizontally and vertically on a grid pager work unintuitively. STEPS TO REPRODUCE 1. Configure 4 workspaces in 2 rows 2. Add a pager widget to your panel 3. Scroll vertically on your pager. Observe as the pager goes left first, instead of down. 4. Edit your pager settings, and deselect "Navigation wraps around". 5. Scroll horizontally on your pager. This will work correctly on the first change (from 1 to 2), but then wrap around to 3. OBSERVED RESULT The anti-wrapping option is not fully honored when using a grid of virtual desktops. EXPECTED RESULT 1. Vertical scrolling should only scroll the pager vertically. 2. Horizontal scrolling should only scroll the pager horizontally. SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux: 6.3.7 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION Since not everyone has access to horizontal scrolling, I'd suggest adding an additional toggle. This additional toggle will make vertical and horizontal scrolling behave strictly. That way, people with only vertical scrolling can still use the current behaviour. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 471161] New: Touchpad settings: disabling "Tapping" disables elements not in grouping
https://bugs.kde.org/show_bug.cgi?id=471161 Bug ID: 471161 Summary: Touchpad settings: disabling "Tapping" disables elements not in grouping Classification: Applications Product: systemsettings Version: 5.27.5 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_touchpad Assignee: plasma-b...@kde.org Reporter: milesbh...@linux.com CC: natalie_clar...@yahoo.de Target Milestone: --- Created attachment 159748 --> https://bugs.kde.org/attachment.cgi?id=159748&action=edit Screenshot of affected area SUMMARY Disabling "Tapping" in the "Touchpad" settings disables elements not in the "Tapping" grouping. STEPS TO REPRODUCE 1. Disable "Tapping" in the "Touchpad" settings. OBSERVED RESULT The section labelled "Two-finger tap", which is not a part of the "Tapping" section, also gets disabled. EXPECTED RESULT Disabling "Tapping" only disables "Tapping". SOFTWARE/OS VERSIONS Linux: 6.3.7 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION I personally *hate* single-finger taps, but love two-finger taps. The inability to configure KDE in the way that I want is of course annoying, and perhaps especially so because this particular situation *looks* like a bug: "Tapping" and "Two-finger taps" are separate sections, so one would not expect them to interact with each other. To resolve this situation in as general a way as possible, I would suggest renaming "Tapping" to "One-finger taps", for consistency; and also of course making it so that disabling "One-finger taps" does not also disable "Two-finger taps". -- You are receiving this mail because: You are watching all bug changes.
[Systemd KCM] [Bug 426137] SystemD KCM: I18N_PLURAL_ARGUMENT_MISSING
https://bugs.kde.org/show_bug.cgi?id=426137 Miles B Huff changed: What|Removed |Added CC||milesbh...@linux.com --- Comment #1 from Miles B Huff --- Created attachment 137396 --> https://bugs.kde.org/attachment.cgi?id=137396&action=edit Screenshot I'm having the same issue. Operating System: Manjaro Linux KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471241] New: Scrolling to a virtual desktop causes all windows to rapidly minimize/maximize
https://bugs.kde.org/show_bug.cgi?id=471241 Bug ID: 471241 Summary: Scrolling to a virtual desktop causes all windows to rapidly minimize/maximize Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Pager Assignee: plasma-b...@kde.org Reporter: milesbh...@linux.com CC: h...@kde.org Target Milestone: 1.0 SUMMARY Scrolling to a virtual desktop causes all windows to rapidly minimize/maximize STEPS TO REPRODUCE 1. Configure 2 virtual desktops (row number does not matter) 2. Add a "Pager" widget to your panel 3. Configure the Pager so that "Selecting current virtual desktop:" is set to "Shows the desktop". 4. Scroll (up/down or left/right, does not matter) OBSERVED RESULT Scrolling changes the virtual desktop, as expected; however, all of the windows on that desktop then rapidly minimize/maximize until the scrolling action completes. EXPECTED RESULT Scrolling should not show the desktop -- only clicking should. SOFTWARE/OS VERSIONS Linux: 6.3.7 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION None. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471242] New: Minimizing then unminimizing all windows changes virtual desktop
https://bugs.kde.org/show_bug.cgi?id=471242 Bug ID: 471242 Summary: Minimizing then unminimizing all windows changes virtual desktop Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Show Desktop/Minimize All Assignee: plasma-b...@kde.org Reporter: milesbh...@linux.com Target Milestone: 1.0 SUMMARY Minimizing then unminimizing all windows changes virtual desktop STEPS TO REPRODUCE 1. Configure at least 2 virtual desktops (row number does not matter) 2. Add a "Pager" widget to your panel 3. Add a "Minimize all Windows" widget to your panel 4. Have windows open on both virtual desktops 5. Be on the first virtual desktop 6. Click the "Minimize all Windows" widget. 7. Click the "Minimize all Windows" widget again. EXPECTED RESULT / OBSERVED RESULT The second click should restore all minimized windows, but it instead causes you to switch to the second virtual desktop, which is extremely annoying. SOFTWARE/OS VERSIONS Linux: 6.3.7 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION None. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 472305] New: KDED setting invalid value to GNOME settings
https://bugs.kde.org/show_bug.cgi?id=472305 Bug ID: 472305 Summary: KDED setting invalid value to GNOME settings Classification: Frameworks and Libraries Product: frameworks-kded Version: 5.108.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: fa...@kde.org Reporter: milesbh...@linux.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY kded5 g_settings_set_value: key 'scaling-factor' in 'org.gnome.desktop.interface' expects type 'u', but a GVariant of type 'i' was given STEPS TO REPRODUCE 0. Have KDE set to support GNOME applications 1. Set your scaling factor to a non-integer OBSERVED RESULT Error when setting scaling factor in GNOME EXPECTED RESULT No such error. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230714 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 Kernel Version: 6.4.2-1-default (64-bit) Graphics Platform: X11 Processors: 16 × Intel® Core™ i7-10870H CPU @ 2.20GHz Memory: 31.2 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2 Manufacturer: System76 Product Name: Oryx Pro System Version: oryp7 -- You are receiving this mail because: You are watching all bug changes.
