[NeoChat] [Bug 485844] Editing the same comment twice, gives empty edit box.

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=485844

S. Christian Collins  changed:

   What|Removed |Added

 CC||s_chriscoll...@hotmail.com

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

[neon] [Bug 490704] Cannot mix incompatible Qt library (5.15.13) with this library (5.15.14)

[Christian González]

https://bugs.kde.org/show_bug.cgi?id=490704

Christian González  changed:

   What|Removed |Added

 CC||chgonzal...@gmail.com

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

[Akonadi] [Bug 386985] akonadi CalDav resource not synching with certain servers

[Christian]

https://bugs.kde.org/show_bug.cgi?id=386985

Christian  changed:

   What|Removed |Added

 CC||christian.tall...@gmx.de

--- Comment #65 from Christian  ---
I can confirm that with the radicale caldav server I can only view events on
the server, but new events created in KOrganizer or Merkuro Calendar are not
synced to the server.
I also have set up the Radicale Caldav Calendar resource on Thunderbird and my
iPhone and iPad.
On all devices the events can be viewed and new events can be added.
Only  the events from akonadi are not sent to the server.

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

[plasma-integration] [Bug 487387] Use of unstyled Qt font selector dialogs constitutes a visual and usability regression

[Christian Z.]

https://bugs.kde.org/show_bug.cgi?id=487387

Christian Z.  changed:

   What|Removed |Added

 CC||cdotz...@gmail.com

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

[i18n] [Bug 489872] DE: Missing translation "Log out Now"

[Christian Z.]

https://bugs.kde.org/show_bug.cgi?id=489872

Christian Z.  changed:

   What|Removed |Added

 CC||cdotz...@gmail.com

--- Comment #1 from Christian Z.  ---
Same for the shutdown menu and some entries in the Desktop context menu. Tried
it on KDE neon testing with Plasma 6.1.3

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

[kmail2] [Bug 482568] Links don't convert cursor to a hand, and don't open when clicked

[Christian]

https://bugs.kde.org/show_bug.cgi?id=482568

Christian (Fuchs)  changed:

   What|Removed |Added

 CC||k...@fuchsnet.ch

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

[plasmashell] [Bug 489991] Crash when USB-C with HDMI screen is pulled from SteamDeck

[Christian Heusel]

https://bugs.kde.org/show_bug.cgi?id=489991

--- Comment #1 from Christian Heusel  ---
Created attachment 171509
  --> https://bugs.kde.org/attachment.cgi?id=171509=edit
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.

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

[plasmashell] [Bug 489991] New: Crash when USB-C with HDMI screen is pulled from SteamDeck

[Christian Heusel]

https://bugs.kde.org/show_bug.cgi?id=489991

Bug ID: 489991
   Summary: Crash when USB-C with HDMI screen is pulled from
SteamDeck
Classification: Plasma
   Product: plasmashell
   Version: 6.1.2
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: christ...@heusel.eu
  Target Milestone: 1.0

Application: plasmashell (6.1.2)

Qt Version: 6.7.2
Frameworks Version: 6.3.0
Operating System: Linux 6.9.8-arch1-1 x86_64
Windowing System: Wayland
Distribution: Arch Linux
DrKonqi: 6.1.2 [CoredumpBackend]

-- Information about the crash:
I have tested my external monitor via a USB-C HDMI adapter and have set the
screen setting to "mirror". It all worked well until I pulled out the USB-C
adapter, after which plasma reliably crashes with the attached stack trace.

The crash can be reproduced every time.

-- Backtrace (Reduced):
#5  QtWaylandClient::QWaylandWindow::waylandScreen (this=0x63bd767c5890) at
/usr/src/debug/qt6-wayland/qtwayland/src/client/qwaylandwindow.cpp:956
#6  QtWaylandClient::QWaylandWindow::devicePixelRatio (this=0x63bd767c5890) at
/usr/src/debug/qt6-wayland/qtwayland/src/client/qwaylandwindow.cpp:1521
#7  0x7821883d2f0c in QtWaylandClient::QWaylandEglWindow::updateSurface
(this=0x63bd767c5890, create=true) at
/usr/src/debug/qt6-wayland/qtwayland/src/hardwareintegration/client/wayland-egl/qwaylandeglwindow.cpp:70
#8  0x7821883d3905 in QtWaylandClient::QWaylandGLContext::makeCurrent
(this=this@entry=0x782064002210, surface=) at
/usr/src/debug/qt6-wayland/qtwayland/src/hardwareintegration/client/wayland-egl/qwaylandglcontext.cpp:318
#9  0x78218f0adc28 in QOpenGLContext::makeCurrent (this=0x782064001f60,
surface=0x63bd73fe4d70) at
/usr/src/debug/qt6-base/qtbase/src/gui/kernel/qopenglcontext.cpp:664


Reported using DrKonqi

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

[plasma-pa] [Bug 487658] New naming style is not great when a lot of similar devices are all connected at once

[Christian González]

https://bugs.kde.org/show_bug.cgi?id=487658

Christian González  changed:

   What|Removed |Added

 CC||chgonzal...@gmail.com

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

[konsole] [Bug 372116] Feature Request: Support OSC 52 (copy to clipboard)

[Christian Muehlhaeuser]

https://bugs.kde.org/show_bug.cgi?id=372116

--- Comment #47 from Christian Muehlhaeuser  ---
I am active, but I think we'll first need to reach a consensus whether a
default write-only solution (like this one) is acceptable without any extra
settings or any user interaction.

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

[kwin] [Bug 483698] choppy framerate in X11 after upgrade to Plasma 6

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=483698

S. Christian Collins  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #7 from S. Christian Collins  ---
This issue is now resolved in Plasma 6.1.1. I am now getting smooth desktop
response in Plasma again. Thank you!

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

[plasmashell] [Bug 487904] Stuff using Kirigami InlineMessage and PlaceholderMessage fail to load with error `Cannot assign object of type \"Action\" to property of type \"Action_QMLTYPE_72*\" as the

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=487904

S. Christian Collins  changed:

   What|Removed |Added

 CC||s_chriscoll...@hotmail.com

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

[Plasma Vault] [Bug 485895] Error loading Vaults

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=485895

S. Christian Collins  changed:

   What|Removed |Added

 CC||s_chriscoll...@hotmail.com

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

[Plasma Vault] [Bug 487597] Error loading vaults

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=487597

S. Christian Collins  changed:

   What|Removed |Added

 CC||s_chriscoll...@hotmail.com

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

[kwin] [Bug 489100] New: Regression since effect merge: no reliable keyboard navigation for workspaces

[Christian]

https://bugs.kde.org/show_bug.cgi?id=489100

Bug ID: 489100
   Summary: Regression since effect merge: no reliable keyboard
navigation for workspaces
Classification: Plasma
   Product: kwin
   Version: 6.1.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: effects-overview
  Assignee: kwin-bugs-n...@kde.org
  Reporter: k...@fuchsnet.ch
  Target Milestone: ---

SUMMARY
Since the overview effect is now used both for the desktop grid and the present
windows effect, there are some regressions. Keyboard navigation for navigating
workspaces in the grid is no longer reliable, since depending on how many
windows there are on a workspace and how the effect ordered them, the amount of
arrow presses to navigate to the next / previous / above / below workspace is
random.

STEPS TO REPRODUCE
1. Open the overview effect in the grid mode  (workspaces ordered as a grid)
2. Try to navigate via keyboard navigation

OBSERVED RESULT
Amount of button presses to navigate e.g. two workspaces to the right or one
down and one left is dependant on how many windows there are, how they are
ordered by the effect and which window is considered e.g. below in the effect.

EXPECTED RESULT
Have a reliable way to navigate workspace only, and not windows
(e.g. by either having a separate keyboard shortcut like wasd  to navigate
workspaces, or an option to skip windows in this view)

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

[plasmashell] [Bug 489099] New: Keyboard navigation broken since reorg of switch

[Christian]

https://bugs.kde.org/show_bug.cgi?id=489099

Bug ID: 489099
   Summary: Keyboard navigation broken since reorg of switch
Classification: Plasma
   Product: plasmashell
   Version: 6.1.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Battery Monitor
  Assignee: plasma-b...@kde.org
  Reporter: k...@fuchsnet.ch
CC: k...@privat.broulik.de, m...@ratijas.tk,
natalie_clar...@yahoo.de
  Target Milestone: 1.0

SUMMARY
Since re-ordering the inhibit action from the header into the plasmoid (why?)
keyboard navigation is now broken.
The down arrow works as expected, the up arrow depends on what item the focus
is currently at, but it's wrong.

STEPS TO REPRODUCE
1.  Update to plasma >= 6.1
2.  Open the battery plasmoid
3.  Try to navigate by keyboard

OBSERVED RESULT
Up arrow doesn't work as it's still bound to the old layout

EXPECTED RESULT
Keys work as expected

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

[kwin] [Bug 486850] Regression: Windows of other workspaces not shown when "organize windows in the grid view" is NOT selected

[Christian]

https://bugs.kde.org/show_bug.cgi?id=486850

--- Comment #1 from Christian (Fuchs)  ---
This bug is still present in 6.1 and basically makes the grid unusable, since
you only see windows of one workspace.

Probably this would just need a trigger to show all windows, as the present
windows effect does, which is not triggered if you don't check the "organize
windows in the grid view" option.

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

[i18n] [Bug 488889] Battery warning not translated

[Christian Lampe]

https://bugs.kde.org/show_bug.cgi?id=49

--- Comment #2 from Christian Lampe  ---
(In reply to Nate Graham from comment #1)
> This label has been here for ages, but I did change its text recently, so I
> think it's far likelier that it simply hasn't been re-translated yet.

Then a bunch of labels must have changed in 6.1, because I suddenly encounter
English messages (like e.g. authorizing the creation of a new user account) all
over the place. Let's hope the translation catches up soon.

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

[Powerdevil] [Bug 488889] New: Battery warning not translated

[Christian Lampe]

https://bugs.kde.org/show_bug.cgi?id=49

Bug ID: 49
   Summary: Battery warning not translated
Classification: Plasma
   Product: Powerdevil
   Version: 6.1.0
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: kont...@lampe2020.de
CC: m...@ratijas.tk, natalie_clar...@yahoo.de
  Target Milestone: ---

Created attachment 170749
  --> https://bugs.kde.org/attachment.cgi?id=170749=edit
A screenshot of the notification.

SUMMARY 
The message that comes up when the battery reaches 10% is not translated. 

STEPS TO REPRODUCE 
1. start Neon on a battery-powered computer and set the display language to
Swedish 
2. wait for the battery to reach 10% 
3. see the message 

OBSERVED RESULT 
The message correctly has a Swedish title, but the message itself is in
English. 

EXPECTED RESULT 
The message is in Swedish (the set display language) 

SOFTWARE/OS VERSIONS 
KDE Neon: 6.0 
KDE Plasma Version: 6.1.0 
KDE Frameworks Version: 6.3.0 
Qt Version: 6.7.0 

ADDITIONAL INFORMATION 
I don't know if this only happens when the system is set to Swedish or also
when another language is set.

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

[dolphin] [Bug 479695] In icons view mode, file name moves left during rename

[Christian]

https://bugs.kde.org/show_bug.cgi?id=479695

Christian (Fuchs)  changed:

   What|Removed |Added

 CC||k...@fuchsnet.ch

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

[kwin] [Bug 483698] choppy framerate in X11 after upgrade to Plasma 6

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=483698

--- Comment #4 from S. Christian Collins  ---
(In reply to Zamundaaa from comment #3)
> Please attach the output of
> > glxinfo | grep timer_query

GL_ARB_texture_view, GL_ARB_timer_query, GL_ARB_transform_feedback2, 
GL_EXT_texture_swizzle, GL_EXT_timer_query, GL_EXT_transform_feedback, 
GL_ARB_texture_swizzle, GL_ARB_texture_view, GL_ARB_timer_query, 
GL_EXT_texture_snorm, GL_EXT_texture_swizzle, GL_EXT_timer_query, 
GL_EXT_discard_framebuffer, GL_EXT_disjoint_timer_query,

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

[kwin] [Bug 484323] High CPU load of kwin_x11 when locking or turning off the screen

[Christian Boltz]

https://bugs.kde.org/show_bug.cgi?id=484323

Christian Boltz  changed:

   What|Removed |Added

 CC||kde-b...@cboltz.de

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

[akregator] [Bug 488176] New: New Akregator theme (especially max-width) breaks some usecases - allow custom CSS?

[Christian Boltz]

https://bugs.kde.org/show_bug.cgi?id=488176

Bug ID: 488176
   Summary: New Akregator theme (especially max-width) breaks some
usecases - allow custom CSS?
Classification: Applications
   Product: akregator
   Version: 6.1.0
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: kde-b...@cboltz.de
  Target Milestone: ---

Created attachment 170238
  --> https://bugs.kde.org/attachment.cgi?id=170238=edit
screenshot with some annotations

SUMMARY

The new Akregator theme breaks some usecases, especially by applying a
max-width.

For example, MediaWiki RecentChanges feeds which contain the changes as two
columns get displayed with very narrow columns, and - as a side effect - need
lots of scrolling.

STEPS TO REPRODUCE
1. Add a RecentChanges feed from a MediaWiki installation, for example
https://en.opensuse.org/index.php?title=Special:RecentChanges=atom
2. choose/view an item that has a content change (= not creation of a new page)

OBSERVED RESULT

Very narrow columns with old and new text, which also needs lots of scrolling
(see attached screenshot).

EXPECTED RESULT

Use the full width, so that the columns have a reasonable width, and don't need
too much scrolling.

Well, at least for this usecase ;-) - and I understand that different people
might have different preferences.

Therefore I propose to add a config option where users can select a custom CSS
file, so that they can adjust the layout to their preference.
(Note: Ideally users should also have a way to see the default CSS and/or HTML
template so that they know what to change - but even a pointer to the source
(src/formatter/html/5.2/normalview.html) is better than nothing).

A more boring solution might be to make the max-width configurable - at least
for me it's the only thing I'd like to change in the new theme.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed
KDE Plasma Version: 24.05.0
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.1

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

[plasmashell] [Bug 487987] New: Regression: (X11) Primary Selection no longer appears in history

[Christian]

https://bugs.kde.org/show_bug.cgi?id=487987

Bug ID: 487987
   Summary: Regression: (X11) Primary Selection  no longer appears
in history
Classification: Plasma
   Product: plasmashell
   Version: 6.0.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Clipboard
  Assignee: plasma-b...@kde.org
  Reporter: k...@fuchsnet.ch
  Target Milestone: 1.0

SUMMARY
On my desktop I have plasma 5.27.11, on my notebook I upgraded to 6.0.5. 
The clipboard settings are (visually, in the GUI) the same, but the behaviour
on 6.0.5 changed.

Selecting text  (X11 Primary Selection) appears in the history on 5.*, while it
no longer does on 6.* unless I activate the option to keep the clipboard and
selection in sync, which I do not want.

There is an option, but it only becomes editable if the sync is enabled, and
doesn't allow me to configure it the way 5.* behaves (or I didn't find out how)

Please fix this regression, as managing both the selection and the clipboard
content is an important usecase to me.
I also don't see why this should not be possible option-wise, as in: why this
specific combination can't be configured.

STEPS TO REPRODUCE
1. Update to Plasma 6.*
2.  Use X11 (potentially same in Wayland, didn't test, not sure about selection
there in general)
3. Mark text with mouse

OBSERVED RESULT
Text doesn't appear in clipboard history

EXPECTED RESULT
Text does appear, as it did in 5.*

If you think this is confusing for users, please at least offer an option
(since the GUI seems somewhat prepared to that) to change that behaviour.

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

[ksplash] [Bug 487632] theme config is ignored

[Christian]

https://bugs.kde.org/show_bug.cgi?id=487632

Christian (Fuchs)  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |LATER
 Status|NEEDSINFO   |RESOLVED

--- Comment #2 from Christian (Fuchs)  ---
(In reply to David Redondo from comment #1)
> Any interesting output in  ksplashqml --test ?
> 
> Does your theme have metadata.json? (metadata.desktop is no longer supported)

Thanks for the pointer, I was able to resolve it, but I think ksplash /
systemsettings could prevent that.
The output of ksplashqml --test was empty with no error message, but it just
showed a blank screen, 

fuchs@comfox /usr/share/plasma % ksplashqml
/usr/share/plasma/look-and-feel/org.kde.oxygen/   
^C
fuchs@comfox /usr/share/plasma % ksplashqml 
^C


There was a metadata.json in the top level folder that was probably converted
from the old format, and the new folders have a .desktop suffix while the old
ones didn't, so the id line did not exactly match the folder name.
Thus the theme was shown and selectable in systemsettings, but it did not work.

Maybe a test could be added that checks for the presence of the folder name and
show a warning / error on the command line if it is not there, and potentially
also make the theme not selectable in systemsettings.

In either case, I'd consider this resolved, but it would be nice if such a
check would be added.

Thanks and have a nice $timeofday :)

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

[ksplash] [Bug 487632] New: theme config is ignored

[Christian]

https://bugs.kde.org/show_bug.cgi?id=487632

Bug ID: 487632
   Summary: theme config is ignored
Classification: Plasma
   Product: ksplash
   Version: 6.0.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: k...@fuchsnet.ch
  Target Milestone: ---

SUMMARY
Since Upgrading to plasma 6.* I have the problem that my chosen theme for
ksplash is completely ignored.
I have a theme called org.kde.oxygen (which is indeed an old, ported oxygen
theme) which appears in systemsettings and I can choose it. The config in
~/.config/ksplashrc is correct. Regardless of that, the default breeze theme is
shown, both when I log in, but also when I do press the play button in
systemsettings.

However, if I just blindly copy the contents of
/usr/share/plasma/look-and-feel/org.kde.oxygen/contents/splash/ into
/usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/splash/, my
theme is shown on login, thus the theme itself is not faulty.

STEPS TO REPRODUCE
1.  Have a custom kspash theme, say
/usr/share/plasma/look-and-feel/org.kde.oxygen/contents/splash/
2.  Choose it in systemsettings
3.  Log in 

OBSERVED RESULT
Wrong theme (default breeze) is shown

EXPECTED RESULT
Chosen theme is shown

Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.0
Kernel Version: 6.8.10-300.fc40.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-8265U CPU @ 1.60GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: LENOVO
Product Name: 20NQS30W00
System Version: ThinkPad X390 Yoga

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

[Akonadi] [Bug 485132] DAV resource: invalid response from backend

[Christian]

https://bugs.kde.org/show_bug.cgi?id=485132

Christian (Fuchs)  changed:

   What|Removed |Added

 CC||k...@fuchsnet.ch

--- Comment #5 from Christian (Fuchs)  ---
Potentially the same as https://bugs.kde.org/show_bug.cgi?id=486871, the error
message is indeed not helpful, but I got the same.
And I can confirm that the ressource is working with every other client,
including akonadi < 6.*, so this is not a bug in the ressource, but in akonadi.

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

[neon] [Bug 487452] Missing Icons in Breeze Light and Twilight.

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=487452

S. Christian Collins  changed:

   What|Removed |Added

 CC||s_chriscoll...@hotmail.com

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

[plasmashell] [Bug 487192] plasma crashed after reboot

[Steinhauser Christian]

https://bugs.kde.org/show_bug.cgi?id=487192

--- Comment #1 from Steinhauser Christian  
---
Created attachment 169596
  --> https://bugs.kde.org/attachment.cgi?id=169596=edit
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.

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

[plasmashell] [Bug 487192] New: plasma crashed after reboot

[Steinhauser Christian]

https://bugs.kde.org/show_bug.cgi?id=487192

Bug ID: 487192
   Summary: plasma crashed after  reboot
Classification: Plasma
   Product: plasmashell
   Version: 5.27.10
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: steinhauserchristian1...@gmail.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Application: plasmashell (5.27.10)

Qt Version: 5.15.10
Frameworks Version: 5.115.0
Operating System: Linux 6.7.12-amd64 x86_64
Windowing System: X11
Distribution: SparkyLinux 8 (Seven-Sisters)
DrKonqi: 5.27.10 [CoredumpBackend]

-- Information about the crash:
sudo apt update
sudo apt dist-upgrade --fix-missing
sudo init 6
after login
everything realy slow
than crashed

The reporter is unsure if this crash is reproducible.

-- Backtrace (Reduced):
#3  0x7f38aa27fa2e in QtQml::qmlExecuteDeferred(QObject*) () from
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#4  0x7f38aa749ddd in QQuickTransition::prepare(QList&,
QList&, QQuickTransitionManager*, QObject*) () from
/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7f38aa73f427 in
QQuickTransitionManager::transition(QList const&,
QQuickTransition*, QObject*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7f38a8af984b in QObject::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f38a9962f32 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5


Reported using DrKonqi

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

[policykit-kde-agent-1] [Bug 485407] polkit-kde-agent crashes with nullptr in PolicyKitListener::finishObtainPrivilege() when run in Hyprland

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=485407

--- Comment #21 from S. Christian Collins  ---
(In reply to Sin Jeong-hun from comment #20)
> I think "Hyperland" is not related. I am using Plasma X11 (version 6.0.4),
> and it happens, too. Took me hours to find out this is a bug, because I
> thought it was a problem of polkit rules and tried modifying rules.

Yeah, I experience this bug as described by the OP under KDE neon User Edition
on my two native installs (my two VirtualBox installs are unaffected). I can
only assume it's the same cause, but I guess I'll find out once 6.0.5 is
released.

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

[krdc] [Bug 482950] KRDC RDP Blue screen shows nothing

[Christian Finnberg]

https://bugs.kde.org/show_bug.cgi?id=482950

Christian Finnberg  changed:

   What|Removed |Added

 CC||christ...@finnberg.net

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

[plasmashell] [Bug 487026] New: Use symbolic icons for systray app if present

[Christian]

https://bugs.kde.org/show_bug.cgi?id=487026

Bug ID: 487026
   Summary: Use symbolic icons for systray app if present
Classification: Plasma
   Product: plasmashell
   Version: 6.0.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: XembedSNIProxy
  Assignee: plasma-b...@kde.org
  Reporter: k...@fuchsnet.ch
CC: mate...@gmail.com
  Target Milestone: 1.0

SUMMARY
As per a discussion in the VDG group: 
I propose adding either an option  (or, as per Nate, just a new default) of
using the -symbolic icon for an app, if present.

Usecase: have icon themes / apps that want to support it by shipping a
-symbolic icon to follow our usually monochrome icons in systray.

Logic would basically be: when loading an icon, check if there is a -symbolic
suffixed version of that icon for that size, if yes: use that, if no: use the
requested icon.

Argument against hardcoding it: would override apps explicit wishes.
Argument against an option: it's an option, and it might not always work, thus
give users wrong expectations if not clearly worded  (e.g. should be [ ] use
monochrome icon if available, not [ ] use monochrome icon)

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

[kontact] [Bug 487025] New: kmail systray click is broken in 6.* if opened through kontact instead of kmail

[Christian]

https://bugs.kde.org/show_bug.cgi?id=487025

Bug ID: 487025
   Summary: kmail systray click is broken in 6.* if opened through
kontact instead of kmail
Classification: Applications
   Product: kontact
   Version: 6.0.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: mail
  Assignee: kdepim-b...@kde.org
  Reporter: k...@fuchsnet.ch
  Target Milestone: ---

SUMMARY
Kmail has an option to show a systray icon for unread mails.
Clicking on this icon used to (and is supposed to, I guess, see below) toggle
showing kmail if clicked.
This no longer works in Plasma 6 / with KDEPim 6 if and only if kmail was
started through kontact. It does work when starting kmail directly. It also
occasionally starts working again after closing kontact, opening kmail, closing
kmail, opening kontact.

STEPS TO REPRODUCE
1. Configure kmail to show a systray icon
2. Start kontact
3. Click the icon

OBSERVED RESULT
The kmail (or kontact) window should toggle  (minimize and un-minimize)

EXPECTED RESULT
Nothing happens on click

Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.0
Kernel Version: 6.8.9-300.fc40.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-8265U CPU @ 1.60GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: LENOVO
Product Name: 20NQS30W00
System Version: ThinkPad X390 Yoga

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

[plasmashell] [Bug 483390] Task Manager window previews hide almost immediately when moving from one task to another in almost all panel orientations and movement directions

[Christian]

https://bugs.kde.org/show_bug.cgi?id=483390

Christian (Fuchs)  changed:

   What|Removed |Added

 CC||k...@fuchsnet.ch

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

[plasmashell] [Bug 486921] Days with a sublabel are oddly shifted up in grid view due to height calculation

[Christian]

https://bugs.kde.org/show_bug.cgi?id=486921

--- Comment #1 from Christian (Fuchs)  ---
Somewhat related, and could be looked into as well when changing the layout:
https://bugs.kde.org/show_bug.cgi?id=470014

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

[plasmashell] [Bug 486921] New: Days with a sublabel are oddly shifted up in grid view due to height calculation

[Christian]

https://bugs.kde.org/show_bug.cgi?id=486921

Bug ID: 486921
   Summary: Days with a sublabel are oddly shifted up in grid view
due to height calculation
Classification: Plasma
   Product: plasmashell
   Version: 6.0.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Calendar
  Assignee: plasma-b...@kde.org
  Reporter: k...@fuchsnet.ch
  Target Milestone: 1.0

Created attachment 169398
  --> https://bugs.kde.org/attachment.cgi?id=169398=edit
Screenshot of current behaviour, misaligned (left), next to proposed aligned
behaviour (can be improved)

SUMMARY
Apparently in Plasma 6.* in the digital clock calender popup, days with
holidays now not only show a coloured dot, but also the name of that holiday as
a label.

Unfortunately these then have a different height than all the other items in
the grid, which makes them stick out like a sore spot.

Changing 

contentItem: Item {
// ColumnLayout makes scrolling too slow, so use anchors to position
labels

PlasmaComponents3.ToolTip.delay: Kirigami.Units.toolTipDelay
PlasmaComponents3.ToolTip.text: model.subLabel || ""
PlasmaComponents3.ToolTip.visible: !!model.subLabel &&
(Kirigami.Settings.isMobile ? dayStyle.pressed : dayStyle.hovered)

Kirigami.Heading {
id: label
anchors {
left: parent.left
right: parent.right
top: parent.top
// bottom: subDayLabel.top
bottom: parent.bottom + Kirigami.Units.smallSpacing
}

fixes that, but that is probably an ugly hack that might not work on all DPI /
resolution combinations, thus a more robust calculation would be nice.

STEPS TO REPRODUCE
1.  Have Plasma 6
2.  Have a digital clock
3.  Have the holiday plugin enabled
4. Be in a month with a public holiday of sorts
5. Click on the clock to make the popup pop up

OBSERVED RESULT
Grid is not well aligned, days with holidays stick out despite there being
plenty of space

EXPECTED RESULT
Grid is well aligned

Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.9-300.fc40.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-8265U CPU @ 1.60GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: LENOVO
Product Name: 20NQS30W00
System Version: ThinkPad X390 Yoga

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

[kwin] [Bug 478556] Sometimes the stacking order is out of sync with Xorg

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=478556

S. Christian Collins  changed:

   What|Removed |Added

 CC||s_chriscoll...@hotmail.com

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

[Akonadi] [Bug 486871] New: Can't fetch caldav or carddav from Nextcloud in Fedora 40, driver error

[Christian]

https://bugs.kde.org/show_bug.cgi?id=486871

Bug ID: 486871
   Summary: Can't fetch caldav or carddav from Nextcloud in Fedora
40, driver error
Classification: Frameworks and Libraries
   Product: Akonadi
   Version: 6.0.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: DAV Resource
  Assignee: kdepim-b...@kde.org
  Reporter: k...@fuchsnet.ch
CC: c...@carlschwan.eu
  Target Milestone: ---

SUMMARY
Since re-installing a fresh Fedora 40 after using Fedora 39, I am no longer
able to add my nextcloud calendar or addressbooks in akonadi. The error message
shown in the window is completely useless (driver error, on German, couldn't
get it to show it in English), on the console it's a bit more usefull, 

org.kde.pim.akonadiserver: Handler exception when handling command
FetchCollections on connection akonadi_davgroupware_resource_0 (0x560355340ab0)
: Hierarchical RID does not specify an existing collection
org.kde.pim.davresource: Unable to fetch collections 320 "Ungültige Antwort des
Treibers"

STEPS TO REPRODUCE
1. Install Fedora 40 with akonadi 6.0.2
2.  Try to add a nextcloud ressource, either via the built in Nextcloud setting
in the drop down or by specifying the URLs manually

OBSERVED RESULT
You get the above error


EXPECTED RESULT
It works

The same nextcloud instance works with other software, e.g. a still running KDE
5.* based kontact on my desktop box, davx on Android etc. 

Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.9-300.fc40.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-8265U CPU @ 1.60GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: LENOVO
Product Name: 20NQS30W00
System Version: ThinkPad X390 Yoga

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

[frameworks-baloo] [Bug 486853] Baloo file extractor crashes a dozen times after updating to Plasma / KDE / Frameworks 6

[Christian]

https://bugs.kde.org/show_bug.cgi?id=486853

--- Comment #2 from Christian (Fuchs)  ---
(In reply to tagwerk19 from comment #1)
> (In reply to Christian (Fuchs) from comment #0)
> > #5  0x7fc211b44aac in standardDeclarationForNode(QTextHtmlParserNode
> > const&) () from /lib64/libQt6Gui.so.6
> > #6  0x7fc211b45bc2 in QTextHtmlParser::declarationsForNode(int) const ()
> > from /lib64/libQt6Gui.so.6
> > #7  0x7fc211b46830 in QTextHtmlParser::parseTag() () from
> > /lib64/libQt6Gui.so.6
> > #8  0x7fc211b46df0 in QTextHtmlParser::parse() () from
> > /lib64/libQt6Gui.so.6
> > #9  0x7fc211aeb2ea in
> > QTextHtmlImporter::QTextHtmlImporter(QTextDocument*, QString const&,
> > QTextHtmlImporter::ImportMode, QTextDocument const*) () from
> > /lib64/libQt6Gui.so.6
> > #10 0x7fc211ad3f16 in QTextDocument::setHtml(QString const&) () from
> > /lib64/libQt6Gui.so.6
> > #11 0x7fc20e11fb7f in
> > KFileMetaData::MobiExtractor::extract(KFileMetaData::ExtractionResult*) ()
> > from /usr/lib64/qt6/plugins/kf6/kfilemetadata/kfilemetadata_mobiextractor.so
> It's looking like a "messed up" ebook (a .mobi with embedded HTML?). There's
> also Bug 475730 and, perhaps more usefully, Bug 475975...

Thanks for the links, I'll go subscribe to the latter. In an ideal world
though, a malformed file should not lead to baloo crashing, very visibly to the
end user as it spams the systray with a dozen of Dr. Konqi instances. If there
is malformed content produced by a third party library, there should be the
equivalent of a catch around that so it could fail on that file gracefully (and
potentially mark it to not re-index)

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

[frameworks-baloo] [Bug 486853] New: Baloo file extractor crashes a dozen times after updating to Plasma / KDE / Frameworks 6

[Christian]

https://bugs.kde.org/show_bug.cgi?id=486853

Bug ID: 486853
   Summary: Baloo file extractor crashes a dozen times after
updating to Plasma / KDE / Frameworks 6
Classification: Frameworks and Libraries
   Product: frameworks-baloo
   Version: 6.1.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: Baloo File Daemon
  Assignee: baloo-bugs-n...@kde.org
  Reporter: k...@fuchsnet.ch
  Target Milestone: ---

Application: baloo_file_extractor (6.1.0)

Qt Version: 6.7.0
Frameworks Version: 6.1.0
Operating System: Linux 6.8.8-300.fc40.x86_64 x86_64
Windowing System: X11
Distribution: "Fedora Linux 40 (KDE Plasma)"
DrKonqi: 6.0.4 [CoredumpBackend]

-- Information about the crash:
After re-installing my laptop with Fedora 40 and putting my /home backup back 
(excluding the baloo folder under .local/share and excluding baloo config under
.config, as I epxected that to be problematic) baloo started re-indexing and
crashed a couple of dozen times in a short row.
I hope the backtrace is somewhat helpful in finding the root cause, else feel
free to get back to me if you need further information.

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo-Dateiinfosammler (baloo_file_extractor), signal:
Segmentation fault


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 9643]
[New LWP 9688]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/libexec/kf6/baloo_file_extractor'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7fc2120ab144 in __pthread_kill_implementation () from
/lib64/libc.so.6
[Current thread is 1 (Thread 0x7fc20e151f40 (LWP 9643))]
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x7fc20e151f40 (LWP 9643))]

Thread 2 (Thread 0x7f8206c0 (LWP 9688)):
#0  0x7fc21211d72d in poll () from /lib64/libc.so.6
#1  0x7fc210d7c724 in g_main_context_iterate_unlocked.isra () from
/lib64/libglib-2.0.so.0
#2  0x7fc210d1cb03 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7fc212a7bf83 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt6Core.so.6
#4  0x7fc2127a26b3 in
QEventLoop::exec(QFlags) () from
/lib64/libQt6Core.so.6
#5  0x7fc2128b402f in QThread::exec() () from /lib64/libQt6Core.so.6
#6  0x7fc21256faf1 in QDBusConnectionManager::run() () from
/lib64/libQt6DBus.so.6
#7  0x7fc21294f35c in QThreadPrivate::start(void*) () from
/lib64/libQt6Core.so.6
#8  0x7fc2120a91b7 in start_thread () from /lib64/libc.so.6
#9  0x7fc21212b39c in clone3 () from /lib64/libc.so.6

Thread 1 (Thread 0x7fc20e151f40 (LWP 9643)):
[KCrash Handler]
#4  0x7fc21280fd83 in QVariant::QVariant(QString const&) () from
/lib64/libQt6Core.so.6
#5  0x7fc211b44aac in standardDeclarationForNode(QTextHtmlParserNode
const&) () from /lib64/libQt6Gui.so.6
#6  0x7fc211b45bc2 in QTextHtmlParser::declarationsForNode(int) const ()
from /lib64/libQt6Gui.so.6
#7  0x7fc211b46830 in QTextHtmlParser::parseTag() () from
/lib64/libQt6Gui.so.6
#8  0x7fc211b46df0 in QTextHtmlParser::parse() () from
/lib64/libQt6Gui.so.6
#9  0x7fc211aeb2ea in QTextHtmlImporter::QTextHtmlImporter(QTextDocument*,
QString const&, QTextHtmlImporter::ImportMode, QTextDocument const*) () from
/lib64/libQt6Gui.so.6
#10 0x7fc211ad3f16 in QTextDocument::setHtml(QString const&) () from
/lib64/libQt6Gui.so.6
#11 0x7fc20e11fb7f in
KFileMetaData::MobiExtractor::extract(KFileMetaData::ExtractionResult*) () from
/usr/lib64/qt6/plugins/kf6/kfilemetadata/kfilemetadata_mobiextractor.so
#12 0x5606c85350cf in Baloo::App::index(Baloo::Transaction*, QString
const&, unsigned long long) ()
#13 0x5606c8536745 in Baloo::App::processNextFile() ()
#14 0x7fc2127fa3f4 in void doActivate(QObject*, int, void**) () from
/lib64/libQt6Core.so.6
#15 0x7fc212707496 in QSingleShotTimer::timerEvent(QTimerEvent*) () from
/lib64/libQt6Core.so.6
#16 0x7fc2127ebccf in QObject::event(QEvent*) () from
/lib64/libQt6Core.so.6
#17 0x7fc212795a99 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt6Core.so.6
#18 0x7fc21294d797 in QTimerInfoList::activateTimers() () from
/lib64/libQt6Core.so.6
#19 0x7fc212a7bdb9 in timerSourceDispatch(_GSource*, int (*)(void*), void*)
() from /lib64/libQt6Core.so.6
#20 0x7fc210d1b68c in g_main_context_dispatch_unlocked.lto_priv () from
/lib64/libglib-2.0.so.0
#21 0x7fc210d7c788 in g_main_context_iterate_unlocked.isra () from

[frameworks-kglobalaccel] [Bug 486852] New: Global Keyboard Shortcut migration from Plasma 5 to Plasma 6 broken, leaves zombie entries

[Christian]

https://bugs.kde.org/show_bug.cgi?id=486852

Bug ID: 486852
   Summary: Global Keyboard Shortcut migration from Plasma 5 to
Plasma 6 broken, leaves zombie entries
Classification: Frameworks and Libraries
   Product: frameworks-kglobalaccel
   Version: 6.1.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: k...@fuchsnet.ch
  Target Milestone: ---

SUMMARY
I upgraded to a new fedora version which brought Plasma / Frameworks / KDE 6.*
instead of 5.*, and I was noticing that all my custom global keyboard shortcuts
were broken, as in: they didn't trigger the action they were configured to.
Interestingly enough they were still listed under systemsettings in the
keyboard shortcuts, under the service for custom / personal keyboard shortcuts,
and trying to re-assign the key combination did lead to a warning that that
combination is already assigned.

STEPS TO REPRODUCE
1.  Have KDE Plasma, Frameworks etc. pp. 5.* 
2.  Have custom keyboard shorcuts
3.  Upgrade to Plasma, Frameworks etc. pp. 6.*

OBSERVED RESULT
Keyboard shorcuts are listed in settings, but they do not work (the action does
not trigger)

EXPECTED RESULT
Preferably they are migrated in a way so they work, but if that is not feasible
for whatever reason, then they should at least be cleaned out

Probably important sidenote: this is from X11 to X11, no wayland / switch
involved.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.8-300.fc40.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-8265U CPU @ 1.60GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: LENOVO
Product Name: 20NQS30W00
System Version: ThinkPad X390 Yoga
ADDITIONAL INFORMATION

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

[kwin] [Bug 486850] New: Regression: Windows of other workspaces not shown when "organize windows in the grid view" is NOT selected

[Christian]

https://bugs.kde.org/show_bug.cgi?id=486850

Bug ID: 486850
   Summary: Regression: Windows of other workspaces not shown when
"organize windows in the grid view" is NOT selected
Classification: Plasma
   Product: kwin
   Version: 6.0.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: effects-overview
  Assignee: kwin-bugs-n...@kde.org
  Reporter: k...@fuchsnet.ch
  Target Milestone: ---

SUMMARY
Thank you very much for the "organize windows in the grid view" option, it is
crucial to me. 
However, it seems that in 6.0.4 it is buggy. If that checkbox is NOT ticket,
only windows from the current virtual desktop are shown in the overview,
windows on all other virtual desktops are hidden.

STEPS TO REPRODUCE
1. uncheck "organize windows in the grid view"
2. have multiple virtual desktops, e.g. I have 6, split over two rows
3. open windows on various virtual desktops, then switch to one
4. open the overview effect

OBSERVED RESULT
Only windows from the current virtual desktop are shown in the grid, other
virtual desktops are all empty

EXPECTED RESULT
All windows are shown

Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.8-300.fc40.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-8265U CPU @ 1.60GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: LENOVO
Product Name: 20NQS30W00
System Version: ThinkPad X390 Yoga

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

[kwin] [Bug 486849] New: Regression: Grid Overview not available as corner action

[Christian]

https://bugs.kde.org/show_bug.cgi?id=486849

Bug ID: 486849
   Summary: Regression: Grid Overview not available as corner
action
Classification: Plasma
   Product: kwin
   Version: 6.0.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: effects-overview
  Assignee: kwin-bugs-n...@kde.org
  Reporter: k...@fuchsnet.ch
  Target Milestone: ---

SUMMARY
Since the merging of various effects into the overview effect (Plasma 6), the
grid overview that has been added (including a keyboard shortcut) can't be
triggered as a corner action (the thing where moving the mouse cursor into a
screen corner triggers something)

STEPS TO REPRODUCE
1.  Go to system settings
2.  Go to screen corner actions
3.  Try to add the grid effect of overview

OBSERVED RESULT
You can't, it's not in the list

EXPECTED RESULT
You can, as it was possible pre-plasma-6 when this was a separate effect

Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.8-300.fc40.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-8265U CPU @ 1.60GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: LENOVO
Product Name: 20NQS30W00
System Version: ThinkPad X390 Yoga

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

[kwin] [Bug 485690] X11 and Wayland use different Window Class Names

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=485690

S. Christian Collins  changed:

   What|Removed |Added

 CC||s_chriscoll...@hotmail.com

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

[kwin] [Bug 483503] Window rules: Force app to specific screen don't work with Wayland

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=483503

S. Christian Collins  changed:

   What|Removed |Added

 CC||s_chriscoll...@hotmail.com

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

[neon] [Bug 434038] Please provide an updated version of Maliit that is usable

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=434038

S. Christian Collins  changed:

   What|Removed |Added

 CC||s_chriscoll...@hotmail.com

--- Comment #12 from S. Christian Collins  ---
On some systems, maalit-keyboard prevents Plasma X11 session from logging in
(Wayland is unaffected). SDDM just freezes after entering the password. I have
experienced this on two systems running KDE neon User Edition, but am unable to
replicate in VirtualBox.

Related bug report:
https://bugs.launchpad.net/ubuntu/+source/maliit-keyboard/+bug/2039721

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

[plasmashell] [Bug 483691] plasma panel unresponsive after connecting secondary monitor aligned to the left of primary (Wayland)

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=483691

--- Comment #12 from S. Christian Collins  ---
(In reply to Nate Graham from comment #11)
> Glad to hear it. S. Christian Collins, is that your experience too?

Yes, this does appear to be fixed now! Hooray!

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

[policykit-kde-agent-1] [Bug 485407] polkit-kde-agent crashes with nullptr

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=485407

S. Christian Collins  changed:

   What|Removed |Added

 CC||s_chriscoll...@hotmail.com

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

[plasmashell] [Bug 407459] new notifications: Abnormal space appears below "Open" and hamburger buttons when a download is completed

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=407459

--- Comment #20 from S. Christian Collins  ---
Reading again through the comments, I realize I've had the "morphing popups"
desktop effect disabled for a while now, which might be why I no longer see the
bug (or any of the other bugs that effect creates). So, the bug might still be
out there, folks. Be sure to lock your doors at night and count your kids.

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

[dolphin] [Bug 464086] keyboard selection gets stuck when trying to delete a file permanently

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=464086

S. Christian Collins  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|REPORTED|RESOLVED

--- Comment #1 from S. Christian Collins  ---
This bug was fixed at some point. Closing.

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

[dolphin] [Bug 425007] dolphin loses "all desktops" setting when a folder is opened via another application

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=425007

S. Christian Collins  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|REPORTED|RESOLVED

--- Comment #6 from S. Christian Collins  ---
I haven't been able to reproduce this bug for a long time, so I consider it
fixed.

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

[kwin] [Bug 468371] Kate window rules: "All Desktops" + "No titlebar and frame" = pager & taskbar only see Kate on Desktop #1

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=468371

S. Christian Collins  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|REPORTED|RESOLVED

--- Comment #5 from S. Christian Collins  ---
I have not encountered this bug in a while, so I am closing it.

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

[ark] [Bug 453452] creating 7zip archive of ~/.mozilla or ~/.thunderbird folder fails

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=453452

--- Comment #1 from S. Christian Collins  ---
This bug is still present in Ark 24.02.2 (Plasma 6.0.4).

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

[plasmashell] [Bug 407459] new notifications: Abnormal space appears below "Open" and hamburger buttons when a download is completed

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=407459

--- Comment #18 from S. Christian Collins  ---
I haven't experienced this bug in a long, long time. I'd say we can probably
close it.

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

[plasmashell] [Bug 465747] desktop icons moved to secondary monitor upon login

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=465747

S. Christian Collins  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #20 from S. Christian Collins  ---
I can no longer reproduce this in Plasma 6. Closing.

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

[plasmashell] [Bug 483689] Invisible text in some widget settings with mixed light/dark theme e.g. Breeze Twilight

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=483689

--- Comment #7 from S. Christian Collins  ---
Created attachment 168619
  --> https://bugs.kde.org/attachment.cgi?id=168619=edit
new look of the bug (sensors details)

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

[plasmashell] [Bug 483689] Invisible text in some widget settings with mixed light/dark theme e.g. Breeze Twilight

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=483689

--- Comment #6 from S. Christian Collins  ---
Created attachment 168618
  --> https://bugs.kde.org/attachment.cgi?id=168618=edit
new look of the bug (pie chart details)

With the upgrade to Plasma 6.0.4 and Frameworks 6.1.0, this bug has changed its
colors, literally. Previously, the text color for certain widgets was being
pulled from the dark plasma theme, conflicting with the light application theme
making the white text impossible to read against the white background (when
using Twilight).

Now, the widget background is also being pulled from the plasma theme, leading
to cases of hard to read black text on a dark background and white check marks
instead of black.

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

[dolphin] [Bug 482899] Dolphin can't write to folder with group write access

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=482899

--- Comment #10 from S. Christian Collins  ---
I can confirm this bug is indeed fixed in Frameworks 6.1. Thank you!

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

[konsole] [Bug 372116] Feature Request: Support OSC 52 (copy to clipboard)

[Christian Muehlhaeuser]

https://bugs.kde.org/show_bug.cgi?id=372116

--- Comment #38 from Christian Muehlhaeuser  ---
(In reply to Shmerl from comment #35)
> Well, I see it being used at least in a few places in the code:
> 
> ```
> src/Vt102Emulation.cpp:322:tokenBufferPos = qMin(tokenBufferPos,
> MAX_TOKEN_LENGTH - 1);
> src/Vt102Emulation.h:127:#define MAX_TOKEN_LENGTH 256 // Max length of
> tokens (e.g. window title)
> src/Vt102Emulation.h:132:uint tokenBuffer[MAX_TOKEN_LENGTH]; // FIXME:
> overflow?
> ```

That looks like an outdated version of the code. Looking at the git history, it
seems like this issue may have been fixed a few weeks ago and the tokenBuffer
now gets resized to fit the content. I've got to take a closer look, but that
might enable me to revisit this issue. Either way MAX_TOKEN_LENGTH is
definitely obsolete now.

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

[konsole] [Bug 372116] Feature Request: Support OSC 52 (copy to clipboard)

[Christian Muehlhaeuser]

https://bugs.kde.org/show_bug.cgi?id=372116

--- Comment #34 from Christian Muehlhaeuser  ---
(In reply to Shmerl from comment #33)
> Apparently some downstream distros are working around this by changing the
> buffer size:
> 
> -#define MAX_TOKEN_LENGTH 256 // Max length of tokens (e.g. window title)
> +#define MAX_TOKEN_LENGTH 65536 // Max length of tokens (e.g. window title)

I'm surprised to hear that, as I don't think changing this constant actually
has any effect. It looks like a remnant that was forgotten to be removed and
it's not actually used anywhere.

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

[plasmashell] [Bug 484473] Symbolic icons have wrong color when using Twilight theme

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=484473

--- Comment #5 from S. Christian Collins  ---
Perhaps the assigned component of this bug should be changed from "widget
explorer" to "icon" or whatever is most appropriate, as this issue clearly
affects more than just the widget explorer. Being assigned to the wrong
component might hamper this bug's visibility to the pertinent developers.

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

[plasmashell] [Bug 483691] plasma panel unresponsive after connecting secondary monitor aligned to the left of primary (Wayland)

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=483691

--- Comment #9 from S. Christian Collins  ---
I took a video reproducing steps 4 and 5 above on my laptop (after the reboot):
https://youtu.be/Ew2JgrpOG7I

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

[plasmashell] [Bug 483691] plasma panel unresponsive after connecting secondary monitor aligned to the left of primary (Wayland)

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=483691

--- Comment #8 from S. Christian Collins  ---
(In reply to Nate Graham from comment #7)
> Either way, we need to know if it reproduces at all in a new clean user
> account. Thanks all!

When I try these steps in a new user account with no changes to the UI from
default, the following happens:
1. Plug in the monitor and configure to the left of primary screen: the panel
works fine.
2. Unplug the monitor: the right side of the panel becomes unresponsive.
3. Reboot & log in again. Panel will again be responsive.
4. Plug in the monitor (which will remember its configuration to the left of
primary): panel is unresponsive.
5. Unplug the monitor: all but the leftmost bit of the panel remains
unresponsive.

I haven't tried this yet with VirtualBox, but here is the system info from the
laptop on which I reproduced the above:

OS: KDE Neon 6.0 User Edition (Plasma Desktop 6.0.3, KDE Frameworks 6.0.0, Qt
6.7.0)
Linux Kernel: 6.5.0-27-lowlatency (64-bit)
PC: HP Pavilion m6-1035dx laptop
CPU/GPU: AMD A10-4600M 2.3 GHz quad-core APU with Trinity [Radeon HD 7660G]
Graphics (using radeon driver)
RAM: 8GB DDR3 (2x 4GB PC3-12800 1600 MHz), 7.2GB usable
Screen #1 (LVDS-1, screen 0):
  - Resolution: 1366 x 768 @ 60 Hz
Screen #2 (HDMI-A-1, screen 1):
  - Monitor: Dell P170Sb 17" LCD Monitor
  - Resolution: 1280 x 1024 @ 75 Hz

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

[kwin] [Bug 465858] shift + drag does not interact with the tiling layout if Both Shifts together enable Caps Lock

[Christian]

https://bugs.kde.org/show_bug.cgi?id=465858

Christian  changed:

   What|Removed |Added

 CC||christian.tall...@gmx.de

--- Comment #13 from Christian  ---
Is there a way to detect what shortcut causes the problem?
I am on openSuse Tumbleweed Plasma 6 and can start the tiling editor but
holding shift + moving the window does not work.
I don´t have the mentioned shortcuts enabled, but there seems to be no way to
configure the tiling action.

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

[plasmashell] [Bug 483691] plasma panel unresponsive after connecting secondary monitor aligned to the left of primary (Wayland)

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=483691

--- Comment #5 from S. Christian Collins  ---
Just now after testing your last steps, I unplugged the secondary monitor, and
only some parts of the panel became responsive again to clicks. The panel
itself isn't dead, though... I can still hit the Meta key to bring up the menu.
It's just dead to mouse clicks throughout some areas of the panel. Again, this
bug only happens when the secondary monitor is configured *to the left* of
primary.

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

[plasmashell] [Bug 483691] plasma panel unresponsive after connecting secondary monitor aligned to the left of primary (Wayland)

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=483691

--- Comment #4 from S. Christian Collins  ---
(In reply to Nate Graham from comment #3)
> Sounds a bit like Bug 483188. Does it start working if you restart
> plasmashell or maximize and de-maximize a window?

Neither of these steps work. The command to restart plasmashell (systemctl
--user restart plasma-plasmashell) does nothing. The panel just sits there,
frozen until I unplug the secondary monitor.

Also, while I mentioned that my affected laptop has an AMD GPU, I can reproduce
this bug in VirtualBox on a different system with an NVIDIA graphics card
(though obviously the NVIDIA driver is not running inside the virtual machine).
See the video linked in my original report.

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

[plasmashell] [Bug 483689] invisible text in widget settings

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=483689

--- Comment #4 from S. Christian Collins  ---
(In reply to Nate Graham from comment #3)
> I can't reproduce the issue. I suspect it may be related to the color sin
> your active color scheme or Plasma theme. Can you reproduce it in a new
> clean user account?

Aah! The issue only appears when using "Breeze Twilight" (light application
theme with dark plasma theme). Perhaps the affected text boxes are getting
their text color from the plasma theme rather than the application theme?

I tested this in a KDE neon VirtualBox install (X11), rebooting between each
theme change as the plasma theme didn't fully change over until I did.

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

[plasmashell] [Bug 483691] plasma panel unresponsive after connecting secondary monitor aligned to the left of primary (Wayland)

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=483691

--- Comment #2 from S. Christian Collins  ---
(In reply to Nate Graham from comment #1)
> What GPU hardware are you using?

It is an old AMD APU: AMD A10-4600M 2.3 GHz quad-core APU with Trinity [Radeon
HD 7660G] Graphics (using radeon driver)

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

[plasmashell] [Bug 483684] memory monitor circle sometimes stuck at 100%

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=483684

S. Christian Collins  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|RESOLVED|REOPENED
 Resolution|DUPLICATE   |---

--- Comment #4 from S. Christian Collins  ---
(In reply to Nate Graham from comment #3)
> 
> *** This bug has been marked as a duplicate of bug 477983 ***

Nate, I don't think these are the same bugs. In bug #477983, it is the sensor
data that is incorrect. In my bug, the reported value is correct, but the
graphical representation (circle) is occasionally stuck at 100%.

Also, in my original report, I had said this only happens on my laptop. I
finally had it happen for the first time on my desktop just the other day. I
wonder if system speed is a factor? My laptop is quite old and slow compared to
my much faster desktop and has the bug happen much more frequently.

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

[plasmashell] [Bug 483702] Plasma crashed when opening the "leave" menu in Kickoff

[Christian Schärf]

https://bugs.kde.org/show_bug.cgi?id=483702

--- Comment #5 from Christian Schärf  ---
I should also mention that I have multi monitor setup: 3840x2160 (UHD), 60 Hz,
125 %; 2560x1440 (WQHD), 144 Hz, 100 %; all running on an AMD GPU. Also, I use
the Wayland session.

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

[plasmashell] [Bug 485046] Opacity Adaptive not working when Visibility Dodge Windows is active

[Christian]

https://bugs.kde.org/show_bug.cgi?id=485046

Christian  changed:

   What|Removed |Added

 CC||christian.tall...@gmx.de

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

[plasmashell] [Bug 485046] New: Opacity Adaptive not working when Visibility Dodge Windows is active

[Christian]

https://bugs.kde.org/show_bug.cgi?id=485046

Bug ID: 485046
   Summary: Opacity Adaptive not working when Visibility Dodge
Windows is active
Classification: Plasma
   Product: plasmashell
   Version: 6.0.3
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: christian.tall...@gmx.de
CC: niccolo.venera...@gmail.com
  Target Milestone: 1.0

Created attachment 168155
  --> https://bugs.kde.org/attachment.cgi?id=168155=edit
Picture of the Problem

SUMMARY
When using a floating panel that has Visibility="Dodge Windows" and
Opacity="Adaptive" the panel correctly dodges, but is always translucent for
me.
When a Window is maximized, I would expect the panel to be opaque when moving
the cursor down, to show the panel.

STEPS TO REPRODUCE
1. Create a floating panel.
2. Set Visibility to "Dodge Windows"
3. Set Opacity to "Adaptive"
4. Maximize a Window.
5. Move the cursor down to show the floating panel.

OBSERVED RESULT
The Panel is translucent.

EXPECTED RESULT
The Panel should be opaque.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed 20240403
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0 
Qt Version: 6.6.3

ADDITIONAL INFORMATION
Graphics Platform: X11

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

[systemsettings] [Bug 407672] printer changes not saved when clicking "Apply"

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=407672

S. Christian Collins  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #10 from S. Christian Collins  ---
Yes, this bug is now fixed. The "Apply" button never becomes active when
changing printer settings, so the user can only hit "OK", which works.

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

[plasmashell] [Bug 484473] Symbolic icons have wrong color when using Twilight theme

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=484473

S. Christian Collins  changed:

   What|Removed |Added

 CC||s_chriscoll...@hotmail.com

--- Comment #2 from S. Christian Collins  ---
Created attachment 167916
  --> https://bugs.kde.org/attachment.cgi?id=167916=edit
wrong color discover and telegram tray icons

I can also confirm this behavior on two systems (one X11, one Wayland) after
the update to Plasma 6.0.3. Affects the discover update notifier and telegram,
among others. I am also using the Twilight theme.

OS: KDE neon 6.0 User Edition
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

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

[kwin] [Bug 475468] On X11 with NVIDIA GPU, window and panel resizing is very laggy when any panels are set to Floating or Adapting transparency

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=475468

S. Christian Collins  changed:

   What|Removed |Added

 CC||s_chriscoll...@hotmail.com

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

[konsole] [Bug 395520] Konsole KPart blur does not work/incorrect warning message

[Christian Muehlhaeuser]

https://bugs.kde.org/show_bug.cgi?id=395520

--- Comment #14 from Christian Muehlhaeuser  ---
The blur technically works now, but still shows a warning message in Yakuake's
"Edit Profiile" dialog:

"Konsole was started before desktop effects were enabled. You need to restart
Konsole to see transparent background."

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

[yakuake] [Bug 483903] Splitting horizontally/vertically the new view is not automatically focused

[Christian Muehlhaeuser]

https://bugs.kde.org/show_bug.cgi?id=483903

--- Comment #3 from Christian Muehlhaeuser  ---
> I apologize, I did not search for my issue in the closed bug reports.
> For the future, I will search in closed/resolved bug reports as well.

No worries, I'd rather see a duplicate ticket than a missing ticket. Any
efforts to de-duplicate the ticket base are greatly appreciated tho!

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

[krfb] [Bug 455238] Add support rdp server

[Christian Stoller]

https://bugs.kde.org/show_bug.cgi?id=455238

Christian Stoller  changed:

   What|Removed |Added

 CC||naitsi...@e.mail.de

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

[yakuake] [Bug 482119] Opening new tab in yakuake does not bring it in a focus.

[Christian Muehlhaeuser]

https://bugs.kde.org/show_bug.cgi?id=482119

Christian Muehlhaeuser  changed:

   What|Removed |Added

 CC||from-kde-b...@176295.com

--- Comment #11 from Christian Muehlhaeuser  ---
*** Bug 483903 has been marked as a duplicate of this bug. ***

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

[yakuake] [Bug 483903] Splitting horizontally/vertically the new view is not automatically focused

[Christian Muehlhaeuser]

https://bugs.kde.org/show_bug.cgi?id=483903

Christian Muehlhaeuser  changed:

   What|Removed |Added

 CC||mue...@gmail.com
 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED

--- Comment #1 from Christian Muehlhaeuser  ---


*** This bug has been marked as a duplicate of bug 482119 ***

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

[yakuake] [Bug 440128] Yakuake sticks on the activity it was started first

[Christian Muehlhaeuser]

https://bugs.kde.org/show_bug.cgi?id=440128

--- Comment #10 from Christian Muehlhaeuser  ---
Thanks for confirming!

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

[yakuake] [Bug 440128] Yakuake sticks on the activity it was started first

[Christian Muehlhaeuser]

https://bugs.kde.org/show_bug.cgi?id=440128

Christian Muehlhaeuser  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #9 from Christian Muehlhaeuser  ---


*** This bug has been marked as a duplicate of bug 440281 ***

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

[yakuake] [Bug 440281] opening yakuake pulls me back to another activity, negating the point of yakuake

[Christian Muehlhaeuser]

https://bugs.kde.org/show_bug.cgi?id=440281

Christian Muehlhaeuser  changed:

   What|Removed |Added

 CC||docampo.an...@gmail.com

--- Comment #3 from Christian Muehlhaeuser  ---
*** Bug 440128 has been marked as a duplicate of this bug. ***

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

[yakuake] [Bug 483714] Focus stays on old terminal

[Christian Muehlhaeuser]

https://bugs.kde.org/show_bug.cgi?id=483714

Christian Muehlhaeuser  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED
 CC||mue...@gmail.com

--- Comment #1 from Christian Muehlhaeuser  ---


*** This bug has been marked as a duplicate of bug 482119 ***

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

[yakuake] [Bug 482119] Opening new tab in yakuake does not bring it in a focus.

[Christian Muehlhaeuser]

https://bugs.kde.org/show_bug.cgi?id=482119

Christian Muehlhaeuser  changed:

   What|Removed |Added

 CC||docampo.an...@gmail.com

--- Comment #10 from Christian Muehlhaeuser  ---
*** Bug 483714 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 483702] Plasma crashed when opening the "leave" menu in Kickoff

[Christian Schärf]

https://bugs.kde.org/show_bug.cgi?id=483702

--- Comment #2 from Christian Schärf  ---
Created attachment 167284
  --> https://bugs.kde.org/attachment.cgi?id=167284=edit
Screenshot

I am adding a screenshot of the item I was clicking when the crash happened so
it is clear what I am talking about.

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

[plasmashell] [Bug 483702] Plasma crashed when opening the "leave" menu in Kickoff

[Christian Schärf]

https://bugs.kde.org/show_bug.cgi?id=483702

--- Comment #1 from Christian Schärf  ---
Created attachment 167282
  --> https://bugs.kde.org/attachment.cgi?id=167282=edit
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.

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

[plasmashell] [Bug 483702] New: Plasma crashed when opening the "leave" menu in Kickoff

[Christian Schärf]

https://bugs.kde.org/show_bug.cgi?id=483702

Bug ID: 483702
   Summary: Plasma crashed when opening the "leave" menu in
Kickoff
Classification: Plasma
   Product: plasmashell
   Version: 6.0.2
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: c.scha...@t-online.de
  Target Milestone: 1.0

Application: plasmashell (6.0.2)

Qt Version: 6.6.2
Frameworks Version: 6.0.0
Operating System: Linux 6.7.9-arch1-1 x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 6.0.2 [CoredumpBackend]

-- Information about the crash:
When attempting to open the "leave" menu ("Verlassen" in German localisation),
plasma crashed. This has already happened to me twice after changing the panel
visibility to "dodge windows" and the panel width to "fit to content" but I am
not sure if the crash is related. It does not crash every time.

The crash can be reproduced sometimes.

-- Backtrace (Reduced):
#5  std::__atomic_base::fetch_add (__m=std::memory_order_acq_rel, __i=1,
this=0x107b83484d7e01, this=, __i=,
__m=) at /usr/include/c++/13.2.1/bits/atomic_base.h:633
#6  QAtomicOps::ref (_q_value=, _q_value=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/thread/qatomic_cxx11.h:258
[...]
#8  QtSharedPointer::ExternalRefCountData::getAndRef
(obj=obj@entry=0x595a9a0e2270) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/tools/qsharedpointer.cpp:1409
#9  0x7442a7d78170 in QWeakPointer::QWeakPointer
(ptr=0x595a9a0e2270, this=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/tools/qsharedpointer_impl.h:685
#10 QWeakPointer::assign (this=0x595a9e5bcee0,
ptr=0x595a9a0e2270) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/tools/qsharedpointer_impl.h:680


Reported using DrKonqi

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

[Discover] [Bug 483701] New: unable to launch Software Sources - root password never accepted

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=483701

Bug ID: 483701
   Summary: unable to launch Software Sources - root password
never accepted
Classification: Applications
   Product: Discover
   Version: 6.0.2
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: plasma-b...@kde.org
  Reporter: s_chriscoll...@hotmail.com
CC: aleix...@kde.org
  Target Milestone: ---

SUMMARY
Clicking the "Software Sources" button in Discover's "Settings" page prompts
for the root password, but the root password (sudo) is never accepted.

STEPS TO REPRODUCE
These steps are for KDE neon and might vary for other distributions.
1. Make sure "software-properties-qt" is installed.
2. Start Discover.
3. Wait for update check to finish.
4. Navigate to the "Settings" page.
5. Click the "Software Sources" button on the right side of the page.

OBSERVED RESULT
A window pops up prompting for the root password. It has the window title "Run
as root — KDE su" and says "The action you requested needs root privileges.
Please enter root's password below or click Ignore to continue with your
current privileges. Command: /usr/bin/software-properties-qt". After entering
the user's password (since Ubuntu uses sudo), another box pops up with:
"Permission denied. Possibly incorrect password, please try again. On some
systems, you need to be in a special group (often: wheel) to use this program."
The password continues to be prompted, but is never accepted.

EXPECTED RESULT
Sudo password should be accepted and software properties launched.

SOFTWARE/OS VERSIONS
Linux: KDE neon 6.0 User Edition
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.

[kwin] [Bug 483698] choppy framerate in X11 after upgrade to Plasma 6

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=483698

--- Comment #2 from S. Christian Collins  ---
I also tested the following environment variables found in other
framerate-related bug reports, but neither of them had any affect in my case:
---
KWIN_DRM_DISABLE_BUFFER_READABILITY_CHECKS=1
KWIN_DRM_NO_AMS=1

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

[kwin] [Bug 483698] choppy framerate in X11 after upgrade to Plasma 6

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=483698

--- Comment #1 from S. Christian Collins  ---
Testing with the KWIN_X11_NO_SYNC_TO_VBLANK=1 environment variable set, I am
now getting well over 60 FPS constantly, so my issue would seem to be possibly
vsync related.

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

[kwin] [Bug 483698] New: choppy framerate in X11 after upgrade to Plasma 6

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=483698

Bug ID: 483698
   Summary: choppy framerate in X11 after upgrade to Plasma 6
Classification: Plasma
   Product: kwin
   Version: 6.0.2
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: s_chriscoll...@hotmail.com
  Target Milestone: ---

Created attachment 167280
  --> https://bugs.kde.org/attachment.cgi?id=167280=edit
additional information from Info Center

SUMMARY
Since upgrading my laptop to Plasma 6, the compositor performance in X11 has
become very choppy. I previously had smooth 60 fps for desktop effects, but now
I get around 32-35 fps when moving a window around and 45-50 fps when doing
nothing. Switching to Wayland, everything stays at a smooth 60 fps.

Here is a video comparing X11 vs. Wayland performance on my laptop:
https://youtu.be/O5LSSBpYJW0

SOFTWARE/OS VERSIONS
Linux: KDE neon 6.0 User Edition
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

LAPTOP INFO
PC: HP Pavilion m6-1035dx
CPU/GPU: AMD A10-4600M 2.3 GHz quad-core APU with Trinity [Radeon HD 7660G]
Graphics (using radeon driver)
RAM: 8GB DDR3 (2x 4GB PC3-12800 1600 MHz), 7.2GB usable

ADDITIONAL INFORMATION
I have attached additional system information from Info Center. I also use the
following X11 settings for my GPU, though deleting this file appears to make no
difference to performance:
---
Section "Device"
Identifier "Card0"
Driver "radeon"
Option "AccelMethod" "glamor"
Option "TearFree" "off"
Option "DRI3" "1"
EndSection
---

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

[yakuake] [Bug 402634] Hotkey to open/retract yakuake doesn't work in Wayland if flag "Use Open/Retract action to focus window" is set

[Christian Muehlhaeuser]

https://bugs.kde.org/show_bug.cgi?id=402634

Christian Muehlhaeuser  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

--- Comment #16 from Christian Muehlhaeuser  ---
*** Bug 454612 has been marked as a duplicate of this bug. ***

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

[yakuake] [Bug 454612] If 'Keep window open when it loses focus' is checked, Yakuake does not open/retract when I press F12

[Christian Muehlhaeuser]

https://bugs.kde.org/show_bug.cgi?id=454612

Christian Muehlhaeuser  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |DUPLICATE
 CC||mue...@gmail.com

--- Comment #8 from Christian Muehlhaeuser  ---


*** This bug has been marked as a duplicate of bug 402634 ***

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

[plasmashell] [Bug 483689] invisible text in widget settings

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=483689

--- Comment #2 from S. Christian Collins  ---
Created attachment 167279
  --> https://bugs.kde.org/attachment.cgi?id=167279=edit
video showing the bug

Whoops! It's attached now.

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

[plasmashell] [Bug 483684] memory monitor circle sometimes stuck at 100%

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=483684

--- Comment #2 from S. Christian Collins  ---
(In reply to Arjen Hiemstra from comment #1)
> This sounds like it might not have the proper maximum value and thus it ends
> up just filling the entire area since it doesn't have a range. The next time
> this happens, can you share the output of "kstatsviewer --details
> memory/physical/used" and also the same output from when it doesn't happen?

I get the same output in both cases:
Name:Used Physical Memory
Short Name:  Used
Description: 
Unit:B
Minimum: 0
Maximum: 7.75892e+09

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

[plasmashell] [Bug 483692] New: folder view widget in panel cannot be resized

[S. Christian Collins]

https://bugs.kde.org/show_bug.cgi?id=483692

Bug ID: 483692
   Summary: folder view widget in panel cannot be resized
Classification: Plasma
   Product: plasmashell
   Version: 6.0.2
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Folder
  Assignee: plasma-b...@kde.org
  Reporter: s_chriscoll...@hotmail.com
CC: h...@kde.org
  Target Milestone: 1.0

SUMMARY
When using the folder view widget in a panel, the popup cannot be resized, even
though a resize cursor is offered when hovering the cursor over the edges of
the popup.

STEPS TO REPRODUCE
1. Add "Folder View" widget to the panel.
2. Click the icon to open the widget and attempt to resize any of its
boundaries.

OBSERVED RESULT
The widget cannot be resized.

EXPECTED RESULT
Either A: The widget should be resizable.
Or B: The resize cursor should not be shown.

SOFTWARE/OS VERSIONS
Linux: KDE neon 6.0 User Edition
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.

[yakuake] [Bug 440128] Yakuake sticks on the activity it was started first

[Christian Muehlhaeuser]

https://bugs.kde.org/show_bug.cgi?id=440128

Christian Muehlhaeuser  changed:

   What|Removed |Added

 CC||mue...@gmail.com

--- Comment #7 from Christian Muehlhaeuser  ---
This sounds similar to 440281, which is apparently fixed. Can you still
reproduce this with Plasma 6?

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

[yakuake] [Bug 440281] opening yakuake pulls me back to another activity, negating the point of yakuake

[Christian Muehlhaeuser]

https://bugs.kde.org/show_bug.cgi?id=440281

Christian Muehlhaeuser  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED
 CC||mue...@gmail.com

--- Comment #2 from Christian Muehlhaeuser  ---
Thanks for confirming Eric!

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