Bug#853171: segmentation fault when disabling a screen with kscreen without upower installed on the system
Hello, I tried to debug this issue and spent "some" time to it. --- The class ShellCorona contains a QMap m_desktopViewforId storing pairs of idx and desktopViews pointers. When a display gets deactivated the method ShellCorona::removeDesktop [1] is called with parameter desktopView. void ShellCorona::removeDesktop(DesktopView *desktopView) { const int idx = m_screenPool->id(desktopView->screenToFollow()->name()); "desktopView->screenToFollow()->name()" returns in my case always "DVI-I-1" even as I disabled in the dialog the "VGA-1" display. Therefore idx is set to 0. Some lines later the desktopView gets deleted and removed from the map. But unfortunately in this map the desktopView pointer, that gets deleted, is stored with idx=1. delete desktopView; m_desktopViewforId.remove(idx); That way desktopView contains now a pointer to already deleted memory. --- Second: When we start without an already existing directory ~/.local/share/kscreen/ then the crash happens also when upower _is_ installed. But there is gets less visible because kscreen saves this configuration and uses it next time at login, make the configuration at least activated there. Without upower both displays are activated by default at login. --- Attached is a valgrind run and some gdb sessions trying to debug to the issue. --- Setting idx to the key that matches the element in the map for the to be deleted desktopView leads to no crash. Kind regards, Bernhard [1] plasma-workspace-5.8.4/shell/shellcorona.cpp Environment: - Minimal Stretch i386 install - apt-get --no-install-recommends --no-install-suggests install sddm plasma-desktop kwin-x11 strace mesa-utils htop systemsettings kde-config-sddm kscreen systemd-coredump gdb libc-dbg plasma-workspace-dbgsym libkf5plasma5-dbgsym libqt5core5a-dbgsym libqt5gui5-dbgsym libqt5widgets5-dbgsym libglib2.0-0-dbg libkf5windowsystem5-dbgsym libkf5plasmaquick5-dbgsym plasma-framework-dbgsym libqt5qml5-dbgsym libqt5quick5-dbgsym libtaskmanager6-dbgsym libkf5itemmodels5-dbgsym libkf5activities5-dbgsym devscripts qtbase5-dev gdbserver git git-gui valgrind kdesdk-scripts - NVIDIA Corporation NV40 [GeForce 6800] (with Nouveau driver) 15.03.2017 22:04:13.175 ; kded ; : KScreen::Output( 145 "VGA-1" connected enabled QPoint(0,0) QSize(1024, 768) "149" ) 15.03.2017 22:04:13.185 ; kded ; : KScreen::Output( 146 "DVI-I-1" connected enabled QPoint(1024,0) QSize(1024, 768) "149" ) mv /usr/bin/plasmashell /usr/bin/plasmashell.orig cat /usr/bin/plasmashell #!/bin/sh #/usr/bin/gdbserver localhost:4567 /usr/bin/plasmashell.orig $@ #/usr/bin/plasmashell.orig $@ > $(tempfile --prefix=plasmashell) 2>&1 /usr/bin/valgrind --log-file=/tmp/valgrind.log /usr/bin/plasmashell.orig $@ ==1042== Invalid read of size 4 ==1042==at 0x487B034: PlasmaQuick::ContainmentView::containment() const (containmentview.cpp:263) ==1042==by 0x13E219: ShellCorona::screenForContainment(Plasma::Containment const*) const (shellcorona.cpp:1826) ==1042==by 0x13E165: ShellCorona::screenForContainment(Plasma::Containment const*) const (shellcorona.cpp:1818) ==1042==by 0x4EF3FAA: Plasma::Containment::screen() const (containment.cpp:489) ==1042==by 0x19677BC6: NotificationsApplet::onScreenChanges() (notificationsapplet.cpp:65) ==1042==by 0x6DBFAAD: call (qobject_impl.h:101) ==1042==by 0x6DBFAAD: QMetaObject::activate(QObject*, int, int, void**) (qobject.cpp:3723) ==1042==by 0x6DBFF8C: QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (qobject.cpp:3602) ==1042==by 0x59F3EE1: KWindowSystem::workAreaChanged() (moc_kwindowsystem_WAINN7OXDV4STE.cpp:337) ==1042==by 0xD6B0E8B: NETEventFilter::nativeEventFilter(xcb_generic_event_t*) (kwindowsystem.cpp:258) ==1042==by 0x6D8E66F: QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) (qabstracteventdispatcher.cpp:466) ==1042==by 0xAC35121: QXcbConnection::handleXcbEvent(xcb_generic_event_t*) (qxcbconnection.cpp:1106) ==1042==by 0xAC35EF6: QXcbConnection::processXcbEvents() (qxcbconnection.cpp:1741) ==1042== Address 0xd3d6d08 is 24 bytes inside a block of size 60 free'd ==1042==at 0x482E938: operator delete(void*) (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) ==1042==by 0x12B6C1: DesktopView::~DesktopView() (desktopview.cpp:74) ==1042==by 0x13F9D0: ShellCorona::removeDesktop(DesktopView*) (shellcorona.cpp:1047) ==1042==by 0x14044E: ShellCorona::screenRemoved(QScreen*) (shellcorona.cpp:1077) ==1042==by 0x6DBFAAD: call (qobject_impl.h:101) ==1042==by 0x6DBFAAD: QMetaObject::activate(QObject*, int, int, void**) (qobject.cpp:3723) ==1042==by 0x6DBFF8C: QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (qobject.cpp:3602) ==1042==by 0x6685EC8: QGuiApplication::screenRemoved(QScreen*) (moc_qguiapplication.cpp:366) ==1042==by 0x66BE982:
libkscreen_5.8.6-2_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 14 Mar 2017 18:55:01 +0100 Source: libkscreen Binary: libkf5screen-dev libkf5screen7 libkf5screen-bin Architecture: source Version: 4:5.8.6-2 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE MaintainersChanged-By: Maximiliano Curia Description: libkf5screen-bin - library for screen management - helpers libkf5screen-dev - library for screen management - development files libkf5screen7 - library for screen management - shared library Changes: libkscreen (4:5.8.6-2) unstable; urgency=medium . * Release to unstable. Checksums-Sha1: 6e73818b6c76d1cfa8e1cafd9c1d36ee2c8f373f 2493 libkscreen_5.8.6-2.dsc 13e522e1087a26405874bd12b7817bcc5f41bdf6 8508 libkscreen_5.8.6-2.debian.tar.xz ac0577595b002b826fad02298b77cc637e1915b4 11519 libkscreen_5.8.6-2_source.buildinfo Checksums-Sha256: 514df6ae45f6497f800bde91021a3b562de6e3c68d250e30e2c9d88ab76cbab1 2493 libkscreen_5.8.6-2.dsc b527d1ac370d9a7619dee9f09bdb731d3d552de2d254e12af8c4d85a4b51a31e 8508 libkscreen_5.8.6-2.debian.tar.xz 7dd824940a1c440e2a88004b3257c6f2e46dad18d0fad645ed3c5156381489be 11519 libkscreen_5.8.6-2_source.buildinfo Files: 439b5b7bd01d3d63c6456233d0b10ad8 2493 libs optional libkscreen_5.8.6-2.dsc 2aab51e5aab98d46855f68f1da640432 8508 libs optional libkscreen_5.8.6-2.debian.tar.xz b06004aa56d1fc21f4a43166d498fc98 11519 libs optional libkscreen_5.8.6-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE+JIdOnQEyG4RNSIVxxl2mbKbIyoFAljJlWMACgkQxxl2mbKb Iyruhg/9H80Vv9S2dONQGERv/Ju5L7Sd+ZuUO80E6Scq7VvrodLfN+UXSkSVsmT2 jbAQqcBQUji/vTYIVcNx9f2IjKMAWAlGuRyeC/KGmBavi+csPrlJjYlNKlTI4wwt Z9VxueclumGstCUGX/D1QIFpaSMwbuI6gFvWvthiH0GVm7S7P9FDgtPd4SBTysKo Ykpu/Qe4oBHC509d2lcUTq2EpktdgebGkWJGCz8OhTNisS/Wo/XRuakXa5WGTfex fDGPIpRiDKTDJqQndndOfN8No75Ci0Pme3R2Q7jDXO2en7cdQwCOLpVWbbS9SXvC x7sKGQg1vIXvraRjiylU5dMcIZVz0hdrrHwxFPWsmxtU+/t6XRYTFAy5uQBqoG4y 8UV4ZGO4QviRsVVhBnTA1dVVUIazdWnhudcXubaCLbdD6m/ygsue1h6LbxvQYndY 7Pbp4EsLei2iey1lAGi+lL06TxBti9p/Cm3zPyL/Un0WM24+ecZEbqxCoeHVS+v9 aWg4v3Mja94vJvJmlv6O3oLsJMU/2RLmxHjsvn3tqi/RfFTxutbYBNIpFcipRrA1 XWPT4eLEzslOisNMHdmyq1W9R4ttrRM7Cq9KTVFiwOpKKv8TGkqmgiLWRWlY23/7 aCNU6caVWVpa6CIkne9dl0fCzPrrYHhyl33h2itrfdgyN3X+ZHg= =olZ6 -END PGP SIGNATURE- Thank you for your contribution to Debian.
kde-gtk-config_5.8.6-1_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 14 Mar 2017 15:23:29 +0100 Source: kde-gtk-config Binary: kde-config-gtk-style kde-config-gtk-style-preview Architecture: source Version: 4:5.8.6-1 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE MaintainersChanged-By: Maximiliano Curia Description: kde-config-gtk-style - KDE configuration module for GTK+ 2.x and GTK+ 3.x styles selecti kde-config-gtk-style-preview - KDE configuration module for GTK+ 2.x and GTK+ 3.x styles selecti Changes: kde-gtk-config (4:5.8.6-1) unstable; urgency=medium . * New upstream release (5.8.6) Checksums-Sha1: 547f5b4451641bcee07e9f309226d6f258e843fb 2531 kde-gtk-config_5.8.6-1.dsc 6346d165f589c30d29b7dba567ffbcd45123e3ef 150436 kde-gtk-config_5.8.6.orig.tar.xz dcf25eab6c90974703dc81da239ced8e6ee28c91 5664 kde-gtk-config_5.8.6-1.debian.tar.xz b34400439e0b1b7fcf589d897d623c9b011d7650 15333 kde-gtk-config_5.8.6-1_source.buildinfo Checksums-Sha256: d3ba870824c4043cb4320ace4270a6a7ba8578a7e75739dd665da46c89463d62 2531 kde-gtk-config_5.8.6-1.dsc 4d54fa4b579c717e8c9792ce7f6b5ed1a728162df2faf50f79781ecb153a361e 150436 kde-gtk-config_5.8.6.orig.tar.xz c7d83a151d0d54ace217aaedff0677de2313eb062ab51987a4576e08fc2b8e7f 5664 kde-gtk-config_5.8.6-1.debian.tar.xz 9064050268dca8b3186496f38a2e62f8be0a6d244cef0c72340116216d24e134 15333 kde-gtk-config_5.8.6-1_source.buildinfo Files: 4d83cff43f0c0eb0781b06345f3f5b3f 2531 kde optional kde-gtk-config_5.8.6-1.dsc e6f18102f80c234b52a8db33c0e15435 150436 kde optional kde-gtk-config_5.8.6.orig.tar.xz a0da4b08e310501bf7577589630ca2d5 5664 kde optional kde-gtk-config_5.8.6-1.debian.tar.xz b8931d9bdd59160c5be48767629e3676 15333 kde optional kde-gtk-config_5.8.6-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE+JIdOnQEyG4RNSIVxxl2mbKbIyoFAljJljAACgkQxxl2mbKb IyplMg//Yj+akW5Qd03QhhX4oC9/57NAJajd4vqM1TobGdk2z91rFQfGCUp64qPl vQjL2DP+expKpnAksHj7v2YNsgcNGBID4inONtha7h8zLfg+O2gjfMJGubHNCB4I ULuR51k9bZgZ8oXU6ztl48GE+UARoHjv7FXLftHANt18VkixMsEw68Wzq/eDx+cL EjBzYRWvF2Nt/W8Cf0Ge042Xio0+Noxl+7njq9NjoEHhsD8YYY2PL+0NOc7Zxgod g8XPmirsEqBmiRq6smfsgdPoOIjPZUD76XGkFTb6ZtDy9I1p2ipJB3aEgdGygsRW Q6V/MZ1soPwNldMIobVgYHFKbFm/OclNcDAl3RJLZ/j8rZBT2FDcGeDTNoWC6aYl U9ktrXsVznUcO55MRzR3H62TEk/qXdQuCnOootMhLv6L2bIBmZqoX7TPHDFwRXNk d6sV/sHTJoD8PdNK3RrvXIrKwdU4o+oqg7Gpl7+i7hj+AUlsYHyb0uYKFyF/DVA3 SxpQ3KIg4GmFLCVyLlDR3dh1dmg8sf/8wTs63Rz6ryuy/paXaUZHLbfq7uD+lqES 6VSBHCFHQKXlxK6dtpFxyKtiXza0fTzYrOILnxVUpuLUfTm8Pzxy75F6wDCzNiT8 DG6et2CgQQ529PMcBjWRq8609AiExVjZNRxGb1VpjbZ48GAHyU4= =GCmq -END PGP SIGNATURE- Thank you for your contribution to Debian.
kscreenlocker_5.8.6-2_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 15 Mar 2017 09:10:42 +0100 Source: kscreenlocker Binary: kscreenlocker-dev libkscreenlocker5 kde-config-screenlocker Architecture: source Version: 5.8.6-2 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE MaintainersChanged-By: Maximiliano Curia Description: kde-config-screenlocker - KCM Module for kscreenlocker kscreenlocker-dev - Development files for kscreenlocker libkscreenlocker5 - Secure lock screen architecture Changes: kscreenlocker (5.8.6-2) unstable; urgency=medium . * Release to unstable Checksums-Sha1: a6927aa9348cb5d7ae3d8a354da9f4536a08c066 3029 kscreenlocker_5.8.6-2.dsc 1c1852825c24f529d95ce61528c9324c5acfde5b 6852 kscreenlocker_5.8.6-2.debian.tar.xz 0f4f071d4ca59cbe412394078a29a0627a2b 23589 kscreenlocker_5.8.6-2_source.buildinfo Checksums-Sha256: 16f47281d129379c3f814656ce344998563068890955837e5d501e7c1e93a72e 3029 kscreenlocker_5.8.6-2.dsc 74b3ec92eb697848fe8b11abd5ca9e8c1d0af4768440ba197a6ece414e64b3c7 6852 kscreenlocker_5.8.6-2.debian.tar.xz 64ee34602a34a5df5e1d4df350adefadd4771a5122b49b0199f1a66f63c119f2 23589 kscreenlocker_5.8.6-2_source.buildinfo Files: 5fc13d718de09e14ea169c5a61928d23 3029 libs optional kscreenlocker_5.8.6-2.dsc 9b2ca2dbf32c3e02f0bf4fc4e396a2d5 6852 libs optional kscreenlocker_5.8.6-2.debian.tar.xz e1bb03eb306725197223917e4c0ebdae 23589 libs optional kscreenlocker_5.8.6-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE+JIdOnQEyG4RNSIVxxl2mbKbIyoFAljJlpQACgkQxxl2mbKb IyqdthAAtegDkedNzLqHtgNeW08aj38Wij6xtFIDIP9T+GN/wMA2zLcX3DdlE++K igFKyIl9wa4lN6IrueLs4PFcpp7dzQwWtyzKp7CAVdCsPycmmzpt4/XzjOT9tfI0 YkCE4fo/A8ffXBClI/TWizEsrr6Hh4GlNHtFnD/cWAJ35qWouX90YMXiTELiB9Kq cnp5NcdkXRLibNPxZMoZH2vOeQAGwn4PqiBA0/o0gOZufP9uPWbgURtQy0iVjN48 t9kHMEHssdrofg9Bn8UJNLZpXWCO3ULZj33HCWpq1CwxOOBAX8DIK2R0wb4YgEaX XRSg5XZEyA806OxHVBQ2xGBR5W4il7nx3tAhViW7QFXd3bKF8sHIXRpLnosBLRc8 mnGExxonXG5igFkfgt2VnaLmEwcubH+jCvShGNR79MPxaT6Lftin+3CkejiP5d+9 R9JuqDScrM7eT8K+EYnoDZuDIkDUICX6C2qtAqa28gKQvnEdYfWDreZbi29rFme3 JjRUugCj1JqhvTndMcO12NeNN7MW6SGhLgxGMvgEtvLWiaruSg9w1wxQ4OnRke7N 2bS6FXPcbt10Wk34bVdyj30nyTFxNV79AbGA8c8douGOBTx+hqIfS7hVLmfCr9+f nsvx3CaZ34dt1g9dbZnzvma9ANZZOtehwthuH7kpPzCSczEjNkY= =mcMv -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of kde-gtk-config_5.8.6-1_source.changes
kde-gtk-config_5.8.6-1_source.changes uploaded successfully to localhost along with the files: kde-gtk-config_5.8.6-1.dsc kde-gtk-config_5.8.6.orig.tar.xz kde-gtk-config_5.8.6-1.debian.tar.xz kde-gtk-config_5.8.6-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Processing of kscreenlocker_5.8.6-2_source.changes
kscreenlocker_5.8.6-2_source.changes uploaded successfully to localhost along with the files: kscreenlocker_5.8.6-2.dsc kscreenlocker_5.8.6-2.debian.tar.xz kscreenlocker_5.8.6-2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Processing of libkscreen_5.8.6-2_source.changes
libkscreen_5.8.6-2_source.changes uploaded successfully to localhost along with the files: libkscreen_5.8.6-2.dsc libkscreen_5.8.6-2.debian.tar.xz libkscreen_5.8.6-2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
plasma-workspace_5.8.6-2_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 15 Mar 2017 19:45:10 +0100 Source: plasma-workspace Binary: plasma-workspace-dev plasma-workspace-wayland plasma-workspace libkworkspace5-5 libplasma-geolocation-interface5 libtaskmanager6 libweather-ion7 sddm-theme-breeze sddm-theme-debian-breeze Architecture: source Version: 4:5.8.6-2 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE MaintainersChanged-By: Maximiliano Curia Description: libkworkspace5-5 - Plasma Workspace for KF5 library libplasma-geolocation-interface5 - Plasma Workspace for KF5 library libtaskmanager6 - Plasma Workspace for KF5 library libweather-ion7 - Plasma Workspace for KF5 library plasma-workspace - Plasma Workspace for KF5 plasma-workspace-dev - Plasma Workspace for KF5 devel files plasma-workspace-wayland - Plasma Workspace for KF5 - Wayland integration sddm-theme-breeze - Breeze SDDM theme sddm-theme-debian-breeze - Debian Breeze SDDM theme Changes: plasma-workspace (4:5.8.6-2) unstable; urgency=medium . * Release to unstable Checksums-Sha1: 95275566a7158cbd2b4ad235aebb4a48e9c8c59a 4580 plasma-workspace_5.8.6-2.dsc 69be0efeaf4fbbe91eb6a2fd424eb770bc22a2fd 29260 plasma-workspace_5.8.6-2.debian.tar.xz 7b69cb0e58967ae463b5c639654ee4181b21309a 27839 plasma-workspace_5.8.6-2_source.buildinfo Checksums-Sha256: b4e1ff607e39f2182a42d09674b6955d00ab82ca6c3fce2f04e3272aec1615e6 4580 plasma-workspace_5.8.6-2.dsc 7079b4c5f650999778468ffa243f4663c9f4fd4277ddccac020a6d4d193aa73b 29260 plasma-workspace_5.8.6-2.debian.tar.xz a2607f9c10190f160ed18eb2abeb32521ea0d3af0046568c52ee6b0b2e7a861d 27839 plasma-workspace_5.8.6-2_source.buildinfo Files: a335ae06b34550a7a31151a4ba122119 4580 kde optional plasma-workspace_5.8.6-2.dsc 89c4cb0f6981e5f14f4c7edcac003a1b 29260 kde optional plasma-workspace_5.8.6-2.debian.tar.xz bad0e6a67547150c425e408aecf847e8 27839 kde optional plasma-workspace_5.8.6-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE+JIdOnQEyG4RNSIVxxl2mbKbIyoFAljJjQQACgkQxxl2mbKb Iyo9/A//UF4tKlztn51Gyd03VpWlemFI7Lu9J+72MFTvjqQE3rsUnmNmjysU0sFB 9Os3n1W9ATUh3KODX4NSu5NSIsoeOkB1dYuV1+aJsB0dVAA9lT+w+x3JDDcd6xKa T7nZyLok3M2nooJNOLl7CCboK2sT615jKOpzu3vxwEpQDSE+MfQXbEYOV6uh1fw5 TNOqm7w+BrJm5UpWtdQCn29vO4vxh1MqybSEKH/yZFWTkgK45YYej7mRXEv29ghB nIplm8+ilm9/OfP58412ulL4/pRDGuXuz6xpTFtAx3akzSL0tA3+v19HK25vbNHH 0/wUEBpHCHaUQKNdM0YJF7JCGPvunrKzEBwxs/b+k9GuuUBu0YkCHhwPLJzIAd7o uGpCTgwn3KDmABJkG3NyQNEQkUyGzkYobK7JRqknSyyxTdpVq3BKeYX4ZBdkCG+L rN1DjZJvAtK6zCajTgfa/E+KLp8aHn9vjwNW12bkXm7ZrXpc3LBcg9c/Vf7Pfr/f cGhm5QGIbYq2zO00jJRGj1XHR+z3TE506PJhh4Id7Cx9Rn1IRrjpGMZ+gKgA5CNP uBaqEdqTifZoQn1qIE9aG35ESIy/HfR3cC8DBZ5b3s8kS7yIN0z271EPeO3jL7AV ePr2trNNib/hv6V7NMtVInt6wxE1KXCB911hLSynUHasuPTaV8w= =yXXJ -END PGP SIGNATURE- Thank you for your contribution to Debian.
Bug#852162: libkscreenlocker5: cannot enter password when two mirrored monitors are connected
Sorry for muddying the discussion. To me, this situation only happens after resume from suspend: - If I select mirroring from SystemSettings and lock -> the input field doesn't give feedback but I am able to log in. - If the computer performs a resume and the screen is mirrored because KDE/Xorg forgot the setup -> this bug: the input field doesn't give feedback and pressing enter results in failure because of wrong password. Alex
Processing of plasma-workspace_5.8.6-2_source.changes
plasma-workspace_5.8.6-2_source.changes uploaded successfully to localhost along with the files: plasma-workspace_5.8.6-2.dsc plasma-workspace_5.8.6-2.debian.tar.xz plasma-workspace_5.8.6-2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#857859: qtwebengine5-examples: WebEngine examples fail to run without qml-module-* packages installed
Package: qtwebengine5-examples Version: 5.7.1+dfsg-6 Severity: normal Dear Maintainer, Running QML based examples fail when the appropriate qml-module-* packages are not installed. For example the 'minimal' example gives: $ /usr/lib/x86_64-linux-gnu/qt5/examples/webengine/minimal/minimal QQmlApplicationEngine failed to load component qrc:/main.qml:43 module "QtWebEngine" is not installed qrc:/main.qml:42 module "QtQuick.Window" is not installed qrc:/main.qml:41 module "QtQuick" is not installed qrc:/main.qml:43 module "QtWebEngine" is not installed qrc:/main.qml:42 module "QtQuick.Window" is not installed qrc:/main.qml:41 module "QtQuick" is not installed qrc:/main.qml:43 module "QtWebEngine" is not installed qrc:/main.qml:42 module "QtQuick.Window" is not installed qrc:/main.qml:41 module "QtQuick" is not installed Installing the following packages fixes 'minimal' example: qml-module-qtquick-window2 qml-module-qtquick2 qml-module-qtwebengine The 'quicknanobrowser' example needs many more QML modules. baruch -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages qtwebengine5-examples depends on: ii libc62.24-9 ii libjs-jquery 3.1.1-2 ii libjs-marked 0.3.6+dfsg-1 ii libqt5core5a 5.7.1+dfsg-3+b1 ii libqt5gui5 5.7.1+dfsg-3+b1 ii libqt5network5 5.7.1+dfsg-3+b1 ii libqt5printsupport5 5.7.1+dfsg-3+b1 ii libqt5qml5 5.7.1-2 ii libqt5webchannel55.7.1-1 ii libqt5webengine5 5.7.1+dfsg-6 ii libqt5webenginecore5 5.7.1+dfsg-6 ii libqt5webenginewidgets5 5.7.1+dfsg-6 ii libqt5widgets5 5.7.1+dfsg-3+b1 ii libstdc++6 6.3.0-6 qtwebengine5-examples recommends no packages. qtwebengine5-examples suggests no packages. -- no debconf information -- http://baruch.siach.name/blog/ ~. .~ Tk Open Systems =}ooO--U--Ooo{= - bar...@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
Bug#835897: marked as done (plasma-discover closes unexpectedly)
Your message dated Wed, 15 Mar 2017 17:12:35 +0100 with message-id <20170315161235.o4mb5e6n4ozox...@gnuservers.com.ar> and subject line Re: Bug#835897: Fwd: [Discover] [Bug 367944] Discover crashes when opened twice. has caused the Debian Bug report #835897, regarding plasma-discover closes unexpectedly to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 835897: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835897 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: plasma-discover Version: 5.7.3-1 Severity: normal Dear Maintainer, when I enter in the command line: /usr/bin/plasma-discover & /usr/bin/plasma-discover & plasma-discover crashes with the following output: QCommandLineParser: argument list cannot be empty, it should contain at least the executable name KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = plasma-discover path = /usr/bin pid = 11045 KCrash: Arguments: /usr/bin/plasma-discover KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 "Message recipient disconnected from message bus without replying" QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 40 and type 'Read', disabling... QSocketNotifier: Invalid socket 36 and type 'Read', disabling... QSocketNotifier: Invalid socket 41 and type 'Read', disabling... Best regards Heinrich Schuchardt -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages plasma-discover depends on: ii appstream 0.9.8-4 ii libappstreamqt1 0.9.8-4 ii libc6 2.23-5 ii libkf5archive5 5.24.0-1 ii libkf5attica5 5.23.0-1 ii libkf5configcore5 5.23.0-1 ii libkf5configgui55.23.0-1 ii libkf5configwidgets55.23.0-1 ii libkf5coreaddons5 5.23.0-1 ii libkf5crash55.23.0-1 ii libkf5dbusaddons5 5.23.0-1 ii libkf5declarative5 5.23.0-1 ii libkf5i18n5 5.23.0-1 ii libkf5kiocore5 5.23.0-1 ii libkf5kiowidgets5 5.23.0-1 ii libkf5newstuff5 5.23.0-1 ii libkf5notifications55.23.0-1 ii libkf5service-bin 5.23.0-1 ii libkf5service5 5.23.0-1 ii libkf5widgetsaddons55.23.0-1 ii libkf5xmlgui5 5.23.0-1 ii libpackagekitqt5-0 0.9.5-3 ii libqt5core5a5.6.1+dfsg-3+b1 ii libqt5dbus5 5.6.1+dfsg-3+b1 ii libqt5gui5 5.6.1+dfsg-3+b1 ii libqt5qml5 5.6.1-5 ii libqt5quick55.6.1-5 ii libqt5widgets5 5.6.1+dfsg-3+b1 ii libqt5xml5 5.6.1+dfsg-3+b1 ii libstdc++6 6.1.1-11 ii packagekit 1.1.1-1 ii plasma-discover-common 5.7.3-1 Versions of packages plasma-discover recommends: ii software-properties-kde 0.96.20.2-1 plasma-discover suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 5.8.3-1 ¡Hola Heinrich! El 2016-09-14 a las 14:00 +0200, Heinrich Schuchardt escribió: An upstream patch has been merged. Thanks for the update, the patch was released in 5.8.0, and is part of the Debian upload 5.8.3-1. I'm assuming that the issue is gone now, if not, please reopen this issue. Happy hacking, -- "Any change looks terrible at first." -- Principle of Design Inertia Saludos /\/\ /\ >< `/ signature.asc Description: PGP signature --- End Message ---
Bug#825961: milou: unable to set separatorVisible on resultdelegateitem
Control: tag -1 + moreinfo ¡Hola TreeBoy! El 2016-05-31 a las 19:51 +0100, TreeBoy escribió: Package: milou Version: 4:5.6.4-1 Severity: important Tags: patch When running krunner it was appearing at the top centre of my display and only one pixel wide and unable to receive keyboard input and therefore could not launch apps. When running from a terminal I received an error along the lines of: "Unable to set separatorVisible on object ResultsListViewDelegate" It said the problem was at line 144 of /usr/lib/x86_64-linux- gnu/qt5/qml/org/kde/milou/ResultDelegate.qml Sorry that it took so long to get back to you. Apparently the message was: Cannot assign to non-existent property "separatorVisible" This seems to be caused by an incomplete upgrade, these kind of upgraded should have been mitigated in 5.7 and 5.8 releases of plasma (using the groups breaks script). So I think that this bug can be closed, can you please confirm that this issue is no longer present? Happy hacking, -- "People get lost in thought because it is unfamiliar territory." -- Fix's Principle Saludos /\/\ /\ >< `/ signature.asc Description: PGP signature
Processed: Re: Bug#825961: milou: unable to set separatorVisible on resultdelegateitem
Processing control commands: > tag -1 + moreinfo Bug #825961 [milou] milou: unable to set separatorVisible on resultdelegateitem Added tag(s) moreinfo. -- 825961: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825961 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#853171: I think that this is an upstream bug.
Dear Maintainers, I think that this bug is an upstream bug. Plasma desktop should not give segmentation faults when upower is missing. Maxi already fixed the kscreen bug setting upower as recommendation, because the functionatily that upower gives to kscreen is remembering the last screens configurations after a reboot. That function fits into the recommendations, not dependency, so it is fixed now. But given a system that has the plasma desktop + kscreen, it should not give segmentation faults when the upower functionality is missing. Given that, I think that this is a upstream bug and that the ones that could fix this are the KDE developers. Regards, Éter.
Bug#797999: marked as done (sddm fails to start whereas kdm works correctly)
Your message dated Wed, 15 Mar 2017 14:45:30 +0100 with message-id <20170315134530.5onrd37p43vnb...@gnuservers.com.ar> and subject line Re: Bug#797999: This bug can be closed has caused the Debian Bug report #797999, regarding sddm fails to start whereas kdm works correctly to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 797999: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797999 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sddm Version: 0.11.0-4 Severity: important If I do dpkg-reconfigure sddm, select it and reboot, I just get a black screen, with X running, no cursor, no mouse nothing in/var/log/sddm.log Note its a docked laptop, with external monitor used, lid closed and laptop monitor automatically desactivated. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.1.6 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF8, LC_CTYPE=en_US.UTF8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages sddm depends on: ii adduser 3.113+nmu3 ii debconf [debconf-2.0] 1.5.57 ii libc6 2.21-0experimental1 ii libgcc1 1:5.2.1-16 ii libpam0g1.1.8-3.1 ii libqt5core5a5.4.2+dfsg-9 ii libqt5dbus5 5.4.2+dfsg-9 ii libqt5gui5 5.4.2+dfsg-9 ii libqt5network5 5.4.2+dfsg-9 ii libqt5qml5 5.4.2-6 ii libqt5quick55.4.2-6 ii libstdc++6 5.2.1-16 ii libsystemd0 225-1 ii libxcb-xkb1 1.10-3+b1 ii libxcb1 1.10-3+b1 ii qml-module-qtquick2 5.4.2-6 ii sddm-theme-breeze [sddm-theme] 4:5.3.2-4+b1 sddm recommends no packages. Versions of packages sddm suggests: pn pam-kwallet5 -- debconf information: sddm/daemon_name: /usr/bin/sddm * shared/default-x-display-manager: kdm --- End Message --- --- Begin Message --- Version: 0.14.0-4 ¡Hola Eric! El 2017-03-15 a las 11:37 +0100, Eric Valette escribió: For the first time I've been able to use sddm on my professional laptop using an external monitor. Hourra. Can remove kdm!!! fixed by 0.14.0-4. These are good news indeed, it means that all the patching to 0.14.0 was worth it. :) Closing the issue with this mail. Happy hacking, -- "Anytime you have a fifty-fifty chance of getting something right, there's a 90 percent probability you'll get it wrong." -- The 50-50-90 rule Saludos /\/\ /\ >< `/ signature.asc Description: PGP signature --- End Message ---
Bug#798786: marked as done ([libpam-kwallet5] kwalletd5 started by libpam-kwallet5 is not used by kwalletmanager5)
Your message dated Wed, 15 Mar 2017 12:22:48 +0100 with message-id <20170315112240.3unmhux2rb3yu...@gnuservers.com.ar> and subject line Re: Bug#798786: [libpam-kwallet5] kwalletd5 started by libpam-kwallet5 is not used by kwalletmanager5 has caused the Debian Bug report #798786, regarding [libpam-kwallet5] kwalletd5 started by libpam-kwallet5 is not used by kwalletmanager5 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 798786: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798786 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libpam-kwallet5 Version: 5.4.0-1 Severity: grave --- Please enter the report below this line. --- After installing the libpam-kwallet5 package, when I login via SDDM, a process such as below is started. Konsole outpu rahul12635 12634 0 22:08 ?00:00:00 /usr/bin/kwalletd5 --pam-login 17 27 Now when I start kwalletmanager, a new kwalletd5 process is created. Konsole output rahul12806 1 0 22:08 ?00:00:04 /usr/bin/kwalletd5 instead of it connecting to the already started kwalletd5 process. Also, when I logout, the initial kwalletd5 process launched by pam is not terminated and becomes a zombie process. So, eventual logins ends up with multiple such processes. Konsole output rahul 4346 1 0 21:17 ?00:00:00 /usr/bin/kwalletd5 --pam-login 17 25 rahul 9801 1 0 21:52 ?00:00:00 /usr/bin/kwalletd5 --pam-login 17 21 rahul11679 1 0 22:03 ?00:00:00 /usr/bin/kwalletd5 --pam-login 17 25 rahul12180 1 0 22:05 ?00:00:00 /usr/bin/kwalletd5 --pam-login 17 26 --- System information. --- Architecture: amd64 Kernel: Linux 4.1.0-2-amd64 Debian Release: stretch/sid 500 trusty ppa.launchpad.net 500 stable dl.google.com 500 stable deb.opera.com 500 oldstable packages.x2go.org 500 all liveusb.info 1000 testing security.debian.org 1000 testing httpredir.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. --- End Message --- --- Begin Message --- Version: 5.6.3-1 ¡Hola Rahul! El 2015-09-13 a las 15:59 +0530, Rahul Amaram escribió: I pointed my repo to unstable and upgraded plasma-workspace. The problem is now solved. I don't see any more zombie kwalletd5 process. NOTE 1: ksshaskpass was broken earlier. Now, ksshaskpass is able to retrieve the credentials at login time for adding my private keys to the ssh agent. I am initializing this by adding "ssh-add" in the startup programs (which indirectly calls ksshaskpass). NOTE 2: It is possible that your kde wallet might get closed after being unlocked upon login. To avoid this, ensure via kde wallet manager "Configure wallet ..." settings that "Close when last application stops using it" is not checked. This package finally solves a long-time problem in Debian :)! Thanks for reporting. I'm closing the issue with the version of kwallet_pam that adds the desktop independant version of the mentioned snippet of startkde. Happy hacking, -- "If it ain't broke, don't fix it" -- Bert Lance "If we can't fix it, it ain't broke" -- Lieutenant Colonel Walt Weir Saludos /\/\ /\ >< `/ signature.asc Description: PGP signature --- End Message ---
Bug#706442: ksshaskpass: askpass dialog does not show
Control: tag -1 + moreinfo ¡Hola Marcus! El 2013-04-30 a las 12:19 +0200, Marcus Better escribió: Package: ksshaskpass Version: 0.5.3-1+b1 Severity: important Using ksshaskpass with KDE, when using ssh to log in to a remote host, the dialog prompt does not show. It executes ksshaskpass in the background but no window shows up, so the login just seems to hang. Had to install kdewalletcli and use kwalletaskpass instead, which shows the dialog correctly. Sorry for taking so long to get back to you. ksshaskpass should be called by ssh-add or by ssh when there is no associated terminal (either using the SSH_ASKPASS environment variable or the ssh-askpass alternative configuration). It's not supposed to do anything when using an interactive ssh, and it's not supposed to be used directly. How were you trying to use ksshaskpass? Happy hacking, -- "It's a well-known fact that computing devices such as the abacus were invented thousands of years ago. But it's not well known that the first use of common computer protocol occurred in the Old Testament. This, of course, was when Moses aborted the Egyptians' process with a control-sea." -- Tom Galloway (recs.arts.comics, February 1992) Saludos /\/\ /\ >< `/ signature.asc Description: PGP signature
Processed: Re: Bug#706442: ksshaskpass: askpass dialog does not show
Processing control commands: > tag -1 + moreinfo Bug #706442 [ksshaskpass] ksshaskpass: askpass dialog does not show Added tag(s) moreinfo. -- 706442: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706442 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#797999: This bug can be closed
For the first time I've been able to use sddm on my professional laptop using an external monitor. Hourra. Can remove kdm!!! fixed by 0.14.0-4. -- eric
Bug#610485: marked as done ([ksshaskpass] menu item fails quietly)
Your message dated Wed, 15 Mar 2017 11:32:50 +0100 with message-id <20170315103244.lqbz72ousyctz...@gnuservers.com.ar> and subject line Re: Bug#610485: ksshaskpass shouldn't be called from the menu item has caused the Debian Bug report #610485, regarding [ksshaskpass] menu item fails quietly to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 610485: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610485 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ksshaskpass Version: 0.5.3-1+b1 Severity: important The menu item for SSH AskPass (ssh-add) fails quietly. The "hourglass" works until the timeout and nothing appears. --- System information. --- Architecture: i386 Kernel: Linux 2.6.36-trunk-686-bigmem Debian Release: 6.0 990 testing security.debian.org 990 testing ftp.ca.debian.org 500 unstable ftp.ca.debian.org 1 experimental ftp.ca.debian.org --- Package information. --- Depends (Version) | Installed -+-= kdebase-runtime | 4:4.4.5-1 libc6 (>= 2.1) | 2.11.2-7 libkdecore5 (>= 4:4.3.4) | 4:4.4.5-2 libkdeui5 (>= 4:4.3.4) | 4:4.4.5-2 libqtcore4 (>= 4:4.5.3) | 4:4.6.3-4 libqtgui4 (>= 4:4.5.3) | 4:4.6.3-4 openssh-client | 1:5.5p1-6 Recommends (Version) | Installed =-+-=== kwalletmanager | 4:4.4.5-1 Package's Suggests field is empty. --- End Message --- --- Begin Message --- Version: 4:5.7.4-1 ¡Hola Diederik! El 2016-08-07 a las 16:45 +0200, Diederik de Haas escribió: I stumbled upon pretty much the same issue [1] as you, but later learned that you shouldn't call the ksshaskpass program directly and that is actually specified in the README.Debian file. This package (therefor?) no longer provides a .desktop file. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831600 The desktop file provided in 0.5.3 was only a way to run ssh-add, that in turn triggers ksshaskpass to be shown (as long as that's configured to provide the ssh-askpass alternative). If you don't have a ssh key it will do nothing, and the hourglass effect won't notice till it's timeout. It would have been better if a proper error message was shown in this case, but that would have required a proper program/script handling it, instead of just calling ssh-add. As mentioned by Diederik the "hacky" desktop file is gone in newer versions. I'm closing the issue for these newer versions. Happy hacking, -- "Politicians and diapers have one thing in common. They should both be changed regularly, and for the same reason." ― José Maria de Eça de Queiroz Saludos /\/\ /\ >< `/ signature.asc Description: PGP signature --- End Message ---
Bug#585043: marked as done (Cannot type password when run from .kde/env during KDE startup)
Your message dated Wed, 15 Mar 2017 11:09:19 +0100 with message-id <20170315100912.ynp7kgoizw3sp...@gnuservers.com.ar> and subject line Re: Bug#585043: Cannot type password when run from .kde/env during KDE startup has caused the Debian Bug report #585043, regarding Cannot type password when run from .kde/env during KDE startup to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 585043: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=585043 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ksshaskpass Version: 0.5.3-1 Severity: important Hello, When ksshaskpass is spawned by program running during early KDE startup it is impossible to type the password. I've following scriptlet in .kde/env: $ cat 01ssh-add.sh /usr/bin/ssh-add $ During startup I can see ksshaskpass window, it even got focus (slightly blue frame round the text input field), but no keystrokes are registered. No black dots are visible during typing the password. No key is added to ssh-agent. The ksshaskpass window, however, can react to key. It looks like only text input field is handicapped. I noticed the problem some time ago. It was either when I upgraded KDE from 4:4.3.4-1 to 4:4.4.3-1 or from 4:4.4.3-1 to 4:4.4.3-2. At the moment I am running current sid and the problem still exists. Regards Artur -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages ksshaskpass depends on: ii kdebase-runtime 4:4.4.4-1 runtime components from the offici ii kdelibs5 4:4.4.4-1 transitional package for the KDE D ii libc6 2.11.1-2 Embedded GNU C Library: Shared lib ii libqtcore44:4.6.2-5 Qt 4 core module ii libqtgui4 4:4.6.2-5 Qt 4 GUI module ii openssh-client1:5.5p1-4 secure shell (SSH) client, for sec Versions of packages ksshaskpass recommends: ii kwalletmanager4:4.4.4-1 secure password wallet manager for ksshaskpass suggests no packages. -- no debconf information -- Artur R. CzechowskiGCS/IT dpu-(++) s-:-- a C++ UL$ P+++ L++(+++) E--- W++ N+(-) K- w !O M- V? PE++ Y+ PGP++ t !5 X R tv--(-) b++ DI+++ D+ G e-(*) h++(---) r++ y+ --- End Message --- --- Begin Message --- ¡Hola Artur! El 2010-06-08 a las 18:23 +0200, Artur R. Czechowski escribió: Package: ksshaskpass Version: 0.5.3-1 Severity: important Hello, When ksshaskpass is spawned by program running during early KDE startup it is impossible to type the password. I've following scriptlet in .kde/env: Sorry for taking so long to get back to you. Sadly this was the wrong location to launch an interactive application. The scripts in ~/.kde/env are executed before the desktop environment, in particular, before the window manager, as such the shown window is unable gain the required focus. The script should be placed in ~/.kde/Autostart (or in ~/.config/autostart-scripts/ in later versions). $ cat 01ssh-add.sh /usr/bin/ssh-add $ Happy hacking, -- "The first 90% of the code accounts for the first 90% of the development time. The remaining 10% of the code accounts for the other 90% of the development time." -- Tom Cargill Saludos /\/\ /\ >< `/ signature.asc Description: PGP signature --- End Message ---
Bug#500632: marked as done (ksshaskpass dead-locks other applications?)
Your message dated Wed, 15 Mar 2017 11:00:56 +0100 with message-id <20170315100049.cxh5igf7z74ry...@gnuservers.com.ar> and subject line Re: Bug#500632: ksshaskpass dead-locks other applications? has caused the Debian Bug report #500632, regarding ksshaskpass dead-locks other applications? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 500632: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500632 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ksshaskpass Version: 0.4.1-1 Severity: important Subject: ksshaskpass blocks itself or other applications Package: ksshaskpass Version: 0.4.1-1 Severity: important I start KSshAskPass using a custom ~/.kde/Autostart/ksshaskpass.desktop file. Than sometimes some applications like kwalletmanager and aggregator hang: 1. aggregator doesn't download RSS feeds 2. after entering the kwallet password, nothing happens. ssh asks again for the passphrase of my keys, so ssh-agent didn't get it. 3. If I start walletmanager, nothing happens. All other applications accessing the Wallet don't work also. 3. kded keeps consuming CPU time If I forcefully kill "kded", suddenly the applications unfreeze and I get a second popup window of ksshaskpass asking me for the passphrase of my ssh key files, but not for the Wallet. $ ps www 3478 3381 PID TTY STAT TIME COMMAND 3381 ?R 4:24 kded [kdeinit] --new-startup 3478 ?S 0:00 /usr/bin/ssh-askpass Enter passphrase for /home/pmhahn/.ssh/id_dsa: $ trace -p 3478 Process 3478 attached - interrupt to quit read(12, $ ls -gG /proc/3478/fd insgesamt 0 lr-x-- 1 64 29. Sep 22:51 0 -> pipe:[7532] l-wx-- 1 64 29. Sep 22:51 1 -> pipe:[8538] lr-x-- 1 64 29. Sep 22:51 10 -> pipe:[8544] l-wx-- 1 64 29. Sep 22:51 11 -> pipe:[8544] lrwx-- 1 64 29. Sep 22:51 12 -> socket:[8547] l-wx-- 1 64 29. Sep 22:51 2 -> /home/pmhahn/.xsession-errors lr-x-- 1 64 29. Sep 22:51 3 -> pipe:[7469] l-wx-- 1 64 29. Sep 22:51 4 -> pipe:[7469] lrwx-- 1 64 29. Sep 22:51 5 -> socket:[8539] lrwx-- 1 64 29. Sep 22:51 6 -> socket:[8541] l-wx-- 1 64 29. Sep 22:51 7 -> pipe:[8538] lr-x-- 1 64 29. Sep 22:51 8 -> pipe:[8543] l-wx-- 1 64 29. Sep 22:51 9 -> pipe:[8543] $ cat /home/pmhahn/.xsession-errors akregator: ERROR: : couldn't create slave : Unable to create io-slave: DCOP aborting while waiting for answer from 'kded' $ strace -p 3381 Process 3381 attached - interrupt to quit $ pidof kwalletd $ pidof kwalletmanager $ # trying to start them doesn't work $ kill 3381 ; echo $? 0 $ kill -SEGV 3381 ; echo $? 0 $ # Here ksshaskpass finally pops up asking for the passphrase of ~/.ssh/id_dsa $ kded --new-startup $ ssh-add --- End Message --- --- Begin Message --- Version: 0.5.3-1 ¡Hola Philipp! El 2008-09-29 a las 23:15 +0200, Philipp Matthias Hahn escribió: Package: ksshaskpass Version: 0.4.1-1 Severity: important Subject: ksshaskpass blocks itself or other applications Package: ksshaskpass Version: 0.4.1-1 Severity: important I start KSshAskPass using a custom ~/.kde/Autostart/ksshaskpass.desktop file. Than sometimes some applications like kwalletmanager and aggregator hang: 1. aggregator doesn't download RSS feeds 2. after entering the kwallet password, nothing happens. ssh asks again for the passphrase of my keys, so ssh-agent didn't get it. 3. If I start walletmanager, nothing happens. All other applications accessing the Wallet don't work also. 3. kded keeps consuming CPU time If I forcefully kill "kded", suddenly the applications unfreeze and I get a second popup window of ksshaskpass asking me for the passphrase of my ssh key files, but not for the Wallet. This is a really old bug reported to the kde 3 version of ksshaskpass, the original report seems to be missing the custom ksshaskpass.desktop. The documented way to start ksshaskpass on session start is to add an executable script in ~/.kde/Autostart (which was replaced by ~/.config/autostart-scripts/ in later versions of plasma), such as ksshaskpass.sh: #!/bin/sh export SSH_ASKPASS=/usr/bin/ksshaskpass ssh-add There is a README.Debian that documents this, in 0.5.3-1 and in later versions. I'm closing this issue with the version in stable, that's as far as I can tested this. Happy hacking, -- "Can you imagine what I would do if I could do all I can?" -- Sun Tzu Saludos /\/\ /\ >< `/ signature.asc Description: PGP signature --- End Message ---
kscreenlocker_5.8.6-1_source.changes ACCEPTED into experimental
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 15 Mar 2017 09:02:11 +0100 Source: kscreenlocker Binary: kscreenlocker-dev libkscreenlocker5 kde-config-screenlocker Architecture: source Version: 5.8.6-1 Distribution: experimental Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE MaintainersChanged-By: Maximiliano Curia Description: kde-config-screenlocker - KCM Module for kscreenlocker kscreenlocker-dev - Development files for kscreenlocker libkscreenlocker5 - Secure lock screen architecture Changes: kscreenlocker (5.8.6-1) experimental; urgency=medium . * New upstream release (5.8.6) Checksums-Sha1: c77ae3d135a43b4d648b4d428743f5721870988a 3029 kscreenlocker_5.8.6-1.dsc a5f9847ee7f32f0d684f3a023f0ab8e66e72ee46 108416 kscreenlocker_5.8.6.orig.tar.xz b44f76a87f932e63ac3a7a0171771b67a88653cd 6840 kscreenlocker_5.8.6-1.debian.tar.xz 6e07073ba93c4d92cb3f9c2f6a2e3352a752c597 23589 kscreenlocker_5.8.6-1_source.buildinfo Checksums-Sha256: 679358cbd7b75946f32781f6fc7381da9df6fb7e04d112453b6f5cb75f3e45fc 3029 kscreenlocker_5.8.6-1.dsc ed519a5c30bc350438d5b8418b484ae72513baf77645fe286f1ac14f302f14b3 108416 kscreenlocker_5.8.6.orig.tar.xz a788181d703b32fd42d043f51cd892030b98749a32dca1bbedf4ce5add3ba84f 6840 kscreenlocker_5.8.6-1.debian.tar.xz 2fc3d231fa36d2462f82c9dd8dabb99bbc3f9105b38cf1dccd0561fdabca4cec 23589 kscreenlocker_5.8.6-1_source.buildinfo Files: 9fdc23bb0d4756652eafd84df0c7275b 3029 libs optional kscreenlocker_5.8.6-1.dsc 1a2cb930d8b041be483f9913719cb689 108416 libs optional kscreenlocker_5.8.6.orig.tar.xz ddc975ba9aac249ebc2187518a5fe4f6 6840 libs optional kscreenlocker_5.8.6-1.debian.tar.xz effb9a275816f17b1ff29e19729e23d5 23589 libs optional kscreenlocker_5.8.6-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE+JIdOnQEyG4RNSIVxxl2mbKbIyoFAljI9uIACgkQxxl2mbKb IyqAZBAAuOeQXXrVzHPVwKMle8cFG88MPFwKsVWK+vs2Gpsn4+ghZD9AZEVSvmaC y9Qq1oWUK7gZFcG2VtQIVf1M3AVHLGelM0VpKs/NXMLr1HD9eCiXuot0HXV2WbWY ivaWtSWeVJRWdw10lhC19m/O3TlE6PcVhxyvgHAPT8U1Z/LWail6kuwVoDN0ZNzI q3PaP4gC/ysUpi+Kpbe3+sncOy+1wB543x6uYiGxsnzk+LYhOUZykAMEFwtwtut5 cRy0xPi/n8eCF3wStj+XUFrU8Dzuey8EKU1TtS3weS8NjtcGbPZSTAQT9eVmVCDY 0UnOfukuenvpZbq8IteE2cZDgyQLxaqTuP07ed3Q/5pVbE8pUsj39aI4+Z8xZD4c 4DbyitfV9aiWbNboSu8wuHNQ6hJtqr9JC7S9JZ4WV0gIr5P2BiYSYxOevKrEOCde UhiCqZAro8xW19wizVpKLKBnUGKMA+ZsI36gQ1K23sPK17eXKuGAQismqTbEWHRu Ku/0SBYQAsDAa3Vg+nhbCRqvaPmdG8FI9Ut7Sv2TdaXpGvXNbukysCYTYqjSxNoB KGxVb66rLI34G3GUAAODStBojY2/RmFXptiPc7yLjM9S6N5SBa7SpdXkUb4e+cb9 0F5qfjbZvZAswqRSJ0qBBxHPHfvnR0YTXth3nNiH5q/8bw3MfbA= =7bBh -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of kscreenlocker_5.8.6-1_source.changes
kscreenlocker_5.8.6-1_source.changes uploaded successfully to localhost along with the files: kscreenlocker_5.8.6-1.dsc kscreenlocker_5.8.6.orig.tar.xz kscreenlocker_5.8.6-1.debian.tar.xz kscreenlocker_5.8.6-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#857799: unblock: kscreenlocker/5.8.6-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Dear release team, KDE Plasma 5.8 is an LTS release that I consider fit to be updated in stretch. This particular request is for kscreenlocker 5.8.6. There is only one upsteam fix in the 5.8.6 version: + Fix crash in Screen Locker KCM on teardown (2601fa1) As well as the translation updates. No changes worth noting in the Debian side. I'm attaching the debdiff of 5.8.6-2 against 5.8.4-1 (currently in stretch), and the gitlog of the upstream changes. I have uploaded 5.8.6-1 to experimental, and I would like to upload 5.8.6-2 to unstable if this request gets approved. Please unblock package kscreenlocker unblock kscreenlocker/5.8.6-2 -- System Information: Debian Release: 9.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'testing'), (500, 'stable'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) commit 51cdac6d92d0ffecf530705e855e74f2f957c4c2 Author: Jonathan RiddellDate: Tue Feb 21 11:42:08 2017 + Update version number for 5.8.6 GIT_SILENT diff --git a/CMakeLists.txt b/CMakeLists.txt index 64b3a48..0c09ca7 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -1,4 +1,4 @@ -set(PROJECT_VERSION "5.8.5") +set(PROJECT_VERSION "5.8.6") set(PROJECT_VERSION_MAJOR 5) cmake_minimum_required(VERSION 2.8.12 FATAL_ERROR) commit 2601fa10725284feb5bcc78006250c0aa92f92dd Author: David Edmundson Date: Fri Feb 10 10:59:31 2017 +0100 Fix crash in Screen Locker KCM on teardown Summary: As described in https://bugreports.qt.io/browse/QTBUG-57714 exposing a QWidget as a context item to QtQuick can crash. Especially as the engine's context property gets deleted whilst deleting the parent item. This patch reworks the code so that exposed properties go through a proxy QObject. CCBUG: 373628 Test Plan: Pressing back whilst in the screenlocker KCM used to crash every time, now it doesn't. Also changed the wallpaper type, new settings appeared, I went from flat image to a specific wallpaper, and then locked my screen. Reviewers: #plasma, graesslin Reviewed By: #plasma, graesslin Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D4535 diff --git a/kcm/kcm.cpp b/kcm/kcm.cpp index aa8cf05..709b692 100644 --- a/kcm/kcm.cpp +++ b/kcm/kcm.cpp @@ -87,7 +87,12 @@ ScreenLockerKcm::ScreenLockerKcm(QWidget *parent, const QVariantList ) m_ui->wallpaperCombo->installEventFilter(this); m_ui->wallpaperConfigWidget->setClearColor(m_ui->palette().color(QPalette::Active, QPalette::Window)); - m_ui->wallpaperConfigWidget->rootContext()->setContextProperty("configDialog", this); +auto proxy = new ScreenLockerProxy(this); + m_ui->wallpaperConfigWidget->rootContext()->setContextProperty("configDialog", proxy); + +connect(this, ::wallpaperConfigurationChanged, proxy, ::wallpaperConfigurationChanged); +connect(this, ::currentWallpaperChanged, proxy, ::currentWallpaperChanged); + m_ui->wallpaperConfigWidget->setSource(QUrl(QStringLiteral("qrc:/kscreenlocker-kcm-resources/config.qml"))); connect(m_ui->wallpaperConfigWidget->rootObject(), SIGNAL(configurationChanged()), this, SLOT(changed())); diff --git a/kcm/kcm.h b/kcm/kcm.h index 8080209..096d17b 100644 --- a/kcm/kcm.h +++ b/kcm/kcm.h @@ -37,12 +37,10 @@ namespace KDeclarative class ConfigPropertyMap; } + class ScreenLockerKcm : public KCModule { Q_OBJECT -Q_PROPERTY(KDeclarative::ConfigPropertyMap *wallpaperConfiguration READ wallpaperConfiguration NOTIFY wallpaperConfigurationChanged) -Q_PROPERTY(QString currentWallpaper READ currentWallpaper NOTIFY currentWallpaperChanged) - public: enum Roles { PluginNameRole = Qt::UserRole +1, @@ -76,3 +74,32 @@ private: ScreenLockerKcmForm *m_ui; ScreenLocker::WallpaperIntegration *m_wallpaperIntegration = nullptr; }; + +//see https://bugreports.qt.io/browse/QTBUG-57714, don't expose a QWidget as a context property +class ScreenLockerProxy : public QObject +{ +Q_OBJECT +Q_PROPERTY(KDeclarative::ConfigPropertyMap *wallpaperConfiguration READ wallpaperConfiguration NOTIFY wallpaperConfigurationChanged) +Q_PROPERTY(QString currentWallpaper READ currentWallpaper NOTIFY currentWallpaperChanged) +public: +ScreenLockerProxy(ScreenLockerKcm *parent) : +QObject(parent), +q(parent) +{ +} + +KDeclarative::ConfigPropertyMap *wallpaperConfiguration() const { +return
Bug#852162: libkscreenlocker5: cannot enter password when two mirrored monitors are connected
Hi, > Sorry, I'm a bit confused by Alex reply. Is the issue related to > suspend or is it reproducible by activating the lock screen directly? The latter. No suspend/resume involved. > > Trying to reproduce the issue I noticed that when using the unified > view the screenlocker prompt won't give feedback for the typed keys. > This might be even considered a feature, to avoid revealing the length > of your password when using beamer and the likes. But contrary to > what's reported entering the password unlocks the screen. Sadly I'm not > sure if this is intended or not. If this is a feature, it is a very stupid one in my eyes… But, no matter what, pressing Enter also does not unlock the screen for me. I cannot get it to do anything as long as the second monitor is plugged in. -nik -- PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4 F296 Dominik George · Hundeshagenstr. 26 · 53225 Bonn Mobile: +49-1520-1981389 · https://www.dominik-george.de/ Teckids e.V. · FrOSCon e.V. Fellowship of the FSFE · Piratenpartei Deutschland Opencaching Deutschland e.V. · Debian Maintainer LPIC-3 Linux Enterprise Professional (Security) signature.asc Description: PGP signature