[plasmashell] [Bug 483805] Reconsider using power profile icons when not using Balanced mode and plugged in but not fully charged - Also add options to enable showing ONLY battery icon and/or percenta

2024-03-25 Thread Logan Turner
https://bugs.kde.org/show_bug.cgi?id=483805

Logan Turner  changed:

   What|Removed |Added

   Version Fixed In|N/A - Not a proper fix  |6.1 (supposedly?)

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 483805] Reconsider using power profile icons when not using Balanced mode and plugged in but not fully charged - Also add options to enable showing ONLY battery icon and/or percenta

2024-03-25 Thread Logan Turner
https://bugs.kde.org/show_bug.cgi?id=483805

--- Comment #10 from Logan Turner  ---
(In reply to Natalie Clarius from comment #9)
> https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3601
> (already approved a while ago but forgotten to actually merge - this is done
> now) solves both problems: The generic battery icon is replaced by a more
> informative power mode icon if applicable, but the charge level is always
> shown (now on top of no matter which icon) if so configured.

Would prefer to have only the graphical battery icon as I explained, admittedly
rudely myself, in the other thread. It's simply a matter of personal
preference, nothing more. I don't have time to keep arguing about this or
debating the practicality of it. If more people vote to have this option added
then that's fine.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 483805] Reconsider using power profile icons when not using Balanced mode and plugged in but not fully charged - Also add options to enable showing ONLY battery icon and/or percenta

2024-03-25 Thread Logan Turner
https://bugs.kde.org/show_bug.cgi?id=483805

Logan Turner  changed:

   What|Removed |Added

Summary|Reconsider using power  |Reconsider using power
   |profile icons when not  |profile icons when not
   |using Balanced mode and |using Balanced mode and
   |plugged in but not fully|plugged in but not fully
   |charged - Also add options  |charged - Also add options
   |to enable showing ONLY  |to enable showing ONLY
   |battery icon|battery icon and/or
   ||percentage

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 483805] Reconsider using power profile icons when not using Balanced mode and plugged in but not fully charged - Also add options to enable showing ONLY battery icon

2024-03-25 Thread Logan Turner
https://bugs.kde.org/show_bug.cgi?id=483805

Logan Turner  changed:

   What|Removed |Added

Summary|Reconsider using power  |Reconsider using power
   |profile icons when not  |profile icons when not
   |using Balanced mode and |using Balanced mode and
   |plugged in but not fully|plugged in but not fully
   |charged |charged - Also add options
   ||to enable showing ONLY
   ||battery icon

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 483805] Reconsider using power profile icons when not using Balanced mode and plugged in but not fully charged

2024-03-25 Thread Logan Turner
https://bugs.kde.org/show_bug.cgi?id=483805

Logan Turner  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Ever confirmed|0   |1
 CC|natalie_clar...@yahoo.de|
 Resolution|FIXED   |---
   Version Fixed In|6.1 |N/A - Not a proper fix

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 471369] Change battery icon based on the current power profile

2024-03-25 Thread Logan Turner
https://bugs.kde.org/show_bug.cgi?id=471369

--- Comment #11 from Logan Turner  ---
I don't know how much clearer I can make this: I've reiterated multiple times.

> What value does the battery picture provide over it? How does seeing the 
> charge level percentage not solve your problem which is to "report the 
> current percentage"?

That is not what we want. I've already explained my reasoning for preferring
always being able to see a graphical indicator rather than a text one. For
developers, perhaps this is the preferred readout but not all of us are
developers. However, to avoid this going even more downhill than it already has
let's move past this.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 471369] Change battery icon based on the current power profile

2024-03-25 Thread Logan Turner
https://bugs.kde.org/show_bug.cgi?id=471369

Logan Turner  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED
   Assignee|natalie_clar...@yahoo.de|plasma-b...@kde.org

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 471369] Change battery icon based on the current power profile

2024-03-25 Thread Logan Turner
https://bugs.kde.org/show_bug.cgi?id=471369

--- Comment #9 from Logan Turner  ---
There is no need for this rude attitude. Some users like myself simply prefer
having a graphical indicator for battery, and taking it away in favour of a
static icon is just stupid, to be completely honest. I've already offered
alternate solutions, that is users who dislike the new change can disable
seeing these new static icons. Some may prefer having a text readout instead,
but again, that is an option users can make. Isn't the whole point of KDE to be
flexible and customisable to everyone's needs?

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 471369] Change battery icon based on the current power profile

2024-03-25 Thread Logan Turner
https://bugs.kde.org/show_bug.cgi?id=471369

--- Comment #7 from Logan Turner  ---
(In reply to Logan Turner from comment #6)
> That is not the point of the request. We don't want to see these leaf or
> lightning bolt symbols at all. Showing the percentage is a highly convoluted
> and round-about way of "fixing" this issue, and also ignores users'
> preferences if they choose to normally disable the percentage readout.

What we are asking for is to not see these two leaf/lightning symbols at all,
just show the battery indicator. The same behaviour as was used on Plasma 5.
Make these extra, static symbols a toggle option that users can enable/disable.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 471369] Change battery icon based on the current power profile

2024-03-25 Thread Logan Turner
https://bugs.kde.org/show_bug.cgi?id=471369

Logan Turner  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|FIXED   |---

--- Comment #6 from Logan Turner  ---
That is not the point of the request. We don't want to see these leaf or
lightning bolt symbols at all. Showing the percentage is a highly convoluted
and round-about way of "fixing" this issue, and also ignores users' preferences
if they choose to normally disable the percentage readout.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 483805] Reconsider using power profile icons when not using Balanced mode and plugged in but not fully charged

2024-03-24 Thread Logan Turner
https://bugs.kde.org/show_bug.cgi?id=483805

--- Comment #8 from Logan Turner  ---
I posted on that other "bug report" that perhaps it should be reconsidered, and
to make this feature optional. As it stands it's simply a matter of preference,
some users want this feature and others don't.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 471369] Change battery icon based on the current power profile

2024-03-24 Thread Logan Turner
https://bugs.kde.org/show_bug.cgi?id=471369

Logan Turner  changed:

   What|Removed |Added

 CC||loganturner...@gmail.com

--- Comment #4 from Logan Turner  ---
I personally feel like this should be an optional feature instead of having it
forced on users. Not everyone likes this change:
https://bugs.kde.org/show_bug.cgi?id=483805

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 483805] Battery icon does not show charge rate when changing power profiles

2024-03-23 Thread Logan Turner
https://bugs.kde.org/show_bug.cgi?id=483805

Logan Turner  changed:

   What|Removed |Added

 Status|CONFIRMED   |REPORTED
 Ever confirmed|1   |0

--- Comment #4 from Logan Turner  ---
(In reply to Natalie Clarius from comment #3)
> Yeah, we had a discussion about this when we introduced the change. The
> reasoning was that when you're not running on battery, there is not all that
> much need to know how much you have left, so seeing the active power profile
> would be more useful information in this case. It is a "battery and power"
> applet and not just a battery applet after all, so it's not like showing
> power state information "defeats the purpose". But I am willing to
> reconsider the priorities if enough people don't like this change. 
> Ideally we would show both pieces of information, but this is hard to
> achieve on such small space.  
> Or we introduce a "Always show battery charge level" option similarly to the
> "Show percentage" option.

I agree with a "Always show battery charge level" option. The performance
toggle could be a seperate applet which by default is hidden in the system
tray, and only appears when the user adjusts it - perhaps clicking on said
applet's icon could cycle through the different performance options. Let's be
real here though; no one is checking their performance settings that often to
have those icons replace the charge indicator, apart from gamers. I personally
think the toggle or seperate indicator is a better idea.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 483805] New: Battery icon does not show charge rate when changing power profiles

2024-03-16 Thread Logan Turner
https://bugs.kde.org/show_bug.cgi?id=483805

Bug ID: 483805
   Summary: Battery icon does not show charge rate when changing
power profiles
Classification: Plasma
   Product: plasmashell
   Version: 6.0.2
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Battery Monitor
  Assignee: plasma-b...@kde.org
  Reporter: loganturner...@gmail.com
CC: k...@privat.broulik.de, m...@ratijas.tk,
natalie_clar...@yahoo.de
  Target Milestone: 1.0

Created attachment 167357
  --> https://bugs.kde.org/attachment.cgi?id=167357=edit
Battery monitor showing a useless, unhelpful lightning bolt symbol

SUMMARY
The new battery plasmoid is really terrible. When changing power profiles
whilst connected to power, it becomes entirely useless and doesn't report the
current percentage, just a leaf or lightning bolt symbol. This is a terrible UI
design and defeats the purpose of even having the battery icon in the first
place.

STEPS TO REPRODUCE
1. Click on battery icon
2. Set performance profile to "Power Save" or "Performance"
3. Observe system tray icon. It no longer reports the current charge level.

OBSERVED RESULT
Battery icon is replaced by a static, non-changing Lightning bolt or Leaf
symbol

EXPECTED RESULT
Battery icon should always show the current charge level. Otherwise it defeats
the purpose of having a battery icon at all. Make this feature a toggle option
in the plasmoid's settings or perhaps have this feature as a separate system
tray icon that only appears when needed..

SOFTWARE/OS VERSIONS
Arch Linux
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kglobalaccel] [Bug 476568] Play/Pause, Previous or Next Track buttons don't work

2023-11-09 Thread Logan Turner
https://bugs.kde.org/show_bug.cgi?id=476568

--- Comment #2 from Logan Turner  ---
(In reply to Nate Graham from comment #1)
> Do you by any chance have multiple Audio Volume widgets, or multiple System
> Trays?

No. This shouldn't be affected by volume controls as media controls are a
seperate issue, and the settings for them have since been integrated into the
System Settings app.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kglobalaccel] [Bug 403636] Media Pause button doesn't work properly

2023-11-04 Thread Logan Turner
https://bugs.kde.org/show_bug.cgi?id=403636

Logan Turner  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kglobalaccel] [Bug 476568] Play/Pause, Previous or Next Track buttons don't work

2023-11-04 Thread Logan Turner
https://bugs.kde.org/show_bug.cgi?id=476568

Logan Turner  changed:

   What|Removed |Added

Version|unspecified |5.111.0
   Assignee|unassigned-b...@kde.org |kdelibs-b...@kde.org
  Component|general |general
Product|kde |frameworks-kglobalaccel

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 476568] New: Play/Pause, Previous or Next Track buttons don't work

2023-11-04 Thread Logan Turner
https://bugs.kde.org/show_bug.cgi?id=476568

Bug ID: 476568
   Summary: Play/Pause, Previous or Next Track buttons don't work
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: loganturner...@gmail.com
  Target Milestone: ---

Created attachment 162873
  --> https://bugs.kde.org/attachment.cgi?id=162873=edit
The screenshot here shows multiple entries for the same buttons.

The media keys bug (https://bugs.kde.org/show_bug.cgi?id=403636) has seemingly
reappeared in the latest KDE Plasma release. Upon login, media keys are
detected and funtion normally. However, after closing the app and reopening it
or another media player, the keys stop responding. I have tested this with both
my Keychron K2 V2 keyboard and JBL T660NC headphones. For some reason, there
are multiple entries for playing and pausing media. Changing these shortcuts
does not affect the bug as it persists regardless. These keys were fully
functional in the previous version.

System info:
OS: Arch Linux
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.111.0
Locale: en_NZ.UTF-8
Kernel: 6.5.8-zen1-1-zen
CPU: Intel Core i5-1135G7 (4C 8T)
GPU: Intel Iris Xe (80 exe. units)
Memory: 16GB 3200MHz DDR4 SODIMM (2x 8GB)
System: HP ProBook 430 G8 (567F3PA)

STEPS TO REPRODUCE
1. Open media app and play media
2. Press the Play/Pause, Previous or Next Track buttons
3. Check if the media player reacts. Retry using the software UI.

OBSERVED RESULT
Media playback can be controlled using the software GUI, but not using the
media keys (I have checked that FN lock is disabled, and the other system keys
work as normal. 

EXPECTED RESULT
The physical media keys control media playback properly, as they did in 5.27.8.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kglobalaccel] [Bug 403636] Media Pause button doesn't work properly

2023-10-25 Thread Logan Turner
https://bugs.kde.org/show_bug.cgi?id=403636

Logan Turner  changed:

   What|Removed |Added

 Resolution|FIXED   |---
Version|unspecified |5.111.0
   Platform|Archlinux   |unspecified
 Status|RESOLVED|REOPENED

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kglobalaccel] [Bug 403636] Media Pause button doesn't work properly

2023-10-25 Thread Logan Turner
https://bugs.kde.org/show_bug.cgi?id=403636

Logan Turner  changed:

   What|Removed |Added

 CC||loganturner...@gmail.com

--- Comment #19 from Logan Turner  ---
Created attachment 162554
  --> https://bugs.kde.org/attachment.cgi?id=162554=edit
Screenshot of the KDE System Settings window for shortcuts

The issue has seemingly reappeared in the latest KDE Plasma release. Upon
login, media keys are detected and funtion normally. However, after closing the
app and reopening it or another media player, the keys stop responding. I have
tested this with both my Keychron K2 V2 keyboard and JBL T660NC headphones. For
some reason, there are multiple entries for playing and pausing media. Changing
these shortcuts does not affect the bug as it persists regardless. These keys
were fully functional in the previous version.

System info:
OS: Arch Linux
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.111.0
Locale: en_NZ.UTF-8
Kernel: 6.5.8-zen1-1-zen
CPU: Intel Core i5-1135G7 (4C 8T)
GPU: Intel Iris Xe (80 exe. units)
Memory: 16GB 3200MHz DDR4 SODIMM (2x 8GB)
System: HP ProBook 430 G8 (567F3PA)

-- 
You are receiving this mail because:
You are watching all bug changes.

[lattedock] [Bug 473876] New: Latte Dock (GitHub build) crashing when launching VirtualBox

2023-08-28 Thread Logan Turner
https://bugs.kde.org/show_bug.cgi?id=473876

Bug ID: 473876
   Summary: Latte Dock (GitHub build) crashing when launching
VirtualBox
Classification: Plasma
   Product: lattedock
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: loganturner...@gmail.com
  Target Milestone: ---

Application: latte-dock (0.10.77)

Qt Version: 5.15.10
Frameworks Version: 5.109.0
Operating System: Linux 6.4.12-zen1-1-zen x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.27.7 [KCrashBackend]

-- Information about the crash:
Latte Dock (Built from GitHub via AUR Package "latte-dock-git") crashes when
opening VirtualBox. I am running version 0.10.77 on Arch Linux.

System Specs:
Intel Core i5-1135G7 (4C, 8T)
Intel Iris Xe Graphics (80 Exe. Units)
16GB RAM (2x 8GB 3200MHz DDR4 SODIMM)
500GB Crucial P2 NVMe PCIe M.2 SSD

The crash can be reproduced sometimes.

-- Backtrace:
Application: Latte Dock (latte-dock), signal: Segmentation fault

[KCrash Handler]
#4  0x7f1021d8b904 in QSGTexture::setFiltering(QSGTexture::Filtering) () at
/usr/lib/libQt5Quick.so.5
#5  0x7f1021dbb630 in
QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState
const&, QSGMaterial*, QSGMaterial*) () at /usr/lib/libQt5Quick.so.5
#6  0x7f1021da464e in
QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*)
() at /usr/lib/libQt5Quick.so.5
#7  0x7f1021da7e3e in QSGBatchRenderer::Renderer::renderBatches() () at
/usr/lib/libQt5Quick.so.5
#8  0x7f1021dac8f1 in QSGBatchRenderer::Renderer::render() () at
/usr/lib/libQt5Quick.so.5
#9  0x7f1021d94535 in QSGRenderer::renderScene(QSGBindable const&) () at
/usr/lib/libQt5Quick.so.5
#10 0x7f1021dfbbfc in QSGOpenGLLayer::grab() () at
/usr/lib/libQt5Quick.so.5
#11 0x7f1021df3ae6 in QSGOpenGLLayer::updateTexture() () at
/usr/lib/libQt5Quick.so.5
#12 0x7f1021f4fcc7 in QQuickOpenGLShaderEffectMaterial::updateTextures()
const () at /usr/lib/libQt5Quick.so.5
#13 0x7f1021d94c39 in QSGRenderer::preprocess() () at
/usr/lib/libQt5Quick.so.5
#14 0x7f1021d944fc in QSGRenderer::renderScene(QSGBindable const&) () at
/usr/lib/libQt5Quick.so.5
#15 0x7f1021d949d4 in QSGRenderer::renderScene(unsigned int) () at
/usr/lib/libQt5Quick.so.5
#16 0x7f1021dedf25 in
QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at
/usr/lib/libQt5Quick.so.5
#17 0x7f1021e4c001 in QQuickWindowPrivate::renderSceneGraph(QSize const&,
QSize const&) () at /usr/lib/libQt5Quick.so.5
#18 0x7f1021df8576 in  () at /usr/lib/libQt5Quick.so.5
#19 0x7f1021dfd334 in  () at /usr/lib/libQt5Quick.so.5
#20 0x7f101fef35da in  () at /usr/lib/libQt5Core.so.5
#21 0x7f101f68c9eb in  () at /usr/lib/libc.so.6
#22 0x7f101f710dfc in  () at /usr/lib/libc.so.6

Thread 21 (Thread 0x7f0fb0ca76c0 (LWP 1933) "latte-do:gdrv0"):
#1  0x7f101f68bd40 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x7f1011ec781c in  () at /usr/lib/dri/iris_dri.so
#3  0x7f1011f1472c in  () at /usr/lib/dri/iris_dri.so
#4  0x7f101f68c9eb in  () at /usr/lib/libc.so.6
#5  0x7f101f710dfc in  () at /usr/lib/libc.so.6

Thread 20 (Thread 0x7f0fb14da6c0 (LWP 1932) "latte-:traceq0"):
#1  0x7f101f68bd40 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x7f1011ec781c in  () at /usr/lib/dri/iris_dri.so
#3  0x7f1011f1472c in  () at /usr/lib/dri/iris_dri.so
#4  0x7f101f68c9eb in  () at /usr/lib/libc.so.6
#5  0x7f101f710dfc in  () at /usr/lib/libc.so.6

Thread 19 (Thread 0x7f0fb1f5b6c0 (LWP 1931) "QSGRenderThread"):
#1  0x7f101f68bd40 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x7f101fefb364 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt5Core.so.5
#3  0x7f1021dfd712 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f101fef35da in  () at /usr/lib/libQt5Core.so.5
#5  0x7f101f68c9eb in  () at /usr/lib/libc.so.6
#6  0x7f101f710dfc in  () at /usr/lib/libc.so.6

Thread 18 (Thread 0x7f0fb277c6c0 (LWP 1930) "latte-do:gdrv0"):
#1  0x7f101f68bd40 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x7f1011ec781c in  () at /usr/lib/dri/iris_dri.so
#3  0x7f1011f1472c in  () at /usr/lib/dri/iris_dri.so
#4  0x7f101f68c9eb in  () at /usr/lib/libc.so.6
#5  0x7f101f710dfc in  () at /usr/lib/libc.so.6

Thread 17 (Thread 0x7f0fb2f7d6c0 (LWP 1929) "latte-:traceq0"):
#1  0x7f101f68bd40 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x7f1011ec781c in  () at /usr/lib/dri/iris_dri.so
#3  0x7f1011f1472c in  () at /usr/lib/dri/iris_dri.so
#4  0x7f101f68c9eb in  () at /usr/lib/libc.so.6
#5  0x7f101f710dfc in  () at /usr/lib/libc.so.6

Thread 16 (Thread 0x7f0fb37fe6c0 (LWP 1928) 

[dolphin] [Bug 467838] Weird colouring bug causes selected location in sidebar to become darkened, therefore not following the colour scheme.

2023-03-26 Thread Logan Turner
https://bugs.kde.org/show_bug.cgi?id=467838

Logan Turner  changed:

   What|Removed |Added

URL||https://imgur.com/a/ZOvn8sH

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 467838] New: Weird colouring bug causes selected location in sidebar to become darkened, therefore not following the colour scheme.

2023-03-26 Thread Logan Turner
https://bugs.kde.org/show_bug.cgi?id=467838

Bug ID: 467838
   Summary: Weird colouring bug causes selected location in
sidebar to become darkened, therefore not following
the colour scheme.
Classification: Applications
   Product: dolphin
   Version: 22.12.3
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: bars: location
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: loganturner...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

Created attachment 157618
  --> https://bugs.kde.org/attachment.cgi?id=157618=edit
A video showing the issue.

STEPS TO REPRODUCE
1. Open dolphin
2. Select a location from the sidebar
3. Click on the selected location again. 

OBSERVED RESULT
The selected location does not follow the colour scheme. For a split second, it
shows your accent colour before dimming it. When clicking on the selected
location again however, it goes back to full brightness.

EXPECTED RESULT
The selected location should follow the rest of the system colour scheme, not
showing a darkened version.

SOFTWARE/OS VERSIONS
Arch Linux, KDE Plasma
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 450293] New: Button to apply touchpad settings is grayed out

2022-02-15 Thread Logan Turner
https://bugs.kde.org/show_bug.cgi?id=450293

Bug ID: 450293
   Summary: Button to apply touchpad settings is grayed out
   Product: systemsettings
   Version: 5.24.0
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: kcm_touchpad
  Assignee: plasma-b...@kde.org
  Reporter: loganturner...@gmail.com
  Target Milestone: ---

Created attachment 146757
  --> https://bugs.kde.org/attachment.cgi?id=146757=edit
A recording showing the bug.

SUMMARY
Cannot change touchpad settings as the "Apply" button is greyed out.


STEPS TO REPRODUCE
1. Open System Settings
2. Go to the Touchpad settings
3. Change some options
4. Log out and log back in
5. Repeat 1-3

OBSERVED RESULT
The "Apply" button does not respond and is grayed out, therefore the settings
cannot be applied.

EXPECTED RESULT
The "Apply" button functions as normal.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.24
(available in About System)
KDE Plasma Version: 5.24
KDE Frameworks Version: 5.90
Qt Version: 5.15.3

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kirigami] [Bug 449884] New: Text looks cut off and buggy when scrolling using trackpad or mouse

2022-02-09 Thread Logan Turner
https://bugs.kde.org/show_bug.cgi?id=449884

Bug ID: 449884
   Summary: Text looks cut off and buggy when scrolling using
trackpad or mouse
   Product: frameworks-kirigami
   Version: 5.90.0
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: notm...@gmail.com
  Reporter: loganturner...@gmail.com
  Target Milestone: Not decided

SUMMARY
When scrolling menus in Kirigami apps (System Settings, System Monitor, etc)
the text looks buggy and cut off whilst scrolling. 

Changing the compositor rendering settings does not affect this bug, and it
persists in both Xorg and Wayland sessions. Using different themes also does
not affect this issue, as it persists regardless of QT theme.

Changing trackpad/mouse settings also does not affect this behavior.

STEPS TO REPRODUCE
1. Open a Kirigami app (System Settings for this example).
2. Ensure that the sidebar view is enabled.
3. Scroll up or down slowly in the sidebar or submenus using your trackpad or
mouse.

OBSERVED RESULT
The text will look distorted and choppy whilst scrolling. I have a screen
recording of the issue as well, which is attached.

EXPECTED RESULT
Text looks smooth and does not become choppy or pixelated when scrolling

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.24
KDE Plasma Version: 5.24
KDE Frameworks Version: 5.90
Qt Version: 5.15.3
Kernel: 5.13.0-28-Generic (X64)

ADDITIONAL INFORMATION
CPU: AMD Athlon 3020e
GPU: AMD Radeon Vega 3 (integrated GPU)
Memory: 4GB
Disk: 128GB SSD

-- 
You are receiving this mail because:
You are watching all bug changes.