[kwin] [Bug 466222] KDE does not remember which screen is being used after resume/restart on wayland

2023-02-22 Thread Ivan Tham
https://bugs.kde.org/show_bug.cgi?id=466222

Ivan Tham  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #4 from Ivan Tham  ---
(In reply to fw.smit01 from comment #2)
> Did you set the Ctrl-p shortcut yourself? It's not set by default in KDE. I
> haven't got this issue on my laptop
> 
> You can try removing the configuration at .local/share/kscreen/* to reset
> it. See if you can reproduce it again after that.

Yeah, after I removed those it works. Also, most likely I am going to ditch
wayland since it keep crashing the wayland session randomly for a few times.

Thanks.

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

[kwin] [Bug 466222] KDE does not remember which screen is being used after resume/restart on wayland

2023-02-22 Thread Ivan Tham
https://bugs.kde.org/show_bug.cgi?id=466222

--- Comment #3 from Ivan Tham  ---
> Did you set the Ctrl-p shortcut yourself? It's not set by default in KDE. I 
> haven't got this issue on my laptop

Sorry, I mean Super+p.

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

[frameworks-kconfig] [Bug 466222] KDE does not remember which screen is being used after resume/restart on wayland

2023-02-21 Thread Ivan Tham
https://bugs.kde.org/show_bug.cgi?id=466222

--- Comment #1 from Ivan Tham  ---
SUMMARY

After resume, I have to always set switch to external screen since I always
disable my laptop screen. In X11, I don't have to do this.

STEPS TO REPRODUCE
1. Ctrl+P, switch to external screen
2. Sleep-Resume / Restart

OBSERVED RESULT
KDE resets to show stuff on both screens

EXPECTED RESULT
KDE remembers which screen was being used

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.27.0
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.1.12-zen1-1.1-zen (64-bit)
Graphics Platform: Wayland
Processors: 6 × AMD Ryzen 5 4500U with Radeon Graphics
Memory: 15.0 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: TIMI
Product Name: RedmiBook 14 II

ADDITIONAL INFORMATION

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

[frameworks-kconfig] [Bug 466222] New: KDE does not remember which screen is being used after resume/restart on wayland

2023-02-21 Thread Ivan Tham
https://bugs.kde.org/show_bug.cgi?id=466222

Bug ID: 466222
   Summary: KDE does not remember which screen is being used after
resume/restart on wayland
Classification: Frameworks and Libraries
   Product: frameworks-kconfig
   Version: 5.103.0
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: matt...@mjdsystems.ca
  Reporter: pickf...@riseup.net
CC: kdelibs-b...@kde.org
  Target Milestone: ---

SUMMARY

After resume, I have to always set switch to external screen since I always
disable my laptop screen. In X11, I don't have to do this.

STEPS TO REPRODUCE
1. Ctrl+P, switch to external screen
2. Sleep-Resume / Restart
3. KDE resets to show stuff on both screens

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[kalendar] [Bug 450570] Imported calendar does not work and kalendar take very long to start

2022-10-07 Thread Ivan Tham
https://bugs.kde.org/show_bug.cgi?id=450570

--- Comment #3 from Ivan Tham  ---
Created attachment 152631
  --> https://bugs.kde.org/attachment.cgi?id=152631=edit
Calendar view

I went back to use calendar in kontact due to kalendar having too many
unnecessary animations and have to run a separate calendar app.

But I noticed that I have no control over the order of the calendars, then the
lunar calendar is going to show up jumbled up as the last calendar which makes
it quite unreadable. Maybe I should open a new issue for this?

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

[kalendar] [Bug 450570] Imported calendar does not work and kalendar take very long to start

2022-10-07 Thread Ivan Tham
https://bugs.kde.org/show_bug.cgi?id=450570

Ivan Tham  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |NOT A BUG
 Status|NEEDSINFO   |RESOLVED

--- Comment #2 from Ivan Tham  ---
Nice, it works now but it doesn't work directly, I need to do it a couple of
times retry a few more times to get it working.

Steps need to get it working:
1. open kalendar
2. configure kalendar (can't press ctrl+shift+, or kalendar will hang/lag),
need to press settings > configure kalendar
3. press kalendar sources tab
4. press add new kalendar source button
5. select iCal Calendar File
6. input
https://lwlsw.github.io/Chinese-Lunar-Calendar-ics/chinese_lunar_my.ics as
filename
7. input `Lunar Calendar` as display name
8. check read-only
9. press okay
10. close add new calendar source pop-up
11. now I see a new resource called akanodi_ical_resource_15 instead of `Lunar
Calendar`
12. press `Restart` for `Lunar Calendar` so `Lunar Calendar` is now added to my
list of calendars besides akanodi_ical_resource_15 (I can't delete this empty
calendar or the lunar calendar will be deleted too)
13. now only I see both `Lunar Calendar` and `akanodi_ical_resource_15` (I have
no idea what is this)
14. I am so not happy with the extra calendar name so I removed both and retry

Second try without inputting `Lunar Calendar` as display name first

1. open kalendar
2. configure kalendar (can't press ctrl+shift+, or kalendar will hang/lag),
need to press settings > configure kalendar
3. press kalendar sources tab
4. press add new kalendar source button
5. select iCal Calendar File
6. input
https://lwlsw.github.io/Chinese-Lunar-Calendar-ics/chinese_lunar_my.ics as
filename
7. close and wait for a couple of minutes (previously I thought it didn't work
and removed the calendar, but now because I am writing a reply to this ticket,
it just shows up), probably I just need to wait but I didn't know
8. close all pop-ups
9. right click `akonadi_ical_resource_17` calendar and press edit
10. enter `Lunar Calendar` as display name
11. select `moon-phase-full` as icon
12. press okay
13. it now works as expected, but imagine I tried this ~10 times in different
ways at different time in order to get this to work

A better way to solve this is to have kalendar have built-in support for
alternative calendars so I wouldn't have to do all this (search for a lunar
calendar, figure out how to get kalendar to import, figure out I need to wait
for a couple of minutes for it to work).

But yeah, can close this ticket since I figured out how to get it working.

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

[kalendar] [Bug 450571] New: LC_TIME zh_CN.UTF-8 letter only weekday label length is invalid

2022-02-19 Thread Ivan Tham
https://bugs.kde.org/show_bug.cgi?id=450571

Bug ID: 450571
   Summary: LC_TIME zh_CN.UTF-8 letter only weekday label length
is invalid
   Product: kalendar
   Version: 1.0.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: claudio.cam...@gmail.com
  Reporter: pickf...@riseup.net
CC: c...@carlschwan.eu
  Target Milestone: ---

SUMMARY
When using LC_TIME zh_CN.UTF-8, when weekday label length is set to letter only
(M), the letter chosen is incorrect.

STEPS TO REPRODUCE
1. Set LC_TIME to zh_CN.UTF-8
2. Set weekday label length to letter only (M)

OBSERVED RESULT
It shows 周, 周, 周, 周, 周, 周, 周 for S, M, T, W, T, F, S (hopefully I am correct
since I don't use english for time).

EXPECTED RESULT
It should have shown 日, 一, 二, 三, 四, 五, 六. It should have take the last
character instead of the first when using zh_CN (and related chinese locale).

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.24.1
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2
Kernel Version: 5.16.10-zen1-1-zen (64-bit)
Graphics Platform: X11
Processors: 6 × AMD Ryzen 5 4500U with Radeon Graphics
Memory: 15.1 GiB of RAM
Graphics Processor: AMD RENOIR

ADDITIONAL INFORMATION

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

[kalendar] [Bug 450570] New: Imported calendar does not work and kalendar take very long to start

2022-02-19 Thread Ivan Tham
https://bugs.kde.org/show_bug.cgi?id=450570

Bug ID: 450570
   Summary: Imported calendar does not work and kalendar take very
long to start
   Product: kalendar
   Version: 1.0.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: claudio.cam...@gmail.com
  Reporter: pickf...@riseup.net
CC: c...@carlschwan.eu
  Target Milestone: ---

SUMMARY
Since kalendar does not support alternative calendars as chinese (agricultural)
calendar, I imported a chinese calendar from
https://github.com/lwlsw/Chinese-Lunar-Calendar-ics using
https://lwlsw.github.io/Chinese-Lunar-Calendar-ics/chinese_lunar_my.ics, it
does not seemed to work (maybe because it's large?) so I removed the calendar
source and now it took 1 minute to start.

STEPS TO REPRODUCE
1. Import calendar source
https://lwlsw.github.io/Chinese-Lunar-Calendar-ics/chinese_lunar_my.ics

OBSERVED RESULT
Thing seemed to be slow now, calendar does not work and even though the
calendar source is removed it is still slow to start, the new calendar source I
also can't seemed to remove it from the sidebar (I tried both delete calendar
and delete calendar source but it is still stuck there).

EXPECTED RESULT
Calendar should show up and works without side effect.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.24.1
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2
Kernel Version: 5.16.10-zen1-1-zen (64-bit)
Graphics Platform: X11
Processors: 6 × AMD Ryzen 5 4500U with Radeon Graphics
Memory: 15.1 GiB of RAM
Graphics Processor: AMD RENOIR

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 431549] Multi X-pointer second keyboard input does not work even when invoked

2021-01-14 Thread Ivan Tham
https://bugs.kde.org/show_bug.cgi?id=431549

--- Comment #2 from Ivan Tham  ---
So multi-pointer will never be supported in Qt?

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

[plasmashell] [Bug 431549] Multi X-pointer second keyboard input does not work even when invoked

2021-01-13 Thread Ivan Tham
https://bugs.kde.org/show_bug.cgi?id=431549

Ivan Tham  changed:

   What|Removed |Added

 CC||pickf...@riseup.net

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

[plasmashell] [Bug 431549] New: Multi X-pointer second keyboard input does not work even when invoked

2021-01-13 Thread Ivan Tham
https://bugs.kde.org/show_bug.cgi?id=431549

Bug ID: 431549
   Summary: Multi X-pointer second keyboard input does not work
even when invoked
   Product: plasmashell
   Version: 5.20.5
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: k...@davidedmundson.co.uk
  Reporter: pickf...@riseup.net
CC: mikel5...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

SUMMARY
Second keyboard for second pointer (or input master) does not work even though
the second keyboard is used to open kickoff (and the same thing happened to
krunner), even when the second keyboard is used to start kickoff but only the
first keyboard (in first input master) is able to type something. 

STEPS TO REPRODUCE
1. xinput create-master
2. xinput reattach (all the second mouse and keyboard)
https://wiki.archlinux.org/index.php/Multi-pointer_X#xinput_utility
3. super (I binded it to alt-f1) from the second input master/keyboard
4. Type something from the second input master/keyboard

OBSERVED RESULT
Only the keyboard from first input master is able to type something, the second
input master is not able to type anything, even if the second pointer is
updated to use the first input master. The same thing is observed for krunner.

EXPECTED RESULT
Second keyboard from second input master should be able to search kickoff
instead of the first keyboard from first input master since it is the one that
initiated it, also the first keyboard should also be able to input if the if
the first pointer clicked on kickoff search bar. Right now second keyboard
can't even enter anything even if the second pointer clicked on the search bar.
The same thing is expected from krunner.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Linux mi 5.10.6-zen1-1-zen #1 ZEN SMP PREEMPT Sat, 09 Jan
2021 18:22:39 + x86_64 GNU/Linux
(available in About System)
Operating System: Arch Linux
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2
Kernel Version: 5.10.6-zen1-1-zen
OS Type: 64-bit
Processors: 6 × AMD Ryzen 5 4500U with Radeon Graphics
Memory: 15.1 GiB of RAM
Graphics Processor: AMD RENOIR

ADDITIONAL INFORMATION
This happens to krunner as well.

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

[akregator] [Bug 406379] Magnet Links not recognised correctly

2020-10-23 Thread Ivan Tham
https://bugs.kde.org/show_bug.cgi?id=406379

Ivan Tham  changed:

   What|Removed |Added

 CC||pickf...@riseup.net

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

[ktorrent] [Bug 409070] Ktorrent not handling magnet links

2020-10-23 Thread Ivan Tham
https://bugs.kde.org/show_bug.cgi?id=409070

Ivan Tham  changed:

   What|Removed |Added

 CC||pickf...@riseup.net

--- Comment #6 from Ivan Tham  ---
The issue is the magnet link is prepended with the original url. Related issue,
https://bugs.kde.org/show_bug.cgi?id=406379 and
https://bugs.kde.org/show_bug.cgi?id=392321

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

[kdeconnect] [Bug 409530] New: Not able to use virtual keyboard

2019-07-05 Thread Ivan Tham
https://bugs.kde.org/show_bug.cgi?id=409530

Bug ID: 409530
   Summary: Not able to use virtual keyboard
   Product: kdeconnect
   Version: 1.3.4
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: messaging-application
  Assignee: si...@ergotech.com
  Reporter: pickf...@riseup.net
  Target Milestone: ---

SUMMARY
On non-KDE, specifically on tiling manager (dwm) with systray.
kdeconnect-indicator is not able to transfer keypress to mobile.

STEPS TO REPRODUCE
1. Start kdeconnect-indicator and setup all the permissions needed.
2. Start kdeconnect on mobile and switch to kdeconnect virtual keyboard.
3. Start typing on desktop (even tried clicking on kdeconnect applet icon but
nothing happens).

OBSERVED RESULT
Keypress are not captured by kdeconnect.

EXPECTED RESULT
Keypress are captured and sent to phone.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Linux arch 5.1.15-arch1-1-ARCH #1 SMP PREEMPT Tue Jun 25
04:49:39 UTC 2019 x86_64 GNU/Linux
(available in About System)
KDE Plasma Version: -
KDE Frameworks Version: 5.59.0
Qt Version: 5.13.0

ADDITIONAL INFORMATION
No desktop environment
Window manager - dwm from git + systray
IME - fcitx (english, pinyin, mozc) but not toggled during testing
Firewall disabled and other functionalities work

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