[plasma-nm] [Bug 479937] New: [openeconnect] Timeout after authentication connecting to GlobalProtect VPN
https://bugs.kde.org/show_bug.cgi?id=479937 Bug ID: 479937 Summary: [openeconnect] Timeout after authentication connecting to GlobalProtect VPN Classification: Plasma Product: plasma-nm Version: 5.27.10 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: knut.tidem...@gmail.com Target Milestone: --- SUMMARY When trying to connect to my work place's GlobalProtect VPN, the connection times out after the authentication and gateway selection phase. This used to work some time ago (roughly 1 year ago), but I do not use this often enough to pinpoint when in stopped working. It could also be something that changed one the server side. What does work is to connect using 'nmcli --ask connection up VPN', so it's definitely something with plasma-nm. STEPS TO REPRODUCE 1. Connect to GlobalProtect VPN 2. Enter username / password and log in 3. Select gateway and the authentication window closes. Timeout occurs in ~1 minute. OBSERVED RESULT Log output is somewhat lacking: Jan 17 11:17:16 kyle NetworkManager[790]: [1705486636.7962] vpn[0x64677478fac0,040f8208-cd33-45b7-8f5a-8805f67317d1,"VPN"]: starting openconnect Jan 17 11:17:16 kyle NetworkManager[790]: [1705486636.7964] audit: op="connection-activate" uuid="040f8208-cd33-45b7-8f5a-8805f67317d1" name="VPN" pid=1205 uid=1000 result="success" Jan 17 11:17:16 kyle kernel: tun: Universal TUN/TAP device driver, 1.6 Jan 17 11:17:16 kyle kded5[1146]: org.kde.plasma.nm.kded: Unhandled VPN connection state change: NetworkManager::VpnConnection::NeedAuth Jan 17 11:17:16 kyle kded5[1146]: kf.networkmanagerqt: void NetworkManager::ConnectionPrivate::onPropertiesChanged(const QVariantMap&) Unhandled property "VersionId" Jan 17 11:17:16 kyle plasmashell[1205]: kf.networkmanagerqt: void NetworkManager::ConnectionPrivate::onPropertiesChanged(const QVariantMap&) Unhandled property "VersionId" Jan 17 11:17:16 kyle kded5[1146]: kf.networkmanagerqt: void NetworkManager::ConnectionPrivate::onPropertiesChanged(const QVariantMap&) Unhandled property "VersionId" Jan 17 11:17:16 kyle plasmashell[1205]: kf.networkmanagerqt: void NetworkManager::ConnectionPrivate::onPropertiesChanged(const QVariantMap&) Unhandled property "VersionId" Jan 17 11:17:17 kyle plasmashell[1205]: file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment" Jan 17 11:17:18 kyle kded5[1146]: QFormLayout::takeAt: Invalid index 0 Jan 17 11:17:39 kyle kded5[1146]: QFormLayout::takeAt: Invalid index 0 Jan 17 11:17:39 kyle kded5[1146]: kf.networkmanagerqt: void NetworkManager::ConnectionPrivate::onPropertiesChanged(const QVariantMap&) Unhandled property "VersionId" Jan 17 11:17:39 kyle kded5[1146]: org.kde.plasma.nm.kded: Unhandled VPN connection state change: NetworkManager::VpnConnection::Connecting Jan 17 11:17:39 kyle NetworkManager[790]: [1705486659.2530] manager: (vpn0): new Tun device (/org/freedesktop/NetworkManager/Devices/3) Jan 17 11:17:39 kyle plasmashell[1205]: kf.networkmanagerqt: void NetworkManager::ConnectionPrivate::onPropertiesChanged(const QVariantMap&) Unhandled property "VersionId" Jan 17 11:17:39 kyle kded5[1146]: kf.networkmanagerqt: void NetworkManager::ConnectionPrivate::onPropertiesChanged(const QVariantMap&) Unhandled property "VersionId" Jan 17 11:17:39 kyle NetworkManager[790]: [1705486659.2563] audit: op="connection-update" uuid="040f8208-cd33-45b7-8f5a-8805f67317d1" name="VPN" args="connection.timestamp,vpn.secrets" pid=1146 uid=1000 result="success" Jan 17 11:17:39 kyle NetworkManager[3631]: POST https://1.2.3.4/ssl-vpn/getconfig.esp Jan 17 11:17:39 kyle plasmashell[1205]: kf.networkmanagerqt: void NetworkManager::ConnectionPrivate::onPropertiesChanged(const QVariantMap&) Unhandled property "VersionId" Jan 17 11:17:39 kyle NetworkManager[3631]: Connected to 1.2.3.4:443 Jan 17 11:17:39 kyle NetworkManager[3631]: SSL negotiation with 1.2.3.4 Jan 17 11:17:39 kyle NetworkManager[3631]: Server certificate verify failed: signer not found Jan 17 11:17:39 kyle NetworkManager[3631]: Connected to HTTPS on 1.2.3.4 with ciphersuite (TLS1.2)-(ECDHE-SECP256R1)-(RSA-SHA256)-(AES-256-GCM) Jan 17 11:17:46 kyle NetworkManager[790]: [170548.3772] audit: op="statistics" interface="enp6s0" ifindex=2 args="2000" pid=1205 uid=1000 result="success" Jan 17 11:17:48 kyle plasmashell[1205]: file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment" Jan 17 11:17:49 kyle kwin_wayland[1006]: This plugin does not support raise() Jan 17 11:18:39 kyle NetworkManager[790]: [1705486719.9773] vpn[0x64677478fac0,040f8208-cd33-45b7-8f5a-8805f67317d1,"VPN"]: connect timeout exceeded Jan 17 11:18:39 kyle nm
[plasmashell] [Bug 476507] Double f (ff) in window title joined and rendered as single special character in the multiple window selection popup
https://bugs.kde.org/show_bug.cgi?id=476507 --- Comment #2 from Knut Andre Tidemann --- After doing a package upgrade and rebooting, I'm unable to reproduce this, so I think we can close it. Sorry for the noise, not sure how this happened, but it was consistent until it was not... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476507] New: Double f (ff) in window title joined and rendered as single special character in the multiple window selection popup
https://bugs.kde.org/show_bug.cgi?id=476507 Bug ID: 476507 Summary: Double f (ff) in window title joined and rendered as single special character in the multiple window selection popup Classification: Plasma Product: plasmashell Version: 5.27.9 Platform: Archlinux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: knut.tidem...@gmail.com CC: qydwhotm...@gmail.com Target Milestone: 1.0 Created attachment 162842 --> https://bugs.kde.org/attachment.cgi?id=162842&action=edit Task Manager character bug SUMMARY When multiple windows of the same application are open and the Task Manager joins them in a single icon you get a pop-up menu when pressing that icon. In this icon the windows are listed with their titles as entries in a popup menu. If a window title has two f's in it, it will be rendered as special character instead. See the attached screenshot. Note that this does not happen in the actual window title, in this case of the KWrite window. My locale settings are: LANG=en_US.UTF-8 LC_MEASUREMENT=nb_NO.UTF-8 LC_TIME=en_GB.UTF-8 SOFTWARE/OS VERSIONS Linux kernel: 6.5.8-arch1-1 (64-bit) KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 (5.15.11+kde+r138-1) Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 455239] New: KRunner does not update search list on 'Enter' fast enough, causes wrong application to launch
https://bugs.kde.org/show_bug.cgi?id=455239 Bug ID: 455239 Summary: KRunner does not update search list on 'Enter' fast enough, causes wrong application to launch Product: krunner Version: 5.24.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.loh...@gmx.de Reporter: knut.tidem...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY If you launch KRunner with alt+f2 and then start typing, the previous search result of the last krunner instance are still shown in the list for the first second or so, even if you begin to type something else. If you are fast typer and write the name of a new application and press 'Enter' it will launch the top result of the last search instead of the new application. This was tested on X.org with the NVidia proprietary driver 515.48.07. CPU and memory are AMD Ryzen 9 5900X and 32GB, so it should not be the hardware that's the problem here. This happens even if krunner is 'hot' in memory. STEPS TO REPRODUCE 1. Start an application through krunner, for example 'kate'. 2. Press alt+f2, then quickly type something else like 'kwrite' and press enter. 3. Notice that 'kate' is now being opened if you did this fast enough, typically in the range of 1-2 seconds. OBSERVED RESULT The wrong application is launched, in this case 'kate'. EXPECTED RESULT The list should be updated before the applicaiton execution happens, which would result in the correct application launching. In this case 'kwrite'. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.24.5-2 KDE Frameworks Version: 5.94.0-1 Qt Version: 5.15.4+kde+r146-1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440894] QtCreator pop-ups steal focus and are moved to top of window stack under wayland
https://bugs.kde.org/show_bug.cgi?id=440894 --- Comment #2 from Knut Andre Tidemann --- Well, thanks for the workaround at least! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440894] New: QtCreator pop-ups steal focus and are moved to top of window stack under wayland
https://bugs.kde.org/show_bug.cgi?id=440894 Bug ID: 440894 Summary: QtCreator pop-ups steal focus and are moved to top of window stack under wayland Product: kwin Version: 5.22.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: knut.tidem...@gmail.com Target Milestone: --- SUMMARY When changing a file opened in Qt Creator from another application, such as the terminal, a pop-up window will appear and steal the focus, asking to reload the contents of the file. This steals both keyboard focus and is put in front of all other windows. This really messes up with any ongoing typing. This might happen with other applications that have this behavior as well, but I've only really noticed it with Qt Creator. The behavior changed from plasma 5.21 to 5.22 as the popup was kept in the background in 5.21. Even setting focus stealing prevention for the Qt Creator application to 'Extreme' does not seem to resolve the issue. STEPS TO REPRODUCE 1. Open a file in Qt Creator 2. Change this file from the terminal OBSERVED RESULT Qt Creator and its pop-up notification steal focus and move to the front of the stack. EXPECTED RESULT The popup is opened in the background and does not steal keyboard focus. SOFTWARE/OS VERSIONS Linux: Arch Linux KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412684] [Wayland] kwin_wayland[3904]: segfault at 10 ip 00007f35691b6c30 sp 00007ffcf514ce98 error 4 in libKF5WaylandServer.so.5.63.0[7f3569191000+60000]
https://bugs.kde.org/show_bug.cgi?id=412684 Knut Andre Tidemann changed: What|Removed |Added CC||knut.tidem...@gmail.com --- Comment #8 from Knut Andre Tidemann --- Can confirm that this happens with both of these graphics cards: 0a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Redwood XT [Radeon HD 5670/5690/5730] 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4850] Running: Arch linux current. linux 5.3.6-arch1-1-ARCH with 'radeon' driver. mesa 19.2.1. qt5 5.13.1 kwin 5.17.0 KF5WaylandServer 5.63.0 -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 377911] [Wayland] RDP doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=377911 Knut Andre Tidemann changed: What|Removed |Added CC||knut.tidem...@gmail.com --- Comment #6 from Knut Andre Tidemann --- As a workaround until this gets fixed, you can start KRDC like this to run it under XWayland: QT_QPA_PLATFORM=xcb krdc This works in Arch Linux at least. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392812] New: Norwegian keyboard layout behaving strangely under wayland
https://bugs.kde.org/show_bug.cgi?id=392812 Bug ID: 392812 Summary: Norwegian keyboard layout behaving strangely under wayland Product: kwin Version: 5.12.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: knut.tidem...@gmail.com Target Milestone: --- I'm having some issues when using the default Norwegian keyboard layout under Plasma/KWin 5.12.4. When pressing the keys right of the 'Æ' and 'Å' keys [1] together with Alt-GR or Shift in order to get some of the special characters, Spectacle is opened instead. I've checked System Settings and the 'Start Screenshot Tool' shortcut is not set. The same happens with the key left of backspace. The cursor changes to the + one and when I click the mouse button, spectacle appears with the captured screenshot. This makes it impossible to type these keys: ~ ^ ´ ` Note that when uninstalling spectacle, these keys still behave strangely. I cannot use the default means of Shift/Alt-GR + Key and then press space to make the character appear alone. Instead I have to press the Shift/Alt-GR + Key combo twice before pressing space to make it appear. [1] - https://en.wikipedia.org/wiki/File:Keyboard_Layout_Norwegian.png -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 375409] Browser can't render (libGL error: failed to create drawable)
https://bugs.kde.org/show_bug.cgi?id=375409 --- Comment #3 from Knut Andre Tidemann --- This problem was solved for me on Arch Linux by rebuilding the libkgapi and kdepim-runtime packages. Not sure if both needs to be rebuilt, but it didn't work with only rebuilding libkgapi. -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 375409] Browser can't render (libGL error: failed to create drawable)
https://bugs.kde.org/show_bug.cgi?id=375409 Knut Andre Tidemann changed: What|Removed |Added CC||knut.tidem...@gmail.com --- Comment #2 from Knut Andre Tidemann --- I have the same issue with arch linux 64 bit packages qt5 5.8.0. (qt5-webengine-5.8.0-8). Using r600g driver with mesa git (17.2.0-devel). This is printed on the console, and the window is just 'blank' and cannot be interacted with: libGL error: failed to create drawable -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 370448] New: Ktorrent 5.0 and 5.0.1 stable tarballs has VERSION_TYPE = bt::DEVEL in ktversion.h
https://bugs.kde.org/show_bug.cgi?id=370448 Bug ID: 370448 Summary: Ktorrent 5.0 and 5.0.1 stable tarballs has VERSION_TYPE = bt::DEVEL in ktversion.h Product: ktorrent Version: 5.0 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: knut.tidem...@gmail.com Both of these stable tarballs are marked as development versions in ktversion.h. Is this the intended behavior? As it is not possible to see from the UI that it announces it self as a development version to trackers and some of them do not like development clients. Reproducible: Always Steps to Reproduce: 1. Open libktcore/ktversion.h in the 5.0 or 5.0.1 stable tarballs from http://download.kde.org/stable/ktorrent/5.0/ Actual Results: VERSION_TYPE is set to DEVEL. Expected Results: I would think VERSION_TYPE should be set to NORMAL in a release. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 368114] New: KTorrent fills up .xsession-errors with connection logs
https://bugs.kde.org/show_bug.cgi?id=368114 Bug ID: 368114 Summary: KTorrent fills up .xsession-errors with connection logs Product: ktorrent Version: 5.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: knut.tidem...@gmail.com It seems that KTorrent is filling up the .xsession-errors log with every connection it makes. Here's an example of the of the output: tor. sep. 1 20:06:56 2016: Accepted connection from 50.65.xx.xx tor. sep. 1 20:06:56 2016: Accepted connection from 81.224.xx.xx tor. sep. 1 20:06:57 2016: Authentication(S) to 50.65.xx.xx : ok tor. sep. 1 20:06:57 2016: Authentication(S) to 81.224.xx.xx : ok tor. sep. 1 20:06:57 2016: Accepted connection from 188.142.xx.xx tor. sep. 1 20:06:57 2016: Accepted connection from 222.97.xx.xx tor. sep. 1 20:06:57 2016: Authentication(S) to 188.142.219.54 : ok tor. sep. 1 20:06:57 2016: Authentication(S) to 222.97.167.160 : failure tor. sep. 1 20:06:58 2016: Accepted connection from 185.148.xx.xx tor. sep. 1 20:06:58 2016: Authentication(S) to 185.148.xx.xx : failure As you can see, they come quite frequently and after 2 and half days of uptime the log is now 230 MB. The client is running with 32 torrents seeding. When I quite ktorrent the messages stop, and they begin again when ktorrent is restarted. Reproducible: Always Steps to Reproduce: 1. Start ktorrent with some torrents running 2. tail -f .xsession-errors Actual Results: KTorrent logs every connection (it seems) Expected Results: Ktorrent should not fill up the .xsession-errors that fast. I'm running the arch linux package of ktorrent, version 5.0.1-2. kio version 5.25.0-1. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 360602] Reply to picks wrong (unrelated list) recipient address
https://bugs.kde.org/show_bug.cgi?id=360602 Knut Andre Tidemann changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #3 from Knut Andre Tidemann --- The issue seems to be that my GMail inbox had the 'This folder contains a mailing list' checkbox enabled. This caused all mail to be addressed to the mesa mailing list. Unchecking this box fixed the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359167] Plasmashell freezes / deadlocks on r600g mesa driver after screen lock
https://bugs.kde.org/show_bug.cgi?id=359167 --- Comment #2 from Knut Andre Tidemann --- I would just like to notify that I have not been able to reproduce this issue after updating to plasma 5.6.0/5.6.1 and mesa-git from roughly two weeks ago. Not sure which of the packages that fixed the issue, but I have not encountered it for two weeks now and it used to happen several times a day. I will leave the issue open for others to comment on in case this issue is not resolved for everyone. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 360602] New: Reply to picks wrong (unrelated list) recipient address
https://bugs.kde.org/show_bug.cgi?id=360602 Bug ID: 360602 Summary: Reply to picks wrong (unrelated list) recipient address Product: kmail2 Version: 5.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: knut.tidem...@gmail.com I have a gmail account configured in KMail. I have also subscribed to a few mailing lists on this account, one of which is the mesa-dev list. When I press the 'Reply' button on any email that is not related to the list at all, KMail replaces the To: field with the mesa-dev list address. This does not happen in the email contains a Reply To: header, but if it does not, the mesa-dev address is always set in the To: field. Reply to All does the same thing, but puts the original address in the From: field as a CC of the email, while the mesa-dev list is still set in the To: field. Is this a bug or could it be configuration problem? Reproducible: Always Steps to Reproduce: 1. Read an incoming mail with no Reply-To header set and not from a mailing list. 2. Press Reply or Reply to All Actual Results: The mesa-dev list is in the To: field of the composer instead of the actual sender of the email. Expected Results: The From address should be put in the To: field of the new message. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 360602] Reply to picks wrong (unrelated list) recipient address
https://bugs.kde.org/show_bug.cgi?id=360602 --- Comment #2 from Knut Andre Tidemann --- Well, it's not an email from the mesa-dev list that is the actual problem. It's all other emails that set the To: field to the mesa-dev list. I can take an example mail that produces this problem if you want, but it is all emails without a Reply-To field. And if you actually want a mesa-dev email I can pick one at random and save it for you. I'm not really sure when the problem started though, but I noticed it last week. What I mean is that picking the mesa email that caused KMail to get stuck in this behaviour would probably be pretty difficult to do, if that is the source of the problem at all. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359167] New: Plasmashell freezes / deadlocks on r600g mesa driver after screen lock
https://bugs.kde.org/show_bug.cgi?id=359167 Bug ID: 359167 Summary: Plasmashell freezes / deadlocks on r600g mesa driver after screen lock Product: plasmashell Version: 5.5.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: knut.tidem...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Hello. I'm having issues with plasmashell freezing / becoming unresponsive after I unlock the screenlocker. It does not happen every time, but pretty frequently. Killing plasmashell and restarting it temporarily solves the problem. This is happening on the official arch linux packages, with mesa and a Radeon HD 5670/5690/5730. It could be a mesa bug as well. Reproducible: Sometimes Steps to Reproduce: 1. Leave computer, wait for lock screen to automatically appear 2. After a while, unlock the computer Actual Results: Plasmashell was frozen. Expected Results: A working plasmashell. The log output from plasmashell does not seem to display anything useful, this is the end of the log and I could see that plasmashell had been frozen for roughly 14 hours by looking at the clock widget: org.kde.plasma.pulseaudio: PROPERTY CHANGED ( 0 ) :: 261 "Properties" org.kde.plasma.pulseaudio: returning roles QHash((264, "HasVolume")(267, "Description")(266, "Name")(269, "Ports")(268, "CardIndex")(270, "ActivePortIndex")(257, "Index")(259, "ObjectName")(258, "PulseObject")(261, "Properties")(260, "Index")(263, "Muted")(262, "Volume")(265, "VolumeWritable")) org.kde.plasma.pulseaudio: PROPERTY CHANGED ( 0 ) :: 261 "Properties" org.kde.plasma.pulseaudio: returning roles QHash((264, "HasVolume")(267, "Description")(266, "Name")(269, "Ports")(268, "CardIndex")(270, "ActivePortIndex")(257, "Index")(259, "ObjectName")(258, "PulseObject")(261, "Properties")(260, "Index")(263, "Muted")(262, "Volume")(265, "VolumeWritable")) org.kde.plasma.pulseaudio: PROPERTY CHANGED ( 0 ) :: 262 "Volume" org.kde.plasma.pulseaudio: returning roles QHash((264, "HasVolume")(267, "Description")(266, "Name")(269, "Ports")(268, "CardIndex")(270, "ActivePortIndex")(257, "Index")(259, "ObjectName")(258, "PulseObject")(261, "Properties")(260, "Index")(263, "Muted")(262, "Volume")(265, "VolumeWritable")) org.kde.plasma.pulseaudio: PROPERTY CHANGED ( 0 ) :: 262 "Volume" org.kde.plasma.pulseaudio: returning roles QHash((264, "HasVolume")(267, "Description")(266, "Name")(269, "Ports")(268, "CardIndex")(270, "ActivePortIndex")(257, "Index")(259, "ObjectName")(258, "PulseObject")(261, "Properties")(260, "Index")(263, "Muted")(262, "Volume")(265, "VolumeWritable")) org.kde.plasma.pulseaudio: PROPERTY CHANGED ( 0 ) :: 268 "CardIndex" org.kde.plasma.pulseaudio: returning roles QHash((264, "HasVolume")(267, "Description")(266, "Name")(269, "Ports")(268, "CardIndex")(270, "ActivePortIndex")(257, "Index")(259, "ObjectName")(258, "PulseObject")(261, "Properties")(260, "Index")(263, "Muted")(262, "Volume")(265, "VolumeWritable")) org.kde.plasma.pulseaudio: PROPERTY CHANGED ( 0 ) :: 268 "CardIndex" org.kde.plasma.pulseaudio: returning roles QHash((264, "HasVolume")(267, "Description")(266, "Name")(269, "Ports")(268, "CardIndex")(270, "ActivePortIndex")(257, "Index")(259, "ObjectName")(258, "PulseObject")(261, "Properties")(260, "Index")(263, "Muted")(262, "Volume")(265, "VolumeWritable")) org.kde.plasma.pulseaudio: PROPERTY CHANGED ( 0 ) :: 269 "Ports" org.kde.plasma.pulseaudio: returning roles QHash((264, "HasVolume")(267, "Description")(266, "Name")(269, "Ports")(268, "CardIndex")(270, "ActivePortIndex")(257, "Index")(259, "ObjectName")(258, "PulseObject")(261, "Properties")(260, "Index")(263, "Muted")(262, "Volume")(265, "VolumeWritable")) org.kde.plasma.pulseaudio: PROPERTY CHANGED ( 0 ) :: 269 "Ports" org.kde.plasma.pulseaudio: returning roles QHash((264, "HasVolume")(267, "Description")(266, "Name")(269, "Ports")(268, "CardIndex")(270, "ActivePortIndex")(257, "Index")(259, "ObjectName")(258, "PulseObject")(261, "Properties")(260, "Index")(263, "Muted")(262, "Volume")(265, "VolumeWritable")) org.kde.plasma.pulseaudio: PROPERTY CHANGED ( 0 ) :: 270 "ActivePortIndex" org.kde.plasma.pulseaudio: returning roles QHash((264, "HasVolume")(267, "Description")(266, "Name")(269, "Ports")(268, "CardIndex")(270, "ActivePortIndex")(257, "Index")(259, "ObjectName")(258, "PulseObject")(261, "Properties")(260, "Index")(263, "Muted")(262, "Volume")(265, "VolumeWritable")) org.kde.plasma.pulseaudio: PROPERTY CHANGED ( 0 ) :: 270 "ActivePortIndex" libkcups: Renew-Subscription last error: 0 successful-ok libkcups: Renew-Subscription last error: 0 successful-ok libkcups: Renew-Subscription last error: 0 successful-ok libkcups: Renew-Subscription last error: 0 successful-ok libkcups: Renew-Subscription las
