https://bugs.kde.org/show_bug.cgi?id=448220
SP changed:
What|Removed |Added
Ever confirmed|0 |1
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=448173
--- Comment #3 from SP ---
I have now installed kde plasma packages 5.24.1-1.fc35 on both computers with
dual displays but the same problem outlined in my earlier bug report persist.
So this has not been resolved. Please let me know of any
https://bugs.kde.org/show_bug.cgi?id=448220
SP changed:
What|Removed |Added
CC||scp.stj...@gmail.com
--- Comment #6 from SP ---
Created
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #7 from SP ---
(In reply to Zamundaaa from comment #5)
> Please enable debug logging and upload a log from when you log in and KWin
> fails to enable the outputs correctly. Then we can see if it's KWins fault,
> if KScreen i
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #8 from SP ---
(In reply to SP from comment #7)
> (In reply to Zamundaaa from comment #5)
> > Please enable debug logging and upload a log from when you log in and KWin
> > fails to enable the outputs correctly. Then we
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #9 from SP ---
There also appears to be no difference with the output of kwin_wayland_drm
taken after logging in to Wayland KDE with only one monitor powered on and
second (after reboot) with both monitors powered on after logging in from
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #10 from SP ---
Created attachment 147051
--> https://bugs.kde.org/attachment.cgi?id=147051&action=edit
Additional output from login to wayland session
The output from logging into a wayland session today has more information t
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #12 from SP ---
Just to be clear - should I run the script from a tty before logging in with
SDDM or after?
(In reply to Zamundaaa from comment #11)
> Okay, so KWin fails to find a configuration that works with both monitors...
> I
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #14 from SP ---
Created attachment 147076
--> https://bugs.kde.org/attachment.cgi?id=147076&action=edit
dmesg-drm-debug.log
Attached is the dmesg-drm-debug.log requested by @Zamundaaa
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #15 from SP ---
(In reply to Zamundaaa from comment #13)
> Doesn't matter. It'll do its thing on the tty, no running sessions are
> affected
ran your script - thanks. Could it be this?
dce110_link_encoder_construc
https://bugs.kde.org/show_bug.cgi?id=379831
SP changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=451797
--- Comment #10 from SP ---
(In reply to Alexander Lohnau from comment #9)
> Is this still reproducible?
Yes I still get a Popup: "Window Rules - System Settings Module / Window Rules
"Error Loading QML file. Invalid KPackage 'kcm
https://bugs.kde.org/show_bug.cgi?id=451797
--- Comment #11 from SP ---
Currently running FC 26 with KDE Plasma 5.25.5 under Wayland
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=451797
--- Comment #12 from SP ---
Currently running FC 36 with KDE Plasma 5.25.5 under Wayland
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=451797
--- Comment #13 from SP ---
(In reply to SP from comment #10)
> (In reply to Alexander Lohnau from comment #9)
> > Is this still reproducible?
>
> Yes I still get a Popup: "Window Rules - System Settings Module / Window
> Rules
https://bugs.kde.org/show_bug.cgi?id=451797
SP changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=451797
SP changed:
What|Removed |Added
Resolution|WAITINGFORINFO |NOT A BUG
Version Fixed In
https://bugs.kde.org/show_bug.cgi?id=451797
--- Comment #15 from SP ---
(In reply to Alexander Lohnau from comment #14)
> > I realized that I had a duplicate kpackage in /usr/local/share/kpackage as
> > well as /usr/share/kpackage. Removed the directory from /usr/local/share
>
https://bugs.kde.org/show_bug.cgi?id=419897
--- Comment #19 from SP ---
I can confirm that the bug appears to have been resolved.
Operating System: Fedora Linux 37
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.9
Kernel Version: 6.2.11-200.fc37.x86_64 (64-bit
https://bugs.kde.org/show_bug.cgi?id=419897
--- Comment #20 from SP ---
Upgraded to KDE Connect 1.24.3 on my S10+ (see specs of my OS etc above).
Tried to browse folders on the phone and could no longer access. Rebooted
computer - problem persists. Restarted phone - problem resolved.
--
You
https://bugs.kde.org/show_bug.cgi?id=460128
Bug ID: 460128
Summary: Request for Move to Activities in Title Bar of
application
Classification: Plasma
Product: plasmashell
Version: 5.25.5
Platform: Fedora RPMs
Platform: Neon
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: sp...@gmx.com
CC: k...@davidedmundson.co.uk
Target Milestone: 1.0
https://bugs.kde.org/show_bug.cgi?id=460324
--- Comment #2 from sp ---
I don't know where is the "crashed processes viewer" app. Where is it? how
can I start it? ...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=460324
--- Comment #4 from sp ---
There's no/nothing resembling a "crashed processes viewer" either in system
settings or krunner.
Is there a terminal/konsole command that can be used?
Don't know if its the right one but in konsole
https://bugs.kde.org/show_bug.cgi?id=460324
--- Comment #6 from sp ---
coredumpctl returns: No coredumps found.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=419897
SP changed:
What|Removed |Added
CC||scp.stj...@gmail.com
--- Comment #4 from SP ---
(In
https://bugs.kde.org/show_bug.cgi?id=419897
--- Comment #5 from SP ---
Discovered that if the desktop kdeconnect widget is made sticky, so that the
window stays open, one can drag and drop files from the desktop and they will
be deposited in the default Download folder on the phone. The error
https://bugs.kde.org/show_bug.cgi?id=419897
--- Comment #7 from SP ---
(In reply to Marek from comment #6)
> Could this be related to https://bugs.kde.org/show_bug.cgi?id=443155 ?
No - that pertains to files sent from the phone to the desktop - whereas I have
no problem doing that with
https://bugs.kde.org/show_bug.cgi?id=486863
--- Comment #4 from sp ---
Can confirm that it still happens under plasma 6.1
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=486863
--- Comment #3 from sp ---
(In reply to Akseli Lahtinen from comment #2)
> Hi, do you have multiple monitors? Do you get this issue on Wayland?
Hello,
Single monitor only, asus pa329q. Connected with display port to asus rx7900xtx
on pcie 1st-s
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: generic-crash
Assignee: plasma-b...@kde.org
Reporter: sp...@gmx.com
Target Milestone: 1.0
Application: plasmashell (6.0.3)
Qt Version: 6.6.2
Frameworks Version: 6.0.0
Operating
https://bugs.kde.org/show_bug.cgi?id=484687
--- Comment #1 from sp ---
Created attachment 167906
--> https://bugs.kde.org/attachment.cgi?id=167906&action=edit
New crash information added by DrKonqi
DrKonqi auto-attaching complete backtrace.
--
You are receiving this mail because:
.02.1
Platform: Neon
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: dolphin-bugs-n...@kde.org
Reporter: sp...@gmx.com
CC: kfm-de...@kde.org
Target Mile
https://bugs.kde.org/show_bug.cgi?id=484687
--- Comment #3 from sp ---
Video driver is amdgpu.
More or less 9 times out 10, when monitor goes to powersave/sleep, when waking
it up, plasmashell crashes. So it almost always crashes.
"Crash report" lets us send "automatic" c
https://bugs.kde.org/show_bug.cgi?id=470062
sp changed:
What|Removed |Added
CC||sp...@gmx.com
--- Comment #2 from sp ---
I too have a
https://bugs.kde.org/show_bug.cgi?id=486863
--- Comment #1 from sp ---
Created attachment 169366
--> https://bugs.kde.org/attachment.cgi?id=169366&action=edit
New crash information added by DrKonqi
DrKonqi auto-attaching complete backtrace.
--
You are receiving this mail because:
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: generic-crash
Assignee: plasma-b...@kde.org
Reporter: sp...@gmx.com
Target Milestone: 1.0
Application: plasmashell (6.0.4)
Qt Version: 6.7.0
Frameworks Version: 6.1.0
Operating
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #16 from SP ---
Does anyone have further suggestions on this bug? It is very erratic. After
some updates it appears to vanish - with both monitors powered on after logging
into a desktop session from SDDM. Then after a few days it
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #17 from SP ---
I suspect this has something to do with the way the files in
./local/share/kscreen are addressed.
I experimented:
1. Moving all files and the output directory in kscreen to a backup directory
and rebooting. Result - only
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #18 from SP ---
Following an update of mesa libraries yesterday it is taking numerous reboots
to be able to login to a KDE Plasma Wayland session with both monitors powered
on. Incredibly frustrating. Is it possible to configure the
https://bugs.kde.org/show_bug.cgi?id=448220
SP changed:
What|Removed |Added
Version|5.23.4 |5.24.2
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=448220
SP changed:
What|Removed |Added
Attachment #147010|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #21 from SP ---
Created attachment 147371
--> https://bugs.kde.org/attachment.cgi?id=147371&action=edit
drm-dmesg log with both monitors powered on after login to KDE
Output of journalctl --boot 0 | grep kwin_wayland_drm wi
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #22 from SP ---
@ZamundaaaI have attached to outputs of "journalctl --boot 0 | grep
kwin_wayland_drm" - one with only one monitor display powered on after login
from SDDM to KDE and the other with both monitors remaining powere
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #23 from SP ---
(In reply to Zamundaaa from comment #19)
> As they make a difference, could you upload the configuration files?
>
> Your dmesg output doesn't tell that anything is wrong at all :/
> Can you try getting
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #24 from SP ---
Created attachment 147372
--> https://bugs.kde.org/attachment.cgi?id=147372&action=edit
tar director of .local/share/kscreen
Attached is the compressed directory ".local/share/kscreen". In a previous
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #25 from SP ---
Created attachment 147374
--> https://bugs.kde.org/attachment.cgi?id=147374&action=edit
Output of script drm-debug
The output of script drm-debug
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #26 from SP ---
(In reply to Zamundaaa from comment #19)
> As they make a difference, could you upload the configuration files?
>
> Your dmesg output doesn't tell that anything is wrong at all :/
> Can you try getting
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #27 from SP ---
> > One thing you could try as a workaround is forcing the legacy driver mode,
> > by putting KWIN_DRM_NO_AMS=1 into /etc/environment and rebooting
Did so but it makes no difference
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #29 from SP ---
Created attachment 147380
--> https://bugs.kde.org/attachment.cgi?id=147380&action=edit
Files in ./local/share/kscreen
Files generated in ./local/share/kscreen after directory was removed and
computer rebooted
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #30 from SP ---
(In reply to Zamundaaa from comment #28)
> The output of the script directly is not useful, only the files that it
> generates are.
>
> > Did so but it makes no difference
> ok, that should more or les
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #31 from SP ---
(In reply to SP from comment #30)
> (In reply to Zamundaaa from comment #28)
> > The output of the script directly is not useful, only the files that it
> > generates are.
> >
> > > Did so but
https://bugs.kde.org/show_bug.cgi?id=448220
SP changed:
What|Removed |Added
Version|5.24.2 |5.24.3
--- Comment #32 from SP ---
It took more than
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #33 from SP ---
On my other computer with almost identical hardware, OS and updates both
monitors remained powered on after login to KDE after first boot. This is not
always the case.
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #35 from SP ---
(In reply to Zamundaaa from comment #34)
> (In reply to SP from comment #29)
> > Created attachment 147380 [details]
> > Files in ./local/share/kscreen
> >
> > Files generated in ./local/share/
https://bugs.kde.org/show_bug.cgi?id=450871
SP changed:
What|Removed |Added
CC||scp.stj...@gmail.com
--- Comment #4 from SP ---
Related
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #36 from SP ---
Possibly related bug 450871 KDE Plasma Multi-Monitor BUG - No Video Output on
one Monitor (No Output Signal) & Display Issue on other monitor after update to
5.24.2
https://bugs.kde.org/show_bug.cgi?id=450871
--
You
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #38 from SP ---
(In reply to Zamundaaa from comment #37)
> Created attachment 147448 [details]
> very verbose logging
>
> Sigh, Dolphin hid the ".local" folder in the archive...
> Looking at the configs,
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #40 from SP ---
(In reply to Zamundaaa from comment #39)
> Tbh I don't know a thing about how to build patched packages for rpm based
> distros either.
> For building and installing directly though,
> git clone https://inve
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #41 from SP ---
Created attachment 147473
--> https://bugs.kde.org/attachment.cgi?id=147473&action=edit
log of journalctl --boot 0 | grep kwin_wayland_drm
Here is the result of journalctl --boot 0 | grep kwin_wayl
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #42 from SP ---
(In reply to Zamundaaa from comment #39)
> Tbh I don't know a thing about how to build patched packages for rpm based
> distros either.
> For building and installing directly though,
> git clone https://inve
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #43 from SP ---
Created attachment 147482
--> https://bugs.kde.org/attachment.cgi?id=147482&action=edit
compressed journalctl log
I downloaded kwin from git a second time and reapplied the patchfile ran cmake
etc - rebooted with o
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #45 from SP ---
Created attachment 147632
--> https://bugs.kde.org/attachment.cgi?id=147632&action=edit
Tar containing three text files results of drm_info
@Zamundaaa I have attached drm_info_reports,tgz which contains three tex
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #49 from SP ---
Created attachment 147650
--> https://bugs.kde.org/attachment.cgi?id=147650&action=edit
drm-info of both monitors active but mirroring the display of only one
@Zamudaaa I ran drm_info again on broken sessions and t
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #50 from SP ---
> 2. if you uninstall xf86-video-amdgpu, reboot and let the default Xorg
> driver take over, which uses the same driver interface as kwin_wayland, do
> sddm and the Plasma X11 session start exhibiting broken be
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #51 from SP ---
(In reply to SP from comment #50)
> > 2. if you uninstall xf86-video-amdgpu, reboot and let the default Xorg
> > driver take over, which uses the same driver interface as kwin_wayland, do
> > sddm and the
https://bugs.kde.org/show_bug.cgi?id=451797
Bug ID: 451797
Summary: Invalid KPackage 'kcm_kwinrules
Product: kwin
Version: 5.23.4
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=451797
--- Comment #2 from SP ---
(In reply to Ismael Asensio from comment #1)
> Thanks for your bug report!
>
> Can you try running "kcmshell5 kcm_kwinrules" and also opening it from the
> application menu (Alt+F3 -> More option
https://bugs.kde.org/show_bug.cgi?id=451797
--- Comment #3 from SP ---
(In reply to SP from comment #2)
> (In reply to Ismael Asensio from comment #1)
> > Thanks for your bug report!
> >
> > Can you try running "kcmshell5 kcm_kwinrules" and also opening it from t
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #53 from SP ---
(In reply to Zamundaaa from comment #44)
> The only suspicious thing I can see here is that in some areas of the log
> there's commits without any pipelines printed:
> > kwin_wayland_drm: com
https://bugs.kde.org/show_bug.cgi?id=448220
SP changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REOPENED
https://bugs.kde.org/show_bug.cgi?id=451797
--- Comment #6 from SP ---
(In reply to Alexander Lohnau from comment #5)
> Please check if /usr/share/kpackage/kcms/kcm_kwinrules/ exists and list the
> containing files
Yes - as I mentioned in my earlier report that directory does exist.
"
https://bugs.kde.org/show_bug.cgi?id=451797
--- Comment #7 from SP ---
(In reply to SP from comment #6)
> (In reply to Alexander Lohnau from comment #5)
> > Please check if /usr/share/kpackage/kcms/kcm_kwinrules/ exists and list the
> > containing files
>
> Yes - as I me
https://bugs.kde.org/show_bug.cgi?id=436104
Bug ID: 436104
Summary: Skype creates hotspot in upper left corner of desktop
in Plasma Wayland session
Product: kwin
Version: 5.20.5
Platform: Fedora RPMs
OS: Lin
https://bugs.kde.org/show_bug.cgi?id=436104
--- Comment #3 from SP ---
@Na(In reply to Nate Graham from comment #1)
> See also Bug 432744. Possibly already fixed.
Thanks Nate.
It does appear to be related to xembedsniproxy. Doing a killall xembedsniproxy
resolves the problem but also remo
https://bugs.kde.org/show_bug.cgi?id=436104
--- Comment #4 from SP ---
(In reply to Nate Graham from comment #2)
> Where are you getting Skype from? I don't have it available in my distro
> repos, and if I try the FlatHub version, it crashes on launch in my Wayland
> session. :
https://bugs.kde.org/show_bug.cgi?id=436104
--- Comment #5 from SP ---
My workaround is to disable xembedsniproxy by renaming it xembedsniproxy.org.
Add the application Skype to the system tray as a widget. In Skype
Tools/Settings/General enable Automatically start Skype; disable Launch Skype
https://bugs.kde.org/show_bug.cgi?id=436104
--- Comment #7 from SP ---
No, I am using Skype for Linux. Skype for Linux is definitely utilizing in
some way xembedsniproxy as disabling that program resolves the problem of the
hotspot in the upper left corner of the desktop. The downside is that
https://bugs.kde.org/show_bug.cgi?id=436104
--- Comment #8 from SP ---
Is there an updated list of programs for KDE that provide SNI/Appindicator
icons and those that still require xembedsniproxy?
It seems that any program that calls xembedsniproxy in Wayland will place the
transparent icon
https://bugs.kde.org/show_bug.cgi?id=436104
--- Comment #9 from SP ---
Correction:
So far, the only program *I have discovered* that does this
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=436104
--- Comment #11 from SP ---
(In reply to Konrad Materka from comment #10)
> There are two protocols for tray icons:
> * obsole XEmbed - some desktop dropped support for it entirely. KDE has some
> xembedsniproxy to translate XEmbed to SNI,
https://bugs.kde.org/show_bug.cgi?id=436104
SP changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
: wishlist
Priority: NOR
Component: general
Assignee: unassigned-b...@kde.org
Reporter: sp...@gmx.com
Target Milestone: ---
Feature request :
add pdf as supported files that can have their content searched.
--
You are receiving this mail because:
You are
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: general
Assignee: neon-b...@kde.org
Reporter: sp...@gmx.com
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
Target Milestone
https://bugs.kde.org/show_bug.cgi?id=440036
SP changed:
What|Removed |Added
Resolution|FIXED |---
Keywords
https://bugs.kde.org/show_bug.cgi?id=440036
--- Comment #6 from SP ---
(In reply to SP from comment #5)
> Since the last few updates "Show in Activities" and the option to move to a
> specific Activity has disappeared from the (right-click) title bar menu of
> open windows. N
https://bugs.kde.org/show_bug.cgi?id=440036
--- Comment #8 from SP ---
(In reply to Alex from comment #7)
> I still have it In 5.27.8.
And now I see it has reappeared on one machine but not on mine. Odd. Will
report when I resolve this.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=440036
--- Comment #9 from SP ---
(In reply to Alex from comment #7)
> I still have it In 5.27.8.
Is there a header or script that governs this? I have tried updating etc all
to no avail. Cannot figure what is disabling this suddenly on my sys
https://bugs.kde.org/show_bug.cgi?id=440036
--- Comment #13 from SP ---
(In reply to Oded Arbel from comment #12)
> I have the issue with the activities menu disappearing from time to time on
> latest Plasma 5 - in my use case it's because the activityd Daemon failed to
> start o
https://bugs.kde.org/show_bug.cgi?id=440036
--- Comment #14 from SP ---
(In reply to Alex from comment #10)
> Do you use the same window decorations? What about X11 vs Wayland? I think
> Wayland still has problems with Activites.
Alex, you are right. The Activities menu reappears
https://bugs.kde.org/show_bug.cgi?id=440036
--- Comment #16 from SP ---
(In reply to Oded Arbel from comment #15)
> (In reply to SP from comment #13)
> > I am mystified. I cannot locate any service "plasma-activityd".
>
> Apologies, the systemd
https://bugs.kde.org/show_bug.cgi?id=422682
SP changed:
What|Removed |Added
CC||scp.stj...@gmail.com
--- Comment #40 from SP ---
(In
https://bugs.kde.org/show_bug.cgi?id=422682
--- Comment #42 from SP ---
(In reply to gudvinr+kde from comment #41)
> (In reply to SP from comment #40)
>
> > KDE Plasma Version: 5.27.8
>
> 5.27.8 released in September, fix for that issue didn't exist back then.
Agreed
https://bugs.kde.org/show_bug.cgi?id=440036
--- Comment #4 from SP ---
Thank you.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=461745
--- Comment #2 from sp ---
(In reply to David Redondo from comment #1)
> Can you confirm the real speed is higher than the one plasma-systemmonitor
> shows?
Yes, the real speed is higher than the one plasma-systemmonitor shows.
Running for examp
https://bugs.kde.org/show_bug.cgi?id=448173
Bug ID: 448173
Summary: One or both dual monitors powers off after login to
Wayland KDE
Product: kde
Version: unspecified
Platform: Fedora RPMs
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=448220
Bug ID: 448220
Summary: One or both dual monitors powers off after login to
Wayland KDE
Product: kwin
Version: 5.23.4
Platform: Fedora RPMs
OS: Linux
S
https://bugs.kde.org/show_bug.cgi?id=448220
SP changed:
What|Removed |Added
Keywords||accessibility, multiscreen
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #2 from SP ---
@Vlad Zahorodnii Thanks - good to know that it is resolved in the next release.
I will wait until February for the finished release. Cannot run beta or
downgrade on these production machines.
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=448173
--- Comment #2 from SP ---
(In reply to Marco Martin from comment #1)
> what does the screen systemsetting module say? in there both monitors are
> configured to be enabled?
Yes both monitors are, of course, enabled in the Display Configuration
1 - 100 of 150 matches
Mail list logo
