[systemsettings] [Bug 430346] Custom script as shortcut is not run
https://bugs.kde.org/show_bug.cgi?id=430346 --- Comment #8 from apache --- Sorry for late answer. > Does the filename end in ".sh"?` I didn't. That was the problem. Now on Plasma 6 shortcuts work. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 430346] Custom script as shortcut is not run
https://bugs.kde.org/show_bug.cgi?id=430346 --- Comment #5 from apache --- In Plasma Version: 6.0.5 when I choose shortcuts add new command or script it doesn't see script files nor any other files only folders, so there is no way to create shortcut in settings. This makes it impossible to verify if this bug is still present unless there is other way to assign shortcut to script. For example: #!/bin/sh kquitapp5 plasmashell && kstart5 plasmashell still works in plasma 6 and I wanted to assign shortcut to it. Manjaro Linux KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.6.44-1-MANJARO (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 480132] Predefined timers only show the hours and minutes, but not the seconds
https://bugs.kde.org/show_bug.cgi?id=480132 --- Comment #1 from apache --- Still occurs in Operating System: Manjaro Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.6.30-2-MANJARO (64-bit) Graphics Platform: Wayland Although second can be set in plasmoids/org.kde.plasma.timer/contents/config/main.xml -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 480132] Predefined timers only show the hours and minutes, but not the seconds
https://bugs.kde.org/show_bug.cgi?id=480132 apache changed: What|Removed |Added CC||sabayo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 487583] New: shouldn't play sound by default, plays two sounds simultaneously, allow custom sound
https://bugs.kde.org/show_bug.cgi?id=487583 Bug ID: 487583 Summary: shouldn't play sound by default, plays two sounds simultaneously, allow custom sound Classification: Plasma Product: kdeplasma-addons Version: 6.0.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: timer Assignee: plasma-b...@kde.org Reporter: sabayo...@gmail.com Target Milestone: --- SUMMARY /usr/share/plasma/plasmoids/org.kde.plasma.timer widget always plays /usr/share/sounds/ocean/stereo/alarm-clock-elapsed.oga sound after time elapsed even when there is another command and sound set in settings. STEPS TO REPRODUCE 1. Go to timer settings → extended 2. Paste command mpv /usr/share/sounds/oxygen/stereo/desktop-login.ogg 3. Set countdown OBSERVED RESULT By default Timer plays /usr/share/sounds/ocean/stereo/alarm-clock-elapsed.oga When you do above steps it plays both sounds simultaneously. EXPECTED RESULT It shouldn't play any sound at all by default or there should be a separate option to activate / deactivate default sound. When there is custom command added to play sound like mpv /usr/share/sounds/oxygen/stereo/desktop-login.ogg it should play only custom sound. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.6.30-2-MANJARO (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 487291] Please port to Plasma 6
https://bugs.kde.org/show_bug.cgi?id=487291 apache changed: What|Removed |Added CC||sabayo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 487291] New: Please port to Plasma 6
https://bugs.kde.org/show_bug.cgi?id=487291 Bug ID: 487291 Summary: Please port to Plasma 6 Classification: Frameworks and Libraries Product: QtCurve Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: yyc1...@gmail.com Reporter: sabayo...@gmail.com CC: h...@kde.org Target Milestone: --- Please make it work on Plasma 6, QT6 I read this Qt6 support (#2) · Issues · System / QtCurve · GitLab https://invent.kde.org/system/qtcurve/-/issues/2 but I don't know who is ultimately responsible for qtcurve and what system Egor uses and how many months it will take. If developer doesn't have suitable distribution perhaps this could be done on virtual machine (I hope). For some users it is a big issue because as Linux users we love customize our systems :) No Qtcurve "Application Style" in Plasma 6 - Help - KDE Discuss https://discuss.kde.org/t/no-qtcurve-application-style-in-plasma-6/15353 -- You are receiving this mail because: You are watching all bug changes.
[kcolorchooser] [Bug 479406] The "Pick Screen Color" button is missing on Wayland session
https://bugs.kde.org/show_bug.cgi?id=479406 apache changed: What|Removed |Added CC||sabayo...@gmail.com --- Comment #16 from apache --- There is no such field as "pick color from screen" Operating System: Manjaro Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.6.30-2-MANJARO (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452888] 24-hour config setting does not propagate to items in the "Copy to clipboard" menu
https://bugs.kde.org/show_bug.cgi?id=452888 apache changed: What|Removed |Added CC||sabayo...@gmail.com --- Comment #18 from apache --- I still have this issue on Wayland Plasma 6. It just doesn't copy date to clipboard. Operating System: Manjaro Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.6.30-2-MANJARO (64-bit) Graphics Platform: Wayland Graphics Processor: Mesa Intel® HD Graphics 610 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478240] Excessively large side margins for non-floating space-filling panel
https://bugs.kde.org/show_bug.cgi?id=478240 apache changed: What|Removed |Added CC||sabayo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480723] New: add buttons to manually order clipboard actions
https://bugs.kde.org/show_bug.cgi?id=480723 Bug ID: 480723 Summary: add buttons to manually order clipboard actions Classification: Plasma Product: plasmashell Version: git-stable-Plasma/5.27 Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: sabayo...@gmail.com Target Milestone: 1.0 Clipboard actions are so great that I want to add more and more actions. For example if someone uses TTS engines there are dozens of voices that can be changed into actions. If there are many actions there is no graphical way to sort / order them. I know that I can use pattern as first step to order something but I prefer to use pattern for categories like "read" or "translate" or "pictures processing", etc. I know there is config file: plasmashellrc but obviously if you could add such up and down buttons to sort actions it would be very handy. -- You are receiving this mail because: You are watching all bug changes.
[bindings] [Bug 430346] Custom script as shortcut is not run
https://bugs.kde.org/show_bug.cgi?id=430346 apache changed: What|Removed |Added CC||sabayo...@gmail.com --- Comment #1 from apache --- I confirm that script that works in terminal, doesn't work when invoked by shortcut added in settings. Script file it is located: /home/user_name/script it starts with #!/bin/sh I gave it execute privileges. I went to settings → shortcuts → own shortcuts → new → global → command or url. I chose shortcut and as action: /home/user_name/./script When shortcut is pressed nothing happens. Operating System: Manjaro Linux KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.5-1-MANJARO (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472826] allow changing Win key assignment
https://bugs.kde.org/show_bug.cgi?id=472826 --- Comment #2 from apache --- Like this? [ModifierOnlyShortcuts] Meta=[dbus Toggle Present Windows (Current desktop)] Is it correct? I am not sure what is correct dbus command. In system settings I can't type Meta. When I press windows button it saves as some strange characters: https://i.imgur.com/fnhvqja.png -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472826] New: allow changing Win key assignment
https://bugs.kde.org/show_bug.cgi?id=472826 Bug ID: 472826 Summary: allow changing Win key assignment Classification: Plasma Product: plasmashell Version: 5.27.6 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: plasma-b...@kde.org Reporter: sabayo...@gmail.com Target Milestone: 1.0 SUMMARY *** Win key is permanently assigned to Kicker and changing assignment to other function (like present windows) works only until restart. *** STEPS TO REPRODUCE Assign Win key to Present Windows (Current Desktop). Reboot system. OBSERVED RESULT It works until I restart system . But even so when I go out of Present Windows view by pressing Win key again I still see menu closing. It is somehow activated anyway. After restart it doesn't show Present Windows at all but only opens Kicker. EXPECTED RESULT Should not be "hardcoded" so that any function can be assigned. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 Kernel Version: 6.4.6-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Pentium® CPU G4560 @ 3.50GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 610 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: H110M-S2H -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 398021] qtcurve dosn't save settings
https://bugs.kde.org/show_bug.cgi?id=398021 --- Comment #9 from apache --- I forgot about the issue. Seems to be ok now. You can close it. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 423232] option to disable pdf preview
https://bugs.kde.org/show_bug.cgi?id=423232 --- Comment #3 from apache --- Could you add option to be able to choose what files are displayed? I don't want Gwenview to display video, gif, pdf, etc. I use dedicated software for them. For example, in Dolphin there is option to choose for what file extensions Dolphin shows preview. It could be similar for Gwenview but allow to choose what files are visible in Gwenview. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 395182] Timer widget looks too small when docked into a panel
https://bugs.kde.org/show_bug.cgi?id=395182 --- Comment #4 from apache --- It is still valid bug on Operating System: Manjaro Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.15.38-1-MANJARO (64-bit) Graphics Platform: X11 Graphics Processor: NVA8 Can anything be finally done about it? At least a workaround. How is it possible that other widgets like calendar or Focus display digits in proper size but timer cannot? I use old version of Timer with these workaround https://forum.kde.org/viewtopic.php?f=67&t=137743 and it still displays numbers correctly and for dark theme as a temporary workaround I copied timer.svgz from /usr/share/plasma/desktoptheme/oxygen/widgets/ to /usr/share/plasma/desktoptheme/default/widgets/ to make it visible on dark theme. I use AlphaBlack Control widget to color panel. Can you tell what to do to make it not be overwritten when Plasma update comes? Should I copy something to: /home/user/.local/share/plasma/desktoptheme/ But what? Entire "default" folder from /usr/share/plasma/desktoptheme/ ? In what folder should I place timer.svgz in /home/user/.local/share/plasma/ so that the widget in user home can display it? -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 311597] the save bar resizes the window beyond measure after exiting the fullscreen mode
https://bugs.kde.org/show_bug.cgi?id=311597 apache changed: What|Removed |Added CC||sabayo...@gmail.com --- Comment #6 from apache --- Created attachment 148264 --> https://bugs.kde.org/attachment.cgi?id=148264&action=edit no tabs at the bottom, no scrollbar below miniatures I have the same right after when I click on image file in Dolphin. Gwenview opens with this wrong scaling so that no tabs at the bottom for F4 bar, no scrollbar below miniatures are visible. I use 1440x900 resolution screen. I deleted Gwenview catche and config files but with no result. Operating System: Manjaro Linux KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.32-1-MANJARO (64-bit) Graphics Platform: X11 Graphics Processor: NVA8 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442087] Change paper color doesn't work
https://bugs.kde.org/show_bug.cgi?id=442087 apache changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|NEEDSINFO |RESOLVED --- Comment #2 from apache --- It looks like it was something wrong with old pdf, because now I made a new one and everything is ok. So it was false report. I will close it then. Thank you for response. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442087] Change paper color doesn't work
https://bugs.kde.org/show_bug.cgi?id=442087 apache changed: What|Removed |Added Platform|Other |Manjaro CC||sabayo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442087] New: Change paper color doesn't work
https://bugs.kde.org/show_bug.cgi?id=442087 Bug ID: 442087 Summary: Change paper color doesn't work Product: okular Version: 21.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: sabayo...@gmail.com Target Milestone: --- When I clock on icon "change paper color" nothing happens. I tried on pdf made in LO Writer. Other options for example: "change light and dark colors" or "revert colors" work. Operating System: Manjaro Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.10.61-1-MANJARO (64-bit) Graphics Platform: X11 Graphics Processor: NVA8 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 332512] Plasma Popups aren't resizable, and if you force-resize them, they forget their size after the computer or plasmashell is restarted
https://bugs.kde.org/show_bug.cgi?id=332512 --- Comment #101 from apache --- @Michael Hamilton > arguably showing an appalling lack of sensibility to real-world usability in > the age of 4K monitors You have reached to the wrong conclusion about what is called real-world. I still use 1280x1024 and it is from the era when there wasn't such thing as planned obsolescence https://en.wikipedia.org/wiki/Planned_obsolescence It still working and that's why I see no reason to replace it. My previous screen although was wider died after only 3 years. And remember that Linux is widely used in use-cases where wide screen is either not needed or investment in hardware such as wide screens are not priority (for example academic institutes). Calendar is still not resizable as it used to be possible. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 383259] kf5.kded: No X-KDE-DBus-ServiceName
https://bugs.kde.org/show_bug.cgi?id=383259 --- Comment #7 from apache --- Now I have: journalctl -b |grep mount sie 25 08:27:26 user-pc systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. sie 25 08:27:26 user-pc systemd[1]: Starting Remount Root and Kernel File Systems... sie 25 08:27:26 user-pc systemd[1]: proc-sys-fs-binfmt_misc.automount: Got automount request for /proc/sys/fs/binfmt_misc, triggered by 194 (systemd-binfmt) sie 25 08:27:26 user-pc systemd[1]: Finished Remount Root and Kernel File Systems. sie 25 08:27:27 user-pc systemd[1]: tmp.mount: Directory /tmp to mount over is not empty, mounting anyway. sie 25 08:27:35 user-pc plasmashell[517]: kf.coreaddons: plugin metadata in "/usr/lib/qt/plugins/libkcm_device_automounter.so" does not have a valid 'MetaData' object Operating System: Manjaro Linux KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.10.59-1-MANJARO (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441312] Add window titles and icons
https://bugs.kde.org/show_bug.cgi?id=441312 --- Comment #9 from apache --- This discussion is pointless. Some will want it some don't. Current Present windows options have show icons and display windows titles options. https://i.imgur.com/vkDW34H.png I don't understand why some users have problem with it. Just keep it optional. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441312] Add window titles and icons
https://bugs.kde.org/show_bug.cgi?id=441312 apache changed: What|Removed |Added CC||sabayo...@gmail.com --- Comment #5 from apache --- Why not making it optional? Some users will disable icons and titles some would prefer to have them displayed. https://pointieststick.com/2021/08/20/this-week-in-kde-some-cool-new-stuff/ > will eventually replace the existing Present Windows effect and probably the > Desktop Grid effect as well, unifying them both into a full-screen overview > of windows, Virtual Desktops and perhaps Activities too! For me it is easier to use Present Windows and Desktop Grid with icons and titles, depending on the size of window and the number of windows open. Titles can be under windows and icons in windows corner so that they don't cover window preview. Take into account that there are users who still use relatively small screens and as a consequence preview windows become small. Search for the largest monitors in 2021 and compare to 10 years' old 1280x1024 and realize that user experience with Present Windows and Desktop Grid are different. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 433258] Network system monitor doesn't work for network bridges
https://bugs.kde.org/show_bug.cgi?id=433258 --- Comment #18 from apache --- Maybe that is the problem that configuration files in ~/.local/share/ksysguard/ are not created / updated properly when files in /usr/share/ksysguard/ are created / replaced by a new version. @miklos This would explain my situation when I had this file but it didn't work properly until I replaced it with a new one from /usr/share/ksysguard/ Did your system create files in ~/.local/share/ksysguard/ after you had removed old ones? Did you try coping from /usr/share/ksysguard/ -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 433258] Network system monitor doesn't work for network bridges
https://bugs.kde.org/show_bug.cgi?id=433258 --- Comment #16 from apache --- This solution worked for me https://bbs.archlinux.org/viewtopic.php?id=224215 Copy the default “SystemLoad2.sgrd” file from /usr/share/ksysguard/ to ~/.local/share/ksysguard/ I already had this file so I overwritten it and it works. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 433258] Network system monitor doesn't work for network bridges
https://bugs.kde.org/show_bug.cgi?id=433258 --- Comment #15 from apache --- It appeared that on one Manjaro installation it works ok when cable is attached to motherboard. But on other installation (the same motherboard but separate disk) regardless of where cable is attached to motherboard or PCI internet card there is no graph. But I don't know what else to check. I reinstalled ksysguard but no results. Is it a configuration issue? -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 433258] Network system monitor doesn't work for network bridges
https://bugs.kde.org/show_bug.cgi?id=433258 --- Comment #12 from apache --- Problem still exist on Manjaro 5.21.5 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 433258] Network system monitor doesn't work for network bridges
https://bugs.kde.org/show_bug.cgi?id=433258 apache changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 433258] Network system monitor doesn't work for network bridges
https://bugs.kde.org/show_bug.cgi?id=433258 --- Comment #9 from apache --- I don't use docker containers or anything unusual. Only cable modem and Manjaro desktop. I didn't change modem configuration. After Plasma update it just stopped working. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 435256] New: add GUI option in plasma-pa for Loopback
https://bugs.kde.org/show_bug.cgi?id=435256 Bug ID: 435256 Summary: add GUI option in plasma-pa for Loopback Product: plasma-pa Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: now...@gmail.com Reporter: sabayo...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY This command doesn't work with pipewire: pactl load-module module-loopback but module loopback is now implemented in pipewire master: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/970#note_864047 I want to hear everything that is connected to line-in or mic. Regular users need visual / GUI switch in plasma-pa, so that they don't need to search for proper command on the Internet and paste to terminal or dig into alsa settings. It should be in system sound settings. This feature is essential for users who want to record their voice from microphone or similar sources, like people who record podcasts, record video courses with audio comments, streamers, etc. Mobile phone may act as a microphone when attached to line-in (with proper software of course). -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 433258] Network system monitor doesn't work for network bridges
https://bugs.kde.org/show_bug.cgi?id=433258 --- Comment #3 from apache --- KSysGuard doesn’t show me Internet graph, while at the same time plasma-systemmonitor shows upload and download. https://i.imgur.com/zxeCg8s.png -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 433258] Network system monitor doesn't work for network bridges
https://bugs.kde.org/show_bug.cgi?id=433258 apache changed: What|Removed |Added CC||sabayo...@gmail.com --- Comment #1 from apache --- I don't know if this is the same or separate bug, but my system monitor doesn't show any traffic line in network history. Before Plasma 5.21 it was working normally. Operating System: Manjaro Linux KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.11.6-1-MANJARO OS Type: 64-bit Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 166183] Please add Trash to Akregator
https://bugs.kde.org/show_bug.cgi?id=166183 apache changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|CONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411314] Notifications are not noticeable enough under certain circumstances
https://bugs.kde.org/show_bug.cgi?id=411314 --- Comment #42 from apache --- @Nate Graham Would it be possible for KDE team to add center of screen position to already existing positions sometime in the near future, regardless of other changes? For some users it will make a huge difference, without waiting for all other goodies to come? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411314] Notifications are not noticeable enough under certain circumstances
https://bugs.kde.org/show_bug.cgi?id=411314 --- Comment #41 from apache --- Although colors of notifications are crucial for me, it is worth remembering that some users may suffer from various medical conditions like for example Achromatopsia: https://en.wikipedia.org/wiki/Achromatopsia https://en.wikipedia.org/wiki/Color_blindness https://www.amirahchambledesign.com/blog/designing-with-the-color-blind-in-mind If you had your driving license exam you certainly remember a test that checks if you can recognize colors correctly. That's why other visual effects and font size may be important to some users. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411314] Notifications are not noticeable enough under certain circumstances
https://bugs.kde.org/show_bug.cgi?id=411314 --- Comment #40 from apache --- > allow notifications to appear closer to the middle of the screen Yes. Regardless of other visual effects, adding screen center position to already existing positions would be a plus. I like the sliding effect but only sliding effect will not make desired usability big difference (at least in my case). Let's imagine you turned your head because someone was talking to you. If you get back to look at your screen and notification is already there but there is no contrast in colors there is still a chance you will miss notification. Color variation is a real game changer. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 427140] drag & drop text from Kate to other window or application
https://bugs.kde.org/show_bug.cgi?id=427140 --- Comment #5 from apache --- Indeed. With new Anki version it also works for me. Thank you for checking. I think it the bug report can be closed now. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 427140] drag & drop text from Kate to other window or application
https://bugs.kde.org/show_bug.cgi?id=427140 --- Comment #3 from apache --- I checked on Plasma 5.20.4 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.2 and it works fine for Kate to Kate or Kate to Firefox but doesn't for Kate to Anki. This is strange because I can drag & drop text from Firefox to Anki. To test in Anki click in Anki on Add option. Anki is one of the most popular applications for learning, so it would be really nice to have it working. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430332] New: It is not possible to resize widgets that open from panel
https://bugs.kde.org/show_bug.cgi?id=430332 Bug ID: 430332 Summary: It is not possible to resize widgets that open from panel Product: plasmashell Version: 5.20.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: sabayo...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 It is not possible to resize widgets that open from panel, like for example Calendar, Tiled Quicklaunch, Menu. It used to be possible with Alt+right mouse click but it doesn’t work now. When calendar widget is on desktop I can see handles to resize: https://i.imgur.com/cLBxnmJ.png but when calendar is on panel there are no such options: https://i.imgur.com/FkVRey9.png Another case: https://www.reddit.com/r/kde/comments/gu73t8/resize_windows_of_widgets_in_panel/ Operating System: Manjaro Linux KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.2 Kernel Version: 5.4.80-2-MANJARO OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 428097] New: KatePartView Toolbar disappears
https://bugs.kde.org/show_bug.cgi?id=428097 Bug ID: 428097 Summary: KatePartView Toolbar disappears Product: kate Version: 20.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: sabayo...@gmail.com Target Milestone: --- Created attachment 132631 --> https://bugs.kde.org/attachment.cgi?id=132631&action=edit sample action SUMMARY Normally I have Main toolbar and Main toolbar like this: https://i.imgur.com/5OrvSQh.png https://i.imgur.com/ZwOvn5N.png https://i.imgur.com/kv823sv.png I had two documents opened and I closed one and this caused KatePartView toolbar to disappear: https://i.imgur.com/Di4jbks.png See attached sample video. STEPS TO REPRODUCE I had two files opened and I closed one. OBSERVED RESULT Also when KatePartView wasn't visible and I clicked with mouse right button on document that I left open as in screenshot https://i.imgur.com/Di4jbks.png no options appeared so I couldn't do copy with mouse. There wasn't mouse pop-up window. EXPECTED RESULT KatePartView should be always visible. Mouse pop-up should always work. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 Kernel Version: 5.4.72-1-MANJARO OS Type: 64-bit Processors: 2 × Intel® Core™2 Duo CPU E7400 @ 2.80GHz Memory: 2.9 GiB of RAM Graphics Processor: GeForce 210/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 427779] Missing shutdown options after update to Plasma 5.20
https://bugs.kde.org/show_bug.cgi?id=427779 apache changed: What|Removed |Added CC||sabayo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 427140] New: drag & drop text from Kate to other window or application
https://bugs.kde.org/show_bug.cgi?id=427140 Bug ID: 427140 Summary: drag & drop text from Kate to other window or application Product: kate Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: sabayo...@gmail.com Target Milestone: --- I am not sure if this is Kate issue or some other Plasma component. Feel free to reassign elsewhere. Recently there was a feature added to Plasma that it is possible now to drag some text and drop it on desktop and a new sticky note is created. That is cool. The issue is that when I have two Kate windows open side by side like in the screenshot it is not possible to drag & drop text. Only copy paste works. https://i.imgur.com/c2N98SE.png Expected result: Make it possible to drag & drop text from any text application to any other text application. This is kind of strange because I was able to drag & drop text from Kate to Writer. But I wasn't able to drag & drop text from Kate to Kate or from Kate to Anki editor window. https://apps.ankiweb.net/ This is software for learning and it is particularly important to me to be able to use drag & drop method. If I spend many hours editing text, making every step easier, effortless is very important. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411314] Notifications are not noticeable enough under certain circumstances
https://bugs.kde.org/show_bug.cgi?id=411314 --- Comment #36 from apache --- > That's why you don't hardcode the colors but inherit them from one's color > scheme, which is what the default plasma theme does. Isn't it a problem discussed above? Actually this is the source of the problem. This is what screenshot from users in this bug report prove. And I don't want to mess with all my colors just to fit them to notifications. At least allow to set these three urgency colors. It is obvious that there must be some contrast between notification color and whatever is behind it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411314] Notifications are not noticeable enough under certain circumstances
https://bugs.kde.org/show_bug.cgi?id=411314 --- Comment #31 from apache --- I read this https://community.kde.org/Plasma/Notifications They propose: "It is up to the application developer to decide which urgency to assign." That is wrong approach. It should be for user to decide what is important. And woudl "color the header area in some way" be much easier to introduce than font color and size? Certainly from usability point of view adding three hard-coded colors for some users could make no difference as it may happen that they may have theme that would make header still not very distinguished against of what is behind it. So, three hard-coded color variation is still not very flexible solution. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411314] Notifications are not noticeable enough under certain circumstances
https://bugs.kde.org/show_bug.cgi?id=411314 --- Comment #30 from apache --- Why not allowing custom css in configuration file to make it pretty and fun https://tobiasahlin.com/moving-letters/ That would be awesome. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411314] Notifications are not noticeable enough under certain circumstances
https://bugs.kde.org/show_bug.cgi?id=411314 --- Comment #29 from apache --- > Perhaps we could color the header area in some way? For example notifications > marked with Urgency=Critical could color the header red. Why not, but what criteria will be used to decide what is "Critical"? Only system notification, like for example: you are running out of space or it is going to be customizable? Because for me Timer notifications are critical. For other users email they are waiting for may be critical. This would require to add some notifications settings like in Mac or Windows. They have quite complex notification center: How To Get the Most From the Notification Center https://www.youtube.com/watch?v=q2mZF4Hs7Fg Windows 10 Settings System Notification and actions what does it do and how to set up https://www.youtube.com/watch?v=IGwym4J8usY -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411314] Notifications are not noticeable enough under certain circumstances
https://bugs.kde.org/show_bug.cgi?id=411314 --- Comment #26 from apache --- Taking into account usability, we have: time factor, look factor, importance of notification factor (which appeared to be subjective / personally biased). I don't know how many unstated here factors you want to take into account to make usability issue clear and proceed to the next step. You may suggest some if they wasn't stated here. I admit that I am not familiar with desktop usability studies. So some insight maybe useful for all taking part in this conversation. > So far people are articulating that they are having difficulty noticing > notifications which time out, particularly on large screens. That's a > legitimate issue. I'm proposing that we first brainstorm solutions to that > issue. What is the difference between large screen and small screen considering usability of notifications? > I'm not sure that would be so effective if the root problem is notifications > not being noticed at all. That crosses out timeout and allow to proceed to the next factor: how to make them more noticeable. You can change font color, background color and font size or even type of notification and their behavior. You can make it more complex and as some articles that you can google by: notification+usability suggest provide different types of notifications: High-attention, Medium-attention, Low-attention. And they can be also characterized by other factors like from what application notification comes from and what it actually notify about. For example: https://uxdesign.cc/a-comprehensive-guide-to-notification-design-2fff67f08b7a But this is the whole new level of complication for this issue and more complex than just allowing to change font size and color. And I am sure whatever you hardcode there will be some users that still want more customization. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411314] Notifications are not noticeable enough under certain circumstances
https://bugs.kde.org/show_bug.cgi?id=411314 --- Comment #24 from apache --- > But I agree that adding an option to increase the font size doesn't make much > sense since notifications simply inherit the font size used throughout the > interface. It also doesn't make any sense to change wallpaper. Gosh. It is not about sense. It is about preference. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411314] Notifications are not noticeable enough under certain circumstances
https://bugs.kde.org/show_bug.cgi?id=411314 --- Comment #22 from apache --- This discussion doesn't make any sense. You claim that the key factor is whether something bad happens if I miss a notification or not. It is not about that. It is about how users (not developers) want to use their desktop environment. You do Plasma for yourself or for users? What is the point of changing default Plasma wallpaper? Anything bad would happen if it stayed the same for years. No. But some people still think it is better to customize. Anything bad would happen if everyone would have to use default theme? No. But still users want to customize. Either someone do it or Cloze it because waiting a year only to continue such discussion is absurd. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411314] Notifications are not noticeable enough under certain circumstances
https://bugs.kde.org/show_bug.cgi?id=411314 --- Comment #19 from apache --- > Notifications are generally intended to be ignorable. The whole point is that there are different type of notifications. For example I use Timer widget. Otherwise I would have to use my phone. Unfortunately Kalarm requires the whole kdepim-runtime and akonadi, so I don't want to install it on my slow PC. Also when I use spotify I like to see notification that the song is changing. May seem trivial but I like it that way. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411314] Notifications are not noticeable enough under certain circumstances
https://bugs.kde.org/show_bug.cgi?id=411314 --- Comment #17 from apache --- > The text in notifications is the same size as text used throughout Plasma. If > it's too small to read in notifications, it should be too small to read > elsewhere, in which case the solution is to increase the font size globally. > :) That is totally wrong argument because it doesn't take into account that users have different approaches and different use-cases of notifications. Notifications are not only confirmation that the job was done but also notify that something must be done, sometimes immediately. The fact that someone is able to read the small size text doesn't mean that user wants to have the same text size on notifications (or across the whole Plasma). The function of notification is to draw user's attention, that is why I want to have bigger text than I use in other elements of Plasma. I would be very happy if you could do something about it before Plasma 6. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 423732] Option to disable recent documents for public accessible computers
https://bugs.kde.org/show_bug.cgi?id=423732 --- Comment #5 from apache --- > Every application may store its list of recently used documents in their > history files Yes. But this is kind of another story. Even when you clear recent documents in Kate there are still visible in task manager. If user wants to remove recent documents, he/she needs to remember about clearing them from two places. Besides, some applications, for example VLC, have option to disable recent files history. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 423232] option to disable pdf preview
https://bugs.kde.org/show_bug.cgi?id=423232 --- Comment #2 from apache --- I pasted: [PreviewSettings] Plugins= with no effect. May I suggest an option below Video https://i.imgur.com/iJpyKsM.png Show pdf (active / inactive) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423732] option to disable recent documents in Tasks on panel
https://bugs.kde.org/show_bug.cgi?id=423732 --- Comment #2 from apache --- If someone forgets to clear it manually other persons (for example at work) can see what documents or movies or pictures were at use. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423732] New: option to disable recent documents in Tasks on panel
https://bugs.kde.org/show_bug.cgi?id=423732 Bug ID: 423732 Summary: option to disable recent documents in Tasks on panel Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: sabayo...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 With right click on application in Tasks widget there are recent documents shown. And for every one application they need to be deleted separately. Add option to permanently disable recent documents in Tasks widget on panel in all applications. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 423432] Fit page icon is misleading
https://bugs.kde.org/show_bug.cgi?id=423432 --- Comment #7 from apache --- @Nate Graham Feel free to change Product to Breeze. In linked thread on kde forum there are icons proposed. Maybe Breeze team will come up with something new. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 423432] Fit page icon is misleading
https://bugs.kde.org/show_bug.cgi?id=423432 --- Comment #6 from apache --- Just renaming text is not enough. I don't know whether it is Okular or Breeze issue. At this stage new design is welcomed. As I am not good at design I started topic on kde forum. Maybe someone will come up with a proposal: help design icons for Okular https://forum.kde.org/viewtopic.php?f=285&t=166740 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 423432] Fit page icon is misleading
https://bugs.kde.org/show_bug.cgi?id=423432 --- Comment #3 from apache --- Yes. I reflected to late that there are different use-cases and other factors. In my opinion, the bottom line is that each function should have its own distinct icon, so that when I have them all on the panel they don't confuse me. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 423432] Fit page icon is misleading
https://bugs.kde.org/show_bug.cgi?id=423432 --- Comment #1 from apache --- I forgot that some pdf documents can have more letter type size and landscape orientation of pages. But the point here is that at present Okular has the same icon for three different functions: https://i.imgur.com/g3sLsxa.png -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 423432] New: Fit page icon is misleading
https://bugs.kde.org/show_bug.cgi?id=423432 Bug ID: 423432 Summary: Fit page icon is misleading Product: okular Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: sabayo...@gmail.com Target Milestone: --- https://i.imgur.com/x4CNgFk.png Fit page icon (Change the magnification of the document view to a value that makes at least one whole page visible) to me is misleading. It looks like it suggest expanding while a click on it contracts page so that it fits program hight. I think the arrows should point inside to indicate contracting: https://i.imgur.com/L7WeNmd.png Or, even better, you can remove left and right arrows so that it shows that page will fit hight of program. https://i.imgur.com/58g4Mhv.png This would match look of the other icon that expands page to program width: https://i.imgur.com/3OtL7Zb.png Certainly the other use-case is possible when page is so minimized that a few pages are visible and clicking on this icon expands page but this is more rare situation. But even considering this, just leaving bottom and upper arrows makes much more sense to me: https://i.imgur.com/mquvqU8.png This indicates that page will fit vertically. And this is what this function actually does. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 423232] New: option to disable pdf preview
https://bugs.kde.org/show_bug.cgi?id=423232 Bug ID: 423232 Summary: option to disable pdf preview Product: gwenview Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: sabayo...@gmail.com Target Milestone: --- Please add option to disable pdf preview. Why? Because that is my preference. I can have pdf preview in Dolphin. When I click on pictures like png, jpg and have Gwenview as picture viewer I want to see those type of files (and perhaps do some operations on them) but not all content of the folder. I don't want to accidentally delete pdf thinking it is some uninteresting jpeg. pdf preview definitely should be optional. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 423229] New: delete page
https://bugs.kde.org/show_bug.cgi?id=423229 Bug ID: 423229 Summary: delete page Product: okular Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: sabayo...@gmail.com Target Milestone: --- Please add option to delete current page. I know that other pdf applications (like PDF Mix Tool) have this feature but it would be convenient to have it in Okular, especially for e-magazines when I look through and want to keep only relevant content. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 421682] add window rule to minimize or cloze to systemtray
https://bugs.kde.org/show_bug.cgi?id=421682 --- Comment #2 from apache --- I don't quite understand. > Technically, this is impossible because This "because" doesn't explain anything. Why not possible? Because it hasn't been done yet or because there is no way to do it? Why KDocker can do it and not kwin? Can you give a more clear explanation? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 421682] New: add window rule to minimize or cloze to systemtray
https://bugs.kde.org/show_bug.cgi?id=421682 Bug ID: 421682 Summary: add window rule to minimize or cloze to systemtray Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: sabayo...@gmail.com Target Milestone: --- That would be useful for a lot of applications that are very frequently used like web browser or some applications from other desktop environments. I know there is kdocker but native option would make kwin even greater. Besides kwin consumes memory which is not the best solution for application that is used all the time, every day. And this will prevent program developers from necessity of adding this option and users from begging for it for every single application that users want to manage this way. For example Zanshin doesn't have this feature yet. -- You are receiving this mail because: You are watching all bug changes.
[zanshin] [Bug 306519] it should be possible to move tasks to a certain position in the list
https://bugs.kde.org/show_bug.cgi?id=306519 --- Comment #3 from apache --- Drag and drop would be awesome but icons for this would be helpful as well. -- You are receiving this mail because: You are watching all bug changes.
[zanshin] [Bug 421286] New: cloze to system tray
https://bugs.kde.org/show_bug.cgi?id=421286 Bug ID: 421286 Summary: cloze to system tray Product: zanshin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: er...@kde.org Reporter: sabayo...@gmail.com CC: mbe...@ipsquad.net Target Milestone: already done Cloze or minimize to system tray. When icon in system tray is clicked window hides. Please add this feature so that the program can be always on hand. This feature is already in Korganizer and Kalarm. So the code is already there. -- You are receiving this mail because: You are watching all bug changes.
[zanshin] [Bug 306519] it should be possible to move tasks to a certain position in the list
https://bugs.kde.org/show_bug.cgi?id=306519 apache changed: What|Removed |Added CC||sabayo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[zanshin] [Bug 420990] New: open web links in default browser
https://bugs.kde.org/show_bug.cgi?id=420990 Bug ID: 420990 Summary: open web links in default browser Product: zanshin Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: er...@kde.org Reporter: sabayo...@gmail.com CC: mbe...@ipsquad.net Target Milestone: already done Allow Zanshin to open web link in default web browser just by a click on a link. I remember that Tomboy has this feature. It doesn't require copy and paste into web browser, which is a huge convenience. A lot of my tasks are made just by pasting web links into Zanshin to read it later. I don't add title nor description. So, only a web link pasted into bottom "add task " field becomes a task. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 417640] New: unintuitive right mouse click default behavior for create new
https://bugs.kde.org/show_bug.cgi?id=417640 Bug ID: 417640 Summary: unintuitive right mouse click default behavior for create new Product: dolphin Version: 19.12.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: sabayo...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- When I do right mouse click in empty folder, the default behavior is correct: the first item on a list is "create new": https://i.imgur.com/K7LSNrz.png But when there is some content in a folder but also there is some "empty space" and I click on this "empty space", not on any file or folder, the default behavior shows "open with" on the first position, which makes no sense at all, because I don't want to open "empty space". When I click on "empty space" this means that I want to create a new folder or a new file. https://i.imgur.com/ZV8zrCX.png "Open with" should be as an option on the first position only when user click on file or folder. Operating System: Manjaro Linux KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.1 Kernel Version: 5.4.18-1-MANJARO OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401500] Slightly increase notification pop up's distance from the screen edge
https://bugs.kde.org/show_bug.cgi?id=401500 --- Comment #4 from apache --- I still have it on 5.16.5 with button size big and window title font size 12. https://imgur.com/sxyknrV Operating System: Manjaro Linux KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 Kernel Version: 4.19.79-1-MANJARO OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411174] Plasmashell totally unresponsive changing the height of panel if the application menu has a custom icon
https://bugs.kde.org/show_bug.cgi?id=411174 --- Comment #14 from apache --- Sorry, I should add hat this happens when I switch from one application to another (usually from Pale moon or Firefox to Dolphin) clicking on tasks widget on panel. Tt sometimes hangs for a while before showing the window of the app I choose. This happens with my custom theme but also with Breeze dark (on Manjaro). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411174] Plasmashell totally unresponsive changing the height of panel if the application menu has a custom icon
https://bugs.kde.org/show_bug.cgi?id=411174 apache changed: What|Removed |Added CC||sabayo...@gmail.com --- Comment #13 from apache --- I have custom icons in menu and on panel and the same errors [user@user-pc ~]$ kquitapp5 plasmashell && kstart5 plasmashell qt.core.logging: Ignoring malformed logging rule: '’*=false’' Omitting both --window and --windowclass arguments is not recommended qt.core.logging: Ignoring malformed logging rule: '’*=false’' [user@user-pc ~]$ invalid metadata "/usr/lib/qt/plugins/kcm_systemd.so" invalid metadata "/usr/lib/qt/plugins/msm_kernel.so" invalid metadata "/usr/lib/qt/plugins/msm_keyboard.so" invalid metadata "/usr/lib/qt/plugins/msm_language_packages.so" invalid metadata "/usr/lib/qt/plugins/msm_locale.so" invalid metadata "/usr/lib/qt/plugins/msm_mhwd.so" invalid metadata "/usr/lib/qt/plugins/msm_timedate.so" invalid metadata "/usr/lib/qt/plugins/msm_users.so" invalid metadata "/usr/lib/qt/plugins/kcm_kio.so" invalid metadata "/usr/lib/qt/plugins/kcm_trash.so" invalid metadata "/usr/lib/qt/plugins/kcm_webshortcuts.so" invalid metadata "/usr/lib/qt/plugins/kio_bluetooth.so" invalid metadata "/usr/lib/qt/plugins/kio_obexftp.so" invalid metadata "/usr/lib/qt/plugins/kstyle_breeze_config.so" invalid metadata "/usr/lib/qt/plugins/kcm_filetypes.so" invalid metadata "/usr/lib/qt/plugins/miloutextplugin.so" invalid metadata "/usr/lib/qt/plugins/kcm_kwin_scripts.so" invalid metadata "/usr/lib/qt/plugins/kcm_kwinoptions.so" invalid metadata "/usr/lib/qt/plugins/kcm_kwinrules.so" invalid metadata "/usr/lib/qt/plugins/kcm_kwinscreenedges.so" invalid metadata "/usr/lib/qt/plugins/kcm_kwintabbox.so" invalid metadata "/usr/lib/qt/plugins/kcm_kwintouchscreen.so" invalid metadata "/usr/lib/qt/plugins/kwincompositing.so" invalid metadata "/usr/lib/qt/plugins/kcm_ssl.so" invalid metadata "/usr/lib/qt/plugins/kcm_krunner_kill.so" invalid metadata "/usr/lib/qt/plugins/krunner_activities.so" invalid metadata "/usr/lib/qt/plugins/krunner_appstream.so" invalid metadata "/usr/lib/qt/plugins/krunner_bookmarksrunner.so" invalid metadata "/usr/lib/qt/plugins/krunner_calculatorrunner.so" invalid metadata "/usr/lib/qt/plugins/krunner_kill.so" invalid metadata "/usr/lib/qt/plugins/krunner_locations.so" invalid metadata "/usr/lib/qt/plugins/krunner_placesrunner.so" invalid metadata "/usr/lib/qt/plugins/krunner_powerdevil.so" invalid metadata "/usr/lib/qt/plugins/krunner_recentdocuments.so" invalid metadata "/usr/lib/qt/plugins/krunner_services.so" invalid metadata "/usr/lib/qt/plugins/krunner_sessions.so" invalid metadata "/usr/lib/qt/plugins/krunner_shell.so" invalid metadata "/usr/lib/qt/plugins/krunner_webshortcuts.so" invalid metadata "/usr/lib/qt/plugins/krunner_windowedwidgets.so" invalid metadata "/usr/lib/qt/plugins/krunner_windows.so" invalid metadata "/usr/lib/qt/plugins/plasma-geolocation-gps.so" invalid metadata "/usr/lib/qt/plugins/plasma-geolocation-ip.so" invalid metadata "/usr/lib/qt/plugins/classic_mode.so" invalid metadata "/usr/lib/qt/plugins/icon_mode.so" invalid metadata "/usr/lib/qt/plugins/systemsettings_sidebar_mode.so" invalid metadata "/usr/lib/qt/plugins/kcm_krunner_charrunner.so" invalid metadata "/usr/lib/qt/plugins/kcm_krunner_dictionary.so" invalid metadata "/usr/lib/qt/plugins/kcm_krunner_spellcheck.so" invalid metadata "/usr/lib/qt/plugins/krunner_charrunner.so" invalid metadata "/usr/lib/qt/plugins/krunner_converter.so" invalid metadata "/usr/lib/qt/plugins/krunner_datetime.so" invalid metadata "/usr/lib/qt/plugins/krunner_dictionary.so" invalid metadata "/usr/lib/qt/plugins/krunner_katesessions.so" invalid metadata "/usr/lib/qt/plugins/krunner_konsoleprofiles.so" invalid metadata "/usr/lib/qt/plugins/krunner_spellcheck.so" invalid metadata "/usr/lib/qt/plugins/kcm_kgamma.so" invalid metadata "/usr/lib/qt/plugins/kcm_hotkeys.so" invalid metadata "/usr/lib/qt/plugins/kcm_about_distro.so" invalid metadata "/usr/lib/qt/plugins/kcm_devinfo.so" invalid metadata "/usr/lib/qt/plugins/kcm_info.so" invalid metadata "/usr/lib/qt/plugins/kcm_memory.so" invalid metadata "/usr/lib/qt/plugins/kcm_nic.so" invalid metadata "/usr/lib/qt/plugins/kcm_opengl.so" invalid metadata
[plasmashell] [Bug 363878] Adjustable spacing between icons
https://bugs.kde.org/show_bug.cgi?id=363878 --- Comment #18 from apache --- > It's not totally clear what you're asking for I was asking for these settings https://bugsfiles.kde.org/attachment.cgi?id=99341 Not necessarily graphical. Option in configuration files would be enough for me. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 363878] option to make icons bigger
https://bugs.kde.org/show_bug.cgi?id=363878 --- Comment #12 from apache --- This is even better example how icon size doesn't match another widget size (time and date) in terms of panel space utilization https://i.imgur.com/nQLEQyT.png I know it is different widget but just to clarify the problem. I hope in Plasma 6 you would come back to plasma 4 solutions in terms of customization of icons, fonts and colors. In my humble opinion you improved what was better. Best is the enemy of good. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 363878] option to make icons bigger
https://bugs.kde.org/show_bug.cgi?id=363878 --- Comment #11 from apache --- Icons on task manager are not scalable in a sense that they can only have size that is set in system settings. (Ok. it is kind of scaling but limited to actual icons size). But task manager seems to have these predefined spaces. The result is that making panel wider only increases space on panel that I marked in red at the bottom of icon. And this is the case until panel is made larger and next fixed size of icon jumps. Example - the same icon size with different spaces - one is from task manager and the other from launcher added to panel from menu: https://i.imgur.com/PnvTja4.png https://i.imgur.com/99sPyPv.png -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 363878] option to make icons bigger
https://bugs.kde.org/show_bug.cgi?id=363878 --- Comment #10 from apache --- https://i.imgur.com/q4HkaeZ.png Icon size settings has fixed values such as for example 48, 64. Increasing, decreasing doesn't change anything because task manager widget (or panel - I am not sure) are designed in the way that there is a space between icon and task manager / panel edge. I marked in in red. Of course it is not a bug. It is bad design that results in icon being always a few pixel smaller than task / panel widget. Maybe this is different approach to "what looks good" but to me these spaces that I marked red are useless / unnecessary / waste of space. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411314] Allow to change notification font size and color in configuration file.
https://bugs.kde.org/show_bug.cgi?id=411314 --- Comment #10 from apache --- > The underlying problem is that you are having difficulty noticing > notifications, right? Right. That's obvious from what I have written so far. But if my solution to my problem doesn't suit you what is your solution proposal? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411314] Allow to change notification font size and color in configuration file.
https://bugs.kde.org/show_bug.cgi?id=411314 --- Comment #8 from apache --- Sorry, but I don't understand this approach. > Because that doesn't fix any underlying problem What would be as you call it "underlying problem"? There is a problem for me and I stated it clearly. > if one exists Yes, I herby declare that there is one for me. And I stated it clearly. I want to have my notifications to have bigger font and different color to differentiate from background. If you don't want to do it then say it openly. But don't make "the only right user experience" philosophy because there isn't such thing. When I write what I want I am perfectly conscious what I want. You are trying to tell me that I don't need it. As you can see on this screenshot https://i.imgur.com/tdL9cmH.png font size and color makes a difference. Why did you left this settings? If you are trying to convince me that it doesn't make any difference and that there is a different kind of a problem (if there is any) why don't you remove this setting? I interpret your words as if you were trying to tell me that I don't need different font but I only need to pay more attention. If that interpretation of your words is correct, then this is absurd to me. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411314] Allow to change notification font size and color in configuration file.
https://bugs.kde.org/show_bug.cgi?id=411314 --- Comment #6 from apache --- The ones that disappear after a few seconds. But the problem is that I need to see them once they appear so keeping them half an hour is not the solution. I frequently use timer widget I must react as notification appears. To do that they must be well visible for me. Why are you reluctant to add some code in configuration to allow users change font? Was this decision to abandon per widget font configuration during shift from Plasma 4 to Plasma 5 was ever discussed in a broader KDE team circle? On Randa meetings or at least on plasma developer's mailing list? Was it forced by some QT constrains. I wonder what was the justification of such practice that limits user's choice. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411314] Allow to change notification font size and color in configuration file.
https://bugs.kde.org/show_bug.cgi?id=411314 --- Comment #4 from apache --- When I multitask and jump from application to application and notifications are not distinct enough from the background it happens that I don't notice them. https://i.imgur.com/ZJx5gY6.png Big colorful, text as in example gif, captures my attention. But I want to be able to customize it to my liking and my needs and change the lines that now are not possible to change. The topic I linked earlier has 745 vies. Not very much but enough to indicate that some users are interested in such customization. By the way, this topic also indicates that users have different use-cases: https://forum.kde.org/viewtopic.php?f=17&t=161698 Sometimes notification is not very important and only confirms a job, sometimes is the most important, more important than current user activity. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411314] Allow to change notification font size and color in configuration file.
https://bugs.kde.org/show_bug.cgi?id=411314 --- Comment #2 from apache --- Believe me I would not bother you if it was purely for beauty purpose, for example to match system theme, but it is not. I guess it uses system font settings. My default font is not 9 but 12. For some system components it is good, but for notifications I barely notice it. And there are different notifications. When I unpack a file I usually wait for it and expect it, but when I use timer set to notify me in half an hour and I am busy doing other stuff, clicking from one application to another it is easy for me to miss a notification. I need big orange font to even notice that there is any notification. Now, I am able only to change this element (the same as in previous version of notifications): https://i.imgur.com/GIZFpWq.gif But this change doesn't cover these two lines: https://i.imgur.com/vSjPRJ6.png -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411314] New: Allow to change notification font size and color in configuration file.
https://bugs.kde.org/show_bug.cgi?id=411314 Bug ID: 411314 Summary: Allow to change notification font size and color in configuration file. Product: plasmashell Version: master Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: sabayo...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Allow to change notification font size and color in configuration file. https://imgur.com/vSjPRJ6 Another example: when I unpack zip file. Text is small and in default color with notification: “unpacking files” and after that “unpacking files finished”. I want to change font size and color of both this texts. There is old thread on KDE forum but it refers to old notifications version https://forum.kde.org/viewtopic.php?f=17&t=156011&sid=e8fd8e8c2e28e6febe2ecb373df508d9 Following this thread only changes one line of text. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409449] module "org.kde.plasma.private.notifications" version 1.0 is not installed
https://bugs.kde.org/show_bug.cgi?id=409449 --- Comment #3 from apache --- I forgot that a year ago I did some modification to notifications: I changed font size and colour. I reinstalled knotifications package and everything is ok now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409449] New: module "org.kde.plasma.private.notifications" version 1.0 is not installed
https://bugs.kde.org/show_bug.cgi?id=409449 Bug ID: 409449 Summary: module "org.kde.plasma.private.notifications" version 1.0 is not installed Product: plasmashell Version: 5.16.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: sabayo...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 121300 --> https://bugs.kde.org/attachment.cgi?id=121300&action=edit screenshot SUMMARY After today update on Manjaro I get this: Error reading (roll-in) file QML: file:///home/user/.local/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/main.qml:29:1: module "org.kde.plasma.private.notifications" version 1.0 is not installed SOFTWARE/OS VERSIONS Manjaro Linux KDE Plasma Version: 5.16.2 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.4 Kernel Version: 5.0.21-1-MANJARO OS Type: 64-bit ADDITIONAL INFORMATION But it seems to work. When I was logged in to Manjaro forum, a pop-up jumped to show me that someone replied to me. This is new behavior. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395956] [Wayland] Calendar events are not shown at first
https://bugs.kde.org/show_bug.cgi?id=395956 apache changed: What|Removed |Added CC||sabayo...@gmail.com --- Comment #2 from apache --- I have this in normal Plasma (not Wayland): Operating System: Manjaro Linux KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 Kernel Version: 5.0.21-1-MANJARO OS Type: 64-bit As you can see, first I click on clock on panel https://imgur.com/XMScWZJ and no information about holiday (for 23rd of June - today) is displayed on the left panel, although it is marked in calendar by blue dot. When I click on any other date and back on 23rd it shows Father's day correctly: https://imgur.com/Z9DxLMR -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 404997] window changes size when crop option is used
https://bugs.kde.org/show_bug.cgi?id=404997 apache changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 404997] window changes size when crop option is used
https://bugs.kde.org/show_bug.cgi?id=404997 --- Comment #5 from apache --- It is ok now. The bug doesn't appear anymore. Now I have: Operating System: Manjaro Linux KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 Kernel Version: 5.0.21-1-MANJARO -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404594] Plasma crash when opening calendar from panel
https://bugs.kde.org/show_bug.cgi?id=404594 --- Comment #5 from apache --- > pacman -R kholidays > checking dependencies… > error: can't prepare transaction (can't resolve dependencies) > :: plasma-workspace: removing kholidays breaks dependency 'kholidays' Edit: I copied the error message to Kate and changed it like this (for every line using, replace Ctrl+R): > #!/bin/sh > rm -rf /usr/share/locale/hi/LC_MESSAGES/libkholidays5_qt.qm > rm -rf /usr/share/locale/hne/LC_MESSAGES/libkholidays5_qt.qm And executed this script. And after that update went without errors. And also my problems with this calendar bug is solved. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404594] Plasma crash when opening calendar from panel
https://bugs.kde.org/show_bug.cgi?id=404594 --- Comment #4 from apache --- During Manjaro update I have this errors: kholidays: /usr/include/KF5/KHolidays/KHolidays/AstroSeasons is in file system kholidays: /usr/include/KF5/KHolidays/KHolidays/Holiday is in file system kholidays: /usr/include/KF5/KHolidays/KHolidays/HolidayRegion is in file system kholidays: /usr/include/KF5/KHolidays/KHolidays/LunarPhase is in file system kholidays: /usr/include/KF5/KHolidays/KHolidays/SunRiseSet is in file system kholidays: /usr/include/KF5/KHolidays/KHolidays/Zodiac is in file system kholidays: /usr/include/KF5/KHolidays/kholidays/astroseasons.h is in file system kholidays: /usr/include/KF5/KHolidays/kholidays/holiday.h is in file system kholidays: /usr/include/KF5/KHolidays/kholidays/holidayregion.h is in file system kholidays: /usr/include/KF5/KHolidays/kholidays/kholidays_export.h is in file system kholidays: /usr/include/KF5/KHolidays/kholidays/lunarphase.h is in file system kholidays: /usr/include/KF5/KHolidays/kholidays/sunriseset.h is in file system kholidays: /usr/include/KF5/KHolidays/kholidays/zodiac.h is in file system kholidays: /usr/include/KF5/kholidays_version.h is in file system kholidays: /usr/lib/cmake/KF5Holidays/KF5HolidaysConfig.cmake is in file system kholidays: /usr/lib/cmake/KF5Holidays/KF5HolidaysConfigVersion.cmake is in file system kholidays: /usr/lib/cmake/KF5Holidays/KF5HolidaysQchTargets.cmake is in file system kholidays: /usr/lib/cmake/KF5Holidays/KF5HolidaysTargets-noconfig.cmake is in file system kholidays: /usr/lib/cmake/KF5Holidays/KF5HolidaysTargets.cmake is in file system kholidays: /usr/lib/libKF5Holidays.so is in file system kholidays: /usr/lib/libKF5Holidays.so.5 is in file system kholidays: /usr/lib/qt/mkspecs/modules/qt_KHolidays.pri is in file system kholidays: /usr/lib/qt/qml/org/kde/kholidays/libkholidaysdeclarativeplugin.so is in file system kholidays: /usr/lib/qt/qml/org/kde/kholidays/qmldir is in file system kholidays: /usr/share/doc/qt/KF5Holidays.qch is in file system kholidays: /usr/share/doc/qt/KF5Holidays.tags is in file system kholidays: /usr/share/locale/ar/LC_MESSAGES/libkholidays5_qt.qm is in file system kholidays: /usr/share/locale/be/LC_MESSAGES/libkholidays5_qt.qm is in file system kholidays: /usr/share/locale/bg/LC_MESSAGES/libkholidays5_qt.qm is in file system kholidays: /usr/share/locale/br/LC_MESSAGES/libkholidays5_qt.qm is in file system kholidays: /usr/share/locale/bs/LC_MESSAGES/libkholidays5_qt.qm is in file system kholidays: /usr/share/locale/ca/LC_MESSAGES/libkholidays5_qt.qm is in file system kholidays: /usr/share/locale/ca@valencia/LC_MESSAGES/libkholidays5_qt.qm is in file system kholidays: /usr/share/locale/cs/LC_MESSAGES/libkholidays5_qt.qm is in file system kholidays: /usr/share/locale/cy/LC_MESSAGES/libkholidays5_qt.qm is in file system kholidays: /usr/share/locale/da/LC_MESSAGES/libkholidays5_qt.qm is in file system kholidays: /usr/share/locale/de/LC_MESSAGES/libkholidays5_qt.qm is in file system kholidays: /usr/share/locale/el/LC_MESSAGES/libkholidays5_qt.qm is in file system kholidays: /usr/share/locale/en_GB/LC_MESSAGES/libkholidays5_qt.qm is in file system kholidays: /usr/share/locale/eo/LC_MESSAGES/libkholidays5_qt.qm is in file system kholidays: /usr/share/locale/es/LC_MESSAGES/libkholidays5_qt.qm is in file system kholidays: /usr/share/locale/et/LC_MESSAGES/libkholidays5_qt.qm is in file system kholidays: /usr/share/locale/eu/LC_MESSAGES/libkholidays5_qt.qm is in file system kholidays: /usr/share/locale/fa/LC_MESSAGES/libkholidays5_qt.qm is in file system kholidays: /usr/share/locale/fi/LC_MESSAGES/libkholidays5_qt.qm is in file system kholidays: /usr/share/locale/fr/LC_MESSAGES/libkholidays5_qt.qm is in file system kholidays: /usr/share/locale/fy/LC_MESSAGES/libkholidays5_qt.qm is in file system kholidays: /usr/share/locale/ga/LC_MESSAGES/libkholidays5_qt.qm is in file system kholidays: /usr/share/locale/gl/LC_MESSAGES/libkholidays5_qt.qm is in file system kholidays: /usr/share/locale/he/LC_MESSAGES/libkholidays5_qt.qm is in file system kholidays: /usr/share/locale/hi/LC_MESSAGES/libkholidays5_qt.qm is in file system kholidays: /usr/share/locale/hne/LC_MESSAGES/libkholidays5_qt.qm is in file system kholidays: /usr/share/locale/hu/LC_MESSAGES/libkholidays5_qt.qm is in file system kholidays: /usr/share/locale/ia/LC_MESSAGES/libkholidays5_qt.qm is in file system kholidays: /usr/share/locale/id/LC_MESSAGES/libkholidays5_qt.qm is in file system kholidays: /usr/share/locale/is/LC_MESSAGES/libkholidays5_qt.qm is in file system kholidays: /usr/share/locale/it/LC_MESSAGES/libkholidays5_qt.qm is in file system kholidays: /usr/share/locale/ja/LC_MESSAGES/libkholidays5_qt.qm is in file system kholidays: /usr/share/locale/kk/LC_MESSAGES/libkholidays5_qt.qm is in file system kholidays: /usr/share/locale/km/LC_MESSAGES/libkholidays5_qt.qm is in file system kholidays: /usr/share/locale/ko/LC_MESSAGES/libkholidays5_qt.qm is in file system kholidays
[plasmashell] [Bug 404594] Plasma crash when opening calendar from panel
https://bugs.kde.org/show_bug.cgi?id=404594 --- Comment #3 from apache --- This bug is a duplicate of Bug 371666 - Plasma crashes irreversibly when enabling Holidays or scroling in Holidays' list https://bugs.kde.org/show_bug.cgi?id=371666 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371666] Plasma crashes irreversibly when enabling Holidays or scroling in Holidays' list
https://bugs.kde.org/show_bug.cgi?id=371666 apache changed: What|Removed |Added CC||sabayo...@gmail.com --- Comment #18 from apache --- This bug has a duplicate: https://bugs.kde.org/show_bug.cgi?id=404594 It is still present in Operating System: Manjaro Linux KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.3 Kernel Version: 5.0.15-1-MANJARO OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404594] Plasma crash when opening calendar from panel
https://bugs.kde.org/show_bug.cgi?id=404594 --- Comment #2 from apache --- Sorry, I forgot about this: Operating System: Manjaro Linux KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.3 Kernel Version: 5.0.9-2-MANJARO OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404594] Plasma crash when opening calendar from panel
https://bugs.kde.org/show_bug.cgi?id=404594 apache changed: What|Removed |Added CC||sabayo...@gmail.com --- Comment #1 from apache --- Created attachment 119762 --> https://bugs.kde.org/attachment.cgi?id=119762&action=edit error I also have a crash. What I did: First crash I had after last update on Manjaro and restart. I could see my desktop for a second and then screen went black and only mouse cursor was visible. The solution was to remove applet setting file: cd .config mv plasma-org.kde.plasma.desktop-appletsrc 02plasma-org.kde.plasma.desktop-appletsrc My desktop look was messed up. All applets and panel was gone. I set it again to my liking. The situation happened again when I clicked on calendar and I clicked on options: make holidays visible and show week numbers and ok. And this crashed plasma and again only black screen and mouse cursor is visible. I did it twice so I am sure that calendar crashes plasma. I wanted to restart plasma with command kquitapp5 plasmashell && kstart5 plasmashell and I attach file with terminal output. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 404997] window changes size when crop option is used
https://bugs.kde.org/show_bug.cgi?id=404997 apache changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from apache --- I don't know how to obtain more info. I already provided the proof - attachment - that the bug exist. When I run gwenview in terminal I get: qt.qpa.xcb: QXcbConnection: XCB error: 13 (BadGC), sequence: 5010, resource id: 0, major code: 130 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 13 (BadGC), sequence: 7153, resource id: 0, major code: 130 (Unknown), minor code: 3 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 404997] window changes size when crop option is used
https://bugs.kde.org/show_bug.cgi?id=404997 --- Comment #2 from apache --- Created attachment 119192 --> https://bugs.kde.org/attachment.cgi?id=119192&action=edit screenvideo > Are you able to provide additional steps on how to reproduce this issue? No. I just press crop and it happens. I attach a recorded video. Perhaps it has something to do with my nvidia card settings or driver. I don't know. I will provide more info if you tell me how. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 357314] Scrollbar can not be dragged from far right
https://bugs.kde.org/show_bug.cgi?id=357314 --- Comment #4 from apache --- I noticed that in Manjaro Breath-Dark it is done properly. It means that mouse touches scrollbar when moved to the screen edge. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 357314] Scrollbar can not be dragged from far right
https://bugs.kde.org/show_bug.cgi?id=357314 apache changed: What|Removed |Added CC||sabayo...@gmail.com --- Comment #3 from apache --- Has anything changed about this? I use libreoffice-still 6.1.5.2 Build ID: 6.1.5-2, VCL: gtk3_kde5; and I have issues with fat window frame. I use Plasma 5 and breeze-dark theme for gtk3 applications and scrollbar is very narrow and what is more important window edge is very wide. As a consequence mouse doesn't touch scrollbar. https://i.imgur.com/RwQyrtG.png Compare: on the left LO frame and on the right: Plasma 5 window with qtcurve applied - no window borders and no problems with mouse. https://i.imgur.com/dD2hShN.png It is a problem with long documents when it is not convenient to use mouse wheel and scrollbar must be used. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 404997] window changes size when crop option is used
https://bugs.kde.org/show_bug.cgi?id=404997 apache changed: What|Removed |Added CC||sabayo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.