from:"RaitaroH"

https://bugs.kde.org/show_bug.cgi?id=422771

Bug ID: 422771
   Summary: Run commands on android with kde connect
   Product: kdeconnect
   Version: 1.10
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: raitarohik...@protonmail.com
  Target Milestone: ---

SUMMARY
We can run commands on the pc from the phone with kde connect, why not the
other way around to? Say for example I could mute the phone from the laptop, or
even change the wifi to off.
This might not something that can be implemented due to app restrictions, but
perhaps if some things could be allowed?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 422770] New: Have a dedicated statusbar icon in android that will allow to run a kde connect command

https://bugs.kde.org/show_bug.cgi?id=422770

Bug ID: 422770
   Summary: Have a dedicated statusbar icon in android that will
allow to run a kde connect command
   Product: kdeconnect
   Version: 1.10
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: raitarohik...@protonmail.com
  Target Milestone: ---

SUMMARY
For example there is a toggle for wifi on an android device in the bar at top.
Why not have a custom kde connect one that can be set to say, run a command on
the pc, that otherwise would have had to be done by opening the kde connect
app, go to run commands, find the command and touch that entry?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 422769] New: Allow to copy settings from one kde connect device to another

https://bugs.kde.org/show_bug.cgi?id=422769

Bug ID: 422769
   Summary: Allow to copy settings from one kde connect device to
another
   Product: kdeconnect
   Version: 1.10
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: plasmoid
  Assignee: albertv...@gmail.com
  Reporter: raitarohik...@protonmail.com
  Target Milestone: ---

SUMMARY
Problem: having "Run commands" for one phone and having to copy them, line by
line, to another "Run commands" settings for a different connected phone.


STEPS TO REPRODUCE
1. Go to kde connect settings
2. Try to copy one device settings to another

OBSERVED RESULT
Is tedious to have to copy settings like that, for example run commands.


EXPECTED RESULT
A copy/paste for at least the run commands.


SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux 
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.70.0
Qt Version: 5.14.2
Kernel Version: 5.4.43-1-MANJARO
OS Type: 64-bit

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 422768] New: Allow reordering of kde connect run commands

https://bugs.kde.org/show_bug.cgi?id=422768

Bug ID: 422768
   Summary: Allow reordering of kde connect run commands
   Product: kdeconnect
   Version: 1.10
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: plasmoid
  Assignee: albertv...@gmail.com
  Reporter: raitarohik...@protonmail.com
  Target Milestone: ---

SUMMARY
Under kde connect settings > run commands it should be possible to rearrange
the items instead of having to delete something and adding it again.


STEPS TO REPRODUCE
1. Open KDE Connect settings
2. Configure "Run commands"
3. You cannot arrange the list

OBSERVED RESULT
List is fixed.


EXPECTED RESULT
Items in the list should be allowed to be moved.


SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux 
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.70.0
Qt Version: 5.14.2
Kernel Version: 5.4.43-1-MANJARO
OS Type: 64-bit

-- 
You are receiving this mail because:
You are watching all bug changes.

[kded-appmenu] [Bug 422765] New: Menus should appear within the space taken by the application

https://bugs.kde.org/show_bug.cgi?id=422765

Bug ID: 422765
   Summary: Menus should appear within the space taken by the
application
   Product: kded-appmenu
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: menu popup
  Assignee: plasma-b...@kde.org
  Reporter: raitarohik...@protonmail.com
  Target Milestone: ---

SUMMARY
When opening an application menu, say for dolphin, the menu shouldn't extend
beyond the application's borders.

STEPS TO REPRODUCE
1. Open dolphin
2. Open configure dolphin menu
This also happens for example in kate and other programs as well.

OBSERVED RESULT
Menu opens beyond borders of application.

EXPECTED RESULT
Menus should stay neatly inside the application they are a part of like in
Firefox or Chromium for example, and of course GNOME Applications.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 422657] New: Windows appear on another virtual desktop

2020-06-09 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=422657

Bug ID: 422657
   Summary: Windows appear on another virtual desktop
   Product: kwin
   Version: 5.18.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: raitarohik...@protonmail.com
  Target Milestone: ---

SUMMARY
I noticed that I open a window and it shows up on another virtual desktop, not
sure why. They should appear under cursor as per system settings I believe, but
they don't.


STEPS TO REPRODUCE
1. Open firefox on desktop 1
2. Firefox appears on desktop 2

OBSERVED RESULT
I am not sure if this happens because there is some "feature" I am unaware of,
nor if it happens because I last closed firefox on desktop 2. For example, I
have a profile of firefox I mostly use on desktop 2, so for some reason if I
open it on desktop 1 it just shows up on 2, no kwin rules no nothing required.


EXPECTED RESULT
Windows should show up on the desktop I opned them on.


SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux 
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.70.0
Qt Version: 5.14.2
Kernel Version: 5.4.43-1-MANJARO
OS Type: 64-bit


ADDITIONAL INFORMATION
I opened firefox from lattedock 0.9.11.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 422658] New: Firefox and Brave windows become unresponsive under certain circumstances

2020-06-09 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=422658

Bug ID: 422658
   Summary: Firefox and Brave windows become unresponsive under
certain circumstances
   Product: kwin
   Version: 5.18.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: compositing
  Assignee: kwin-bugs-n...@kde.org
  Reporter: raitarohik...@protonmail.com
  Target Milestone: ---

SUMMARY
A while ago I opened a bug for Waterfox
https://github.com/MrAlex94/Waterfox/issues/1057 I noticed now this is not
Waterfox specific and instead it seems to be a kwin issue because I have this
issue in Firefox 77.0.1 and even in Brave 81.1.9.76 both under KDE Neon 5.18.5
on another laptop, and Waterfox on this laptop running Manjaro (details below).


STEPS TO REPRODUCE
I mention that the steps in that github bug report are not the only things that
cause this! Also:
1. Open firefox or brave and place the window on another virtual desktop
2. Play some video on that desktop
3. Come back to it after... a while, not exactly sure how much
4. Window is frozen or transparent now

OBSERVED RESULT
For some reason the window is not responsive, it seems "frozen" but audio still
plays. Brave still responds to mouse events (timeline for a video shows up on
mouse hover as observed in an OBS test recording of this for a stream done in
Brave), whereas Firefox mostly becomes transparent and additionally blurry. A
simple kwin_x11 --replace seems to fix the issue, and then it comes back.

EXPECTED RESULT
These windows should not become unresponsive like that. This becomes especially
annoying when I need to record some stream and then this happens.


SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux 
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.70.0
Qt Version: 5.14.2
Kernel Version: 5.4.43-1-MANJARO
OS Type: 64-bit

Same stuff for KDE Neon 5.18.5 but kernel is 5.3.0-54-generic instead.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 421738] New: Taskmanager should be centered properly when against flexible spaces

https://bugs.kde.org/show_bug.cgi?id=421738

Bug ID: 421738
   Summary: Taskmanager should be centered properly when against
flexible spaces
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: raitarohik...@protonmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 128585
  --> https://bugs.kde.org/attachment.cgi?id=128585=edit
Example of what this bug refers to

SUMMARY
I opened a bug https://bugs.kde.org/show_bug.cgi?id=421733, and after a bit o
back and forth I was redirected here.

STEPS TO REPRODUCE
1. Make an empty panel
2. Add task manager
3. Add 2 flexible spacers, one on each side
4. Open a few windows

ACTUAL RESULT
The tasks are getting more and more un-centered as you open more applications.
(drift to the left)

EXPECTED RESULT
I would like for the tasks to be properly centered against flexible spacers.
More so, if they are not of equal size. Say... on the right there is the tray
icons a spacer will be shorter than the spacer on the other side where there is
just the menu. (refer to attachment)


SOFTWARE/OS VERSIONS
lattedock: 0.9.11
Operating System: Manjaro Linux 
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.69.0
Qt Version: 5.14.2
Kernel Version: 5.4.39-1-MANJARO

-- 
You are receiving this mail because:
You are watching all bug changes.

[lattedock] [Bug 421733] Allow to justify elements in the center of the screen, besides available space

https://bugs.kde.org/show_bug.cgi?id=421733

--- Comment #12 from RaitaroH  ---
(In reply to Michail Vourlakos from comment #11)
> On the other hand I might be wrong. If we add in an empty plasmapanel a
> plasma taskmanager and two Spacers, is it centered? If that is the case then
> Latte needs to update its implementation.

It seems centered for one open application. After that it sorta drifts to the
left.

-- 
You are receiving this mail because:
You are watching all bug changes.

[lattedock] [Bug 421733] Allow to justify elements in the center of the screen, besides available space

https://bugs.kde.org/show_bug.cgi?id=421733

--- Comment #10 from RaitaroH  ---
(In reply to Michail Vourlakos from comment #9)
> (In reply to RaitaroH from comment #8)
> > (In reply to Michail Vourlakos from comment #7)
> > > long story short, you need a taskmanager that behaves like this,
> > > unfortunately Plasma taskmanagers do not.
> > 
> > What about having a setting for the latte plasmoid to show window names?
> > Wouldn't that accomplish everything?
> 
> it would but I am not really interested. Latte Tasks can not take the burden
> for all Tasks requirements. A new applet is needed that will support this.

With that in mind perhaps I should open a request for the normal tasks plasmoid
to allow this to work?

-- 
You are receiving this mail because:
You are watching all bug changes.

[lattedock] [Bug 421733] Allow to justify elements in the center of the screen, besides available space

https://bugs.kde.org/show_bug.cgi?id=421733

--- Comment #8 from RaitaroH  ---
(In reply to Michail Vourlakos from comment #7)
> long story short, you need a taskmanager that behaves like this,
> unfortunately Plasma taskmanagers do not.

What about having a setting for the latte plasmoid to show window names?
Wouldn't that accomplish everything?

-- 
You are receiving this mail because:
You are watching all bug changes.

[lattedock] [Bug 421733] Allow to justify elements in the center of the screen, besides available space

https://bugs.kde.org/show_bug.cgi?id=421733

--- Comment #4 from RaitaroH  ---
(In reply to RaitaroH from comment #3)
> Created attachment 128577 [details]
> Image reference

@Michail Vourlakos is the git version able to do as per image? If that is the
case then I know what I need to do from the AUR :)

-- 
You are receiving this mail because:
You are watching all bug changes.

[lattedock] [Bug 421733] Allow to justify elements in the center of the screen, besides available space

https://bugs.kde.org/show_bug.cgi?id=421733

--- Comment #3 from RaitaroH  ---
Created attachment 128577
  --> https://bugs.kde.org/attachment.cgi?id=128577=edit
Image reference

-- 
You are receiving this mail because:
You are watching all bug changes.

[lattedock] [Bug 421733] New: Allow to justify elements in the center of the screen, besides available space

https://bugs.kde.org/show_bug.cgi?id=421733

Bug ID: 421733
   Summary: Allow to justify elements in the center of the screen,
besides available space
   Product: lattedock
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: raitarohik...@protonmail.com
  Target Milestone: ---

SUMMARY
Right now justify makes it so that what is in between is centered in the
available space. I would like a normal panel, but, with the task manager
centered, in the middle of the screen, not middle of available space in the
panel. Right now using dock mode is my best option, but no ideal (it resizes).
What I would like is menu in one corner, in the other corner the
pager+trayicons+clock, and in the middle of the screen to have the task
manager. Due to the right corner needing way more space, right now the task
manager is not centered "properly".

STEPS TO REPRODUCE
1. Try to justify the task manger
2. It is centered but not in the center of the screen

EXPECTED RESULT
There should be an option to justify in the center of the screen.


SOFTWARE/OS VERSIONS
lattedock: 0.9.11
Operating System: Manjaro Linux 
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.69.0
Qt Version: 5.14.2
Kernel Version: 5.4.39-1-MANJARO

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420541] Critical notifications (and only critical notifications) should be more attention-getting

2020-05-02 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=420541

--- Comment #10 from RaitaroH  ---
And... it appeared! Awesome.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 420541] Critical notifications (and only critical notifications) should be more attention-getting

2020-05-02 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=420541

--- Comment #9 from RaitaroH  ---
(In reply to Nate Graham from comment #8)
> Great, now all that's left to do here is to (maybe) improve the visibility
> of critical notifications. Moving to the appropriate place where we would
> implement that.

Can't wait to see this issue in "Adventures in Linux and KDE" Sir! :)

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 420541] Low and critical battery notifications should not time out or should take a very long time to time out

2020-04-30 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=420541

--- Comment #4 from RaitaroH  ---
(In reply to Nate Graham from comment #3)
> If we made that a full-screen overlay, I guarantee that there would be a
> subset of users who would call for our heads on platters. :) Imagine how
> disruptive it would be if you were giving a presentation or playing a game.
Aren't we talking about KDE here? THE KDE with too many settings? Couldn't this
be an optional setting for those who want it? I totally agree that a fullscreen
thing can be bothering... and that's the point is it not? There is already a
mute notifications option as well which could be used with this. Personally I
made my battery notifications to always show up.


> Yes, you want to be notified that you need to stop what you're doing or plug
> in the computer, but not at the cost of obscuring everything you're
> currently doing.
Precisely because I am doing something important, I would like to not lose all
that progress, because I missed a notification whilst being too absorbed in
whatever I was doing. Isn't that right?

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 420541] More obvious low and critical battery notifications

2020-04-25 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=420541

--- Comment #2 from RaitaroH  ---
(In reply to Kai Uwe Broulik from comment #1)
> Critical battery notification is a popup that will show on top of everything.
> If your laptop dies before that, looks more like a hardware problem. You can
> configure the warning and critical threshold in settings, though. 
> I'll leave exploring better visualization of the critical battery state to
> the VDG.

For me is more a case of having a demanding workload. I don't want to keep the
cable in at all times to not damage the battery. So for me the battery % is
always in mind, yet I still may forget about it.
I also juggle machines sometimes as well, so I believe what I suggested is a
much better solution than a small thing in a corner that will also disappear
after a timer. As a small patch for the time being, I would suggest the battery
notifications to never disappear unless the user takes that action.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 420541] New: More obvious low and critical battery notifications

2020-04-25 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=420541

Bug ID: 420541
   Summary: More obvious low and critical battery notifications
   Product: Powerdevil
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: raitarohik...@protonmail.com
  Target Milestone: ---

SUMMARY
I believe the current implementation of battery notifications is rather flawed.
What is the issue? I never notice the notifications, they might not even be
sent at all (I will open another bug if that is the case). Still, I find myself
missing the notification while being occupied working on something.

How to fix: make it more obvious. Windows10 at the very least creates this
horrible fullscreen popup that won't go away unless acknowledged. I think that
is preferable, especially if made pretty. Powerdevil should have some custom
notification system, perhaps a rework of the shutdown options maybe?
I made a very basic example. I took the shutdown options plasma has and simply
added an icon and some appropriate text. Something like this should appear
instead of a low/critical notification. If the battery is done charging a
normal system notification should suffice. This type of
"fullscreen-notification" could also be used for other things, maybe even by
plasma users through some cli command.
See mock-up image: https://i.imgur.com/mYZ7oZo.png

STEPS TO REPRODUCE
1. Reach low batter level
2. Get a notification about battery
3. Not see the notification
4. Proceed to have the laptop die

OBSERVED RESULT
The notifications for battery are easy to miss.

EXPECTED RESULT
Telling the user about battery is important enough to warrant the creation of a
separate system, at least a copy of the shutdown options that is changed for
this purpose.

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux 
KDE Plasma Version: 5.18.4
KDE Frameworks Version: 5.69.0
Qt Version: 5.14.2
Kernel Version: 5.4.34-1-MANJARO
OS Type: 64-bit

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 419905] New: transmission-qt menus are not blurred

2020-04-10 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=419905

Bug ID: 419905
   Summary: transmission-qt menus are not blurred
   Product: kwin
   Version: 5.18.4
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: raitarohik...@protonmail.com
  Target Milestone: ---

SUMMARY
I would guess transmission-qt is just based on some old qt? Because it's menus
are simply transparent and not blurred, not to mention that global menu does
not work with transmission-qt either.

STEPS TO REPRODUCE
1. Open transmission-qt
2. Have menu blur set
3. See that transmission-qt menu blur does not work

OBSERVED RESULT


EXPECTED RESULT
Menus should be blurred (well, in global menu too!)

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux 
KDE Plasma Version: 5.18.4
KDE Frameworks Version: 5.68.0
Qt Version: 5.14.2
Kernel Version: 5.4.30-1-MANJARO
OS Type: 64-bit


ADDITIONAL INFORMATION
transmission-qt 2.94 (d8e60ee44f)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 415864] Inconsistent kdeconnect notifications on desktop

2020-02-02 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=415864

--- Comment #1 from RaitaroH  ---
Seems that the new 1.13.7 version from fdroid fixed this.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 415864] Inconsistent kdeconnect notifications on desktop

2020-02-02 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=415864

RaitaroH  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 416707] New: Virtual desktop wrap-around doesn't work for qdbus org.kde.KWin /KWin org.kde.KWin.nextDesktop

2020-01-24 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=416707

Bug ID: 416707
   Summary: Virtual desktop wrap-around doesn't work for qdbus
org.kde.KWin /KWin org.kde.KWin.nextDesktop
   Product: kwin
   Version: 5.17.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: input
  Assignee: kwin-bugs-n...@kde.org
  Reporter: raitarohik...@protonmail.com
  Target Milestone: ---

SUMMARY
There are shortcuts to switch to the next/prev virtual desktop. Those are:
qdbus org.kde.KWin /KWin org.kde.KWin.nextDesktop
qdbus org.kde.KWin /KWin org.kde.KWin.previousDesktop
The problem is that running these in a terminal or calling them from sxhkd for
example does not allow wrapping around of desktops, say 1-2-3-4-1 doesn't work
and I am stuck at 1.

STEPS TO REPRODUCE
1. go to the last desktop
2. in a terminal run `qdbus org.kde.KWin /KWin org.kde.KWin.nextDesktop`
3. make sure the setting to wrap around desktops is enabled (in the Virtual
Desktops settings)
4. nothing happens when command is entered. Going to desktop 1 doesn't work,
going back to previous does work, unless is run on first desktop in which case
it won't wrap to last.

OBSERVED RESULT
Virtual desktop wrapping doesn't work if the above qdbus commands are used. On
the other hand if the shortcuts from Global Shortcuts > Kwin are used then
everything is totally fine and works as expected.
On that note, invoking the shortcut with qdbus like this instead, does work:
qdbus org.kde.kglobalaccel /component/kwin
org.kde.kglobalaccel.Component.invokeShortcut 'Switch to Next Desktop'

EXPECTED RESULT
qdbus commands should act the same way as the global shortcuts/invoke shortcut
command.

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux 
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.66.0
Qt Version: 5.14.0
Kernel Version: 5.4.13-3-MANJARO
OS Type: 64-bit

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 415864] New: Inconsistent kdeconnect notifications on desktop

2020-01-04 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=415864

Bug ID: 415864
   Summary: Inconsistent kdeconnect notifications on desktop
   Product: kdeconnect
   Version: unspecified
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: raitarohik...@protonmail.com
  Target Milestone: ---

SUMMARY
Some notifications from the phone are properly creating a 'notify-send' type of
notification, the one that appears in the corner of the screen. Some other
notifications are instead only showing up in the kcon system tray icon.


STEPS TO REPRODUCE
1. Send a: sms message, whatsapp message, discord message to phone
2. Phone vibrates, notifies etc.
3. At this point kcon sends the information to the desktop
4a. If it was a sms then I get a notification on the desktop as well (same with
youtube).
4b. If it was whatsapp/discord I do not get a notification on the desktop.
Instead, the kcon tray icon is the only way to see I even received anything.
5. Also, the 'reply' button in the notification for sms (because it shows up)
doesn't do anything. Replying only works if clicking the '<-" arrow in the kcon
system tray which opens the window where I can type a message. Likewise,
youtube notifications seem to have new buttons that also do not seem to do
anything.

OBSERVED RESULT
Whatsapp/discord notifications are not properly sent to the desktop, even
though in the past they were. SMS and youtube notifications are sent, but they
appear to have broken actions.

EXPECTED RESULT
All notifications that appear on the phone should also appear on the desktop.
If there is a reply button or any other action button then that should work.

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux 
KDE Plasma Version: 5.17.4
KDE Frameworks Version: 5.65.0
Qt Version: 5.14.0
Kernel Version: 5.4.6-2-MANJARO
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz
Memory: 15.3 GiB of RAM

$ kdeconnect-cli --version
QCommandLineParser: already having an option named "h"
QCommandLineParser: already having an option named "help-all"
kdeconnect-cli 1.4.0

Android
- android version 9
- kdeconnect - 1.13.5 from fdroid

ADDITIONAL INFORMATION
Notifications for kcon, and in general, are not muted.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 415397] New: Continue youtube video where you leftoff (bidirectional)

2019-12-20 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=415397

Bug ID: 415397
   Summary: Continue youtube video where you leftoff
(bidirectional)
   Product: kdeconnect
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: raitarohik...@protonmail.com
  Target Milestone: ---

SUMMARY

On spotify you can switch between different machines, so for example if you
need to leave the computer you can just 'switch' to the phone and it will be as
if you were listening on that device from the beginning. I wish this could work
with youtube (& others) as well, over kdeconnect. NO MORE I say, no more
scrubbing through the timeline of a youtube video you had to "Open on 'phone'"
as a caveman to get to where you were and be off by a few seconds or even
minutes. 

So what if... you could just have a little icon in the kcon notification for
media playback... say a shuffle icon kinda thing next to the playback buttons
that could open that video on the phone with no extra input? And the video
should continue at the very second as well. Same thing should also be available
in the kcon app as well and kcon tray indicator. An easy way to open whatever
kcon got from plasma-browser-integration: youtube videos primarily.

The process should be possible because:
1. kcon already has the information of what video is watched on youtube and
it's timeline position thanks to plasma-browser-integration
2. kcon can then receive the video and have it opened on the phone

The only change needed is add '=150' for example at the end of the url for
the youtube video to open it at the time specified, so in this case 2min 30sec.

The reverse though... that would require kcon to be able to see a youtube video
is playing. So perhaps if kcon can read notifications it can also have the same
'switch' icon/button send the video to the desktop and have it play there.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 414790] Password field not in focus at login page

2019-12-03 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=414790

--- Comment #2 from RaitaroH  ---
Nice thank you very much.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 414790] New: Password field not in focus at login page

2019-12-03 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=414790

Bug ID: 414790
   Summary: Password field not in focus at login page
   Product: plasmashell
   Version: 5.17.3
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: raitarohik...@protonmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

SUMMARY
Before I start, sorry but I have no idea where to file this bug under.
When the computer boots up and the login screen is shown, the password input
field is not focused, that is if I start typing nothing happens. I need to
manually click on the field to be able to type anything. 
This bug doesn't affect my lockscreen though. On the lockscreen the password
field is focused by default.

STEPS TO REPRODUCE
1. Boot up computer
2. Reach login screen
3. Type - password not entered due to field not being focused

OBSERVED RESULT
Password field is not focused.

EXPECTED RESULT
The password field should be focused by default so that one can just start
typing instead of having to fiddle with a mouse.

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux 
KDE Plasma Version: 5.17.3
KDE Frameworks Version: 5.64.0
Qt Version: 5.13.2
Kernel Version: 4.19.85-1-MANJARO
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz
Memory: 15.3 GiB of RAM


ADDITIONAL INFORMATION
I also have a monitor connected with HDMI. My keyboard is bluetooth so it takes
a bit to connect, though this is not the issue.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 414788] New: Stream audio from computer to paired phone

2019-12-03 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=414788

Bug ID: 414788
   Summary: Stream audio from computer to paired phone
   Product: kdeconnect
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: raitarohik...@protonmail.com
  Target Milestone: ---

SUMMARY

In essence would be nice to have the phone function as an additional audio sink
for the computer. This would allow for example using headphones with the phone
while being further away from the computer (so bluetooth headphones with extra
steps). 
It could allow using the phone's speakers if those sound better (which can be
the case for some) or even work for those who don't have speakers  attached to
their computer (or they are broken) and just want to use their phone for this.

-- 
You are receiving this mail because:
You are watching all bug changes.

[gwenview] [Bug 414230] New: Zoom in gwenview like in okular

2019-11-17 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=414230

Bug ID: 414230
   Summary: Zoom in gwenview like in okular
   Product: gwenview
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: raitarohik...@protonmail.com
  Target Milestone: ---

Many times it would be useful to be able to zoom in/out an image very smoothly
like you can a pdf in okular by pressing and holding the middle button then
move the mouse forward and backward. Wouldn't this be so much better in
gwenview? Right now a middle click just resets the zoom and you can only zoom
in big increments which isn't ideal.

And if we are here, why not have this everywhere where zoom is an option? Now,
I understand middle click might be used for something else, but is not the
button I am asking for, is the very small steps of the zoom making it easy to
achieve just the right zoom level. So CTRL+Scroll as always but smaller steps.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 413430] New: Unlock computer by simply unlocking the phone

2019-10-25 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=413430

Bug ID: 413430
   Summary: Unlock computer by simply unlocking the phone
   Product: kdeconnect
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: raitarohik...@protonmail.com
  Target Milestone: ---

SUMMARY

Right now I have a command under kde connect (loginctl unlock-session) that
allows to unlock the laptop. Pretty straight forward stuff. Except I kinda wish
to have an option where if I unlock my phone kde connect automatically unlocks
the linux session as well, without me having to open kconn, go to actions and
find where unlock command is. Seems that chrome-os actually let's you do that
now.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-browser-integration] [Bug 410715] Low resolution art url in plasma-browser-integration and kde-connect

2019-08-09 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=410715

--- Comment #3 from RaitaroH  ---
Considering the above I actually modified my script to get thumbnails. I am
aware this sorta formating has to be rewritten in the language
plasma-browser-integration is written into.

`echo "$input" | awk -F'\\=' '{print
"https://i.ytimg.com/vi/"$2"/maxresdefault.jpg"}'`
If the link is in the `navigator.mediaSession.metadata.artwork` format instead:
`echo "$inputg" | awk -F'/vi/' '{split($2,t,"/"); print
"https://i.ytimg.com/vi/"t[1]"/maxresdefault.jpg"}'`
Both give the same maxres image.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-browser-integration] [Bug 410715] Low resolution art url in plasma-browser-integration and kde-connect

2019-08-08 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=410715

--- Comment #2 from RaitaroH  ---
(In reply to Kai Uwe Broulik from comment #1)
> Thanks for your detailed analysis. However, website specific workarounds are
> outside the scope of this extension. If YouTube decided to provide only low
> resolution thumanils, that's all we got. Media Sessions API lets a website
> offer multiple sizes and many websites do.
> 
> Open the developer console (Ctrl+Shift+I) and type
> navigator.mediaSession.metadata.artwork
> and you can see that YouTube only provides a single 320x180 thumbnail.

The command you priveded gives a link that is pretty much as so:
`https://img.youtube.com/vi//hqdefault.jpg` followed by
`?blablablabla`
Except everything after `.jpg` is not needed, it still points to the image.
Then this thing can be easily made into the required image by simply replacing
`hqdefault` with `highresdefault`

Ex:
url: https://www.youtube.com/watch?v=xBQvKyAizt8
`navigator.mediaSession.metadata.artwork` -->
`https://i.ytimg.com/vi/xBQvKyAizt8/hqdefault.jpg?.` - I removed everything
after ? becase is way too long.
So now this can be easily modified to become
`https://i.ytimg.com/vi/xBQvKyAizt8/hqdefault.jpg`. But what we need is this
instead --> `https://i.ytimg.com/vi/xBQvKyAizt8/maxresdefault.jpg`
Same res as the image got through youtube-dl.
Can't plasma-browser-integration perform some modification on the link to get
the higher res thing? I was able to even write this and get the link with pure
javascript and no youtube api thing. I modified a little booklet I have to make
this.
```
history.replaceState(window.location=(window.location+'').replace('watch?v=','').replace('www.youtube.com','i.ytimg.com/vi').replace(/\=(.+)/i,'').replace(/\=(.+)/i,'').concat('/maxresdefault.jpg'));location.reload(false);
```

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-browser-integration] [Bug 410715] New: Low resolution art url in plasma-browser-integration and kde-connect

2019-08-08 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=410715

Bug ID: 410715
Summary: Low resolution art url in plasma-browser-integration
and kde-connect
Product: plasma-browser-integration
Version: unspecified
Platform: Neon Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: k...@privat.broulik.de
Reporter: raitarohik...@protonmail.com
Target Milestone: ---

SUMMARY

I think it is pretty amazing that kde connect (1.12.93 android) can display
cover art in notifications, and also on the lock screen as cover art. The
problem is that the cover art is ok for a notification (and even there I say is
a bit too low res), but horrible for a lock screen.

I dug a bit in `/data/data/org.kde.kdeconnect_tp/cache/album_art` directory to
see if this is an android issue or not. The image there is exactly the same as
the image given by plasma-browser integration. If I look at the metadata
`qdbus org.mpris.MediaPlayer2.plasma-browser-integration
/org/mpris/MediaPlayer2 org.mpris.MediaPlayer2.Player.Metadata`
I get `mpris:artUrl:
https://i.ytimg.com/vi/-viYoD2cqq8/hqdefault.jpg?sqp=-oaymwEjCNACELwBSFryq4qpAxUIARUAGAElAADIQj0AgKJDeAE==AOn4CLDv0KjDxszVqpt_obmwbrpELdWLIw`.
This url gives an image that is 334x187.
I then went on the link and used youtube-dl to get a better thumbnail
`youtube-dl -j --flat-playlist $1 | jq -r '.thumbnails' | grep -Eo
"(http|https)://[a-zA-Z0-9./?=_-]*` and I got
`https://i.ytimg.com/vi/UniMooWDPI0/maxresdefault.jpg` which is 1280x720. The
improvement is obvious.

I understand that p-b-i uses that cover-art just in the widget for media, but
even there the image is just so lowres if you have even a 1080p screen, let
alone to be used as cover art by kde connect in the `multimedia control`, or in
the android notifications... let alone as cover art for the lockscreen.
Perhaps is either browser-integration at fault here for not sending a higher
res to kconn, or perhaps is kcon's fault. I am not so sure.

STEPS TO REPRODUCE
1. Have plasma-browser-integration enabled in browser. waterfox alpha and brave
have the same issue.
2. Have an youtube video playing.
3. Check to see the resolution of the cover art url on desktop/android.
4. Have cover art set for lockscreen if you desire. There it is just horrible.

OBSERVED RESULT
The cover-art used by plasma-browser-integration and kdeconnect are too low
resolution.

EXPECTED RESULT
Use the full thumbnail image.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.16
KDE Plasma Version: 5.16.4
KDE Frameworks Version: 5.60.0
Qt Version: 5.12.3
Kernel Version: 4.15.0-55-generic
OS Type: 64-bit

--
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408475] kwin hangs when changing workspaces and manually maximize windows

2019-07-16 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=408475

--- Comment #12 from RaitaroH  ---
Well, I have discovered something, maybe. 
I have a bug with waterfox alpha here:
https://github.com/MrAlex94/Waterfox/issues/1057
I have noticed right now that changing workspaces caused the waterfox issue.
After a bit of testing I can say that, perhaps, changing the power states AC >
Battery, or vice-versa seems to cause kwin to hang pretty bad. Therefore, I
logged out, than I logged back in. After I got the wifi notification kwin was
able to switch workspaces as intended, but 2-3 sec later my fans start spinning
and kwin went all snail again. 

Also, changing from workspace 1 > 2 is really slow, but if I go from 2 to 1 is
pretty close to how is supposed to be. I am not sure how small is the time
window in which I can change from 2 to 1 and still be fast.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408475] kwin hangs when changing workspaces and manually maximize windows

2019-06-24 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=408475

--- Comment #11 from RaitaroH  ---
(In reply to Vlad Zagorodniy from comment #10)
> What version of Qt do you have?

Operating System: KDE neon 5.16
KDE Plasma Version: 5.16.1
KDE Frameworks Version: 5.59.0
Qt Version: 5.12.3
Kernel Version: 4.15.0-52-generic

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408475] kwin hangs when changing workspaces and manually maximize windows

2019-06-23 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=408475

--- Comment #9 from RaitaroH  ---
(In reply to RaitaroH from comment #8)
> (In reply to Vlad Zagorodniy from comment #7)
> > Hmm, does the problem still persist?
> Is a lot better than the last message. I can't say is completely gone, but
> at worst it takes 2 seconds to switch the desktop now.

I think it might have something to do with many wake cycles / logout-login
cycles. In #8 it happened because I had to suspend a bunch of times during the
day. I can't seem to consistently reproduce it myself though.

I am happy if it doesn't come back but I cannot be 100% certain is gone. I also
have, from time to time, a weird bug in konsole too when opening vim (same kind
of run-eproducible, happens only sometimes bug)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408475] kwin hangs when changing workspaces and manually maximize windows

2019-06-22 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=408475

--- Comment #8 from RaitaroH  ---
(In reply to Vlad Zagorodniy from comment #7)
> Hmm, does the problem still persist?
Is a lot better than the last message. I can't say is completely gone, but at
worst it takes 2 seconds to switch the desktop now.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408475] kwin hangs when changing workspaces and manually maximize windows

2019-06-20 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=408475

--- Comment #6 from RaitaroH  ---
And as I thought...
5.16 fixed the kwin problem...
And now is back a bit over a week later.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Bluedevil] [Bug 408654] Denied bluetooth pairing request - phone appears in the tray anyway

https://bugs.kde.org/show_bug.cgi?id=408654

--- Comment #6 from RaitaroH  ---
(In reply to David Rosca from comment #5)
> You are now mixing two issues together.
> 
> If you see the device as connected in the tray it doesn't actually mean that
> it is paired. If there is a pairing in progress, you will of course see the
> device as connected (otherwise it wouldn't be able to initiate the pairing).
> 
> If the pairing process is not canceled/accepted after you accept/reject the
> PIN code, then that's a bug. But please note here, you need to accept the
> PIN code on both sides - on your PC and also on your phone.

For the iphone the pin request happened multiple times (twice), that is what it
was weird about it. I cannot reproduce that with my android phone. The request
shows once and that's it. I have no idea if that is a bug or not, I reported
still.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Bluedevil] [Bug 408654] Denied bluetooth pairing request - phone appears in the tray anyway

https://bugs.kde.org/show_bug.cgi?id=408654

--- Comment #4 from RaitaroH  ---
May I ask for the first attachment to be deleted thank you. I marked it as
obsolete...

-- 
You are receiving this mail because:
You are watching all bug changes.

[Bluedevil] [Bug 408654] Denied bluetooth pairing request - phone appears in the tray anyway

https://bugs.kde.org/show_bug.cgi?id=408654

--- Comment #3 from RaitaroH  ---
Created attachment 120844
  --> https://bugs.kde.org/attachment.cgi?id=120844=edit
Phone shows up paired (fix)

-- 
You are receiving this mail because:
You are watching all bug changes.

[Bluedevil] [Bug 408654] Denied bluetooth pairing request - phone appears in the tray anyway

https://bugs.kde.org/show_bug.cgi?id=408654

RaitaroH  changed:

   What|Removed |Added

 Attachment #120843|0   |1
is obsolete||

-- 
You are receiving this mail because:
You are watching all bug changes.

[Bluedevil] [Bug 408654] Denied bluetooth pairing request - phone appears in the tray anyway

https://bugs.kde.org/show_bug.cgi?id=408654

--- Comment #2 from RaitaroH  ---
Created attachment 120843
  --> https://bugs.kde.org/attachment.cgi?id=120843=edit
Phone shows up paired

(In reply to David Rosca from comment #1)
> Can you please check if the device is paired? Open the Bluetooth tray, click
> on the device (iPhone) and you should see "Paired: Yes/No".

When I try to connect my phone this is what happens after I click the incorrect
pin. 

The phone shows: "Pair with PC? Cancel / Pair" this keeps going for about 30
seconds. If I click Cancel or Pair the phone shows an error "couldn't pair
because of bad PIN or key" pretty much. But again, the tray keeps showing the
phone as connected for 30 sec while the phone just sits there until the timeout
or until further action from me with results in un-pairing because of the
paring was denied on the PC.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Bluedevil] [Bug 408654] Denied bluetooth pairing request - phone appears in the tray anyway

https://bugs.kde.org/show_bug.cgi?id=408654

RaitaroH  changed:

   What|Removed |Added

Summary|Denied pairing request -|Denied bluetooth pairing
   |phone appears in the tray   |request - phone appears in
   |anyway  |the tray anyway

-- 
You are receiving this mail because:
You are watching all bug changes.

[Bluedevil] [Bug 408654] New: Denied pairing request - phone appears in the tray anyway

https://bugs.kde.org/show_bug.cgi?id=408654

Bug ID: 408654
   Summary: Denied pairing request - phone appears in the tray
anyway
   Product: Bluedevil
   Version: 5.16.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: system tray
  Assignee: now...@gmail.com
  Reporter: raitarohik...@protonmail.com
  Target Milestone: ---

SUMMARY

A notification popped up in the right corner of the screen
A Bluetooth notification asking if this is the correct pin
To my surprise it happened not once, but twice
And I clicked incorrect pin as many times
And yet the bloody iPhone from some stranger
Kept bugging my Bluetooth connection
And then in my curiosity I checked my system tray
And there it was that iPhone, connected, to my dismay

I thought perhaps some bad poem might brighten up the mood a bit. Yes some
random iPhone requested a pairing to my pc and I refused, twice. Still, the
phone appeared connected in the system tray widget for some reason. I
disconnected it manually from there. Not sure what, how or why this happened,
nor if it is an attack vector.
On my android phone the notification did not pop up twice, nor did the phone
manage to connect. It seems the phone shortly appears in the tray as well but
gives an error on the phone and disappears from the tray. Not sure if the
iPhone person saw an error though.

STEPS TO REPRODUCE
1. Have bluetooth visibility to Always Visible
2. Have some phone request a pairing
3. Click pin is incorrect in the notification
4. Check the tray

OBSERVED RESULT
The phone appears to be connected in the tray.

EXPECTED RESULT
If the pairing is denied, I expect it to not connect and not show up as
connected.

SOFTWARE/OS VERSIONS

Operating System: KDE neon 5.16
KDE Plasma Version: 5.16.0
KDE Frameworks Version: 5.59.0
Qt Version: 5.12.3
Kernel Version: 4.15.0-51-generic

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408475] kwin hangs when changing workspaces and manually maximize windows

https://bugs.kde.org/show_bug.cgi?id=408475

--- Comment #5 from RaitaroH  ---
(In reply to Vlad Zagorodniy from comment #4)
> > desktopchangeosdEnabled=true
> 
> Hmm, this one uses QtQuick. Most likely a duplicate of bug 406180.

Actually I think it is, ALT+TAB does hang but is not as severe in my case,
switching desktops is.
Also, I want to mention I upgraded to Neon 5.16 and the issue is gone for some
reason. Knowing my system it will be coming back shortly.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408475] kwin hangs when changing workspaces and manually maximize windows

2019-06-12 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=408475

--- Comment #3 from RaitaroH  ---
(In reply to Vlad Zagorodniy from comment #1)
> Can you post your kwinrc?

I have posted the kwinrc.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408475] kwin hangs when changing workspaces and manually maximize windows

2019-06-12 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=408475

--- Comment #2 from RaitaroH  ---
Created attachment 120811
  --> https://bugs.kde.org/attachment.cgi?id=120811=edit
kwinrc files

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408476] New: Making blur easier to enforce

2019-06-09 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=408476

Bug ID: 408476
   Summary: Making blur easier to enforce
   Product: kwin
   Version: 5.15.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: compositing
  Assignee: kwin-bugs-n...@kde.org
  Reporter: raitarohik...@protonmail.com
  Target Milestone: ---

SUMMARY

One can already set up rules to change a window's opacity... why not also add
the option to enforce blur? Right now this can be done through shell hacks or
the Force Blur script, but something that would apply globally would be great.
Or even have some sort of toggle that says: Apply blur to every transparent
window/context menu.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 408475] New: kwin hangs when changing workspaces and manually maximize windows

2019-06-09 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=408475

Bug ID: 408475
   Summary: kwin hangs when changing workspaces and manually
maximize windows
   Product: kwin
   Version: 5.15.5
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: raitarohik...@protonmail.com
  Target Milestone: ---

Created attachment 120714
  --> https://bugs.kde.org/attachment.cgi?id=120714=edit
output of qdbus org.kde.KWin /KWin supportInformation

SUMMARY
When I try to change a desktop either by keyboard shortcut or with pager kwin
hangs for around 10 seconds or more. In that state I can still see the screen,
move the cursor around, hear the audio. Sometimes I don't even move to the next
desktop and it looks like I moved back to where I was. Same thing happens if I
grab a windows and I snap it to any side of the screen (it does not affect the
tile shortcuts).

STEPS TO REPRODUCE
1. change virtual desktop (workspace)
2. manually snap a window


OBSERVED RESULT
Kwin lags for a long time.


EXPECTED RESULT
Kwin working as it should.

OS VERSIONS
SOFTWARE/Operating System: KDE neon 5.15
KDE Plasma Version: 5.15.5
KDE Frameworks Version: 5.58.0
Qt Version: 5.12.0
Kernel Version: 4.15.0-51-generic
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz
Memory: 7.4 GiB of RAM
Kwin 5.15.5
Nvidia driver version: 430.14 (GeForce GTX 1050 Ti 4GB)
X.org version: 1.19.6 (11906000)

ADDITIONAL INFORMATION
I have tried with no effect

update the kernel

updated the nvidia driver to 430.9

disable fade animation

disable wobbly windows

set render loop to basic

use OpenGL 2.0 and Smooth under compositor

disable the FORCE BLUR script that might be causing this

disable my force transparency which is global


This is what happens when kwin is in that state:

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND
13997 raitaro   25   5 3549848 127484  95120 S   6,7  1,6   0:42.05 kwin
13997 raitaro   25   5 3549848 127484  95120 S   0,0  1,6   0:42.05 kwin
13997 raitaro   25   5 3549848 127484  95120 S   0,0  1,6   0:42.44 kwin
13997 raitaro   25   5 3549848 127484  95120 S   0,7  1,6   0:42.46 kwin
13997 raitaro   25   5 3549848 127484  95120 S   0,0  1,6   0:42.46 kwin
13997 raitaro   25   5 3549844 127484  95120 S  20,0  1,6   0:43.06 kwin
13997 raitaro   25   5 3549844 127484  95120 S  99,3  1,6   0:46.05 kwin
13997 raitaro   25   5 3549844 127584  95120 D  46,7  1,6   0:47.45 kwin
13997 raitaro   25   5 3549844 127584  95120 D   0,0  1,6   0:47.45 kwin

The command kwin --replace  gives me a few things:
Could not create scene graph context for backend 'opengl' - check that plugins
are installed correctly in /usr/lib/x86_64-linux-gnu/qt5/plugins
trying to show an empty dialog
trying to show an empty dialog
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3720, resource
id: 29360256, major code: 18 (ChangeProperty), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 4299, resource
id: 29360239, major code: 2 (ChangeWindowAttributes), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 8641, resource
id: 29360580, major code: 2 (ChangeWindowAttributes), minor code: 0
WobblyWindowsConfig::instance called after the first use - ignoring

I also attached the output of qdbus org.kde.KWin /KWin supportInformation

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 400096] Meta opening krunner breaks at random

2019-02-26 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=400096

--- Comment #3 from RaitaroH  ---
Some extra info. Is not just meta, is also alt as well.

[ModifierOnlyShortcuts]
Alt=com.github.zren.PlasmaHUD,/PlasmaHUD,com.github.zren.PlasmaHUD,toggleHUD

So after a few questions from Zren I sent him the following. The meta shortcut,
or the alt shortcut simply don't last after a kwin replace. Not even 30
seconds.

killall krunner && kstart5 krunner

Omitting both --window and --windowclass arguments is not recommended

Could not create scene graph context for backend 'opengl' - check that
plugins are installed correctly in /usr/lib/x86_64-linux-gnu/qt5/plugins

kwin also spits out, with every kstart5:

qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 11109,
resource id: 96469001, major code: 18 (ChangeProperty), minor code: 0

qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 21180,
resource id: 35651593, major code: 18 (ChangeProperty), minor code: 0

qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 34681,
resource id: 96469001, major code: 18 (ChangeProperty), minor code: 0


On the other hand killing krunner and opening it manually actually works, but
it does not fix the meta problem. What I can see is only "kwin --replace" does
that.

▶ krunner &

[1] 12724

[1] + 12724 done krunner

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 402168] New: Notification after deleting files "Deleting: Finished" + "open" button

2018-12-15 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=402168

Bug ID: 402168
   Summary: Notification after deleting files "Deleting: Finished"
+ "open" button
   Product: plasmashell
   Version: 5.14.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: raitarohik...@protonmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 116943
  --> https://bugs.kde.org/attachment.cgi?id=116943=edit
Observed notification

SUMMARY
For a second I thought the bug was opened but it was for kio and it is from
2012. After deleting a few files I get a notif like in the attachment.
Obviously  clicking open gives an error


STEPS TO REPRODUCE
1. Delete multiple files
2. Observed every time. It has no option to hide it.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.14
KDE Plasma Version: 5.14.4
Qt Version: 5.11.2
KDE Frameworks Version: 5.53.0

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 241557] Zoom effect conflicts with other desktop effects like Blur

2018-11-11 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=241557

RaitaroH  changed:

   What|Removed |Added

 CC||raitarohik...@protonmail.co
   ||m

--- Comment #25 from RaitaroH  ---
(In reply to Brandin Starliper from comment #24)
> I can confirm that this causes issues still in 5.14 to an extent, I'd like
> to keep my desktop pretty while also keeping my eyesight. The problem with
> the blur effect is that so long as there's some sort of transparency, there
> seems to be some visual artifacts that I'm not sure how they come to be.

I can also confirm. Doesn't seem to matter if it is widget, terminal etc. Also
I can see my background image even after I switched it, but is like a combo of
the old image and the newer one, quite weird.

-- 
You are receiving this mail because:
You are watching all bug changes.

[latte-dock] [Bug 400907] Raise dock then show widget on keyboard activation

https://bugs.kde.org/show_bug.cgi?id=400907

--- Comment #9 from RaitaroH  ---
(In reply to Michail Vourlakos from comment #8)
> (In reply to RaitaroH from comment #7)
> > (In reply to Michail Vourlakos from comment #6)
> > > Show me a screenshot when you press Meta+'
> > 
> > Even better. Here is a video with screenkey on.
> > 
> 
> yep, exactly...
> The Meta+1 triggers the Latte internal code...
> the other shortcut is triggering plasma internal code, LAtte can not do
> anything about it...

Dang XD. Welp then. Thank you for your time

-- 
You are receiving this mail because:
You are watching all bug changes.

[latte-dock] [Bug 400907] Raise dock then show widget on keyboard activation

https://bugs.kde.org/show_bug.cgi?id=400907

--- Comment #7 from RaitaroH  ---
(In reply to Michail Vourlakos from comment #6)
> Show me a screenshot when you press Meta+'

Even better. Here is a video with screenkey on.

https://youtu.be/KTEPciUryNk

-- 
You are receiving this mail because:
You are watching all bug changes.

[latte-dock] [Bug 400910] Double click on panel with task manager - weird behavior

https://bugs.kde.org/show_bug.cgi?id=400910

RaitaroH  changed:

   What|Removed |Added

 Resolution|INTENTIONAL |FIXED

--- Comment #3 from RaitaroH  ---
(In reply to Michail Vourlakos from comment #2)
> This is default behavior for now and there will be an option for this later.
> You can double click to maximize/restore the active window and you can drag
> also to move.

Cool.

-- 
You are receiving this mail because:
You are watching all bug changes.

[latte-dock] [Bug 400910] Double click on panel with task manager - weird behavior

https://bugs.kde.org/show_bug.cgi?id=400910

--- Comment #1 from RaitaroH  ---
Ups, here is the video: https://youtu.be/KbIQdPaDI7Y

-- 
You are receiving this mail because:
You are watching all bug changes.

[latte-dock] [Bug 400910] New: Double click on panel with task manager - weird behavior

https://bugs.kde.org/show_bug.cgi?id=400910

Bug ID: 400910
   Summary: Double click on panel with task manager - weird
behavior
   Product: latte-dock
   Version: git (master)
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: raitarohik...@protonmail.com
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. Have a panel
2. Put the default task manager on it
3. Double click somewhere on the panel, on the task manager itself

OBSERVED RESULT
First the "tabs" showed there flicker, secondly the application that is focused
maximizes for some reason.

EXPECTED RESULT
No flicker. The maximize is actually quite nice.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.14
KDE Plasma Version: 5.14.3
Qt Version: 5.11.2
KDE Frameworks Version: 5.51.0
latte-dock --version: lattedock 0.8.75

ADDITIONAL INFORMATION
This is the output of "kwin --replace"

kwin --replace
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 176, resource
id: 119537671, major code: 20 (GetProperty), minor code: 0
qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 1927, resource
id: 73400327, major code: 42 (SetInputFocus), minor code: 0
OpenGL vendor string:   NVIDIA Corporation
OpenGL renderer string: GeForce GTX 1050 Ti/PCIe/SSE2
OpenGL version string:  4.6.0 NVIDIA 390.87
OpenGL shading language version string: 4.60 NVIDIA
Driver: NVIDIA
Driver version: 390.87
GPU class:  Unknown
OpenGL version: 4.6
GLSL version:   4.60
X server version:   1.19.6
Linux kernel version:   4.15
Requires strict binding:no
GLSL shaders:   yes
Texture NPOT support:   yes
Virtual Machine:no

-- 
You are receiving this mail because:
You are watching all bug changes.

[latte-dock] [Bug 400907] Raise dock then show widget on keyboard activation

https://bugs.kde.org/show_bug.cgi?id=400907

--- Comment #4 from RaitaroH  ---
Just to be extra clear, on the dock I use META+1 to activate that widget. On
the panel I use the global shortcut under latte-dock section set from right
click on that widget on the same latte-panel.

-- 
You are receiving this mail because:
You are watching all bug changes.

[latte-dock] [Bug 400907] Raise dock then show widget on keyboard activation

https://bugs.kde.org/show_bug.cgi?id=400907

--- Comment #3 from RaitaroH  ---
(In reply to Michail Vourlakos from comment #1)
> Which shortcut?
> 
> Latte shortcut or build in internal applet shortcut?

If we take the menu for example. I right click on it `Configure application
launccher` > KeyShorts > I have it set there. If I check in Global shortcuts,
under Latte Dock I see the shortcut there just fine: Activate App launcher
Widget > Meta+Shift+Z. No alternative, just global.

Here are the same widget on both a dock, issued with activate entry, and in the
panel issued with a global shortcut under latte-dock.

https://imgur.com/a/xZ9A2Qr

-- 
You are receiving this mail because:
You are watching all bug changes.

[latte-dock] [Bug 400907] New: Raise dock then show widget on keyboard activation

https://bugs.kde.org/show_bug.cgi?id=400907

Bug ID: 400907
   Summary: Raise dock then show widget on keyboard activation
   Product: latte-dock
   Version: git (master)
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: raitarohik...@protonmail.com
  Target Milestone: ---

SUMMARY

Basically I think would be better to raise the panel first, then above it have
the widget come up. For example I activate my calendar a lot, but I also want
to see the time. The calendar will cover the dock if it is hidden. Only after
the calendar was shown the panel itself comes up but will end up behind the
calendar widget window. Having it on top would be bad too, so I suppose having
Latte raise first then issue the widget would be best.

I only used the calendar as an example. Same happens with the launcher or
anything else.


STEPS TO REPRODUCE
1. Have a dock/panel hidden
2. Activate a widget with the shortcut


SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.14
KDE Plasma Version: 5.14.3
Qt Version: 5.11.2
KDE Frameworks Version: 5.51.0
latte-dock --version: lattedock 0.8.75

-- 
You are receiving this mail because:
You are watching all bug changes.

[konqueror] [Bug 243794] soundcloud.com does not work properly

2018-11-09 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=243794

RaitaroH  changed:

   What|Removed |Added

 CC||raitarohik...@protonmail.co
   ||m

--- Comment #1 from RaitaroH  ---
I can confirm soundcloud is not even seen at all by the music applet.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Breeze] [Bug 400870] New: sddm-theme-breeze - remove white border around avatar/make it transparent

2018-11-09 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=400870

Bug ID: 400870
   Summary: sddm-theme-breeze - remove white border around
avatar/make it transparent
   Product: Breeze
   Version: 5.14.2
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: raitarohik...@protonmail.com
  Target Milestone: ---

SUMMARY
I personally think that the breeze theme for the sddm is really great, except
one small thing. The white border around the avatar.

To remove it I use sed but the gist is: `property var colorBorder: transparent`
instead of the default.


Here is the command.


> sudo sed -i 's/property\ var\ colorBorder\:\ 
> PlasmaCore.ColorScope.textColor/property\ var\ colorBorder\:\ transparent/g' 
> /usr/share/sddm/themes/breeze/components/UserDelegate.qml 
> /usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserDelegate.qml


Operating System: KDE neon 5.14
KDE Plasma Version: 5.14.3
Qt Version: 5.11.2
KDE Frameworks Version: 5.51.0

-- 
You are receiving this mail because:
You are watching all bug changes.

[latte-dock] [Bug 400806] Weird enlargement animation instead of smooth growth

https://bugs.kde.org/show_bug.cgi?id=400806

--- Comment #3 from RaitaroH  ---
(In reply to Michail Vourlakos from comment #2)
> Git commit 0cd33727b8631da9d49154bd50e79a7c8ea6288f by Michail Vourlakos.
> Committed on 07/11/2018 at 17:00.
> Pushed by mvourlakos into branch 'master'.
> 
> restore iconOverlay default behavior
> 
> M  +2-2containment/package/contents/code/AppletIdentifier.js
> M  +2-2containment/package/contents/ui/applet/communicator/Engine.qml
> 
> https://commits.kde.org/latte-dock/0cd33727b8631da9d49154bd50e79a7c8ea6288f

Fixed indeed, thank you. And the edit mode is fine too. Nice job.



By the way I always get this when building, in case it helps... somehow

-- qmlplugindump failed for QtQuick.Controls.
-- Could NOT find QtQuick.Controls-QMLModule (missing:
QtQuick.Controls-QMLModule_FOUND) 
-- qmlplugindump failed for QtQuick.Controls.Styles.Plasma.
-- Could NOT find QtQuick.Controls.Styles.Plasma-QMLModule (missing:
QtQuick.Controls.Styles.Plasma-QMLModule_FOUND) 
-- qmlplugindump failed for org.kde.plasma.core.
-- Could NOT find org.kde.plasma.core-QMLModule (missing:
org.kde.plasma.core-QMLModule_FOUND) 
-- qmlplugindump failed for org.kde.plasma.components.
-- Could NOT find org.kde.plasma.components-QMLModule (missing:
org.kde.plasma.components-QMLModule_FOUND) 
-- Disabling debug info
-- Configuring done
-- Generating done
-- Build files have been written to: /home/raitaro/github/latte-dock/build

-- 
You are receiving this mail because:
You are watching all bug changes.

[latte-dock] [Bug 400806] New: Weird enlargement animation instead of smooth growth

https://bugs.kde.org/show_bug.cgi?id=400806

Bug ID: 400806
   Summary: Weird enlargement animation instead of smooth growth
   Product: latte-dock
   Version: git (master)
  Platform: unspecified
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: raitarohik...@protonmail.com
  Target Milestone: ---

Created attachment 116156
  --> https://bugs.kde.org/attachment.cgi?id=116156=edit
Observed animation problem

SUMMARY
I suppose giving you the gif I recorded would be better. I just rebuilt latte
today from git:

latte-dock --version
lattedock 0.8.75

I get this weird animation, or lack there of. Basically icons just grow quickly
and not smoothly.


STEPS TO REPRODUCE
1. Have the latest version of git (as of 7th October 2017)
2. Have a dock with icons. 
3. Size 48px, zoom on hover 80%, distance 15%

OBSERVED RESULT
Terrible animation.


EXPECTED RESULT
Like usual.


Operating System: KDE neon 5.14
KDE Plasma Version: 5.14.3
Qt Version: 5.11.2
KDE Frameworks Version: 5.51.0

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 400654] Allow toolbar to be placed to the right of places

https://bugs.kde.org/show_bug.cgi?id=400654

--- Comment #6 from RaitaroH  ---
(In reply to Nate Graham from comment #5)
> Anything's possible. :)

So do you accept the challenge? :0

-- 
You are receiving this mail because:
You are watching all bug changes.

[latte-dock] [Bug 399619] Panel edit mode extends beyond screen boundary

https://bugs.kde.org/show_bug.cgi?id=399619

RaitaroH  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #5 from RaitaroH  ---
(In reply to Michail Vourlakos from comment #4)
> maybe it is fixed...

It is. Also XD, great fix

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 400654] Allow toolbar to be placed to the right of places

2018-11-06 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=400654

--- Comment #4 from RaitaroH  ---
(In reply to Christoph Feck from comment #2)
> QMainWindow enforces this specific order. See image at
> http://doc.qt.io/qt-5/qmainwindow.html#details

And I assume nothing can be done right?

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 400654] Allow toolbar to be placed to the right of places

2018-11-06 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=400654

--- Comment #3 from RaitaroH  ---
(In reply to Nate Graham from comment #1)
> This is going to sound stupid... but how to you make the toolbar vertical
> and relocate it? It never even occurred to me that this was possible, and
> now that I know it is, I can't figure out how to do it.

Wow, you don't know about it? 

Right click on the toolbar/places. Uncheck lock. You will get a handle at the
top. Now you can move it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 400612] Discover shouldn't have flatpak-backend and snap-backend as hard dependency

https://bugs.kde.org/show_bug.cgi?id=400612

--- Comment #4 from RaitaroH  ---
(In reply to Nate Graham from comment #3)
> Thanks, it takes a big man to apologize!

Thank you.

I can say at the very least that removing discover (along with flatpak and
snapd) is not so bad (a few GBs free for me). I dont't get update notifs
obviously but I always found them quite hit or miss. I just use the terminal to
update from time to time and it works fine. Though not everybody can do that.

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 400654] New: Allow toolbar to be placed to the right of places

https://bugs.kde.org/show_bug.cgi?id=400654

Bug ID: 400654
   Summary: Allow toolbar to be placed to the right of places
   Product: dolphin
   Version: 18.08.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: panels: places
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: raitarohik...@protonmail.com
  Target Milestone: ---

Right now it is possible to have the toolbar, then the places, then everything
else. I think it can save some vertical space to have the toolbar vertical, but
I can only place it to the left of the places panel which I don't like that
much. It adds some empty space at the bottom and looks less clean. Doing it the
other way around, having places > toolbar > everything else, I think looks a
lot better.

Operating System: KDE neon 5.14
KDE Plasma Version: 5.14.2
Qt Version: 5.11.2
KDE Frameworks Version: 5.51.0

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 400611] Blur context menu on file drop

https://bugs.kde.org/show_bug.cgi?id=400611

--- Comment #3 from RaitaroH  ---
I found it in another place too. Open Screen Locking and right click on the
`Configure Screen Locking` text at the top. Works with other settings modules.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 400612] Discover shouldn't have flatpak-backend and snap-backend as hard dependency

https://bugs.kde.org/show_bug.cgi?id=400612

--- Comment #2 from RaitaroH  ---
(In reply to Nate Graham from comment #1)
> > But is stupid.
> https://community.kde.org/Get_Involved/Bug_Reporting#Remember_your_manners
> 
> I understand that this is frustrating, but let's try to keep it technical.
> Insults tend not to motivate people. :)

I just said it was stupid, but very well, my apologies.

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 400035] Vim display problems if started with `konsole -e "vim"

https://bugs.kde.org/show_bug.cgi?id=400035

RaitaroH  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #11 from RaitaroH  ---
Well I have been using gvim for now. I also see that sometimes gvim doesn't
display a line or 2 even if they are there, but is not the same as the bug I
showed in the video, or if it is then it is veeery low intensity. I suppose
'worksforme'

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 400611] Blur context menu on file drop

https://bugs.kde.org/show_bug.cgi?id=400611

--- Comment #1 from RaitaroH  ---
I managed to find it in another place. Unlock panels, then right click on the
`Places` text.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 400612] New: Discover shouldn't have flatpak-backend and snap-backend as hard dependency

https://bugs.kde.org/show_bug.cgi?id=400612

Bug ID: 400612
   Summary: Discover shouldn't have flatpak-backend and
snap-backend as hard dependency
   Product: Discover
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: raitarohik...@protonmail.com
  Target Milestone: ---

SUMMARY
I know about this commit:
https://packaging.neon.kde.org/kde/plasma-discover.git/commit/?h=Neon/release=f7929ece16fb73bdb05103dfbdefe9ad11213cd7

But is stupid. I don't want flatpak nor snapd on my system because I don't use
them, so I removed them along with the entire discover application, which I
never use because is unreliable.

Operating System: KDE neon 5.14
KDE Plasma Version: 5.14.2
Qt Version: 5.11.2
KDE Frameworks Version: 5.51.0
OS Type: 64-bit

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 400611] New: Blur context menu on file drop

https://bugs.kde.org/show_bug.cgi?id=400611

Bug ID: 400611
   Summary: Blur context menu on file drop
   Product: dolphin
   Version: 18.08.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: raitarohik...@protonmail.com
CC: elvis.angelac...@kde.org
  Target Milestone: ---

SUMMARY
Context menus are still not perfect in some places, this time not on the
desktop, not in vlc, but instead in dolphin.

STEPS TO REPRODUCE
1. Select a file.
2. Drop it somewhere.
3. You will get the move/copy/cancel actions in a context menu. Those are still
corrupted if you have blur enabled. Also works in mounted usb drives, on deskto
and works in folderview widget on desktop.

OBSERVED RESULT
Context menu corruption.

EXPECTED RESULT
Sweet blur.

SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 5.14.2
KDE Frameworks Version: 5.51.0
Qt Version: 5.11.2
KDE Neon

ADDITIONAL INFORMATION
Nvidia 390.97, xorg 1.19.6

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 400035] Vim display problems if started with `konsole -e "vim"

2018-10-26 Thread RaitaroH

https://bugs.kde.org/show_bug.cgi?id=400035

--- Comment #10 from RaitaroH  ---
(In reply to Nate Graham from comment #9)
> Hmm, well I'm afraid if it's not consistent than it's going to be a
> challenge to debug. Any chance you could try to find a reproducible test
> case?

Could it be Nvidia or Kwin at fault instead?

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 400035] Vim display problems if started with `konsole -e "vim"

https://bugs.kde.org/show_bug.cgi?id=400035

--- Comment #8 from RaitaroH  ---
Damn... I have been trying to reproduce this today but, I can't. My new vimrc,
the old vimrc, no vimrc, konsole -e or not. Well it is in line with my
experience so far. I had a reinstall of KDE Neon (a failed Antergos installed)
and I hoped the problem would go away. A few days it was, it came back, it went
away, it came back, today it seems it went away again. Is this even possible...

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 400035] Vim display problems if started with `konsole -e "vim"

https://bugs.kde.org/show_bug.cgi?id=400035

--- Comment #7 from RaitaroH  ---
Created attachment 115823
  --> https://bugs.kde.org/attachment.cgi?id=115823=edit
qdbus org.kde.KWin /KWin supportInformation

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 400035] Vim display problems if started with `konsole -e "vim"

https://bugs.kde.org/show_bug.cgi?id=400035

--- Comment #6 from RaitaroH  ---
(In reply to Nate Graham from comment #5)
> Does the issue reproduce if you temporarily move aside your vimrc file?

Well the problem doesn't seem to appear but I noticed that after looking in my
vimrc for what may cause it, relativenumber was pretty much it from what I
could tell. Even still the problem appeared with that not being there but it
was less severe. The most effective resolve was to have the desktop file
changed instead. Not to mention that the problem appeared basically only when
starting from a double click in dolphin rather than starting vim from a
terminal. Not sure if that helps. Yet again... my vimrc doesn't seem to impact
gvim or urxvt at all, or konsole if vim is started as a command from the
terminal...

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 400096] Meta opening krunner breaks at random