Bug 495607 - after momentary desktop display BLACK SCREEN
Summary: after momentary desktop display BLACK SCREEN
Status: RESOLVED NOT A BUG
Alias: None
Product: Powerdevil
Classification: Plasma
Component: general (show other bugs)
Version: 6.2.2
Platform: Arch Linux Linux
: NOR grave
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2024-10-30 20:01 UTC by garybig
Modified: 2024-11-08 22:42 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
attachment-923939-0.html (2.52 KB, text/html)
2024-11-01 00:11 UTC, garybig
Details
attachment-1113229-0.html (1.97 KB, text/html)
2024-11-01 17:33 UTC, garybig
Details
attachment-1125196-0.html (2.18 KB, text/html)
2024-11-01 18:48 UTC, garybig
Details
attachment-2476004-0.html (2.31 KB, text/html)
2024-11-06 16:29 UTC, garybig
Details
attachment-2530446-0.html (1.06 KB, text/html)
2024-11-06 21:17 UTC, garybig
Details
attachment-2541437-0.html (1.43 KB, text/html)
2024-11-06 22:29 UTC, garybig
Details

Note You need to log in before you can comment on or make changes to this bug.
Description garybig 2024-10-30 20:01:53 UTC
SUMMARY
after momentary desktop display BLACK SCREEN


STEPS TO REPRODUCE
1. boot up, after momentary desktop display BLACK SCREEN

2. NOT PRESENT IN v 6.1.5-1
3. Absolutely a bug in v 6.2.2-1

OBSERVED RESULT
BLACK SCREEN

EXPECTED RESULT
normal plasma desktop with desktop icon and bottom task manager bar

SOFTWARE/OS VERSIONS

Linux/KDE Plasma:  powerdevil 6.2.2-1
KDE Plasma Version: 6.2

ADDITIONAL INFORMATION
not present in powerdevil v 6.1.5-1
Comment 1 garybig 2024-10-30 20:06:49 UTC
LOOK AT code changes in powerdevil v 6.2.2-1   FROM   v   6.1.5-1

THIS ONE SINGLE PACKAGE bombs my EndeavourOS and Cachy OS  partitions

Do I even need powerdevil?  Plasma requires it -- how can I remove or disable it?
Comment 2 Nate Graham 2024-10-31 22:57:36 UTC
Are you saying that you've determined that Powerdevil causes this issue because you removed it and the issue went away? Or was there some other way you determined that Powerdevil was at fault?
Comment 3 garybig 2024-11-01 00:11:23 UTC
Created attachment 175427 [details]
attachment-923939-0.html

Yes. Reinstalled EndeavourOS with previous plasma 6.1.  Very slowly
whittled it down to only *ONE* possible suspect. Let my system update to
powerdevil 6.2.2 and  *BAM !!!*!  * Black screen *and a long time to reset
my system to having just powerdevil 6.1.5

good luck -- *please fix* or I will remain on *powerdevil 6.1.5*


On Thu, Oct 31, 2024 at 3:57 PM Nate Graham <
bugzilla_noreply_at_kde.org_garybig@duck.com> wrote:

> https://bugs.kde.org/show_bug.cgi?id=495607
>
> Nate Graham <nate@kde.org> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>              Status|REPORTED                    |NEEDSINFO
>             Version|git-stable-Plasma/6.2       |6.2.2
>          Resolution|---                         |WAITINGFORINFO
>                  CC|                            |nate@kde.org
>            Severity|critical                    |grave
>
> --- Comment #2 from Nate Graham <nate@kde.org> ---
> Are you saying that you've determined that Powerdevil causes this issue
> because
> you removed it and the issue went away? Or was there some other way you
> determined that Powerdevil was at fault?
>
> --
> You are receiving this mail because:
> You reported the bug.
> You are on the CC list for the bug.
Comment 4 Nate Graham 2024-11-01 17:02:05 UTC
Plasma 6.1 with Powerdevil 6.2 is likely going to cause problems anyway; we don't support picking and choosing versions like this. Powerdevil 6.2 had interdependent changes with KWin 6.2 and Plasma 6.2
Comment 5 garybig 2024-11-01 17:33:07 UTC
Created attachment 175452 [details]
attachment-1113229-0.html

you are advising me that the change to powerdevil package cannot be UNDONE

you are telling me essentially that I am screwed

wonderful

On Fri, Nov 1, 2024 at 10:02 AM Nate Graham <
bugzilla_noreply_at_kde.org_garybig@duck.com> wrote:

> https://bugs.kde.org/show_bug.cgi?id=495607
>
> Nate Graham <nate@kde.org> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>              Status|NEEDSINFO                   |REPORTED
>            Keywords|                            |regression
>          Resolution|WAITINGFORINFO              |---
>
> --- Comment #4 from Nate Graham <nate@kde.org> ---
> Plasma 6.1 with Powerdevil 6.2 is likely going to cause problems anyway; we
> don't support picking and choosing versions like this. Powerdevil 6.2 had
> interdependent changes with KWin 6.2 and Plasma 6.2
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
> You reported the bug.
Comment 6 Nate Graham 2024-11-01 17:35:55 UTC
Well, the issue needs to be investigated. It's not clear what's causing it yet.

To rule out local changes, can you create a new user account, log into it, and see if the issue happens there? If not, that means there's something in your normal user account that triggers this issue. Then we can try to locate what it is.

If it still happens in the new user account, it's more likely to be a bug in our software or an issue with the GPU drivers or the monitor.
Comment 7 garybig 2024-11-01 18:48:30 UTC
Created attachment 175459 [details]
attachment-1125196-0.html

If I create a new user account AND the bug persists -- it will take me a
long hour to restore my system to working status.

If possible, I would like NOT to subject myself to this time-consuming task

On Fri, Nov 1, 2024 at 10:35 AM Nate Graham <
bugzilla_noreply_at_kde.org_garybig@duck.com> wrote:

> https://bugs.kde.org/show_bug.cgi?id=495607
>
> Nate Graham <nate@kde.org> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>          Resolution|---                         |WAITINGFORINFO
>              Status|REPORTED                    |NEEDSINFO
>
> --- Comment #6 from Nate Graham <nate@kde.org> ---
> Well, the issue needs to be investigated. It's not clear what's causing it
> yet.
>
> To rule out local changes, can you create a new user account, log into it,
> and
> see if the issue happens there? If not, that means there's something in
> your
> normal user account that triggers this issue. Then we can try to locate
> what it
> is.
>
> If it still happens in the new user account, it's more likely to be a bug
> in
> our software or an issue with the GPU drivers or the monitor.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
> You reported the bug.
Comment 8 garybig 2024-11-06 16:29:22 UTC
Created attachment 175591 [details]
attachment-2476004-0.html

I have used powerdevil on a different user account and experienced the same
BLACK SCREEN issue.

Please advise me if the powerdevil package architect can reset it to
function as the 6.1 version did.

This issue has dogged me for over a month --- I realize I am only one of a
few having this issue. It EXISTS.

On Fri, Nov 1, 2024 at 10:35 AM Nate Graham <
bugzilla_noreply_at_kde.org_garybig@duck.com> wrote:

> https://bugs.kde.org/show_bug.cgi?id=495607
>
> Nate Graham <nate@kde.org> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>          Resolution|---                         |WAITINGFORINFO
>              Status|REPORTED                    |NEEDSINFO
>
> --- Comment #6 from Nate Graham <nate@kde.org> ---
> Well, the issue needs to be investigated. It's not clear what's causing it
> yet.
>
> To rule out local changes, can you create a new user account, log into it,
> and
> see if the issue happens there? If not, that means there's something in
> your
> normal user account that triggers this issue. Then we can try to locate
> what it
> is.
>
> If it still happens in the new user account, it's more likely to be a bug
> in
> our software or an issue with the GPU drivers or the monitor.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
> You reported the bug.
Comment 9 Nate Graham 2024-11-06 18:56:06 UTC
Does the cursor/mouse pointer appear on the black screen? Or no?
Comment 10 garybig 2024-11-06 21:17:13 UTC
Created attachment 175599 [details]
attachment-2530446-0.html

My recollection is that the pointer did not appear

There must be some *OBVIOUS* changes visible to the package modifying
developer/programmer

On Wed, Nov 6, 2024 at 10:56 AM Nate Graham <
bugzilla_noreply_at_kde.org_garybig@duck.com> wrote:

> https://bugs.kde.org/show_bug.cgi?id=495607
>
> --- Comment #9 from Nate Graham <nate@kde.org> ---
> Does the cursor/mouse pointer appear on the black screen? Or no?
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
> You reported the bug.
Comment 11 Nate Graham 2024-11-06 21:18:05 UTC
Just in case your recollection is faulty, can you try it again to see if it happens?
Comment 12 garybig 2024-11-06 22:29:55 UTC
Created attachment 175600 [details]
attachment-2541437-0.html

I have wasted a LOT of time recovering from this black screen bug and wish
to let others troubleshoot and diagnose.

The changes to the package have to be apparent to the package developer. I
have listed my specific hardware being used.

It would be far easier to just switch full-time to XFCE. I believe staying
on Manjaro STABLE may also relieve me of needing to troubleshoot bugs. I do
appreciate rolling-release distributions.  Immutable linux seems worth a
consider.

On Wed, Nov 6, 2024 at 1:18 PM Nate Graham <
bugzilla_noreply_at_kde.org_garybig@duck.com> wrote:

> https://bugs.kde.org/show_bug.cgi?id=495607
>
> --- Comment #11 from Nate Graham <nate@kde.org> ---
> Just in case your recollection is faulty, can you try it again to see if it
> happens?
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
> You reported the bug.
Comment 13 Nate Graham 2024-11-08 22:40:09 UTC
Oh, I see now that you've opened multiple reports for this. Please don't do that anymore.

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