Bug 502969

Summary:	General settings page does not render
Product:	[Applications] kasts	Reporter:	jason0
Component:	general	Assignee:	bart
Status:	RESOLVED DOWNSTREAM
Severity:	major
Priority:	NOR
Version First Reported In:	24.12.3
Target Milestone:	---
Platform:	Pop!_OS
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description jason0 2025-04-18 15:36:35 UTC

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY


STEPS TO REPRODUCE
1. open the settings
2. click on general settings


OBSERVED RESULT

in the terminal I can see the following type of log:
org.kde.kasts.desktop[36235]: qrc:/qt/qml/org/kde/kasts/qml/Settings/SettingsPage.qml:14:1: QML SettingsPage: Created graphical object was not placed in the graphics scene.
Apr 17 16:09:30 pop-os gnome-shell[6848]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
Apr 17 16:09:30 pop-os gnome-shell[6848]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
Apr 17 16:09:30 pop-os gnome-shell[6848]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
Apr 17 16:09:30 pop-os geoclue[3341]: Failed to query location: Not Found



EXPECTED RESULT

I do see the window stack position log also on general startup so I don't think that's necessarily part of the problem (and thus it would still be logging that)

But the general settings page should render.


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

Comment 1 bart 2025-04-22 20:58:01 UTC

I think we would need to have more info to be able to debug this.  I don't fully understand what is happening.
Could you perhaps share a screenshot if it's some visual glitch?

Comment 2 jason0 2025-04-28 03:05:28 UTC

(In reply to bart from comment #1)
> I think we would need to have more info to be able to debug this.  I don't
> fully understand what is happening.
> Could you perhaps share a screenshot if it's some visual glitch?

Well the good news is that it's working now. And the version has been upgraded quite recently to 25.04.0 -- unfortunately I haven't easily been able to determine which commit(s) fixed the issue. But, based on this, seems reasonable to close the ticket if that's the practice followed here!

Comment 3 bart 2025-04-28 06:15:49 UTC

I think the package was missing a runtime dependency, which is easy enough to do with qml apps. A lot of packagers don't realize that they can't strip the dependencies down to just what's needed to get it to compile, until they get hit by it.

Anyway, glad that it's solved.