Re: Bug#1092632: evolution-data-server: Please don't depend on gnome-keyring

On Fri, 10 Jan 2025 at 19:53:31 +1100, Tim Connors wrote: > But evolution doesn't appear to actually need gnome-keyring. Maybe > "recommends" would be a better option? Or > gnome-keyring|pinentry-gtk2|pinentry-qt (still only recommends, > because you don't *need* gpg keys in order to be able to r

Bug#1085343: qt6-base: calls dbus_get_local_machine_id() which has bad error-handling

Source: qt6-base Version: 6.7.2+dfsg-3 Severity: normal Tags: upstream src/dbus/qdbusconnection.cpp calls dbus_get_local_machine_id(), which has no good mechanism for reporting an error, and therefore will spam warnings to standard error (and possibly crash) if the D-Bus machine ID has not been se

Bug#1085341: qtbase-opensource-src: calls dbus_get_local_machine_id() which has bad error-handling

Source: qtbase-opensource-src Version: 5.15.13+dfsg-4 Severity: normal Tags: upstream src/dbus/qdbusconnection.cpp calls dbus_get_local_machine_id(), which has no good mechanism for reporting an error, and therefore will spam warnings to standard error (and possibly crash) if the D-Bus machine ID

Bug#1085338: qtbase-opensource-src-gles: calls dbus_get_local_machine_id() which has bad error-handling

Source: qtbase-opensource-src-gles Version: 5.15.13+dfsg-2 Severity: normal Tags: upstream src/dbus/qdbusconnection.cpp calls dbus_get_local_machine_id(), which has no good mechanism for reporting an error, and therefore will spam warnings to standard error (and possibly crash) if the D-Bus machin

Bug#1063665: konqueror: start page -> "The requested operation could not be completed", "Undocumented error"

On Sat, 10 Feb 2024 at 19:30:35 +, Simon McVittie wrote: > I have not yet verified whether this is reproducible in the live image > itself (that's the next thing on my list). Yes it is. > Unknown error code 1,560,894,720 Please send a full bug report at > https://bugs.kd

Bug#1063665: konqueror: start page -> "The requested operation could not be completed", "Undocumented error" code 1560894720

Package: konqueror Version: 4:20.12.0-4 Severity: normal Tags: bullseye upstream Forwarded: https://bugs.kde.org/show_bug.cgi?id=451480 Issue found during Debian 11.9 point release media testing, sorry if this is already a known problem (I couldn't fnd a duplicate bug report). To reproduce ==

Re: Bug#1050798: plasma-workspace: please provide a kde-portals.conf for xdg-desktop-portal

, 29 Aug 2023 at 11:36:32 +0100, Simon McVittie wrote: > xdg-desktop-portal 1.17.x (currently in experimental) introduces a new > way to select which portals will be used for which desktop environments, > modelled on mimeapps.list: > > - each desktop environment should provide a fil

Bug#1050798: plasma-workspace: please provide a kde-portals.conf for xdg-desktop-portal

Source: plasma-workspace Severity: normal Tags: trixie sid User: xdg-desktop-por...@packages.debian.org Usertags: portals.conf Control: affects -1 plasma-mobile xdg-desktop-portal 1.17.x (currently in experimental) introduces a new way to select which portals will be used for which desktop environ

Bug#1035301: gdm3/bullseye: logging in to Plasma and then Xfce fails

Package: gdm3,plasma-desktop,xfce4-session Tags: bullseye Control: found -1 gdm3/3.38.2.1-1 Control: fixed -1 gdm3/43.0-3 Control: found -1 plasma-desktop/4:5.20.5-4 Control: fixed -1 plasma-desktop/4:5.27.2-1 Control: found -1 xfce4-session/4.16.0-1 Control: fixed -1 xfce4-session/4.18.1-1 Severit

Re: Bug#1032258: plasma-welcome: contains unintended patches providing a nonsensical welcome screen

Version: 5.27.2-1 On Thu, 02 Mar 2023 at 15:06:22 +0100, Aurélien COUDERC wrote: > Le 2 mars 2023 14:09:46 GMT+01:00, Simon McVittie a écrit : > >Package: plasma-welcome > >Justification: not suitable for inclusion in a stable release in this form > >Control: fixed -1 5.27

Bug#1032258: plasma-welcome: contains unintended patches providing a nonsensical welcome screen

Package: plasma-welcome Version: 5.27.0-1 Severity: serious Justification: not suitable for inclusion in a stable release in this form Control: fixed -1 5.27.2-1 To reproduce: * install Debian 12 with Plasma * install plasma-welcome * run plasma-welcome Expected result: a welcome screen that mak

Bug#1011865: kmouth: FTBFS: "The list of supported platorms is ''" (empty)

Control: retitle -1 kmouth: FTBFS: "The list of supported platorms is ''" (empty) Control: tags -1 + fixed-upstream Control: forwarded -1 https://invent.kde.org/accessibility/kmouth/-/commit/cfb889ab38befe1e378d92ab9915aed14ec5843b On Thu, 26 May 2022 at 21:06:48 +0200, Lucas Nussbaum wrote: > R

Bug#1011918: ktimer: FTBFS: "The list of supported platorms is ''" (empty)

Control: retitle -1 ktimer: FTBFS: "The list of supported platorms is ''" (empty) Control: tags -1 + fixed-upstream Control: forwarded -1 https://invent.kde.org/utilities/ktimer/-/commit/cb9b5d87331a36dc4e80177bbd16c4d0eb4d On Thu, 26 May 2022 at 21:06:52 +0200, Lucas Nussbaum wrote: > Relev

Bug#1005074: plasma-workspace: please provide some default MIME-handling application associations

Package: plasma-workspace Version: 4:5.23.5-1 Severity: normal X-Debbugs-Cc: debian-desk...@lists.debian.org Steps to reproduce: - Install task-kde-desktop - Also install gimp, nautilus and libglib2.0-bin - Have a PDF file (if you're testing in a VM like I was, there's one in /usr/share/doc/sha

Bug#993673: clazy: please make the build reproducible

avoided by building with -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON (which will be the default in debhelper compat level 14, but that's still experimental at the moment) as in the attached patch. smcv >From a12b63efc378a914c4f5c9cda6bf01143dbbaaeb Mon Sep 17 00:00:00 2001 From: Simon McVittie Date

Re: Bug#985914: xdg-desktop-portal-kde: should be Multi-Arch: foreign, so it satisfies steam:i386 Recommends

Control: retitle -1 xdg-desktop-portal-kde: should be Multi-Arch: foreign, so it satisfies steam:i386 Recommends Control: reassign -1 xdg-desktop-portal-kde Control: affects -1 + steam Control: tags -1 + patch On Thu, 25 Mar 2021 at 17:49:42 -0500, Boyd Stephen Smith Jr. wrote: > steam:i386 has a

Re: Bug#977754: evince does not display EPS or PS files anymore and shows "Loading..." forever

Control: reassign 977754 libspectre 0.2.9-1 Control: merge 975387 977754 Control: affects 975387 + evince On Mon, 21 Dec 2020 at 14:58:55 +0100, Patrice Duroux wrote: > I suggest you to look at #975387 as I think it is related to this issue. Reassigning to libspectre and merging with the libspect

Re: Bug#977693: gtk+3.0: Wayland primary selection interoperability with GTK clients on Plasma Desktop

Control: found -1 3.24.23-3 Control: notfound -1 3.24.24-1 Control: tags -1 + moreinfo On Sat, 19 Dec 2020 at 02:06:49 +0100, Sandro Knauß wrote: > currently it is impossible to use middle click pasting between Wayland > clients and GTK clients running on XWayland, like for example Chromium > an

Bug#970989: breeze-gtk-theme: does not define @text_view_bg named colour

Package: breeze-gtk-theme Version: 5.17.5-2 Severity: important Tags: upstream GTK 3.24.22 introduced a new named colour, @text_view_bg, which the vte terminal library has started to rely on, causing misrendering in themes that do not define it (see

Bug#969612: Bug#966535: transition: pipewire 0.3

On Wed, 09 Sep 2020 at 13:17:05 +0100, Simon McVittie wrote: > + weston > * Either upload experimental version to unstable, or disable > pipewire integration in unstable (as was already done in experimental) > + krfb > * Maintainers say they will appl

Bug#969613: xdg-desktop-portal-kde: please transition to pipewire 0.3, initially in experimental

Control: tags -1 + patch On Sun, 06 Sep 2020 at 00:08:08 +0100, Simon McVittie wrote: > pipewire 0.3 has now hit experimental. As discussed in #966535 and > on #debian-kde, the first step for transition #966535 is to make sure > the few packages that currently B-D on pipewire 0

Bug#969612: krfb: please transition to pipewire 0.3, initially in experimental

Control: tags -1 + patch On Sun, 06 Sep 2020 at 00:02:46 +0100, Simon McVittie wrote: > pipewire 0.3 has now hit experimental. As discussed in #966535 and > on #debian-kde, the first step for transition #966535 is to make sure > the few packages that currently B-D on pipewire 0

Bug#969613: xdg-desktop-portal-kde: please transition to pipewire 0.3, initially in experimental

Package: xdg-desktop-portal-kde Version: 5.17.5-2 Severity: normal Control: block #966535 by -1 pipewire 0.3 has now hit experimental. As discussed in #966535 and on #debian-kde, the first step for transition #966535 is to make sure the few packages that currently B-D on pipewire 0.2 can be recomp

Bug#969612: krfb: please transition to pipewire 0.3, initially in experimental

Package: krfb Version: 4:20.08.1-1 Severity: normal Control: block #966535 by -1 pipewire 0.3 has now hit experimental. As discussed in #966535 and on #debian-kde, the first step for transition #966535 is to make sure the few packages that currently B-D on pipewire 0.2 can be recompiled with 0.3.

Bug#966535: transition: pipewire 0.3

Package: release.debian.org Severity: normal Tags: moreinfo Control: block -1 by 954022 Control: affects -1 + src:pipewire User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: pipew...@packages.debian.org, k...@packages.debian.org, wes...@packages.debian.org, mut...@pack

Re: Bug#960696: chrome-gnome-shell: /usr/share/applications/org.gnome.ChromeGnomeShell.desktop is misconfigured

Control: reassign -1 chrome-gnome-shell,src:kservice Control: found -1 kservice/5.62.0-1 On Fri, 15 May 2020 at 22:08:35 +0800, Jason L. Quinn wrote: > Start of any QT application from the console produces the following chrome- > gnome-shell related error message: > > > kf5.k

Is Avahi Qt 5 main loop glue desirable?

avahi 0.8, which is currently being packaged, adds Qt 5 main loop glue (avahi-qt5.pc) in addition to its old Qt 4 and Qt 3 support (which has been disabled in Debian since 2017). The initial upload will probably leave the Qt 5 support disabled, because members of the Utopia team are more familiar

Bug#955848: libaccounts-glib-dev: unnecessarily Depends on deprecated dbus-glib

Package: libaccounts-glib-dev Version: 1.23-1 Severity: normal User: pkg-utopia-maintain...@lists.alioth.debian.org Usertags: dbus-glib-deprecation Control: block 895291 by -1 dbus-glib is a deprecated D-Bus library with some significant design flaws, and is essentially unmaintained. As announced

Re: Bug#927907: flatpak directories not added to XDG_DATA_DIRS on Plasma + Wayland

On Fri, 30 Aug 2019 at 08:17:47 +0100, Simon McVittie wrote: > Perhaps the answer is for Flatpak to have a systemd environment generator, > systemd.environment-generator(7), instead of or in addition to the > hooks we currently have? Actually, it has had one of these since 1.1.3, so that

Re: Bug#927907: flatpak directories not added to XDG_DATA_DIRS on Plasma + Wayland

Control: retitle -1 flatpak directories not added to XDG_DATA_DIRS on Plasma + Wayland On Thu, 25 Apr 2019 at 00:10:51 +0300, Ioan Eugen Stan wrote: > Note that the directories > > '/var/lib/flatpak/exports/share' > '/home/ieugen/.local/share/flatpak/exports/share' > > are not in the search pat

Bug#905697: kdepimlibs: don't depend on libical

On Fri, 08 Feb 2019 at 22:46:21 +0100, Sandro Knauß wrote: > Keep in mind, that kdepimlibs is an old grufted lib set that we also would > like to kill. Perhaps you could ask the ftp team to override its Section to oldlibs to indicate this? > But we also have other packages depending on it like:

Bug#915616: libksysguard: 'testsuite' autopkgtest does not test the installed version

Source: libksysguard Version: 4:5.14.3-1 Severity: normal The 'testsuite' autopkgtest for libksysguard is done with the build-needed restriction, does not list any binary packages built by libksysguard as test dependencies, and is basically a wrapper around dh_auto_test. It appears this means it

Bug#915613: libksysguard: autopkgtest intermittently fails: testCPUGraphHistory() 'percentageHist.size() > 0' returned FALSE

Source: libksysguard Version: 4:5.14.3-1 Severity: important X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: flaky The autopkgtest for libksysguard appears to be unreliable, with intermittent failures. The testing migration infrastructure can't distinguish betwe

Re: xdg-desktop-portal-gtk is installed when user specifies to install xdg-desktop-portal-kde with flatpak

On Thu, 20 Sep 2018 at 22:23:37 +0100, Andrew Hayzen wrote: > tl;dr; Should xdg-desktop-portal-kde provide xdg-deskop-portal-backend? Presumably. If it's a valid implementation of the same interfaces as xdg-desktop-portal-gtk (installs /usr/share/xdg-desktop-portal/portals/*.portal listing various

Re: [Pkg-utopia-maintainers] Bug#903837: dbus: SDDM with theme Breeze and KDE programs (e.g. Dolphin) take +30 seconds to start

Control: reassign 903837 libffi6 3.3~20160224-1 Control: close 903837 3.2.1-8 On Mon, 16 Jul 2018 at 01:12:01 +0200, Michael Biebl wrote: > You have an outdated version of libffi6 installed from experimental. Packages in experimental are not expected to be ready for general use (if they were read

Re: Bug#903837: dbus: SDDM with theme Breeze and KDE programs (e.g. Dolphin) take +30 seconds to start

Control: tags -1 + moreinfo On Sun, 15 Jul 2018 at 18:33:39 +0300, Alex Dănilă wrote: > The following take very long to start, 30 seconds to 2 minutes: > - SDDM with theme Breeze (doesn't happen with default Maui) > - kscreenlocker_greet - the first to show the behaviour, since about 1 week > - Am

Bug#898208: kwidgetsaddons: KDateComboBoxTest::testSignals() fails: 'QTest::qWaitForWindowActive(combo.data())' returned FALSE

Source: kwidgetsaddons Version: 5.44.0-1 Severity: important User: debian...@lists.debian.org Usertags: flaky The autopkgtest for kwidgetsaddons appears to be unreliable: it intermittently succeeds or fails with: FAIL! : KDateComboBoxTest::testSignals() 'QTest::qWaitForWindowActive(combo.data()

Bug#854034: soprano: build-depends on libraptor1-dev but uses libraptor2

+ @@ -1,3 +1,12 @@ +soprano (2.9.4+dfsg-4.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Remove obsolete libraptor1-dev build-dependency (Closes: #nn). +Build-depend on libraptor2-dev instead, which is what +soprano-daemon actually uses. + + -- Simon McVittie F

Bug#836299: signond: please use dbus-run-session to run tests

Source: signond Version: 8.57+20150423-3 Severity: normal Tags: upstream User: d...@packages.debian.org Usertags: dbus-launch dbus-launch-for-tests As described in I'm trying to reduce how much dbus-launch is used in Debian. This packag

Bug#836108: libaccounts-qt: please use dbus-run-session to run tests

Source: libaccounts-qt Version: 1.13+20150813-1 Severity: normal User: d...@packages.debian.org Usertags: dbus-launch dbus-launch-for-tests As described in I'm trying to reduce how much dbus-launch is used in Debian. This package curren

Re: Bug#836107: Acknowledgement of maintainer-only report (libaccounts-glib: please use dbus-run-session to run tests)

Control: reassign 836107 libaccounts-glib 1.21-1 On Tue, 30 Aug 2016 at 16:24:25 +, Debian Bug Tracking System wrote: > Your message has been sent to the package maintainer(s): > Thomas Preud'homme Sorry, this bug report was intended for a different package, but used a previous bug report a

Bug#835916: kde4libs: please switch from dbus-x11 to default-dbus-session-bus | dbus-session-bus

Source: kde4libs Version: 4.14.23-1 Severity: normal User: d...@packages.debian.org Usertags: dbus-launch default-dbus-session-bus dbus-launch-for-infra As described in I'm trying to reduce how much dbus-launch is used in Debian. kdelib

Bug#835915: kde-runtime: please use dbus-run-session, or dbus-daemon directly, in tests

Source: kde-runtime Version: 16.08.0-1 Severity: minor Tags: upstream User: d...@packages.debian.org Usertags: dbus-launch dbus-launch-for-tests (Opening this as a separate bug because it isn't in the same category as the usual autopkgtest-explicitly-using-dbus-launch issues that Maximiliano is ta

Bug#835839: cantor: please use dbus-run-session to run tests

Source: cantor Version: 16.04.2-1 Severity: normal User: d...@packages.debian.org Usertags: dbus-launch dbus-launch-for-tests As described in I'm trying to reduce how much dbus-launch is used in Debian. This package currently uses dbus-

Bug#835837: baloo-kf5: please use dbus-run-session to run tests

Source: baloo-kf5 Version: 5.25.0-1 Severity: normal User: d...@packages.debian.org Usertags: dbus-launch dbus-launch-for-tests As described in I'm trying to reduce how much dbus-launch is used in Debian. This package currently uses dbu

Bug#835832: artikulate: please use dbus-run-session to run tests

Source: artikulate Version: 16.04.3-1 Severity: normal Tags: patch User: d...@packages.debian.org Usertags: dbus-launch dbus-launch-for-tests As described in I'm trying to reduce how much dbus-launch is used in Debian. This package curr

Bug#835830: akonadi-search: please use dbus-run-session to run tests

Source: akonadi-search Version: 16.04.2-2 Severity: normal Tags: patch User: d...@packages.debian.org Usertags: dbus-launch dbus-launch-for-tests As described in I'm trying to reduce how much dbus-launch is used in Debian. akonadi-searc

Bug#835831: analitza: please use dbus-run-session to run tests

Source: analitza Version: 16.04.0-2 Severity: normal Tags: patch User: d...@packages.debian.org Usertags: dbus-launch dbus-launch-for-tests As described in I'm trying to reduce how much dbus-launch is used in Debian. This package curren

Bug#835828: akonadi-calendar: please use dbus-run-session to run tests

Source: akonadi Version: 16.04.2-2 Severity: wishlist Tags: patch User: d...@packages.debian.org Usertags: dbus-launch dbus-launch-for-tests As described in I'm trying to reduce how much dbus-launch is used in Debian. akonadi-calendar c

Bug#835827: akonadi: please use dbus-run-session to run tests

Source: akonadi Version: 16.04.3-2 Severity: normal Tags: patch User: d...@packages.debian.org Usertags: dbus-launch dbus-launch-for-tests Akonadi currently uses dbus-launch to run autopkgtests. As described in I'm trying to reduce how

Re: Bug#802659: dbus-python: Please drop recommends on PyQt4 packages

Sorry for the delay in responding to this; dbus-python hasn't been high on my priority list. On Thu, 22 Oct 2015 at 12:29:54 +0300, Dmitry Shachnev wrote: > Drop obsolete recommendations of Qt 4 packages ... > * python3-dbus.mainloop.qt is a package providing support for Qt (4.x) main > lo

Re: Bug#797644: kdelibs5-dev: kopete FTBFS: No rule to make target '/usr/lib/libsoprano.so', needed by 'kopete/kopete'

On Tue, 01 Sep 2015 at 09:20:17 +0100, Simon McVittie wrote: > If a particular -dev package requires linking with some other library, > it should depend on that library's -dev package (the same principle > as depending on the -dev packages of the libraries mentioned in a > pk

Bug#797644: kdelibs5-dev: kopete FTBFS: No rule to make target '/usr/lib/libsoprano.so', needed by 'kopete/kopete'

Package: kdelibs5-dev Version: 4:4.14.10-3 Severity: serious Justification: kopete fails to build from source (but built successfully in the past) Control: affects -1 kopete X-Debbugs-Cc set to kop...@packages.debian.org since it is known to be affected. While building kopete to verify that a pr

Bug#795818: libindi: FTBFS on arm64: symbols mismatch

Source: libindi Version: 1.0.0-2 Severity: serious Justification: fails to build from source (but built successfully in the past) libindi is still failing to build on arm64. The culprit seems to be lines specific to arm64 and sh4 in the symbols file, like these: - (arch=!arm64 !sh4)_ZN4INDI10Bas

Bug#791129: transition: libindi1 (GCC 5)

user release.debian@packages.debian.org usertag 791129 + transition retitle 791129 transition: libindi1 (GCC 5) tags 791129 = pending block 791129 by 790756 reassign 791129 release.debian.org severity 791129 normal forwarded 791129 https://release.debian.org/transitions/html/auto-libindi.html t

Bug#795143: libindi: FTBFS on !any-amd64 !ppc64el: symbols mismatch

Source: libindi Version: 1.0.0-1 Severity: serious Justification: fails to build from source (but built successfully in the past) libindi builds have now been attempted on every architecture except hurd-i386, and they are failing to build from source on every non-amd64, non-ppc64el architecture: <

Bug#785207: qtbase-opensource-src: FTBFS (test failure) if unable to resolve www.example.com, www.foo.com

On 13/05/15 17:12, Lisandro Damián Nicanor Pérez Meyer wrote: > On Wednesday 13 May 2015 16:55:06 Simon McVittie wrote: >> I'm still waiting for my test-build for this patch to get as far as >> actually running a test :-/ but hopefully it works. > > Considering i

Bug#785207: qtbase-opensource-src: FTBFS (test failure) if unable to resolve www.example.com, www.foo.com

existed in the Debian build. The Ubuntu build also skips quite a lot of tests - enabling them is clearly not trivial. I'm still waiting for my test-build for this patch to get as far as actually running a test :-/ but hopefully it works. -- Simon McVittie Collabora Ltd. <http://www.coll

Bug#785207: qtbase-opensource-src: FTBFS (test failure) if unable to resolve www.example.com, www.foo.com

ild as soon as I get a bug# to track this with), but I believe the attached patch from upstream v5.5.0-alpha1 should address that. This is potentially RC, depending on interpretation of Policy: https://bugs.debian.org/770016 -- Simon McVittie Collabora Ltd. <http://www.collabora.com/> Fro

Re: Bug#766462: with plymouth installed, I don't get any gettys on my VCs

Control: reassign 766462 gdm3 Control: affects 766462 kdm wdm plymouth Control: tags 766462 = patch pending On 01/03/15 21:58, Simon McVittie wrote: > Cc kdm, lightdm, slim, wdm maintainers to warn you that you might be > getting a RC bug (with a simple fix, add one 3-line file) assig

Re: Bug#766462: with plymouth installed, I don't get any gettys on my VCs

On 01/03/15 21:58, Simon McVittie wrote: > On Sun, 09 Nov 2014 at 12:11:49 +0100, Laurent Bigonville wrote: >> This bug is triggered by the fact that GDM systemd service is enabled >> while KDM is also enabled. GDM .service file explicitly conflicts with >> plymouth-qui

Re: Bug#766462: with plymouth installed, I don't get any gettys on my VCs

On 03/03/15 09:52, Yves-Alexis Perez wrote: > On mar., 2015-03-03 at 03:59 +, Mike Gabriel wrote: >> IMHO, if gettys don't come up properly, the system is rather broken >> and this is a no-go for jessie. > > Sure, but I had the impression that this wasn't the case for lightdm > (and slim), a

Re: Bug#766462: with plymouth installed, I don't get any gettys on my VCs

Cc kdm, lightdm, slim, wdm maintainers to warn you that you might be getting a RC bug (with a simple fix, add one 3-line file) assigned or cloned to your DM implementations. Peter Palfrader wrote: > I just upgraded to jessie, and with plymouth installed, I don't get > any gettys/login prompts on a

Bug#767164: extra-cmake-modules: Should not be in Jessie

On Tue, 28 Oct 2014 at 22:00:09 +0100, Sune Vuorela wrote: > e-c-m is not fully ready for jessie, and nothing should be using it Actually, attica-kf5 Build-Depends on it. Either attica-kf5, which is a library but is a leaf package, needs to be removed from jessie, or e-c-m needs to stay in jessie.

Re: Bug#747180: dbus reports CanSuspend/CanHibernate as false

retitle 747180 o.fd.PowerManagement reports CanSuspend = false reassign 747180 kde-workspace-bin thanks On 06/05/14 09:38, Pawel Palucha wrote: > As I understand, KDE queries dbus if the system is able to perform > suspend/hibernate. This is what I get when I query dbus for suspend: > > # dbus-se

Re: Bug#702474: dbus: Screensaver service seems to be absent.

reassign 702474 kde-workspace-bin thanks On 06/03/13 23:19, Boris Barbour wrote: > After a recent upgrade (and after testing the very latest dbus suggested by > reportbug), > I can no longer lock my kde session (in particular, using the Lock/Logout > widget). This seems more likely to be caused

Re: Bug#623492: plasma-desktop segfaults, prevents all (?) other kde apps from loading

reassign 623492 kdebase-workspace-bin thanks KDE maintainers bcc'd, please see the bug for further context. On Thu, 21 Apr 2011 at 11:42:55 +0100, Simon McVittie wrote: > This indicates a bug in whatever's using libdbus (looks like QtDBus, or > something higher up the stac