[plasma-systemmonitor] [Bug 470730] Processes wrongly sorted by network speed
https://bugs.kde.org/show_bug.cgi?id=470730 Aroun changed: What|Removed |Added CC||k...@b-vo.fr --- Comment #4 from Aroun --- I'm willing to offer $25 for this to be fixed -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 455014] Add option to change scroll speed
https://bugs.kde.org/show_bug.cgi?id=455014 Aroun changed: What|Removed |Added CC||k...@b-vo.fr --- Comment #3 from Aroun --- I vote for this to be resolved. Scroll speed in okular is ok now. Plus, under mouse setting page in plasma 6 wayland has a scroll speed setting -- You are receiving this mail because: You are watching all bug changes.
[Merkuro] [Bug 482281] New: Increase readability / set text colour / option for text in black and white
https://bugs.kde.org/show_bug.cgi?id=482281 Bug ID: 482281 Summary: Increase readability / set text colour / option for text in black and white Classification: Applications Product: Merkuro Version: 24.02.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: claudio.cam...@kde.org Reporter: k...@b-vo.fr CC: c...@carlschwan.eu Target Milestone: --- Created attachment 166339 --> https://bugs.kde.org/attachment.cgi?id=166339=edit Screenshot with #003600 as an example SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Depending on the color of the agenda, it may be very difficult to read the text of the events. Even the screenshots 2,3, and 5 show this issue https://apps.kde.org/merkuro.calendar/ For example, with #003600 and #008000. The first one is very hard to read. The second one is hard to read and in opinion not very nice looking text. In attachment, one screenshot with #003600 as an example. In Evolution, the text defaults to either black or white depending on the color of the agenda and I much prefer that look. Would it be possible to improve the readability by setting the text to white or black either by default, individually, or as a global option? SOFTWARE/OS VERSIONS Linux/KDE Plasma: KaOS 2024 (available in About System) KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 477402] New: FR: press space to play/pause video
https://bugs.kde.org/show_bug.cgi?id=477402 Bug ID: 477402 Summary: FR: press space to play/pause video Classification: Applications Product: gwenview Version: 23.08.2 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: k...@b-vo.fr Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Open a video in Gwenview 2. Press space OBSERVED RESULT Nothing happens EXPECTED RESULT The video plays/stops SOFTWARE/OS VERSIONS Linux/KDE Plasma: Tuxedo OS 2 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470793] systemsettings fails to open silently
https://bugs.kde.org/show_bug.cgi?id=470793 --- Comment #3 from Aroun --- (In reply to Nate Graham from comment #1) > When this happens, if you run `ps -ef | grep -i systemsettings`, does it > show that System Settings was already open (and presumably hung in the > background)? Ok that might be the case. It seems the situation didn't come again for now. I will check if it is hanging in the background when it happens and then I guess killing it is a workaround to be able to open it again. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470793] New: systemsettings fails to open silently
https://bugs.kde.org/show_bug.cgi?id=470793 Bug ID: 470793 Summary: systemsettings fails to open silently Classification: Applications Product: systemsettings Version: 5.27.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: k...@b-vo.fr Target Milestone: --- SUMMARY This bug does not happen usually, but when it starts happening, it happens consistently until I reboot the system. systemsettings does not open and exits with code 0. STEPS TO REPRODUCE Something that I could not identify might lead to this situation. Right now I changed the color scheme in appearance settings and then it started 1. `systemsettings`: nothing happens 2. `echo $?` gives 0 OBSERVED RESULT systemsettings does not open EXPECTED RESULT systemsettings opens SOFTWARE/OS VERSIONS Linux/KDE Plasma: Tuxedo OS 2 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 470120] FR: stop/pause playback after current track
https://bugs.kde.org/show_bug.cgi?id=470120 --- Comment #2 from Aroun --- The use case is that I am playing an album or a playlist in Elisa. Then I have to go somewhere. I want to pause the music, but not in the middle of the track. I want the track to finish before leaving. Then, when I come back, I want to resume the music from the beginning of the very next track. It can be useful for audiobooks as well. "Stop after current track" can mean "stop after current chapter". And be able to resume from next chapter is just a nice feature imo. Workarounds are: wait for the track to finish and hopefully stop at the right time, or remove the rest of the playlist and manually add it later. Amarok had this, see https://docs.kde.org/trunk5/en/amarok/amarok/references.html and https://docs.kde.org/trunk5/en/amarok/amarok/amarok_amarokmenu2-4.png Guayadeque, strawberry, and probably other players also have this. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 470120] New: FR: stop/pause playback after current track
https://bugs.kde.org/show_bug.cgi?id=470120 Bug ID: 470120 Summary: FR: stop/pause playback after current track Classification: Applications Product: Elisa Version: 23.04.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: k...@b-vo.fr Target Milestone: --- SUMMARY Feature request: stop/pause playback after current track I would like to pause the playback when the current track ends. Then I would like to be able to resume to the next track. I think Amarok had this. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 417284] Support for the "just play literally any music, and keep going until i say stop" use case
https://bugs.kde.org/show_bug.cgi?id=417284 Aroun changed: What|Removed |Added CC||k...@b-vo.fr -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 450345] Discover Fails to Install System Updates
https://bugs.kde.org/show_bug.cgi?id=450345 Aroun changed: What|Removed |Added CC||k...@b-vo.fr -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 444201] Restart needed to update, and automatic updates not working
https://bugs.kde.org/show_bug.cgi?id=444201 Aroun changed: What|Removed |Added CC||k...@b-vo.fr -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 447245] Auto updates do not work
https://bugs.kde.org/show_bug.cgi?id=447245 Aroun changed: What|Removed |Added CC||k...@b-vo.fr -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 445652] /var/lib/PackageKit/offline-update-action file not deleted automatically, causing Discover to always suggest a reboot
https://bugs.kde.org/show_bug.cgi?id=445652 Aroun changed: What|Removed |Added CC||k...@b-vo.fr -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407667] Clicking on an expired notification in the history should launch or focus the app that sent it
https://bugs.kde.org/show_bug.cgi?id=407667 --- Comment #8 from Aroun --- Can we not vote for this? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 468915] New: Battery fully charged
https://bugs.kde.org/show_bug.cgi?id=468915 Bug ID: 468915 Summary: Battery fully charged Classification: Plasma Product: Powerdevil Version: 5.27.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: k...@b-vo.fr CC: m...@ratijas.tk Target Milestone: --- Created attachment 158391 --> https://bugs.kde.org/attachment.cgi?id=158391=edit Screenshot SUMMARY My laptop battery is sometimes shown as "fully charged" when it is only 10% of the target. My target is 81% but it stops at 8%. If I set the target to 92%, it will charge to 9% and then stop. If I set 100, then it will charge completely. There seem to be a *10 issue somewhere. ``` cat /sys/class/power_supply/BAT*/charge_control_end_threshold 81 ``` I don't always get this behavior, but I couldn't identify the exact conditions leading to this. STEPS TO REPRODUCE 1. Set charging limit to 81% 2. Use laptop for few days (not sure exactly what leads to this) 3. Battery will stop charging at anything above 8% OBSERVED RESULT Battery stops charging at value 10 times less than the target EXPECTED RESULT Battery stops charging at target value SOFTWARE/OS VERSIONS Linux/KDE Plasma: NixOS 23.05 (available in About System) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468261] New: [Colors:Header][Inactive] section missing in KColorSchemeEditor
https://bugs.kde.org/show_bug.cgi?id=468261 Bug ID: 468261 Summary: [Colors:Header][Inactive] section missing in KColorSchemeEditor Classification: Applications Product: systemsettings Version: 5.27.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_colors Assignee: plasma-b...@kde.org Reporter: k...@b-vo.fr CC: noaha...@gmail.com, tantalising...@gmail.com, uhh...@gmail.com Target Milestone: --- Created attachment 157938 --> https://bugs.kde.org/attachment.cgi?id=157938=edit KColorSchemeEditor screenshot SUMMARY It is currently not possible to change the colors of hte [Colors:Header][Inactive] section in KColorSchemeEditor. STEPS TO REPRODUCE 1. Edit a color scheme 2. Pick color set OBSERVED RESULT Header section is available but not the Header[Inactive] EXPECTED RESULT Add Header (inactive) section SOFTWARE/OS VERSIONS Linux/KDE Plasma: NixOS unstable 23.05 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 468070] New: sddm-theme: showlogo=shown has no effect
https://bugs.kde.org/show_bug.cgi?id=468070 Bug ID: 468070 Summary: sddm-theme: showlogo=shown has no effect Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: k...@b-vo.fr Target Milestone: --- SUMMARY I use the breeze sddm theme. I created a file theme.conf.user, in which I set a different background image. I also try to add a logo with `showlogo=shown`, and tried with default logo as well as changing the logo to a custom one. I cannot see the logo in sddm. STEPS TO REPRODUCE 1. Create `theme.conf.user` for sddm breeze theme 2. Create a `[General]` category 3. set `showlogo=shown` OBSERVED RESULT No visible difference in sddm EXPECTED RESULT The logo is shown somewhere SOFTWARE/OS VERSIONS Linux/KDE Plasma: NixOS unstable 23.05 KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 365787] Ability to modify user's groups via GUI
https://bugs.kde.org/show_bug.cgi?id=365787 Aroun changed: What|Removed |Added CC||k...@b-vo.fr -- You are receiving this mail because: You are watching all bug changes.
[kuser] [Bug 376157] kf5 kuser
https://bugs.kde.org/show_bug.cgi?id=376157 Aroun changed: What|Removed |Added CC||k...@b-vo.fr -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467696] `plasmashell -v` segmentation fault (core dumped)
https://bugs.kde.org/show_bug.cgi?id=467696
--- Comment #10 from Aroun ---
(In reply to Fushan Wen from comment #9)
> Can you run `QDBUS_DEBUG=1 plasmashell -v` and post the output here?
[:~] % QDBUS_DEBUG=1 plasmashell -v
QDBusConnectionPrivate(0x7efd38001c00) : connected successfully
QDBusConnectionPrivate(0x7efd38001c00) got message (signal):
QDBusMessage(type=Signal, service="org.freedesktop.DBus",
path="/org/freedesktop/DBus", interface="org.freedesktop.DBus",
member="NameAcquired", signature="s", contents=(":1.524") )
QDBusConnectionPrivate(0x7efd38001c00) delivery is suspended
QDBusConnectionPrivate(0x7efd38001c00) sending message:
QDBusMessage(type=MethodCall, service="org.freedesktop.portal.Desktop",
path="/org/freedesktop/portal/desktop",
interface="org.freedesktop.DBus.Properties", member="Get", signature="",
contents=("org.freedesktop.portal.Screenshot", "version") )
QDBusConnectionPrivate(0x7efd38001c00) got message reply:
QDBusMessage(type=MethodReturn, service=":1.4", signature="v",
contents=([Variant(uint): 2]) )
QDBusConnectionPrivate(0x7efd38001c00) Adding rule:
"type='signal',path='/plasmashellrc',interface='org.kde.kconfig.notify',member='ConfigChanged'"
QDBusConnectionPrivate(0x7efd38001c00) Adding rule:
"type='signal',path='/kdeglobals',interface='org.kde.kconfig.notify',member='ConfigChanged'"
QDBusConnectionPrivate(0x7efd38001c00) Adding rule:
"type='signal',path='/BreezeStyle',interface='org.kde.Breeze.Style',member='reparseConfiguration'"
QDBusConnectionPrivate(0x7efd38001c00) Adding rule:
"type='signal',path='/BreezeDecoration',interface='org.kde.Breeze.Style',member='reparseConfiguration'"
QDBusConnectionPrivate(0x7efd38001c00) Adding rule:
"type='signal',path='/KGlobalSettings',interface='org.kde.KGlobalSettings',member='notifyChange'"
QDBusConnectionPrivate(0x7efd38001c00) Adding rule:
"type='signal',path='/KWin',interface='org.kde.KWin',member='reloadConfig'"
plasmashell 5.27.3
QDBusConnectionPrivate(0x7efd38001c00) Disconnected
zsh: segmentation fault (core dumped) QDBUS_DEBUG=1 plasmashell -v
[:~] 139 %
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 467696] `plasmashell -v` segmentation fault (core dumped)
https://bugs.kde.org/show_bug.cgi?id=467696 --- Comment #7 from Aroun --- (In reply to David Redondo from comment #5) > Indeed I would not suspect anything kde related at first glance, please > report to qt @David Redondo Please check the reply from Qt https://bugreports.qt.io/browse/QTBUG-112258?focusedCommentId=714487=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-714487. Any idea how to move forward? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467696] `plasmashell -v` segmentation fault (core dumped)
https://bugs.kde.org/show_bug.cgi?id=467696 Aroun changed: What|Removed |Added Resolution|UPSTREAM|BACKTRACE --- Comment #6 from Aroun --- (In reply to David Redondo from comment #5) > Indeed I would not suspect anything kde related at first glance, please > report to qt Reported at https://bugreports.qt.io/browse/QTBUG-112258 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467696] `plasmashell -v` segmentation fault (core dumped)
https://bugs.kde.org/show_bug.cgi?id=467696 Aroun changed: What|Removed |Added Resolution|BACKTRACE |--- Status|NEEDSINFO |REOPENED Ever confirmed|0 |1 --- Comment #4 from Aroun --- (In reply to David Redondo from comment #3) > Without the relevant symbols this looks more like an issue in Qt to me, but > without them I can't do anything here really I finally managed to build plasma-workspace with Qt debugging symbols. Please see the backtrace: ``` Thread 2 "QDBusConnection" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x70a3c640 (LWP 470584)] 0x7524b5fa in QObject::disconnect (sender=0x591fa0, signal=signal@entry=0x0, receiver=receiver@entry=0x7fffec001c00, method=method@entry=0x0) at kernel/qobject.cpp:3141 3141kernel/qobject.cpp: No such file or directory. (gdb) bt #0 0x7524b5fa in QObject::disconnect (sender=0x591fa0, signal=signal@entry=0x0, receiver=receiver@entry=0x7fffec001c00, method=method@entry=0x0) at kernel/qobject.cpp:3141 #1 0x75cc4f40 in QObject::disconnect (member=0x0, receiver=0x7fffec001c00, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:359 #2 QDBusConnectionPrivate::closeConnection (this=this@entry=0x7fffec001c00) at qdbusintegrator.cpp:1162 #3 0x75cb9f40 in QDBusConnectionManager::run ( this=0x75d24060 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:189 #4 0x750b8814 in QThreadPrivate::start ( arg=0x75d24060 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:330 #5 0x74888e86 in start_thread (arg=) at pthread_create.c:442 #6 0x7490fd30 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 ``` -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467696] `plasmashell -v` segmentation fault (core dumped)
https://bugs.kde.org/show_bug.cgi?id=467696 Aroun changed: What|Removed |Added Version|5.26.5 |5.27.3 --- Comment #2 from Aroun --- Thank you @ Bug Janitor Service I updated my system to NixOS unstable and the crash still happens. I updated the bug description accordingly. SOFTWARE/OS VERSIONS Linux/KDE Plasma: NixOS unstable KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467696] `plasmashell -v` segmentation fault (core dumped)
https://bugs.kde.org/show_bug.cgi?id=467696 Aroun changed: What|Removed |Added CC||k...@b-vo.fr -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467696] New: `plasmashell -v` segmentation fault (core dumped)
https://bugs.kde.org/show_bug.cgi?id=467696 Bug ID: 467696 Summary: `plasmashell -v` segmentation fault (core dumped) Classification: Plasma Product: plasmashell Version: 5.26.5 Platform: NixOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: k...@b-vo.fr Target Milestone: 1.0 SUMMARY On NixOS 22.11, and also on unstable (plasma 5.27.3), executing `plasmashell -v` outputs the name of the program and the version, but then segfaults. As a comparison, executing `kbroadcastnotification -v`, gives a similar output but does not segfault. Please see the issue reported on the nix repo https://github.com/NixOS/nixpkgs/issues/220168#issuecomment-1475003453 The segfault seem to be the cause for an issue on latte-dock https://github.com/NixOS/nixpkgs/issues/212828 STEPS TO REPRODUCE If you are on NixOS: 1. Open konsole 2. `plasmashell -v` will segfault If you don't have NixOS, a quick way to reproduce is: 1. Download the official NixOS virtualbox ova from https://nixos.org/download.html#nixos-virtualbox 2. Import it in VirtualBox 3. Start the vm 4. Open konsole 5. `plasmashell -v` will segfault OBSERVED RESULT [:~] % plasmashell -v plasmashell 5.26.5 zsh: segmentation fault (core dumped) plasmashell -v EXPECTED RESULT No segfault SOFTWARE/OS VERSIONS Linux/KDE Plasma: NixOS 22.11 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION This is the backtrace that I could produce. I am trying hard to get the debugging symbols working but it seems they are not loading. ``` Thread 2 "QDBusConnection" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7076c640 (LWP 43533)] 0x753bdc6c in QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () from /nix/store/mcg2zb0kvb8vqlipmnyc0yyklmasg202-qtbase-5.15.7/lib/libQt5Core.so.5 (gdb) bt #0 0x753bdc6c in QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () from /nix/store/mcg2zb0kvb8vqlipmnyc0yyklmasg202-qtbase-5.15.7/lib/libQt5Core.so.5 #1 0x75d14608 in ?? () from /nix/store/mcg2zb0kvb8vqlipmnyc0yyklmasg202-qtbase-5.15.7/lib/libQt5DBus.so.5 #2 0x75d06568 in ?? () from /nix/store/mcg2zb0kvb8vqlipmnyc0yyklmasg202-qtbase-5.15.7/lib/libQt5DBus.so.5 #3 0x75199e41 in ?? () from /nix/store/mcg2zb0kvb8vqlipmnyc0yyklmasg202-qtbase-5.15.7/lib/libQt5Core.so.5 #4 0x74c33e86 in start_thread (arg=) at pthread_create.c:442 #5 0x74cbad70 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 ``` This is the relevant `dbus-monitor` output: ``` method call time=1679500202.855109 sender=:1.214 -> destination=org.freedesktop.DBus serial=1 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=Hello method return time=1679500202.855125 sender=org.freedesktop.DBus -> destination=:1.214 serial=1 reply_serial=1 string ":1.214" signal time=1679500202.855132 sender=org.freedesktop.DBus -> destination=(null destination) serial=185 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged string ":1.214" string "" string ":1.214" signal time=1679500202.855154 sender=org.freedesktop.DBus -> destination=:1.214 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired string ":1.214" method call time=1679500202.855475 sender=:1.214 -> destination=org.freedesktop.portal.Desktop serial=2 path=/org/freedesktop/portal/desktop; interface=org.freedesktop.DBus.Properties; member=Get string "org.freedesktop.portal.Screenshot" string "version" method return time=1679500202.855735 sender=:1.4 -> destination=:1.214 serial=362 reply_serial=2 variant uint32 2 method call time=1679500202.995686 sender=:1.214 -> destination=org.freedesktop.DBus serial=3 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch string "type='signal',path='/plasmashellrc',interface='org.kde.kconfig.notify',member='ConfigChanged'" method call time=1679500202.995812 sender=:1.214 -> destination=org.freedesktop.DBus serial=4 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch string "type='signal',path='/kdeglobals',interface='org.kde.kconfig.notify',member='ConfigChanged'" method call time=1679500202.996948 sender=:1.214 -> destination=org.freedesktop.DBus serial=5 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch string "type='signal',path='/BreezeStyle',interface='org.kde.Breeze.Style',member='reparseConfiguration'" method call time=1679500202.996996 sender=:1.214 -> destination=org.freedesktop.DBus serial=6 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch string
[Discover] [Bug 464713] New: FR: grid view in Discover
https://bugs.kde.org/show_bug.cgi?id=464713 Bug ID: 464713 Summary: FR: grid view in Discover Classification: Applications Product: Discover Version: 5.25.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: k...@b-vo.fr CC: aleix...@kde.org Target Milestone: --- Created attachment 155541 --> https://bugs.kde.org/attachment.cgi?id=155541=edit how a grid view can help SUMMARY A grid view would allow seeing more results at once, and find quickly what we are looking for. Please see attached a comparison with another software center which has a grid view and uses screen space much better imo. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.10 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 -- You are receiving this mail because: You are watching all bug changes.
