https://bugs.kde.org/show_bug.cgi?id=383024
--- Comment #1 from SP <scp.stj...@gmail.com> ---
It appears to have been resolved.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=383024
Bug ID: 383024
Summary: After recent updates can no longer switch to
Activities
Product: plasmashell
Version: 5.10.4
Platform: Other
OS: Linux
Status:
https://bugs.kde.org/show_bug.cgi?id=382662
Bug ID: 382662
Summary: Leave screen dark
Product: plasmashell
Version: 5.10.1
Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
Severity: major
https://bugs.kde.org/show_bug.cgi?id=382662
--- Comment #1 from SP <scp.stj...@gmail.com> ---
I am guessing this is an SDDM bug - but I cannot see where to file that so I
have chosen "general". The theme in use is "Breeze"
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=379831
Bug ID: 379831
Summary: Could not find a suitable SoundController plugin
Product: minuet
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=379668
SP <scp.stj...@gmail.com> changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.kde.org/show_bug.cgi?id=379668
Bug ID: 379668
Summary: Minuet 0.2 will not start
Product: minuet
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: critical
https://bugs.kde.org/show_bug.cgi?id=379668
SP <scp.stj...@gmail.com> changed:
What|Removed |Added
Severity|critical|normal
--
You are rec
https://bugs.kde.org/show_bug.cgi?id=379831
SP <scp.stj...@gmail.com> changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.kde.org/show_bug.cgi?id=386408
--- Comment #9 from SP <scp.stj...@gmail.com> ---
(In reply to Christoph Feck from comment #8)
> Please also test 'qpdfview', which is a pure Qt program. If this reproduces
> the issue, the bug would be in the way Qt interacts with the pri
https://bugs.kde.org/show_bug.cgi?id=316497
SP <scp.stj...@gmail.com> changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Reso
https://bugs.kde.org/show_bug.cgi?id=386408
--- Comment #6 from SP <scp.stj...@gmail.com> ---
@Albert Astals Cid
I am not going to get into a pissing contest here but your logic is
questionable. If the printer prints correctly with other programs but not with
one program,
https://bugs.kde.org/show_bug.cgi?id=386408
--- Comment #2 from SP <scp.stj...@gmail.com> ---
(In reply to Albert Astals Cid from comment #1)
> Does print preview show the colors correctly?
Yes
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=386408
Bug ID: 386408
Summary: Text color printed incorrectly
Product: okular
Version: 1.0.0
Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=344180
--- Comment #27 from SP <scp.stj...@gmail.com> ---
Goodness, surprised to see this "bug" report revived after all these years.
After so many upgrades I had quite forgotten about the dashboard - which would
now seem inappropriate.
https://bugs.kde.org/show_bug.cgi?id=344180
--- Comment #28 from SP <scp.stj...@gmail.com> ---
@Thomas Platzer You are still using KDE4??? That's two years out of date! Kde
Applications 16.04 was released April 2016. 14.04 must have been pre December
2014. Treat yourself to an u
https://bugs.kde.org/show_bug.cgi?id=399732
--- Comment #3 from sp ---
well, I've tried it now and it works. Must have been the latest set of updates
that fixed it.
So guess you can close the ticket.
for information:
-I was using nvida proprietary drivers.
-And get the following errors just
https://bugs.kde.org/show_bug.cgi?id=400986
Bug ID: 400986
Summary: Cannot browse folders on device
Product: kdeconnect
Version: 1.3
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=400986
SP changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=400986
--- Comment #5 from SP ---
Solved:
According to ntoan96 ( bug 400703 )
"The newest version of kdeconnect on Android is 1.10 which only works fine with
kdeconnect 1.3.2 or later. Meanwhile, the kdeconnect package on Kubuntu is at
version 1.3.1. S
https://bugs.kde.org/show_bug.cgi?id=400986
SP changed:
What|Removed |Added
Resolution|FIXED |UPSTREAM
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=400703
--- Comment #5 from SP ---
Installing kde-connect-1.3.3-1.fc28 from Koji and rebooting resolved the
problem
https://koji.fedoraproject.org/koji/buildinfo?buildID=1163017
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=400703
SP changed:
What|Removed |Added
CC||scp.stj...@gmail.com
--- Comment #4 from SP ---
Thank
https://bugs.kde.org/show_bug.cgi?id=400945
--- Comment #2 from SP ---
(In reply to SP from comment #1)
> This is related to the bug I have reported bug 40096 and another bug 400935
> Might be related to a recent update related to fusermount? Or maybe related
> to kdeconnect not u
https://bugs.kde.org/show_bug.cgi?id=400945
SP changed:
What|Removed |Added
CC||scp.stj...@gmail.com
--- Comment #1 from SP
https://bugs.kde.org/show_bug.cgi?id=400945
--- Comment #3 from SP ---
Sorry bug 400986
(I'm getting dyslexic it seems)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=400780
SP changed:
What|Removed |Added
CC||scp.stj...@gmail.com
--- Comment #3 from SP ---
related
https://bugs.kde.org/show_bug.cgi?id=400986
--- Comment #4 from SP ---
also related:
Bug 400945
Bug 400780
Bug 400703
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=400986
--- Comment #1 from SP ---
I looked at the permissions for fusermount and realize that the stickybit was
not set - so:
chmod rwsr-xr-x /usr/bin/fusermount
I still cannot browse the device:
The file or folder
/run/user/1001/6a2c2a9ed051c297/storage
https://bugs.kde.org/show_bug.cgi?id=400935
SP changed:
What|Removed |Added
CC||scp.stj...@gmail.com
--- Comment #2 from SP ---
This may
https://bugs.kde.org/show_bug.cgi?id=400986
--- Comment #2 from SP ---
> and in .xsessions:
That should be .xsession-errors
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=400986
--- Comment #3 from SP ---
related: bug 400935
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=400935
--- Comment #4 from SP ---
@Tom Chiverton - Yes, it is always annoying. As you noted, installing
Kdeconnect 1.3.3 either from binary or from source resolves the problem. When
I attempted to do so on my Fedora system using the GUI installer, Apper
https://bugs.kde.org/show_bug.cgi?id=413069
sp changed:
What|Removed |Added
CC||sp...@gmx.com
--- Comment #1 from sp ---
I can also
https://bugs.kde.org/show_bug.cgi?id=429485
--- Comment #11 from sp ---
here's the result of systemctl --user status pipewire.service :
● pipewire.service - Multimedia Service
Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; vendor
preset: disabled)
Active: inactive
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=429485
--- Comment #16 from sp ---
1st:
sudo rm /usr/share/alsa-card-profile/mixer/profile-sets/audigy.conf
sudo reboot
result: did not work.
then:
sudo rm /lib/udev/rules.d/90-pipewire-alsa.rules
sudo reboot
result : DID work.
didn't bother to do : (you
https://bugs.kde.org/show_bug.cgi?id=429485
--- Comment #9 from sp ---
Hi,
In turning on pc today, I DID see the some updates and one of them being
pipewire0.3.16.
So I did the upgrade but nothing has change. Problem is still there.
I did the commands that you told me and and the second one
https://bugs.kde.org/show_bug.cgi?id=429485
--- Comment #5 from sp ---
You'll find attached the results of the various commands you asked. Hope it
helps.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=429485
--- Comment #7 from sp ---
Created attachment 133594
--> https://bugs.kde.org/attachment.cgi?id=133594=edit
log_dpkg_pulse-pipewire-ls-pw-cli
There you go. Again hope it helps.
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=429485
--- Comment #4 from sp ---
Created attachment 133592
--> https://bugs.kde.org/attachment.cgi?id=133592=edit
log of lsof
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=429485
--- Comment #3 from sp ---
Created attachment 133591
--> https://bugs.kde.org/attachment.cgi?id=133591=edit
log of systemctl
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=429485
--- Comment #2 from sp ---
Created attachment 133590
--> https://bugs.kde.org/attachment.cgi?id=133590=edit
log of journalctl
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=429485
--- Comment #14 from sp ---
The problem still persist.
Like I've said in the 1st entry, don’t know if this is related to the other
tickets about pipewire/pulseaudio. This one is a bit diferent.
I'v attached arecord-log... the result of running arecord
https://bugs.kde.org/show_bug.cgi?id=429485
--- Comment #13 from sp ---
Created attachment 133670
--> https://bugs.kde.org/attachment.cgi?id=133670=edit
arecord-log arecord -l and arecord -L in terminal
--
You are receiving this mail because:
You are watching all bug changes.
: 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
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:
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. :( Loo
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 XEmb
https://bugs.kde.org/show_bug.cgi?id=436104
SP changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
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
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 #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=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=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
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
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
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
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
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
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://invent.kd
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #41 from SP ---
Created attachment 147473
--> https://bugs.kde.org/attachment.cgi?id=147473=edit
log of journalctl --boot 0 | grep kwin_wayland_drm
Here is the result of journalctl --boot 0 | grep kwin_wayland_drm >
kwin_wayla
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #43 from SP ---
Created attachment 147482
--> https://bugs.kde.org/attachment.cgi?id=147482=edit
compressed journalctl log
I downloaded kwin from git a second time and reapplied the patchfile ran cmake
etc - rebooted with only
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
--
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 #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://invent.kd
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 #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/sh
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 #21 from SP ---
Created attachment 147371
--> https://bugs.kde.org/attachment.cgi?id=147371=edit
drm-dmesg log with both monitors powered on after login to KDE
Output of journalctl --boot 0 | grep kwin_wayland_drm with both monit
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #24 from SP ---
Created attachment 147372
--> https://bugs.kde.org/attachment.cgi?id=147372=edit
tar director of .local/share/kscreen
Attached is the compressed directory ".local/share/kscreen". In a previous
experiment
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #25 from SP ---
Created attachment 147374
--> https://bugs.kde.org/attachment.cgi?id=147374=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
SP changed:
What|Removed |Added
Attachment #147010|0 |1
is obsolete
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 #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 #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
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
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #29 from SP ---
Created attachment 147380
--> https://bugs.kde.org/attachment.cgi?id=147380=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 #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 #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
--- 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
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 #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 #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 #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
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=379831
SP changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution
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 is
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
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 #10 from SP ---
Created attachment 147051
--> https://bugs.kde.org/attachment.cgi?id=147051=edit
Additional output from login to wayland session
The output from logging into a wayland session today has more information than
the previ
https://bugs.kde.org/show_bug.cgi?id=448220
--- Comment #14 from SP ---
Created attachment 147076
--> https://bugs.kde.org/attachment.cgi?id=147076=edit
dmesg-drm-debug.log
Attached is the dmesg-drm-debug.log requested by @Zamundaaa
--
You are receiving this mail because:
You are watch
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_construct: Failed
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=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
1 - 100 of 146 matches
Mail list logo
