[plasmashell] [Bug 401029] Task manager shows Hangouts with generic Chrome icon
https://bugs.kde.org/show_bug.cgi?id=401029 --- Comment #3 from Jurica Vukadin --- The problem is that google-chrome.desktop as shipped has StartupWMClass=Google-chrome, so all Chrome windows always match on appId (i.e. XClassHint::res_class). xWindowsWMClassName (XClassHint::res_name) and rewrite rules are never even evaluated. Shouldn't the xWindowsWMClassName be evaluated first, since it is more specific? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401029] Task manager shows Hangouts with generic Chrome icon
https://bugs.kde.org/show_bug.cgi?id=401029 --- Comment #1 from Jurica Vukadin --- Created attachment 116305 --> https://bugs.kde.org/attachment.cgi?id=116305=edit Patch Matching xWindowsWMClassName before appId fixes it for me. No need for rules in taskmanagerrulesrc either. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401029] New: Task manager shows Hangouts with generic Chrome icon
https://bugs.kde.org/show_bug.cgi?id=401029 Bug ID: 401029 Summary: Task manager shows Hangouts with generic Chrome icon Product: plasmashell Version: 5.14.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: u.ra...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Task manager (as well as Icon only task manager) always shows Hangouts with the generic Chrome icon. I tried adding the following rule for Chrome in /etc/xdg/taskmanagerrulesrc: [Rewrite Rules][Google-chrome][1] Property=ClassName Identifier=StartupWMClass Match=(?<=crx_)(?'match'[a-z]+) Target=chrome-%1-default I also have the following desktop file in .local/share/applications/, named chrome-nckgahadagoaajjgafhacjanaoiihapd-default.desktop: [Desktop Entry] Version=1.0 Terminal=false Type=Application Name=Google Hangouts Icon=chrome-nckgahadagoaajjgafhacjanaoiihapd-default NoDisplay=true Exec=/opt/google/chrome/chrome StartupWMClass=crx_nckgahadagoaajjgafhacjanaoiihapd The icons are in: .local/share/icons/hicolor/128x128/apps/chrome-nckgahadagoaajjgafhacjanaoiihapd-default.png .local/share/icons/hicolor/48x48/apps/chrome-nckgahadagoaajjgafhacjanaoiihapd-default.png And yet, both task managers always show the generic Chrome icon. If I set the NoDisplay property to false, I can see the launcher in the application menu (under the Lost section) with the correct Hangouts icon. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401029] Task manager shows Hangouts with generic Chrome icon
https://bugs.kde.org/show_bug.cgi?id=401029 --- Comment #6 from Jurica Vukadin --- Oh, I see, it wants file:// + the absolute path to the .desktop file. Working fine now. Thanks for your support. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401029] Task manager shows Hangouts with generic Chrome icon
https://bugs.kde.org/show_bug.cgi?id=401029 --- Comment #5 from Jurica Vukadin --- Okay, I added: Google-chrome::crx_nckgahadagoaajjgafhacjanaoiihapd=chrome-nckgahadagoaajjgafhacjanaoiihapd-default.desktop to the mapping section of taskmanagerrulesrc. This works, but now the taskbar ignores the icon set in the .desktop file and uses the one it pulled from the _NET_WM_ICON atom, which is unfortunately only 16x16 in size. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 365255] inconsistent behavior with alt+7
https://bugs.kde.org/show_bug.cgi?id=365255 --- Comment #11 from Jurica Vukadin --- It seems the 'grave' keysym (mapped to the 3rd level of the '7' key on Croatian layout) has something to do with this. Similarly, the 'asciitilde' keysym prevents Alt+1 from working. If I remove or replace the keysyms, or move them to the 1st or 2nd level, the shortcuts start working. I.e., for key 7 (AE07): symbols[Group1]= [ 7, slash, grave, dead_grave ] # default, doesn't work symbols[Group1]= [ 7, slash, dead_grave, grave ] # doesn't work symbols[Group1]= [ 7, grave, slash, dead_grave ] # works symbols[Group1]= [ 7, slash, 7, dead_grave ] # works symbols[Group1]= [ 7, slash ]# works Can also be reproduced with the German layout: setxkbmap de # dump the layout xkbcomp $DISPLAY de.xkb # edit the entry for the 7 key in de.xkb, e.g.: # -symbols[Group1]= [ 7, slash, braceleft,seveneighths ] # +symbols[Group1]= [ 7, slash, grave, seveneighths ] # set the modified layout xkbcomp de.xkb $DISPLAY Alt+7 is busted now. Also, it seems bugs #310881 and #398069 are the same as this one. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 365255] inconsistent behavior with alt+7
https://bugs.kde.org/show_bug.cgi?id=365255 Jurica Vukadin changed: What|Removed |Added CC||u.ra...@gmail.com --- Comment #10 from Jurica Vukadin --- I've been poking at this in my spare time. It seems Alt+7 (and Alt+1 as well, I'm using Croatian layout), gets intercepted by KGlobalAccelImpl::nativeEventFilter(), while the others do not. I've added some debug prints to KGlobalAccelImpl::nativeEventFilter() and get this when I hit Alt+7: responseType: 2 Got XKeyPress event keyQt= "837" (this is Qt::AltModifier | Qt::Key_7) For others I only get "responseType: 85" when I hit the Alt key. Any clues how I can chase this down further? -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 407389] New: Unable to configure PEAP-EAP-TLS in the editor
https://bugs.kde.org/show_bug.cgi?id=407389 Bug ID: 407389 Summary: Unable to configure PEAP-EAP-TLS in the editor Product: plasma-nm Version: 5.15.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: editor Assignee: jgrul...@redhat.com Reporter: u.ra...@gmail.com Target Milestone: --- My company uses the not-so-popular PEAP-EAP-TLS for wired 802.1x security, where the phase 2 auth is TLS. The connection editor does not allow for this, and only lists MSCHAPv2, MD5, and GTC as phase 2 auth options. It would be great if there was support for this in the editor, since it is supported by the NetworkManager itself, i.e., the following semi-manually crafted config file gets the connection up and running: [connection] id=Wired connection 1 uuid=324df8f5-49e5-3b33-af23-be59d14e45bf type=ethernet autoconnect-priority=-100 permissions= [ethernet] auto-negotiate=true mac-address=xx:xx:xx:xx:xx mac-address-blacklist= [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=ignore [802-1x] eap=peap identity=host/XXX.domain.local ca-path=/etc/ssl/certs phase1-peapver=0 phase2-autheap=tls phase2-ca-path=/etc/ssl/certs phase2-private-key=file:///etc/wpa_supplicant/.domain.local.p12 phase2-private-key-password=x -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401029] Task manager shows Hangouts with generic Chrome icon
https://bugs.kde.org/show_bug.cgi?id=401029 --- Comment #8 from Jurica Vukadin --- Still present on 5.23.90. Let me know what further info is needed. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 464590] New: kded5 crash after monitor wakes from sleep
https://bugs.kde.org/show_bug.cgi?id=464590
Bug ID: 464590
Summary: kded5 crash after monitor wakes from sleep
Classification: Plasma
Product: KScreen
Version: 5.26.90
Platform: Archlinux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: common
Assignee: kscreen-bugs-n...@kde.org
Reporter: u.ra...@gmail.com
Target Milestone: ---
SUMMARY
Thread 1 (Thread 0x7ff0ee639840 (LWP 25283)):
#0 __pthread_kill_implementation (threadid=,
signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44
#1 0x7ff0ee2a16b3 in __pthread_kill_internal (signo=11,
threadid=) at pthread_kill.c:78
#2 0x7ff0ee251938 in __GI_raise (sig=11) at raise.c:26
#3 0x7ff0ef7dd37c in KCrash::defaultCrashHandler(int) (sig=11) at
kcrash.cpp:611
#4 0x7ff0ee2519e0 in () at /usr/lib/libc.so.6
#5 KScreen::Output::id() const (this=0x0) at output.cpp:189
#6 0x7ff0d408171d in
KScreen::Config::setOutputPriority(QSharedPointer const&,
unsigned int) (this=0x7ff0dc006980, output=..., priority=1) at
qsharedpointer_impl.h:301
#7 0x7ff0d408b26f in
KScreen::SetConfigOperationPrivate::fixPrimaryOutput() (this=)
at qsharedpointer_impl.h:301
#8 KScreen::SetConfigOperation::start() (this=0x55dd8d2953c0) at
setconfigoperation.cpp:114
#9 0x7ff0eeab1a70 in QObject::event(QEvent*) (this=0x55dd8d2953c0,
e=0x55dd8cfd9720) at qobject.cpp:1347
#10 0x7ff0ef978b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x55dd8d2953c0, e=0x55dd8cfd9720) at
qapplication.cpp:3640
#11 0x7ff0eea8de08 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x55dd8d2953c0, event=0x55dd8cfd9720) at qcoreapplication.cpp:1064
#12 0x7ff0eea8e913 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=0x0, event_type=0, data=0x55dd8c9e4f20) at
qcoreapplication.cpp:1821
#13 0x7ff0eead4d48 in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=0x55dd8caf3950) at qeventdispatcher_glib.cpp:277
#14 0x7ff0eda6d87b in g_main_dispatch (context=0x7ff0e4005010) at
gmain.c:3454
#15 g_main_context_dispatch (context=0x7ff0e4005010) at gmain.c:4172
#16 0x7ff0edac4c89 in g_main_context_iterate.constprop.0
(context=0x7ff0e4005010, block=1, dispatch=1, self=) at
gmain.c:4248
#17 0x7ff0eda6c132 in g_main_context_iteration (context=0x7ff0e4005010,
may_block=1) at gmain.c:4313
#18 0x7ff0eead8b2c in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x55dd8caf7f20, flags=...) at qeventdispatcher_glib.cpp:423
#19 0x7ff0eea865ac in
QEventLoop::exec(QFlags) (this=0x7ffd4d226bf0,
flags=...) at qflags.h:69
#20 0x7ff0eea910d9 in QCoreApplication::exec() () at qflags.h:121
#21 0x7ff0eef39fe2 in QGuiApplication::exec() () at
qguiapplication.cpp:1870
#22 0x7ff0ef976f2a in QApplication::exec() () at qapplication.cpp:2832
#23 0x55dd8ab71040 in main(int, char**) (argc=,
argv=) at kded.cpp:785
STEPS TO REPRODUCE
Happens every time monitor wakes from sleep.
ADDITIONAL INFORMATION
I only have a single display connected via display port, nothing special.
cat .local/share/kscreen/a37e14e3c2e6a407e13f5a947ec3f01a
[
{
"enabled": true,
"id": "8da2bf5db1a73ca49dd6dc4ceb00755b",
"metadata": {
"fullname": "xrandr-LG Electronics-LG Ultra HD-406240",
"name": "DisplayPort-0"
},
"mode": {
"refresh": 59.99662399291992,
"size": {
"height": 2160,
"width": 3840
}
},
"overscan": 0,
"pos": {
"x": 0,
"y": 0
},
"priority": 1,
"rgbrange": 0,
"rotation": 1,
"scale": 1,
"vrrpolicy": 2
}
]
cat .local/share/kscreen/outputs/8da2bf5db1a73ca49dd6dc4ceb00755b
{
"id": "8da2bf5db1a73ca49dd6dc4ceb00755b",
"metadata": {
"fullname": "xrandr-LG Electronics-LG Ultra HD-406240",
"name": "DisplayPort-0"
},
"mode": {
"refresh": 59.99662399291992,
"size": {
"height": 2160,
"width": 3840
}
},
"overscan": 0,
"rgbrange": 0,
"rotation": 1,
"scale": 1,
"vrrpolicy": 2
}
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 481736] Notifications pops up in the middle of the screen after being away from pc for a while
https://bugs.kde.org/show_bug.cgi?id=481736 Jurica Vukadin changed: What|Removed |Added CC||u.ra...@gmail.com --- Comment #2 from Jurica Vukadin --- Created attachment 166054 --> https://bugs.kde.org/attachment.cgi?id=166054=edit Notification position I am seeing the same on RC2 even without idle, regardless of the system settings config. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481736] Notifications pops up in the middle of the screen after being away from pc for a while
https://bugs.kde.org/show_bug.cgi?id=481736 --- Comment #8 from Jurica Vukadin --- Seems to be X11-only in my case. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481736] Notifications pops up in the middle of the screen after being away from pc for a while
https://bugs.kde.org/show_bug.cgi?id=481736 --- Comment #5 from Jurica Vukadin --- (In reply to Nate Graham from comment #4) > Are folks who could reproduce this issue in the past still able to do so > with the final 6.0 release? Yep, and it does seem to have something to do with DPMS. I just reproduced it with: $ xset dpms force off $ notify-send test -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481736] On X11, Notifications pop up in the middle of the screen after being away from pc for a while
https://bugs.kde.org/show_bug.cgi?id=481736 Jurica Vukadin changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #18 from Jurica Vukadin --- Still seeing this with Arch 6.0.3 packages. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481736] On X11, Notifications pop up in the middle of the screen after being away from pc for a while
https://bugs.kde.org/show_bug.cgi?id=481736 --- Comment #23 from Jurica Vukadin --- Created attachment 167990 --> https://bugs.kde.org/attachment.cgi?id=167990=edit New notification. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481736] On X11, Notifications pop up in the middle of the screen after being away from pc for a while
https://bugs.kde.org/show_bug.cgi?id=481736 --- Comment #20 from Jurica Vukadin --- I ran this: notify-send -t $((60 * 1000)) "old notification" sleep 5 spectacle -bfn xset dpms force off sleep 30 xset dpms force on sleep 5 spectacle -bfn "old notification" was in the correct position before going to sleep. It moved slightly up after waking. I then did a notify-send "new notification" and that showed up the mid-low-center. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481736] On X11, Notifications pop up in the middle of the screen after being away from pc for a while
https://bugs.kde.org/show_bug.cgi?id=481736 --- Comment #21 from Jurica Vukadin --- Created attachment 167988 --> https://bugs.kde.org/attachment.cgi?id=167988=edit Old notification before sleep. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481736] On X11, Notifications pop up in the middle of the screen after being away from pc for a while
https://bugs.kde.org/show_bug.cgi?id=481736 --- Comment #22 from Jurica Vukadin --- Created attachment 167989 --> https://bugs.kde.org/attachment.cgi?id=167989=edit Old notification after sleep. -- You are receiving this mail because: You are watching all bug changes.
