[kwin] [Bug 483804] kwin_wayland crashes on Lenovo laptop with hybrid cards UHD Graphics 620 + AMD GPU Radeon 540/540X/550/550X

2024-04-06 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=483804

--- Comment #7 from Musikolo  ---
One last thing, I forgot to add the following. My laptop only works with X11
(SDDM + Plasma) with mesa-amber (classic drivers), while for Wayland (SDDM +
Plasma), it only works with mesa (newer drivers). Really weird and a huge
source of confusion, at least for me, but it is the way it is.

Thanks again!

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

[kwin] [Bug 483804] kwin_wayland crashes on Lenovo laptop with hybrid cards UHD Graphics 620 + AMD GPU Radeon 540/540X/550/550X

2024-04-06 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=483804

Musikolo  changed:

   What|Removed |Added

 Resolution|--- |NOT A BUG
 Status|REPORTED|RESOLVED

--- Comment #6 from Musikolo  ---
I've been trying out different things, and I found solution for my issue. I was
using mesa-amber because mesa wasn't working for me since version 22.00. For
some reason, the newer mesa drivers were causing my screen get out of sync and
we could see nothing in SDDM. Today, I've been testing different options, and I
found the problem was that, for some reason, my primary graphic device was i915
(intel) rather than radeonsi. I also found the radeonsi driver is not available
in mesa-amber. So, I upgraded to mesa and switched the devices. I restarted and
I could use SDDM with Wayland. From there, I can log in to Plasma with
kwin_wayland. So, I'm marking this bug as resolved. I'll add new notes if I
find something else others could get advantage of.

As always, thanks for the great work you're doing!

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

[kwin] [Bug 483804] kwin_wayland crashes on Lenovo laptop with hybrid cards UHD Graphics 620 + AMD GPU Radeon 540/540X/550/550X

2024-03-24 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=483804

--- Comment #5 from Musikolo  ---
Created attachment 167703
  --> https://bugs.kde.org/attachment.cgi?id=167703=edit
coredumpctl backtrade 2nd attempt

I hope I got what you need this time. Please let me know what I'm missing, if
you still didn't get what you need.

Thanks.

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

[kwin] [Bug 483804] kwin_wayland crashes on Lenovo laptop with hybrid cards UHD Graphics 620 + AMD GPU Radeon 540/540X/550/550X

2024-03-22 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=483804

Musikolo  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|BACKTRACE   |---

--- Comment #3 from Musikolo  ---
Backtrace provided as indicated in the given link. I attached 2 file in the
last zip file, one with debug info, and another without.

I hope that contains the info you need to squeeze this miserable bug!

If anything else is needed, I'll be happy to help.

Thanks!

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

[kwin] [Bug 483804] kwin_wayland crashes on Lenovo laptop with hybrid cards UHD Graphics 620 + AMD GPU Radeon 540/540X/550/550X

2024-03-22 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=483804

--- Comment #2 from Musikolo  ---
Created attachment 167634
  --> https://bugs.kde.org/attachment.cgi?id=167634=edit
coredumpctl gdb bt content

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

[kwin] [Bug 483804] New: kwin_wayland crashes on Lenovo laptop with hybrid cards UHD Graphics 620 + AMD GPU Radeon 540/540X/550/550X

2024-03-16 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=483804

Bug ID: 483804
   Summary: kwin_wayland crashes on Lenovo laptop with hybrid
cards UHD Graphics 620 + AMD GPU Radeon
540/540X/550/550X
Classification: Plasma
   Product: kwin
   Version: 6.0.2
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: core
  Assignee: kwin-bugs-n...@kde.org
  Reporter: musik...@hotmail.com
  Target Milestone: ---

Created attachment 167356
  --> https://bugs.kde.org/attachment.cgi?id=167356=edit
kwin_wayland command on X11 + coredump + lspci + lsmod outputs

SUMMARY
When logging in to SDDM with Wayland,  it crashes. If I enabled SDDM to use
kwin_wayland, it crashes too. When I logging in to Plasma 6 in X11 and launch a
wayland window, it crashes too.

STEPS TO REPRODUCE
1. Start SDDM in X11
2. Log in to Plasma 6
3. From a shell run the commands:  export $(dbus-launch); kwin_wayland
--xwayland

OBSERVED RESULT
A Segmentation fault error occurs.

EXPECTED RESULT
It should display something in Wayland.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: yes
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
Attached files with as much information as possible. If anything thing is
needed, I'll be happy to help.

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

[kmymoney] [Bug 452690] File > Open Recent option grays out

2023-07-07 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=452690

Musikolo  changed:

   What|Removed |Added

   Platform|Other   |Archlinux

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

[kmymoney] [Bug 452690] File > Open Recent option grays out

2023-07-07 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=452690

Musikolo  changed:

   What|Removed |Added

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

--- Comment #1 from Musikolo  ---
Happy to say that the issue was addressed and solved in version 5.1.3. 

Thanks for the quick response!

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

[kio-extras] [Bug 296526] Dolphin is too slow when upload a file on a SSH server

2023-07-07 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=296526

Musikolo  changed:

   What|Removed |Added

 CC||musik...@hotmail.com

--- Comment #39 from Musikolo  ---
Same issue over here. Using Dolphin with fish, it uploads files at 100 KB/s.
However, using scp over command line, it uploaded files at 8 MB/s. This
occurred while accessing the remote server over a WireGuard VNP connection.
When I'm on the same network as the remote server and I don't need VPN
connection, things improve quite a bit, but it's still significantly slower
than scp command.

Using Arch Linux and Dolphin 23.04.2.

If there is anything else I can do to provide the info needed sort this issue
out, please let me know.

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

[frameworks-kio] [Bug 373062] WebDav - Cannot rename or delete files when special characters in the path

2022-11-30 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=373062

Musikolo  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #4 from Musikolo  ---
(In reply to Justin Zobel from comment #3)
> Thank you for reporting this issue in KDE software. As it has been a while
> since this issue was reported, can we please ask you to see if you can
> reproduce the issue with a recent software version?
> 
> If you can reproduce the issue, please change the status to "REPORTED" when
> replying. Thank you!

Hi Justin,

No, the issue is no longer occurring. I can now copy files with special
characters, rename and delete them.

I think the issue is gone, so I'm updating the status accordingly.

Please let me know if anything else is needed.

Thanks.

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

[kmymoney] [Bug 452690] New: File > Open Recent option grays out

2022-04-16 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=452690

Bug ID: 452690
   Summary: File > Open Recent option grays out
   Product: kmymoney
   Version: 5.1.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: file
  Assignee: kmymoney-de...@kde.org
  Reporter: musik...@hotmail.com
  Target Milestone: ---

SUMMARY
***
I have 3 databases I often work on. I noticed that in version 5.1.2, when I
open the 3 databases through the "File" > "Open Recent" option, it grays out. I
need to quit the application to get it enabled again. Every time I repeat the
process, the option grays out again.
***

STEPS TO REPRODUCE
0. Pre-condition: I have 3 databases under the Open Recent option. (If you have
other number, do the same thing with all of them)
1. From current database 1, open database 2 through the "Open Recent" option
2. From current database 2, open database 3 through the "Open Recent" option
3. From current database 3, open database 1 through the "Open Recent" option,
and you'll find the option is grayed out.

OBSERVED RESULT
When all databases are opened through the "File" > "Open Recent" option, it
grays out.

EXPECTED RESULT
The "File" > "Open Recent" option should never gray out when you have recently
opened any database.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.93.0
Qt Version:  5.15.3

ADDITIONAL INFORMATION
Kernel version: 5.17.3

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

[kmymoney] [Bug 430630] New: Values of date picker runs out of control for scheduled payments and transactions again

2020-12-20 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=430630

Bug ID: 430630
   Summary: Values of date picker runs out of control for
scheduled payments and transactions again
   Product: kmymoney
   Version: 5.1.0
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: musik...@hotmail.com
  Target Milestone: ---

I'm experiencing the issue #424378 I reported a few months ago, occurring
again. 
- https://bugs.kde.org/show_bug.cgi?id=424378

Using Arch Linux with the latest available packages.

Please let me know if you need any more details.

Thank you.

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

[kmymoney] [Bug 424378] New: Values of date picker runs out of control for scheduled payments and transactions

2020-07-18 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=424378

Bug ID: 424378
   Summary: Values of date picker runs out of control for
scheduled payments and transactions
   Product: kmymoney
   Version: 5.1.0
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: musik...@hotmail.com
  Target Milestone: ---

SUMMARY
When enter a scheduled payment and just do one single click on the up or down
arrow of date picker, the day portion of the date runs up or down out of
control.

STEPS TO REPRODUCE (PATH A)
1. Go to "Home" on the left panel.
2. In the "Payments" area, click on the "Enter schedule" payment button of an
existing scheduled payment.
3. Directly click on the up or down arrow button of the date picker to increase
or decrease the existing date and wait for a couple of seconds.

STEPS TO REPRODUCE (PATH B)
1. Go to "Schedule payments" on the left panel.
2. Right-click on any existing transaction and click on the "Edit scheduled
transaction" option.
3. Directly click on the up or down arrow button of the date picker to increase
or decrease the existing date and wait for a couple of seconds.

OBSERVED RESULT
The day component of the date picker runs up out of control until it reaches
the end of the month. Conversely, if you clicked on the down arrow button, the
day goes down out of control until it reaches the beginning of the month.

EXPECTED RESULT
It should go up or down one single day per click, unless you hold your click
(long-press) on either the up or down arrow button.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Plasma Version: 5.19.3
KDE Frameworks Version: 5.72.0
Qt Version: 5.15.0

ADDITIONAL INFORMATION
Kernel version: 5.7.8-arch1-1

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

[plasmashell] [Bug 401088] "Filesystem mounted at '/' is not responding" notification on log in to Plasma 5.14.3

2020-05-05 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=401088

--- Comment #23 from Musikolo  ---
Yes, I can confirm the same thing. After updating to the latest packages in
ArchLinux, it's working fine now! I saw new version of plasma-desktop (from
5.18.4.1-2 to 5.18.5-1) which contains plasmashell. This is the only relevant
thing I found that could have any relationship with previous bug.

Thank you all!

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

[plasmashell] [Bug 401088] "Filesystem mounted at '/' is not responding" notification on log in to Plasma 5.14.3

2020-05-01 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=401088

--- Comment #20 from Musikolo  ---
Created attachment 128091
  --> https://bugs.kde.org/attachment.cgi?id=128091=edit
strace_kstart5_plasmashell.log

Hi guys,

I've been looking into the issue with plasmashell, this is what I found:

1.- I stop it with: kbuildsycoca5 && kquitapp5 plasmashell
2.- I start it with: strace kstart5 plasmashell

As you can see at the very end of the attached strace_kstart5_plasmashell.log
file, there are a bunch of error with SystemLoadViewer plasma, then it does
nothing for ~24 seconds, and then it prints the following error and plasmashell
shows up:

trying to show an empty dialog
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19:
QML Loader: Binding loop detected for property "height"
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19:
QML Loader: Binding loop detected for property "height"

I wonder whether the "Binding loop" error found in the Desktop.qml file could
be the root cause. That file belongs to the plasma-desktop 5.18.4.1-1 package
in ArchLinux.

I hope it helps!

Thanks.

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

[plasmashell] [Bug 401088] "Filesystem mounted at '/' is not responding" notification on log in to Plasma 5.14.3

2020-04-28 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=401088

--- Comment #15 from Musikolo  ---
Hi,

I started getting this issue since I upgraded to Plasma 5.18.4 a couple of days
ago. Never had this issue before. I tried with another user in the same
computer, and it does the same thing.

I'm attaching my logs since the moment I log in to SDDM until plasmashell
completes loading. For the sake of simplicity, I'm attaching two files
journalct-full.log containing all the logs, and journalctl-plasmashell.log
containing the logs just for plasmashell.

As you can see the logs, there is jump from 21:30:09 to 21:30:34 at the end of
both files.

If you need me to do any tests that helps find the root cause, please let me
know.

Thank you!

--
Operating System: Arch Linux 
KDE Plasma Version: 5.18.4.1
KDE Frameworks Version: 5.69.0
Qt Version: 5.14.2

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

[plasmashell] [Bug 401088] "Filesystem mounted at '/' is not responding" notification on log in to Plasma 5.14.3

2020-04-28 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=401088

--- Comment #14 from Musikolo  ---
Created attachment 127969
  --> https://bugs.kde.org/attachment.cgi?id=127969=edit
journalctl - Plasmashell log entries only since SDDM to plasmashell completes

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

[plasmashell] [Bug 401088] "Filesystem mounted at '/' is not responding" notification on log in to Plasma 5.14.3

2020-04-28 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=401088

Musikolo  changed:

   What|Removed |Added

 CC||musik...@hotmail.com

--- Comment #13 from Musikolo  ---
Created attachment 127968
  --> https://bugs.kde.org/attachment.cgi?id=127968=edit
journalctl - Full log since SDDM to plasmashell completes

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

[plasmashell] [Bug 394981] Icons for JetBrains products are now only displayed in search

2019-11-09 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=394981

Musikolo  changed:

   What|Removed |Added

 CC||musik...@hotmail.com

--- Comment #13 from Musikolo  ---
I've also been experiencing the same issue with datagrip. As Tekeyser
mentioned, the app icon is displayed correctly under the Applications menu, but
it won't show when added as a favorite. The work around is just changing the
icon type from svg to png in the desktop file. 

In the case of Arch Linux, this is done by just replacing the ".svg" extension
with ".png" at
https://aur.archlinux.org/cgit/aur.git/tree/jetbrains-datagrip.desktop?h=datagrip#n5
Fortunately, this can easily done because both formats are available.

I hope a solution is found, because it's kind of an annoying bug.

Thank you!

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

[plasmashell] [Bug 409296] powermanagement data engine returns incorrect sleep states in login time

2019-10-24 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=409296

--- Comment #4 from Musikolo  ---
The issue still persists in KDE Plasma 5.17.1. 

Is there any tentative version in which this will be fixed?

Thank you!

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

[Phonon] [Bug 357601] Add option to only use HDMI audio output if it's video is being used/enabled

2019-10-21 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=357601

Musikolo  changed:

   What|Removed |Added

 CC||musik...@hotmail.com

--- Comment #1 from Musikolo  ---
Following the topic of this thread, I would like to add to the wish list, a
feature to remember the last configuration used for HDMI devices. This would
make very handy to plug & play your laptop to your TV. Instead, when I plug an
HDMI device, I have to manually choose the corresponding HDMI output device.
Likewise, when I unplug it, I have to manually revert it back to the original
settings.

Having a feature that automatically does this will great improve the experience
and usability of external devices.

Thank you!

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

[plasma-pa] [Bug 407397] Impossible to adjust the volume level of the notification sounds

2019-08-03 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=407397

--- Comment #14 from Musikolo  ---
I just found that after clicking on the mute button of the Notification Sounds
bar, although the sound level is 0%, notification sound is back again! This is
very strange, but it worked!!

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

[plasma-pa] [Bug 407397] Impossible to adjust the volume level of the notification sounds

2019-08-02 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=407397

Musikolo  changed:

   What|Removed |Added

 CC||musik...@hotmail.com

--- Comment #13 from Musikolo  ---
Hi,

I'm also having the same issue as shown in the screen recording.

Laptop model: Lenovo E480
Operating System: Arch Linux
KDE Plasma Version: 5.16.4
KDE Frameworks Version: 5.60.0
Qt Version: 5.13.0
Linux Kernel: 5.2.5

lspci -v output for audio device:
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
Subsystem: Lenovo Sunrise Point-LP HD Audio
Flags: bus master, fast devsel, latency 64, IRQ 144
Memory at f152 (64-bit, non-prefetchable) [size=16K]
Memory at f151 (64-bit, non-prefetchable) [size=64K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl

Using the same software in my other laptop (Slimbook Pro) everything works
good. I don't know if the issue shows up when you change the volume levels, it
becomes zero/muted and you cannot change it anymore. Not fully sure this is
true, but I suspect so.

When you click on the mute volume button, you see the bar highlights a bit, but
volume level stays zero. When you adjust the volume, bar darkens again
indicating it got muted again.

I hope a solution is found shortly. 

Thank you!

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

[plasmashell] [Bug 409296] New: powermanagement data engine returns incorrect sleep states in login time

2019-06-28 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=409296

Bug ID: 409296
   Summary: powermanagement data engine returns incorrect sleep
states in login time
   Product: plasmashell
   Version: 5.16.2
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: DataEngines
  Assignee: plasma-b...@kde.org
  Reporter: musik...@hotmail.com
  Target Milestone: 1.0

SUMMARY
When logging in to KDE Plasma, powermanagement data engine returns incorrect
"sleep state" values which breaks dependent plasmoids/widgets.

STEPS TO REPRODUCE
1. Install a plasmoid that depends on "sleep states" from powermanagement data
engine (such as https://github.com/Musikolo/plasma5-applets-system-panel)
2. Reboot & log in to KDE Plasma
3. powermanagement returns incorrect values of "sleep states" for
HybridSuspend, Hibernate and Suspend states.


OBSERVED RESULT
Because powermanagement returns incorrect "sleep states", dependent plasmoids
do not work as expected. The returned "sleeps states" in login time are as
shown below:

{"Hibernate":true,"HybridSuspend":false,"LockScreen":true,"Logout":true,"Standby":false,"Suspend":false}

Restarting plasmashell fixes the issue (kbuildsycoca5 && kquitapp5 plasmashell
&& kstart5 plasmashell). This suggests there might be a race condition on the
normal log in process affecting some laptops.

EXPECTED RESULT
After logging in to KDE Plasma, powermanagement data engine "sleep states"
should be correctly provided, as shown below:

{"Hibernate":true,"HybridSuspend":true,"LockScreen":true,"Logout":true,"Standby":false,"Suspend":true}


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 5.16.2
KDE Frameworks Version: 5.59.0
Qt Version: 5.12.4

ADDITIONAL INFORMATION
I have widget that depends on powermanagement sleep states to decide whether to
enable or not some related actions. Some version between KDE Plasma 5.8 &
5.16.2, I noticed my widget was behaving in an unexpected and incorrect way.
Recently, I decided to improve the code and debug the issue.

Logs when the issue occurs:

powermanagement onNewData sourceName=Sleep States -
data={"Hibernate":false,"HybridSuspend":false,"LockScreen":true,"Logout":true,"Standby":false,"Suspend":false}
- Sleep
States={"Hibernate":false,"HybridSuspend":false,"LockScreen":true,"Logout":true,"Standby":false,"Suspend":false}
powermanagement onNewData sourceName=Sleep States -
data={"Hibernate":false,"HybridSuspend":false,"LockScreen":true,"Logout":true,"Standby":false,"Suspend":false}
- Sleep
States={"Hibernate":false,"HybridSuspend":false,"LockScreen":true,"Logout":true,"Standby":false,"Suspend":false}
powermanagement source connected=Sleep States - Sleep
States={"Hibernate":false,"HybridSuspend":false,"LockScreen":true,"Logout":true,"Standby":false,"Suspend":false}
powermanagement source connected=PowerDevil - Sleep
States={"Hibernate":false,"HybridSuspend":false,"LockScreen":true,"Logout":true,"Standby":false,"Suspend":false}
suspendToRam - Sleep States={"objectName":"","Sleep
States":{"Hibernate":false,"HybridSuspend":false,"LockScreen":true,"Logout":true,"Standby":false,"Suspend":false}}


Logs when EITHER the issue does NOT occur OR after restarting plasmashell:

powermanagement onNewData sourceName=Sleep States -
data={"Hibernate":true,"HybridSuspend":true,"LockScreen":true,"Logout":true,"Standby":false,"Suspend":true}
- Sleep
States={"Hibernate":true,"HybridSuspend":true,"LockScreen":true,"Logout":true,"Standby":false,"Suspend":true}
powermanagement onNewData sourceName=Sleep States -
data={"Hibernate":true,"HybridSuspend":true,"LockScreen":true,"Logout":true,"Standby":false,"Suspend":true}
- Sleep
States={"Hibernate":true,"HybridSuspend":true,"LockScreen":true,"Logout":true,"Standby":false,"Suspend":true}
powermanagement source connected=Sleep States - Sleep
States={"Hibernate":true,"HybridSuspend":true,"LockScreen":true,"Logout":true,"Standby":false,"Suspend":true}
powermanagement source connected=PowerDevil - Sleep
States={"Hibernate":true,"HybridSuspend":true,"LockScreen":true,"Logout":true,"Standby":false,"Suspend":true}
suspendToRam - Sleep States={"objectName":"","Sleep
States":{"Hibernate":true,"HybridSuspend":true,"LockScreen":true,"Logout":true,"Standby":false,"Suspend":true}}
powermanagement source connected=Sleep States - Sleep
States={"Hibernate":true,"HybridSuspend":true,"LockScreen":true,"Logout":true,"Standby":false,"Suspend":true}


I found the issue is not reproducible in all my 3 laptops:
- Slimbook Pro : It does happen
- Slimbook Pro2: It does happen
- Lenovo E480  : It does NOT happen

All these 3 laptops use up-to-date Arch Linux distros.

If you need further detail or want me to test anything, please let me know.

Thank you!

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

[kmymoney] [Bug 397356] New: Ledger > Amount selection lost when switching windows

2018-08-10 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=397356

Bug ID: 397356
   Summary: Ledger > Amount selection lost when switching windows
   Product: kmymoney
   Version: 5.0.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: musik...@hotmail.com
  Target Milestone: ---

Hi,

When I'm either entering a new transaction or editing one in the ledger, I find
very annoying that the selection of the Amount field is lost when switching
windows. So, when you enter the new amount, it gets appended after the existing
one, instead of replacing it.

Steps to reproduce:
  1.- Create a new transaction in the ledger.
  2.- Fill up every field, moving to the next one by using the tab key.
  3.- When you are positioned in the Amount field, the default amount (0.00) is
selected.
  4.- Ctrl+Tab to check your bank account in your browser or third party
financial application.
  5.- Ctrl+Tab to come back to KMyMoney and enter the amount.
  6.- New value is appended after old one (0.00). The same applies when
editing. You need to manually delete the old value, and then enter the new one.

Expected behavior:
  1.- Same as before.
  2.- Same as before.
  3.- Same as before.
  4.- Same as before.
  5.- Same as before.
  6.- Existing value keeps selected, so when entering the new amount, old
amount is replaced with the new one.

Thanks your so much!

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

[Spectacle] [Bug 397072] Wishlist > Option to repeat last capture

2018-08-02 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=397072

--- Comment #3 from Musikolo  ---
Thanks for your prompt response.

I'm replying your questions below:

- Is that setting difficult to find, i.e. why did you miss to discover it?

It's not difficult to find, but it's really unexpected and not intuitive at
all. I would have never expected such an option for this action to be under the
"Configure" menu. Following this criteria, why don't we have options for other
actions such as "Active Window" or "On Click", ...etc. It's completely
unexpected.


- Should we check that setting by default, because otherwise it will be missed?

I would only shared the idea of enabling this option by default, if the UI
remains the same. However, I would prefer to add a new option/capture mode in
the "Area" dropdown list below "Rectangular Region" than changing the current
behavior. Such a new option/capture mode should be called something like
"Repeat Last Capture". It would work for rectangular regions, current screen,
or whatever the capture was before. Just repeat what I did before. It's simple,
it's intuitive, and it's easy to find and understand.


- Some argue that creating new rectangles will be more difficult when there is
already a preselected region. Could you try that and tell me if that is the
case for you?

I don't think creating rectangles becomes more difficult. However, we would be
changing the behavior just to cover the lack of an option/capture mode in the
"Area" dropdown list. The feeling I got when I tested for the first time it's a
bit strange. You click on the screen, and this time a rectangle is drawn. I'm
no longer creating the rectangle myself. Then, if I want to come back to the
old behavior, I have to go to the "Configure" menu and change the settings.
Strange... I don't standard actions should be hidden under the "Configure"
menu.

If you need anything else, please just let me know. It's great to collaborate
with you guys!

I hope it helps!

Best regards.

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

[Spectacle] [Bug 397072] New: Wishlist > Option to repeat last capture

2018-08-01 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=397072

Bug ID: 397072
   Summary: Wishlist > Option to repeat last capture
   Product: Spectacle
   Version: 18.04.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: musik...@hotmail.com
  Target Milestone: ---

I use Spectacle almost everyday, and I love it, but I often miss an option: a
feature to allow me to repeat the last capture.

Imagine you are getting screenshots of something in the screen that changes
over time. You want to capture the same rectangular region multiple times. You
would like your screenshots to share the same coordinates, so that when you
traverse them in your favorite image viewer, they look nice and transitions are
smooth.

As a suggestion, I think there should be another option called "Repeat last
capture" in the "Area" dropdown list. Then you click on the "Take a New
Screenshot" button, and voila!

Thank you!

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

[kmymoney] [Bug 390593] Clearing ledger search box doesn't return to the previous position

2018-02-17 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=390593

--- Comment #4 from Musikolo <musik...@hotmail.com> ---
I tried with Shift-Tab, and although it moves the focus on the ledger history
area, it still doesn't restore the position where I was.

In my case, I was checking the last entry (at the bottom) of my ledger, clicked
on the search box and typed something unrelated with the description of the
last entry. Then when I clicked on the cross (X) button to clear the search,
but the position is changed. I need to scroll down the history to restore the
position where I was. Same happens when I use Shift-Tab.

Thank you!

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

[kmymoney] [Bug 390593] Clearing ledger search box doesn't return to the previous position

2018-02-17 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=390593

--- Comment #2 from Musikolo <musik...@hotmail.com> ---
Unfortunately, your workaround doesn't work for me. When I use Alt-Tab, the
next application shows up, i.e., it cycles to the next application I have open.

It doesn't look like something very tough to fix, but I cannot state anything
since I don't know how the code is.

Thank you!

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

[kmymoney] [Bug 390593] New: Clearing ledger search box doesn't return to the previous position

2018-02-16 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=390593

Bug ID: 390593
   Summary: Clearing ledger search box doesn't return to the
previous position
   Product: kmymoney
   Version: 5.0.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: musik...@hotmail.com
  Target Milestone: ---

When you have a long ledger history and search something, if you click on the
cross (X) button to clear the search box, it doesn't return the focus to the
previous position. It's always changing the position to the top of the page
which is somehow annoying.

Thank you and congrats for your awesome job!

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

[okular] [Bug 169847] split view feature

2018-02-15 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=169847

--- Comment #27 from Musikolo <musik...@hotmail.com> ---
Sounds fair! Can you please pass me a link to the source code?

This said, I had no intention of pushing, because as you said, open source
software is all good will... ;-)

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

[okular] [Bug 169847] split view feature

2018-02-15 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=169847

--- Comment #25 from Musikolo <musik...@hotmail.com> ---
Is there any chance this feature gets eventually implemented? 

I'm asking because it was originally requested over 9 years ago, and I see
nothing that suggests it's coming anytime in the future.

Thank you and long live Okular!

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

[kmymoney] [Bug 390249] New: Ctrl+Shift+Space shortcut no longer available

2018-02-10 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=390249

Bug ID: 390249
   Summary: Ctrl+Shift+Space shortcut no longer available
   Product: kmymoney
   Version: 5.0.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: musik...@hotmail.com
  Target Milestone: ---

Hi

Since I upgraded to the version 5.0.0 of KMyMoney, I've noticed the shortcut
Ctrl+Shift+Space to mark a transaction as reconciled, no longer works. I've
also checked the "Configure Shortcuts" window, but I didn't find anything that
allowed me to create a shortcut to mark a transaction as reconciled.

This is a very convenient shortcut because it's very common action you do all
the time. It was available by default in the version 4.x. I would really
appreciate, if you could migrate/implement this shortcut to/in the new version
any time soon.

Thank you so much for the great job you are doing!

P.S: You can find more info under the section "Transaction Menu" at
https://docs.kde.org/trunk5/en/extragear-office/kmymoney/reference.html

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

[kmymoney] [Bug 390120] Toolbar height is overkill

2018-02-08 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=390120

Musikolo <musik...@hotmail.com> changed:

   What|Removed |Added

Summary|Toolbar height rending too  |Toolbar height is overkill
   |big |

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

[kmymoney] [Bug 390120] New: Toolbar height rending too big

2018-02-08 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=390120

Bug ID: 390120
   Summary: Toolbar height rending too big
   Product: kmymoney
   Version: 5.0.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: reports
  Assignee: kmymoney-de...@kde.org
  Reporter: musik...@hotmail.com
  Target Milestone: ---

Created attachment 110473
  --> https://bugs.kde.org/attachment.cgi?id=110473=edit
Toolbar height rending too big

Hi guys,

I've just installed Plasma 12 along with many wonderful KDE applications. Among
my updates it was KMyMoney 5.0.0. I've found a lot of changes in the new
version, and most of them are great. However, when you want to see a report,
I've noticed that the report toolbar is not rending well. The vertical space it
takes is too much. However, if I click on the "Chart" button, the toolbar
height looks good. Click again on "Report" button, and toolbar height is
overkill. 

I've attached a screenshot and highlighted the area not rendering well.

Please, let me know if you need further detail.

Thank you and congrats for the upgrade!

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

[frameworks-plasma] [Bug 385936] IconItem not displaying system-suspend icon correctly

2017-10-18 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=385936

--- Comment #2 from Musikolo <musik...@hotmail.com> ---
Created attachment 108450
  --> https://bugs.kde.org/attachment.cgi?id=108450=edit
Using breeze-dark icon full path

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

[frameworks-plasma] [Bug 385936] IconItem not displaying system-suspend icon correctly

2017-10-18 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=385936

--- Comment #1 from Musikolo <musik...@hotmail.com> ---
Created attachment 108449
  --> https://bugs.kde.org/attachment.cgi?id=108449=edit
Using breeze icon full path

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

[frameworks-plasma] [Bug 385936] New: IconItem not displaying system-suspend icon correctly

2017-10-18 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=385936

Bug ID: 385936
   Summary: IconItem not displaying system-suspend icon correctly
   Product: frameworks-plasma
   Version: 5.39.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: libplasmaquick
  Assignee: notm...@gmail.com
  Reporter: musik...@hotmail.com
  Target Milestone: ---

Created attachment 108448
  --> https://bugs.kde.org/attachment.cgi?id=108448=edit
Using icon name

Hi,

I'm the developer of plasma5-applets-system-panel plasmoid. You can find the
source code of this project at
https://github.com/Musikolo/plasma5-applets-system-panel

I've been working these days on adding icons for breeze-dark, the new theme
I've decided to use, since such a theme wasn't supported before. While doing
this, I've  noticed that IconItem is not working correctly for system-suspend
icon. I have no issues loading any other standard system-* icon.

I have a data structure that contains the icon name among other things:
-
https://github.com/Musikolo/plasma5-applets-system-panel/blob/master/src/package/contents/code/data.js

Using the above data structure, I'm loading the icon at:
-
https://github.com/Musikolo/plasma5-applets-system-panel/blob/master/src/package/contents/ui/main.qml#L117

When I use the icon name, default option, I get what you can see in attachment
1. However, if I pass the full path of the icon, it shows the icon as expected:
- breeze (attachment 2): /usr/share/icons/breeze/actions/22/system-suspend.svg
- breeze-dark (attachment 3):
/usr/share/icons/breeze-dark/actions/22/system-suspend.svg

All other icons shown in the screenshots are loaded by name, and they are
printed correctly. To my understanding, this is a bug since this is not the
desired/expected behavior. Furthermore, if I copy the image system-suspend.svg
as system-suspend2.svg under .../actions/22 folder, I can successfully use icon
name system-suspend2. This proves the image itself is good.

Please, let me know if you further details.


N.B: All screenshots have been zoomed-in 10X to better visualize my issue.

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

[frameworks-kio] [Bug 373062] WebDav - Cannot rename or delete files when special characters in the path

2017-09-04 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=373062

--- Comment #2 from Musikolo <musik...@hotmail.com> ---
Hi Elvis,

I've further looked into the issue and find out more information. The error I
get it's still occurring but the cause it's slightly different to what I
thought.

If I copy or move a file which name is having vowels with accents, the
operation completes successfully. When I try to rename the file, this is what I
get:

A) If I rename the file removing all accents, the operation succeeds.
B) If I rename the file keeping one or more accents, the operation fails with
an error message that says "Access was denied while attempting to move the
specified file or folder."

After that I can delete the file renamed in A) seamlessly. However, if try to
delete the file renamed in B), I get an error that says "The file or folder
webdavs://mysesrver/remote.php/webdav/adiós.txt does not exist." The problem
here is not related to the delete operation. The real issue is that after the
error, dolphin shows the file as successfully renamed and, when I try to delete
the file with the new name, the operation obviously fails because the naming
never happened. If I refresh and retry, I can successfully delete such a file
file.

>From command line, the same happens:
[me@MyPC tmp]$ kioclient5 copy 'a.txt' 'webdavs://myserver/remote.php/webdav/'
[me@MyPC tmp]$ kioclient5 move 'webdavs://myserver/remote.php/webdav/a.txt'
'webdavs://myserver/remote.php/webdav/b.txt'
[me@MyPC tmp]$ kioclient5 move 'webdavs://myserver/remote.php/webdav/b.txt'
'webdavs://myserver/remote.php/webdav/bá.txt'
"Access was denied while attempting to move the specified file or folder."
[me@MyPC tmp]$ kioclient5 move 'webdavs://myserver/remote.php/webdav/b.txt'
'webdavs://myserver/remote.php/webdav/ba.txt'
[me@MyPC tmp]$ kioclient5 ls 'webdavs://cubox.ddns.net/remote.php/webdav/' |
grep ba.txt
ba.txt
[me@MyPC tmp]$

So to sum up, the only issue we have is at renaming a file with accents.
Everything else is fine. Maybe dolphin should be updated to refresh the file
names even after an error occurs when renaming to prevent other operations to
fails afterwards.

I hope this helps and the issue gets fixed shortly.

Thank you!

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

[dolphin] [Bug 373062] New: WebDav - Cannot rename or delete files when special characters in the path

2016-11-28 Thread Musikolo
https://bugs.kde.org/show_bug.cgi?id=373062

Bug ID: 373062
   Summary: WebDav - Cannot rename or delete files when special
characters in the path
   Product: dolphin
   Version: 16.08.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: musik...@hotmail.com
  Target Milestone: ---

I've got a server with OwnCloud. I often manage my files with Dolphin through
the WebDav KIO. I would say everything used to work nicely, but since a few
weeks ago, I've noticed that I'm unable to rename files if there are special
characters (such as accented vowels) in the path. The same happens if you try
to delete a file having special characters in the path.

Dolphin shows an error message that reads: Access was denied while attempting
to move the specified file or folder.

The surprising thing is that I'm allowed to copy files with special characters
in the path (directory or filename itself) though.

P.S: My current dolphin version 16.08.3

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