Bug 488310

Summary:	FC40 KDE wayland or X11 is completely unusable... Sigh...
Product:	[Plasma] kstart	Reporter:	QofZahadoom <ikouts>
Component:	general	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED NOT A BUG
Severity:	grave	CC:	nate
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	attachment-4053397-0.html attachment-4053565-0.html

Description QofZahadoom 2024-06-10 16:43:27 UTC

THE WHOLE KDE in fc40 is broken... Using XPS 9720 laptop with a serious nvidia card. Both wayland and x11 are broken.

So many bugs I am not sure where to start. After applying the updates on 10th June and the extra update-testing repo packages on the same day, FC40 wayland plasma and x11 plasma are totally off.

Running nmcli command to connect and write this let say bug report.

Apologize for the bandwith. Just to make it more scientific. Kstart5 plasmashell does not work, panels are non existent, bluetooh goes on/off, screen resolution and pixelation issues everywhere, fonts screwer, previous KDE settings ignored (yes I used system upgrade in fedora).

If you can fix something please do it.

Thx for the bandwidth.

Comment 1 Nate Graham 2024-06-10 20:42:13 UTC

> So many bugs I am not sure where to start
With the first one; eat the elephant one bite at a time. "Aaaaaaeverything is bad" is not an actionable bug report we can investigate, it's an unactionable rant.

I'm sorry you've having a problem here, but bugs need to be reported in a way that makes them actionable or else there's nothing anyone can do. See https://community.kde.org/Get_Involved/Issue_Reporting

In this case it sounds like there is a deeper problem, maybe a botched upgrade? I'd recommend following up with the Fedora people first,

Comment 2 QofZahadoom 2024-06-10 20:43:13 UTC

Created attachment 170360 [details]
attachment-4053397-0.html

I apologize..

Best
Thank you
On 6/10/24 11:42 PM, Nate Graham wrote:
> https://bugs.kde.org/show_bug.cgi?id=488310
>
> Nate Graham<nate@kde.org>  changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                   CC|                            |nate@kde.org
>           Resolution|---                         |NOT A BUG
>               Status|REPORTED                    |RESOLVED
>
> --- Comment #1 from Nate Graham<nate@kde.org>  ---
>> So many bugs I am not sure where to start
> With the first one; eat the elephant one bite at a time. "Aaaaaaeverything is
> bad" is not an actionable bug report we can investigate, it's an unactionable
> rant.
>
> I'm sorry you've having a problem here, but bugs need to be reported in a way
> that makes them actionable or else there's nothing anyone can do. See
> https://community.kde.org/Get_Involved/Issue_Reporting
>
> In this case it sounds like there is a deeper problem, maybe a botched upgrade?
> I'd recommend following up with the Fedora people first,
>

Comment 3 QofZahadoom 2024-06-10 20:44:03 UTC

Created attachment 170361 [details]
attachment-4053565-0.html

I apologize..

Best
Thank you

On 6/10/24 11:42 PM, Nate Graham wrote:
> https://bugs.kde.org/show_bug.cgi?id=488310
>
> Nate Graham<nate@kde.org>  changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                   CC|                            |nate@kde.org
>           Resolution|---                         |NOT A BUG
>               Status|REPORTED                    |RESOLVED
>
> --- Comment #1 from Nate Graham<nate@kde.org>  ---
>> So many bugs I am not sure where to start
> With the first one; eat the elephant one bite at a time. "Aaaaaaeverything is
> bad" is not an actionable bug report we can investigate, it's an unactionable
> rant.
>
> I'm sorry you've having a problem here, but bugs need to be reported in a way
> that makes them actionable or else there's nothing anyone can do. See
> https://community.kde.org/Get_Involved/Issue_Reporting
>
> In this case it sounds like there is a deeper problem, maybe a botched upgrade?
> I'd recommend following up with the Fedora people first,
>