https://bugs.kde.org/show_bug.cgi?id=375373
--- Comment #4 from Alexandre Pereira <pereira.a...@gmail.com> ---
Thanks, just updated git packages and confirm it is working.
Thanks very much for the quick feedback !
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=375373
--- Comment #2 from Alexandre Pereira <pereira.a...@gmail.com> ---
Ok, I think i discovered what is happening: unpin works while app is not
running, if pinning is for "all activities".
If pinning just to "one activity",
https://bugs.kde.org/show_bug.cgi?id=375372
--- Comment #2 from Alexandre Pereira <pereira.a...@gmail.com> ---
It would be extremely nice!
Thanks.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=375372
Bug ID: 375372
Summary: Ability to choose activity to pin apps while they are
not running
Product: plasmashell
Version: master
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=375373
Bug ID: 375373
Summary: unpinning an app in taskmanager, while that app inst
running, doesn't work
Product: plasmashell
Version: master
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=385135
--- Comment #4 from Alexandre Pereira ---
humufr,
even now on plasma git packages, its the same.
just follow the instruction: edit ~/.config/plasmashellrc and remove the
[ScreenConnectors] section.
this happens because monitors have one name on Xorg
https://bugs.kde.org/show_bug.cgi?id=393723
--- Comment #5 from Alexandre Pereira <pereira.a...@gmail.com> ---
> Alexandre what distro, GPU, GPU driver do you use? X11 or Wayland?
I am using Kubuntu CI unstable packages and openSUSE KDE git packages.
X11 works perfectly. The proble
https://bugs.kde.org/show_bug.cgi?id=393723
--- Comment #6 from Alexandre Pereira <pereira.a...@gmail.com> ---
Are you using this package ?
https://packaging.neon.kde.org/kde/kwin.git/commit/
It seems to be following +kwin (4:5.12.4-1).
It should not show in Manjaro, as they are using
https://bugs.kde.org/show_bug.cgi?id=393723
--- Comment #7 from Alexandre Pereira <pereira.a...@gmail.com> ---
Sorry, forgot to mention that I have an ATI video card.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=393723
Bug ID: 393723
Summary: Kwin master with bad blur effect on secondary monitor
( works perfectly on primary )
Product: kwin
Version: git master
Platform: Other
OS:
https://bugs.kde.org/show_bug.cgi?id=398219
--- Comment #11 from Alexandre Pereira ---
Just did :) All good !
Besides working properly, I notice that now it says the proper name of the
monitor, even if is primary ( usually always said on primary ).
To be honest, this has happened to me
https://bugs.kde.org/show_bug.cgi?id=398219
--- Comment #4 from Alexandre Pereira ---
Created attachment 114774
--> https://bugs.kde.org/attachment.cgi?id=114774=edit
Image of System settings screen section
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398219
--- Comment #2 from Alexandre Pereira ---
just tested it with master branch ( using gentoo, so this is very easy to do ).
see this pastebin, ran with latte-dock -dr : https://pastebin.com/kkhJr2zc
I tried to change one dock from primary to another
https://bugs.kde.org/show_bug.cgi?id=398219
--- Comment #6 from Alexandre Pereira ---
Created attachment 114777
--> https://bugs.kde.org/attachment.cgi?id=114777=edit
Latte Dock RC file
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398219
--- Comment #5 from Alexandre Pereira ---
Created attachment 114775
--> https://bugs.kde.org/attachment.cgi?id=114775=edit
Latte Dock Layout File
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398219
--- Comment #7 from Alexandre Pereira ---
Does these attachments help ?
I can try to make a video also... when OBS emerges :P
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398219
--- Comment #13 from Alexandre Pereira ---
Just a heads up, because I think it may be related to this fix, but don't know
for sure.
Right now, If I change monitor names ( Like switching from Xorg to Wayland or
vice versa ), latte-dock doesn't start
https://bugs.kde.org/show_bug.cgi?id=398220
--- Comment #3 from Alexandre Pereira ---
thanx David for the reply.
Sorry for the lame video, but i got a invisible window, a konsole window, and
recorded a video:
https://youtu.be/-c5my2wp0tg
the window is a konsole window, other konsole windows
https://bugs.kde.org/show_bug.cgi?id=385135
Alexandre Pereira <pereira.a...@gmail.com> changed:
What|Removed |Added
CC||per
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #32 from Alexandre Pereira ---
ok, i understand, its a corner case that you can't even test in your system.
thanks for all the assistance ! if i find out something interesting I will let
you know.
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=361135
--- Comment #2 from Alexandre Pereira ---
(In reply to Andrew Crouthamel from comment #1)
> Dear Bug Submitter,
>
> This bug has been stagnant for a long time. Could you help us out and
> re-test if the bug is valid in the latest version?
https://bugs.kde.org/show_bug.cgi?id=398220
--- Comment #8 from Alexandre Pereira ---
Also, found out ( hinted by a user on reddit with this problem also ), that the
window is recoverable. Minimizing the window ( through keyboard ) and then
restoring it again, makes ir become visible and working
https://bugs.kde.org/show_bug.cgi?id=400753
Bug ID: 400753
Summary: Add support for custom StartupWMClass
Product: Falkon
Version: unspecified
Platform: unspecified
OS: Linux
Status: REPORTED
Severity:
https://bugs.kde.org/show_bug.cgi?id=398220
--- Comment #7 from Alexandre Pereira ---
Just to confirm comment #4, in my case its also only Xwayland apps.
It was happening in kde apps also, because they were using Xwayland ( using
opensuse, they seem to use xwayland if not using
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #9 from Alexandre Pereira ---
It does have a trial, but its a once, for 2 weeks.
Can you make a patch/version that outputs more debug into the terminal ? Or can
you tell me where to look for/ which function to analyse, and I will do some
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #34 from Alexandre Pereira ---
More info:
Seems the problem goes away with that checkbox because kwin stops detecting
that window.
More testing, shows that there is a problem with multiple rules for the same
app/window, starting 5.14
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #33 from Alexandre Pereira ---
Freaking nailed it, found out what was the problem
See video : https://drive.google.com/open?id=10Q9pNV959RyGSCbr6fh9WPJEQSXdQudC
Don't know why that started to be a problem. Those rules are actually from
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #4 from Alexandre Pereira ---
(In reply to Michail Vourlakos from comment #3)
> (In reply to Alexandre Pereira from comment #2)
> > (In reply to Michail Vourlakos from comment #1)
> > > Is this happening with other wine ap
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #6 from Alexandre Pereira ---
more testing:
With more windows ( with 3 windows running ), plasmashell keeps using 0%~1%
cpu, but latte-dock increases to 10%~15%.
Seems for each windows, latte-dock increases around 5% cpu.
testing
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #7 from Alexandre Pereira ---
unfortunatly the app is a subscription based app ( I am paying for using the
app, which is vital for work )
Is there any way I can help debugging what latte-dock is doing ?
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #14 from Alexandre Pereira ---
(In reply to Michail Vourlakos from comment #13)
> (In reply to Alexandre Pereira from comment #11)
> > I tried "strace latte-dock" in a terminal window.
> > There is definitly diff
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #17 from Alexandre Pereira ---
(In reply to Michail Vourlakos from comment #16)
> (In reply to Alexandre Pereira from comment #14)
> > (In reply to Michail Vourlakos from comment #13)
> > > (In reply to Alexandre Pereir
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #20 from Alexandre Pereira ---
[debug 14:23:24.305305] - Modal : false
[debug 14:23:24.305305] - Demands attention : false
[debug 14:23:24.305305] - Prop1: QFlags(0x8000) Prop2 QFlags()
[debug 14:23:24.306306] - Modal : false
[debug 14
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #12 from Alexandre Pereira ---
(In reply to Michail Vourlakos from comment #10)
> (In reply to Alexandre Pereira from comment #9)
> > It does have a trial, but its a once, for 2 weeks.
> >
> > Can you make a patch/vers
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #11 from Alexandre Pereira ---
I tried "strace latte-dock" in a terminal window.
There is definitly different behaviour when idle before and after opening
"SierraCharts" wine app.
I did a video of it, "SierraChar
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #15 from Alexandre Pereira ---
btw, here is the video link:
https://drive.google.com/file/d/1GS13ZZMKeKgwzZbRSma23CXsEIb4QKX7/view?usp=sharing
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #18 from Alexandre Pereira ---
This is what I am getting:
[debug 13:46:43.304304] - Prop1: QFlags(0x8000) Prop2 QFlags()
[debug 13:46:43.305305] - Prop1: QFlags(0x2000) Prop2 QFlags()
[debug 13:46:43.306306] - Prop1: QFlags(0x8000
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #25 from Alexandre Pereira ---
Also, more info:
I made a debug print on every function call of that file. only
windowChangedProxy was "spammed".
Also, I tested disabling (removing) the windowChangedProxy signal connect, so
its
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #28 from Alexandre Pereira ---
Ok, found out how to make latte-dock use less cpu: unpin all my latte-dock
pinned launchers.
That made it almost use no cpu.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #27 from Alexandre Pereira ---
I am doing more investigations on this.
Right now I have latte-dock using between 0%~1% cpu with 2 windows. most of the
time its at 0%. But its like this because I "rm -rf .config/latte*".
https://bugs.kde.org/show_bug.cgi?id=399149
Alexandre Pereira changed:
What|Removed |Added
Resolution|FIXED |---
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=399149
Alexandre Pereira changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #30 from Alexandre Pereira ---
(In reply to Michail Vourlakos from comment #29)
> (In reply to Alexandre Pereira from comment #28)
> > Ok, found out how to make latte-dock use less cpu: unpin all my latte-dock
> > p
https://bugs.kde.org/show_bug.cgi?id=398219
Bug ID: 398219
Summary: Unable to set latte-dock other than on primary monitor
upon restart
Product: latte-dock
Version: 0.8.0
Platform: Gentoo Packages
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=398220
Bug ID: 398220
Summary: Invisible windows appear randomly on wayland
Product: kwin
Version: git master
Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=398220
--- Comment #1 from Alexandre Pereira ---
Example of "present windows" effect showing an area where an invisible window
is, and its close button next to it.
Clicking on that button results in kwin crash.
https://imgur.com/a/hMInSn
https://bugs.kde.org/show_bug.cgi?id=399149
Bug ID: 399149
Summary: Wine application with latte-dock master and plasma
5.14 beta always uses cpu
Product: latte-dock
Version: git (master)
Platform: Other
OS:
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #2 from Alexandre Pereira ---
(In reply to Michail Vourlakos from comment #1)
> Is this happening with other wine apps?
Sorry for the late reply.
I have been doing more testing, and no... actually is the only wine app that
d
https://bugs.kde.org/show_bug.cgi?id=400753
--- Comment #5 from Alexandre Pereira ---
thanks for you comment.
It would be really cool. The way I am using falkon is to have a default profile
where I do normal web browsing, and then have falkon with custom profiles (
where I pick a template
https://bugs.kde.org/show_bug.cgi?id=402552
--- Comment #2 from Alexandre Pereira ---
What do you mean help turn from that into steps ? Only use 1 virtual desktop ?
Sorry, my valgrind experience is very very limited.
here is what i got:
valgrind --leak-check=yes plasmashell
==6392
https://bugs.kde.org/show_bug.cgi?id=402552
Bug ID: 402552
Summary: Crash of plasmashell on latest git opensuse packages (
current day 25-12-2018)
Product: kde
Version: unspecified
Platform: unspecified
OS:
https://bugs.kde.org/show_bug.cgi?id=400753
--- Comment #3 from Alexandre Pereira ---
Thank you !! very much
I will test ASAP on opensuse git packages !
Will this work on wayland too ?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=402552
--- Comment #3 from Alexandre Pereira ---
I think i have a reproducable method, on wayland:
* Set left mouse button to "switch application window" on plasmashell plasma
desktop configurations.
* Click/Focus on a window and then
https://bugs.kde.org/show_bug.cgi?id=405628
Bug ID: 405628
Summary: plasmashell crash when clicking on opensuse updater
Product: kde
Version: unspecified
Platform: unspecified
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #35 from Alexandre Pereira ---
Hi,
Can you give some info as how and where it was resolved ?
I still suffer from this problem :( Only workaround I found was using the app
through explorer.exe virtual desktop, but its bad, wine's virtual
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #42 from Alexandre Pereira ---
Finally, been doing more testing and am able to reproduce with konsole.
OK, so no need to open lots of konsole apps, only 1 or 2 will suffice ( i test
with 2 because I run sometimes 2 windows of the wine app
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #49 from Alexandre Pereira ---
(In reply to Michail Vourlakos from comment #48)
> (In reply to Alexandre Pereira from comment #47)
> > I think I solved it ( I can be wrong, as the history of this bug report
> > shows )
&
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #53 from Alexandre Pereira ---
(In reply to Michail Vourlakos from comment #52)
> (In reply to Alexandre Pereira from comment #51)
> > Another workaround is to keep latte-dock and kwin rules as it is (using
> > title rule
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #37 from Alexandre Pereira ---
Unfortunatly i cannot hide the clock ( and whats even worse, the title has
clock and network packets info ).
I did a test, which some 6 konsole windows running "qdbus $KONSOLE_DBUS_SE
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #40 from Alexandre Pereira ---
Also, sorry, in konsole, options for title be app name to be disabled ( or
else, the title will always be the app running )
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #43 from Alexandre Pereira ---
Created attachment 117964
--> https://bugs.kde.org/attachment.cgi?id=117964=edit
kwin rule affecting konsole
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #46 from Alexandre Pereira ---
(In reply to Michail Vourlakos from comment #45)
> (In reply to Alexandre Pereira from comment #44)
> > OK, more testing:
> >
> > setting update frequency to 5 seconds, latte-dock
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #55 from Alexandre Pereira ---
in what way ? the app changing its title ? or the kwin rules part ?
if the app changing its title, i will search for an easier way
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #39 from Alexandre Pereira ---
sorry, the command is correct, but only for fish shell.
for bash its :
qdbus $KONSOLE_DBUS_SERVICE $KONSOLE_DBUS_SESSION
org.kde.konsole.Session.setTitle 1 `date +%s%N`
what I do is create a date.sh
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #44 from Alexandre Pereira ---
OK, more testing:
setting update frequency to 5 seconds, latte-dock usage is almost none, being
at 0% most of the time and then from time to time ( i guess 5 seconds ) a 2%
usage.
If you are having trouble
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #47 from Alexandre Pereira ---
I think I solved it ( I can be wrong, as the history of this bug report shows )
I think the latte-dock high cpu usage with when kwin is using a rule that
compares the title.
So in the konsole test, i removed
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #51 from Alexandre Pereira ---
Another workaround is to keep latte-dock and kwin rules as it is (using title
rules), but instead of using latte-dock taskmanager, use a latte-dock panel and
then add the plasma icon taskmanager into it.
So
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #63 from Alexandre Pereira ---
Did you had alot of pinned apps ? I noticed that if I "start clean" with no
pinned apps, cpu usage is nowhere near as normal. Readding them makes cpu usage
go again high.
Well, ok, if I am able t
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #67 from Alexandre Pereira ---
(In reply to Michail Vourlakos from comment #66)
> If you run latte through command prompt with, latte-dock -d
>
> Do you get something interesting especially when the issue appears?
no, not really
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #65 from Alexandre Pereira ---
(In reply to Michail Vourlakos from comment #64)
> (In reply to Alexandre Pereira from comment #63)
> >
> > It sucks that you cannot reproduce it, makes it really hard. If I can give
> >
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #61 from Alexandre Pereira ---
btw, don't know if this is important:
I was just testing with new latte-dock configs, and I noticed that if I
praticly don't have any launchers pinned, it seems like it doesn't use alot of
cpu
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #59 from Alexandre Pereira ---
Created attachment 117969
--> https://bugs.kde.org/attachment.cgi?id=117969=edit
latte config files
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #60 from Alexandre Pereira ---
it does happen, with your kwin rules and script. So uploaded latte config
files.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=406439
Bug ID: 406439
Summary: plasma shell crashes on startup if using a panel with
system tray
Product: plasmashell
Version: master
Platform: openSUSE RPMs
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=406439
--- Comment #2 from Alexandre Pereira ---
(In reply to David Edmundson from comment #1)
> What Qt version?
5.12.2
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #69 from Alexandre Pereira ---
(In reply to Michail Vourlakos from comment #68)
> (In reply to Alexandre Pereira from comment #67)
> > (In reply to Michail Vourlakos from comment #66)
> >
>
> is it possible to test aga
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #77 from Alexandre Pereira ---
(In reply to Michail Vourlakos from comment #76)
> (In reply to Alexandre Pereira from comment #75)
> > (In reply to Michail Vourlakos from comment #74)
> > > If you are using latest git vers
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #71 from Alexandre Pereira ---
(In reply to Michail Vourlakos from comment #70)
> (In reply to Alexandre Pereira from comment #69)
> > (In reply to Michail Vourlakos from comment #68)
> > > (In reply to Alexandre Pereir
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #72 from Alexandre Pereira ---
Created attachment 120359
--> https://bugs.kde.org/attachment.cgi?id=120359=edit
latest git version with top
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #73 from Alexandre Pereira ---
attached screenshot showing latte-dock using high cpu:
notice: Disconnecting the sierrachart app, actually makes it not constantly
update the title. So at least **visibly** the title is not changing.
I
https://bugs.kde.org/show_bug.cgi?id=399149
--- Comment #75 from Alexandre Pereira ---
(In reply to Michail Vourlakos from comment #74)
> If you are using latest git version then the issue is different...
>
> 1. Which commit is your Latte git version using?
> 2. The Latte git versi
https://bugs.kde.org/show_bug.cgi?id=408534
--- Comment #3 from Alexandre Pereira ---
Created attachment 120767
--> https://bugs.kde.org/attachment.cgi?id=120767=edit
chromium gmail desktop file
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408534
--- Comment #2 from Alexandre Pereira ---
(In reply to Michail Vourlakos from comment #1)
> 1. Is this reproducable under X11?
> 2. Can you send also the desktop file in question?
1. It doesn't seem to, at least I cannot trigger it. Seems its w
https://bugs.kde.org/show_bug.cgi?id=408534
--- Comment #5 from Alexandre Pereira ---
better confirmed with whatsapp firefox profile .desktop file
It works properly with X11 and not with Wayland ( the chromium example could be
dubious, because on X11 chromium sets the correct startupwmclass
https://bugs.kde.org/show_bug.cgi?id=408534
--- Comment #4 from Alexandre Pereira ---
Created attachment 120768
--> https://bugs.kde.org/attachment.cgi?id=120768=edit
whatsapp firefox profile
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408534
--- Comment #7 from Alexandre Pereira ---
(In reply to Michail Vourlakos from comment #6)
> please send a more general desktop file demonstrating the issue, I cant
> reproduce with the ones send...
>
> Is there any other application with
https://bugs.kde.org/show_bug.cgi?id=408534
Bug ID: 408534
Summary: Wayland: Launcher above "original launcher" when using
applications with incorrect StartupWMCLASS
Product: lattedock
Version: git (master)
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=408534
--- Comment #11 from Alexandre Pereira ---
this may be too soon, since testing for 15 minutes, but after changing kde to
unstable
kde repositories on opensuse ( using git packages for plasma and kde apps and
kde frameworks ), instantly and without
https://bugs.kde.org/show_bug.cgi?id=408534
--- Comment #9 from Alexandre Pereira ---
you think sending my latte-dock profile would help ?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408534
--- Comment #10 from Alexandre Pereira ---
Created attachment 121245
--> https://bugs.kde.org/attachment.cgi?id=121245=edit
latte-dock files
my latte-dock rc files, just in case they might help
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=412152
--- Comment #18 from Alexandre Pereira ---
Pawel and everyone, sorry!!! made a typoo, its not amdgpu_dc=1 , its
amdgpu.dc=1.
for reference, here is my grub kernel boot parameters:
radeon.cik_support=0 radeon.si_support=0 amdgpu.dpm=1 amdgpu.dc=1
https://bugs.kde.org/show_bug.cgi?id=412152
--- Comment #14 from Alexandre Pereira ---
strangely i have this bug if i boot with amdgpu_dc=0.
with amdgpu_dc=1, kwin loads the wayland session.
can anyone test ?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=412152
Alexandre Pereira changed:
What|Removed |Added
CC||pereira.a...@gmail.com
--
You
https://bugs.kde.org/show_bug.cgi?id=418269
--- Comment #3 from Alexandre Pereira ---
> I also don't see the problem here.
The issue is that the selector of icon size also changes the icon size on list
mode.
So, either one of two solutions:
* let icon size slider be visible while on list m
https://bugs.kde.org/show_bug.cgi?id=417888
--- Comment #2 from Alexandre Pereira ---
tested the fix on X11 also, works properly without issues
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=418431
Bug ID: 418431
Summary: latte-dock show all running apps ( all activities )
but only launchers from current activity
Product: lattedock
Version: 0.9.9
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=418431
--- Comment #2 from Alexandre Pereira ---
oh :(
I was getting started to really like this workflow. the way i have it when I am
not using latte-dock, is have the "activity launchers" in kickoff and a panel
with taskmanager showing all ru
https://bugs.kde.org/show_bug.cgi?id=417888
--- Comment #1 from Alexandre Pereira ---
been testing a fix, which seems to work ( tested on wayland )
on file
/usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/code/tools.js:
function activateTask(index, model, modifiers, task
https://bugs.kde.org/show_bug.cgi?id=418269
Bug ID: 418269
Summary: folderview popup config dialog icon/list selection
Product: plasmashell
Version: master
Platform: Other
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=418269
--- Comment #1 from Alexandre Pereira ---
Created attachment 126468
--> https://bugs.kde.org/attachment.cgi?id=126468=edit
folderview config listmode
--
You are receiving this mail because:
You are watching all bug changes.
1 - 100 of 304 matches
Mail list logo
