[kwin] [Bug 366063] Window switcher does not start with specific key combination

[Mikiya Okuno via KDE Bugzilla]

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

--- Comment #4 from Mikiya Okuno  ---
Hi Martin,

The problem continues to happen after restarting KWin. The odd thing is that
window focus just switches to the previous window without displaying window
switcher. CTRL(changed from ALT)+TAB does something, but it's like unfinished.

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

[kwin] [Bug 366063] Window switcher does not start with specific key combination

[Mikiya Okuno via KDE Bugzilla]

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

--- Comment #2 from Mikiya Okuno  ---
Hi Martin,

I'm sorry for slow response. Your suspect is right. The problem happens only
when layout is changed using xmodmap. It doesn't happen when layout is changed
using GUI system settings. For example, "Left Alt as Ctrl, Left Ctrl as Win,
Left Win as Alt" doesn't cause a problem. (But there is no suitable
configuration for me in GUI system settings thoug... My preference is to just
swap Left Alt and Left Ctrol.)

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

[Powerdevil] [Bug 367698] New: only one screen is dimmed

[Mikiya Okuno via KDE Bugzilla]

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

Bug ID: 367698
   Summary: only one screen is dimmed
   Product: Powerdevil
   Version: 5.7.3
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-de...@kde.org
  Reporter: mikiya.ok...@gmail.com

I set "Dim screen" to 5 min on "Power Management"->"Energy Saving" setting at
"On AC Power" mode. I connect two monitors and clone output. After 5 minutes
idle time, only one of them is dimmed.

Reproducible: Always

Steps to Reproduce:
1. Connect two monitors.
2. Enable "Dim screen".
3. See if all monitors are dimmed.

Actual Results:  
Only the primary screen is dimmed.

Expected Results:  
All screens are dimmed.

"Screen Energy Saving" is okay. Two screens are powered off after the period.

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

[plasmashell] [Bug 366153] New: All Window Icons Are Intermittently Become "Active" on Task Manager Falsely

[Mikiya Okuno via KDE Bugzilla]

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

Bug ID: 366153
   Summary: All Window Icons Are Intermittently Become "Active" on
Task Manager Falsely
   Product: plasmashell
   Version: 5.7.2
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: mikiya.ok...@gmail.com
CC: plasma-b...@kde.org

When working on KF 5.24/KDE Plasma 5.7, window icons on task manager become
falsly active intermittently. I mean all window icons have same colors as if
they are active. After mouse over, window icons are fixed and become inactive
if they are actually inactive.

Reproducible: Sometimes

Steps to Reproduce:
1. Open/close windows.
2. Switch desktop using pager.
3. Make one window full-screen.
etc etc

Actual Results:  
You'll see the problem intermittently under normal operation.

Expected Results:  
Window icon should indicate the actual status.

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

[kwin] [Bug 339660] One key stroke misses on keyboard shortcut with two keyboards

[Mikiya Okuno via KDE Bugzilla]

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

Mikiya Okuno  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from Mikiya Okuno  ---
I'm sorry that I missed to respond to this bug. I do not experience the problem
any more (on 5.7.2).

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

[plasmashell] [Bug 366064] New: Alternative Shortcut for "Activate Appliction Menu Widget" Is Lost

[Mikiya Okuno via KDE Bugzilla]

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

Bug ID: 366064
   Summary: Alternative Shortcut for "Activate Appliction Menu
Widget" Is Lost
   Product: plasmashell
   Version: 5.7.2
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Application Menu (Kicker)
  Assignee: h...@kde.org
  Reporter: mikiya.ok...@gmail.com
CC: plasma-b...@kde.org

Alternative shortcut for "Activate Appliction Menu Widget" is lost on various
situations, such as log-out and log-in.

Reproducible: Always

Steps to Reproduce:
1. Open system settings -> Shortcuts -> Global Keyboard Shortcuts -> Plasma and
set alternative global for "Activate Appliction Menu Widget".
2. Log out Plasma session, then login again.
3. See the shortcut is lost.

Actual Results:  
The shortcut is lost.

Expected Results:  
The shortcut is available.

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

[kwin] [Bug 366063] New: Window switcher does not start with specific key combination

[Mikiya Okuno via KDE Bugzilla]

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

Bug ID: 366063
   Summary: Window switcher does not start with specific key
combination
   Product: kwin
   Version: 5.7.2
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: effects-various
  Assignee: kwin-bugs-n...@kde.org
  Reporter: mikiya.ok...@gmail.com

I change LEFT ALT to LEFT CTRL using Xmodmap. I register CTRL+TAB as "walk
through window". The key combination LEFT CTRL (originally LEFT ALT) + TAB
switches window to the previous one, but it doesn't display window switcher.
Although, RIGHT CTRL + TAb displays window switcher properly.

Reproducible: Always

Steps to Reproduce:
1. Use xmodmap to change LEFT ALT to LEFT CTRL.
2. Register CTRL+TAB as "walk through window".
3. Press LEFT CTRL (originally LEFT ALT) + TAB.

Actual Results:  
Switches window to the previous one, but it doesn't display window switcher.

Expected Results:  
Display window switcher.

shell> cat .Xmodmap
clear lock
clear control
clear mod1

keycode 64 = Control_L NoSymbol Control_L
keycode  66 = Control_L NoSymbol Control_L

add mod1 = Alt_L Meta_L
add control = Control_L Control_R

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

[konversation] [Bug 362404] Crash with ISO 2022-JP Charset

[Mikiya Okuno via KDE Bugzilla]

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

--- Comment #1 from Mikiya Okuno  ---
Crash will happen if getCodec() returns null on the following code:

uint currentLength =
getIdentity()->getCodec()->fromUnicode(channel).length();

getCodec() returns NULL because m_codec is set to NULL in
Identity::setCodecName().

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

[konversation] [Bug 362404] New: Crash with ISO 2022-JP Charset

[Mikiya Okuno via KDE Bugzilla]

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

Bug ID: 362404
   Summary: Crash with ISO 2022-JP Charset
   Product: konversation
   Version: 1.6
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konversation-de...@kde.org
  Reporter: mikiya.ok...@gmail.com

Crash happens if ISO 2022-JP charset is set to one of IRC server. This is
because KCharsets::codecForName() returns NULL for "ISO 2022-JP". To prevent
this issue, charset name should be changed to "ISO-2022-JP", which has two
hyphens instead of one space and one hyphen.

I filed bug #362401 for KCharsets problem. However, Konversation should also
handle the situation when KCharsets::codecForName() returns NULL, in order to
avoid crash.

Reproducible: Always

Steps to Reproduce:
1. Connect to server with Codec=ISO 2022-JP defined in konversationrc
2. See crash happens
3.

Actual Results:  
konversasion crashes.

Expected Results:  
It should report an error instead of crash.

Stacktrace

(gdb) bt
#0  QTextCodec::fromUnicode (this=0x0, str=...) at codecs/qtextcodec.cpp:806
#1  0x00540285 in Server::generateJoinCommand
(this=this@entry=0x1191220, tmpList=...) at
/home/portage/portage/net-irc/konversation-1.6/work/konversation-1.6/src/irc/server.cpp:3804
#2  0x00541213 in Server::updateAutoJoin (this=this@entry=0x1191220,
channels=...) at
/home/portage/portage/net-irc/konversation-1.6/work/konversation-1.6/src/irc/server.cpp:3775
#3  0x005446c6 in Server::Server (this=0x1191220, parent=, settings=...) at
/home/portage/portage/net-irc/konversation-1.6/work/konversation-1.6/src/irc/server.cpp:129
#4  0x00516f8c in ConnectionManager::connectTo
(this=this@entry=0xdb1540, flag=flag@entry=Konversation::CreateNewConnection,
settings=...) at
/home/portage/portage/net-irc/konversation-1.6/work/konversation-1.6/src/connectionmanager.cpp:155
#5  0x00517470 in ConnectionManager::connectTo (this=0xdb1540,
flag=flag@entry=Konversation::CreateNewConnection, serverGroupId=) at
/home/portage/portage/net-irc/konversation-1.6/work/konversation-1.6/src/connectionmanager.cpp:95
#6  0x004ef162 in Application::newInstance
(this=this@entry=0x7fffc3c0, args=args@entry=0x7fffc350) at
/home/portage/portage/net-irc/konversation-1.6/work/konversation-1.6/src/application.cpp:248
#7  0x004cc531 in main (argc=1, argv=) at
/home/portage/portage/net-irc/konversation-1.6/work/konversation-1.6/src/main.cpp:150

See "this" is NULL(0x0) at frame #0.

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

[frameworks-kdelibs4support] [Bug 362401] New: KCharsets::codecForName() returns null for "ISO 2022-JP"

[Mikiya Okuno via KDE Bugzilla]

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

Bug ID: 362401
   Summary: KCharsets::codecForName() returns null for "ISO
2022-JP"
   Product: frameworks-kdelibs4support
   Version: 5.20.0
  Platform: Gentoo Packages
   URL: http://api.kde.org/frameworks-api/frameworks5-apidocs/
kcodecs/html/classKCharsets.html
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: mikiya.ok...@gmail.com

It only accepts "ISO-2022-JP", as defined in "static const char
builtin_string[]" in kcharsets.cpp. IMHO, KCharsets::codecForName() should
accept charset name with or without hyphens.

Doe to this, Konversation crashed for my environment, where one of IRC server
has ISO 2022-JP charset :(

Reproducible: Always

Steps to Reproduce:
1. Call KCharsets::charsets()->codecForName("ISO 2022-JP");
2. Call KCharsets::charsets()->codecForName("ISO-2022-JP");
3. Compare difference

Actual Results:  
KCharsets::charsets()->codecForName("ISO 2022-JP") retunrs NULL

Expected Results:  
Shoudl return same result as
KCharsets::charsets()->codecForName("ISO-2022-JP").

n/a

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