Bug#774884: kmail: Cannot choose my smime cert in KMail
Do you have gpgsm installed? If not, please install it, try again, and let us know if that solves it. Scott K -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/119e5166-346d-4053-92b0-72b59a406...@kitterman.com
Bug#774884: kmail: Cannot choose my smime cert in KMail
Hi Scott, yes , it is installed! Kai --- ###+++--- GPGConf ---+++### debug-level basic log-file socket:///home/kmh/.gnupg/log-socket auto-issuer-key-retrieve ###+++--- GPGConf ---+++### Mi 27 Aug 2014 14:00:39 CEST # GPGConf edited this configuration file. # It will disable options before this marked block, but it will # never change anything below these lines. --- Paket: gpgsm Neu: ja Zustand: Installiert Automatisch installiert: nein Multi-Arch: foreign Version: 2.0.26-3 Priorität: optional Bereich: utils Verwalter: Debian GnuPG Maintainers Architektur: amd64 Unkomprimierte Größe: 501 k Hängt ab von: gnupg-agent (= 2.0.26-3), scdaemon (= 2.0.26-3), libassuan0 (>= 2.0.1), libbz2-1.0, libc6 (>= 2.14), libgcrypt20 (>= 1.6.1), libgpg-error0 (>= 1.10), libksba8 (>= 1.2.0), libreadline6 (>= 6.0), zlib1g (>= 1:1.1.4) Empfiehlt: dirmngr Kollidiert mit: gpgsm Beschädigt: gnupg2 (< 2.0.0-2), gnupg2 (< 2.0.0-2) Ersetzt: gnupg2 (< 2.0.0-2), gnupg2 (< 2.0.0-2) Liefert: gpgsm Bereitgestellt von: gpgsm Am Freitag, 9. Januar 2015, 06:51:40 schrieb Scott Kitterman: > Do you have gpgsm installed? If not, please install it, try again, and let > us know if that solves it. > > Scott K -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1812354.BkIfifGhJL@toaster
Bug#755359: [kdm] systemd seem to fail to start display-manager.service
Control: tags -1 unreproducible On 01/08/2015 11:49 PM, Francesco Muzio wrote: > systemd[1]: Cannot add dependency job for unit display-manager.service, > ignoring: Unit display-manager.service failed to load: No such file or > directory. > > I think it's a normal behaviour if kdm does not provide service file as > do other Display Manager like GDM3 and SLIM So, I did *lots* of testing today. I installed Debian Jessie using the netinst installation image, both the Beta 2 and a daily snapshot, both i386 and amd64 and always just installed a minimal base system using tasksel by just selecting "SSH server" and "Standard system utilities" [1]. I then rebooted the freshly installed system which had no graphical user interface installed whatsoever and logged in as the standard user. Then became the root user (using sudo) and installed just 'plasma desktop' and 'kdm': apt-get install plasma-desktop kdm After that finished, I rebooted the machine and it booted right into kdm without any issues or error messages. Whatever I did, I could *NOT* reproduce your problem - at all. Thus, I conclude that you are either using broken installation media or the Debian mirror you are using is broken. If that still is not the case, please give me a step-by-step instruction on how you installed your Debian system. Thanks, Adrian > [1] http://screenshots.debian.net/screenshot/tasksel -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54afe97f.1010...@physik.fu-berlin.de
Processed: Re: [kdm] systemd seem to fail to start display-manager.service
Processing control commands: > tags -1 unreproducible Bug #755359 [kdm] [kdm] systemd seem to fail to start display-manager.service Added tag(s) unreproducible. -- 755359: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b755359.142081472528172.transcr...@bugs.debian.org
Bug#774974: qbs FTBFS on slow mips and mipsel buildds due to timeout during testing
Package: qbs
Version: 1.3.1+dfsg-4
Tags: sid patch
Severity: normal
Justification: FTBFS
User: debian-m...@lists.debian.org
Usertags: mips-patch
Packge qbs FTBFS on slow buildds for mips and mipsel.
Build failed on testing with an error:
> Totals: 136 passed, 1 failed, 10 skipped
> * Finished testing of TestBlackbox *
> make[5]: *** [check] Error 1
This behavior is noticed from version 1.3.1+dfsg-4 and higher.
Here are build logs on lucatelli, corelli and mayer.
https://buildd.debian.org/status/fetch.php?pkg=qbs&arch=mips&ver=1.3.3%2Bdfsg-1&stamp=1418663080
https://buildd.debian.org/status/fetch.php?pkg=qbs&arch=mips&ver=1.3.2%2Bdfsg-1&stamp=1418295892
https://buildd.debian.org/status/fetch.php?pkg=qbs&arch=mips&ver=1.3.2%2Bdfsg-1&stamp=1415115482
https://buildd.debian.org/status/fetch.php?pkg=qbs&arch=mips&ver=1.3.1%2Bdfsg-4&stamp=1413691942
https://buildd.debian.org/status/fetch.php?pkg=qbs&arch=mipsel&ver=1.3.3%2Bdfsg-1&stamp=1418664087
I was able to reproduce this failure locally on Cavium CN5230.
Increasing some timeouts (wait time) solves this issue for me.
I had tested it on versions:
qbs_1.3.2+dfsg-1 and qbs_1.3.3+dfsg-1
Patch that contains needed changes is attached.
Could you please consider including these changes?
Best Regards,
Dejan
diff -uNr qbs-1.3.2+dfsg.orig/tests/auto/api/tst_api.cpp qbs-1.3.2+dfsg/tests/auto/api/tst_api.cpp
--- qbs-1.3.2+dfsg.orig/tests/auto/api/tst_api.cpp 2014-10-07 12:07:15.0 +0200
+++ qbs-1.3.2+dfsg/tests/auto/api/tst_api.cpp 2014-11-25 16:32:33.0 +0100
@@ -532,7 +532,7 @@
qbs::Project project = setupJob->project();
const QScopedPointer buildJob(project.buildAllProducts(qbs::BuildOptions()));
QTimer::singleShot(1000, buildJob.data(), SLOT(cancel()));
-QVERIFY(waitForFinished(buildJob.data(), 30));
+QVERIFY(waitForFinished(buildJob.data(), 60));
}
void TestApi::infiniteLoopBuilding_data()
@@ -551,7 +551,7 @@
QScopedPointer setupJob(qbs::Project().setupProject(setupParams,
m_logSink, 0));
QTimer::singleShot(1000, setupJob.data(), SLOT(cancel()));
-QVERIFY(waitForFinished(setupJob.data(), 30));
+QVERIFY(waitForFinished(setupJob.data(), 60));
QVERIFY2(setupJob->error().toString().toLower().contains("cancel"),
qPrintable(setupJob->error().toString()));
}
diff -uNr qbs-1.3.2+dfsg.orig/tests/auto/blackbox/tst_blackbox.cpp qbs-1.3.2+dfsg/tests/auto/blackbox/tst_blackbox.cpp
--- qbs-1.3.2+dfsg.orig/tests/auto/blackbox/tst_blackbox.cpp 2014-12-09 18:29:51.0 +0100
+++ qbs-1.3.2+dfsg/tests/auto/blackbox/tst_blackbox.cpp 2014-11-24 19:04:43.0 +0100
@@ -99,7 +99,7 @@
QProcess process;
process.setProcessEnvironment(params.environment);
process.start(cmdLine);
-const int waitTime = 5 * 6;
+const int waitTime = 10 * 6;
if (!process.waitForStarted() || !process.waitForFinished(waitTime)) {
m_qbsStderr = process.readAllStandardError();
if (!params.expectFailure)
Bug#774974: marked as done (qbs FTBFS on slow mips and mipsel buildds due to timeout during testing)
Your message dated Fri, 09 Jan 2015 17:18:26 +
with message-id
and subject line Bug#774974: fixed in qbs 1.3.3+dfsg-3
has caused the Debian Bug report #774974,
regarding qbs FTBFS on slow mips and mipsel buildds due to timeout during
testing
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.)
--
774974: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774974
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qbs
Version: 1.3.1+dfsg-4
Tags: sid patch
Severity: normal
Justification: FTBFS
User: debian-m...@lists.debian.org
Usertags: mips-patch
Packge qbs FTBFS on slow buildds for mips and mipsel.
Build failed on testing with an error:
> Totals: 136 passed, 1 failed, 10 skipped
> * Finished testing of TestBlackbox *
> make[5]: *** [check] Error 1
This behavior is noticed from version 1.3.1+dfsg-4 and higher.
Here are build logs on lucatelli, corelli and mayer.
https://buildd.debian.org/status/fetch.php?pkg=qbs&arch=mips&ver=1.3.3%2Bdfsg-1&stamp=1418663080
https://buildd.debian.org/status/fetch.php?pkg=qbs&arch=mips&ver=1.3.2%2Bdfsg-1&stamp=1418295892
https://buildd.debian.org/status/fetch.php?pkg=qbs&arch=mips&ver=1.3.2%2Bdfsg-1&stamp=1415115482
https://buildd.debian.org/status/fetch.php?pkg=qbs&arch=mips&ver=1.3.1%2Bdfsg-4&stamp=1413691942
https://buildd.debian.org/status/fetch.php?pkg=qbs&arch=mipsel&ver=1.3.3%2Bdfsg-1&stamp=1418664087
I was able to reproduce this failure locally on Cavium CN5230.
Increasing some timeouts (wait time) solves this issue for me.
I had tested it on versions:
qbs_1.3.2+dfsg-1 and qbs_1.3.3+dfsg-1
Patch that contains needed changes is attached.
Could you please consider including these changes?
Best Regards,
Dejan
diff -uNr qbs-1.3.2+dfsg.orig/tests/auto/api/tst_api.cpp qbs-1.3.2+dfsg/tests/auto/api/tst_api.cpp
--- qbs-1.3.2+dfsg.orig/tests/auto/api/tst_api.cpp 2014-10-07 12:07:15.0 +0200
+++ qbs-1.3.2+dfsg/tests/auto/api/tst_api.cpp 2014-11-25 16:32:33.0 +0100
@@ -532,7 +532,7 @@
qbs::Project project = setupJob->project();
const QScopedPointer buildJob(project.buildAllProducts(qbs::BuildOptions()));
QTimer::singleShot(1000, buildJob.data(), SLOT(cancel()));
-QVERIFY(waitForFinished(buildJob.data(), 30));
+QVERIFY(waitForFinished(buildJob.data(), 60));
}
void TestApi::infiniteLoopBuilding_data()
@@ -551,7 +551,7 @@
QScopedPointer setupJob(qbs::Project().setupProject(setupParams,
m_logSink, 0));
QTimer::singleShot(1000, setupJob.data(), SLOT(cancel()));
-QVERIFY(waitForFinished(setupJob.data(), 30));
+QVERIFY(waitForFinished(setupJob.data(), 60));
QVERIFY2(setupJob->error().toString().toLower().contains("cancel"),
qPrintable(setupJob->error().toString()));
}
diff -uNr qbs-1.3.2+dfsg.orig/tests/auto/blackbox/tst_blackbox.cpp qbs-1.3.2+dfsg/tests/auto/blackbox/tst_blackbox.cpp
--- qbs-1.3.2+dfsg.orig/tests/auto/blackbox/tst_blackbox.cpp 2014-12-09 18:29:51.0 +0100
+++ qbs-1.3.2+dfsg/tests/auto/blackbox/tst_blackbox.cpp 2014-11-24 19:04:43.0 +0100
@@ -99,7 +99,7 @@
QProcess process;
process.setProcessEnvironment(params.environment);
process.start(cmdLine);
-const int waitTime = 5 * 6;
+const int waitTime = 10 * 6;
if (!process.waitForStarted() || !process.waitForFinished(waitTime)) {
m_qbsStderr = process.readAllStandardError();
if (!params.expectFailure)
--- End Message ---
--- Begin Message ---
Source: qbs
Source-Version: 1.3.3+dfsg-3
We believe that the bug you reported is fixed in the latest version of
qbs, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 774...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Dmitry Shachnev (supplier of updated qbs package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 09 Jan 2015 19:46:15 +0300
Source: qbs
Binary: qbs libqbscore1 libqbsqtprofilesetup1 qbs-dev qbs-dbg qbs-examples
qbs-doc qbs-doc-html
Architecture: source all
Version: 1.3.3+dfsg-3
Distrib
Processing of qbs_1.3.3+dfsg-3_amd64.changes
qbs_1.3.3+dfsg-3_amd64.changes uploaded successfully to localhost along with the files: qbs_1.3.3+dfsg-3.dsc qbs_1.3.3+dfsg-3.debian.tar.xz qbs-examples_1.3.3+dfsg-3_all.deb qbs-doc_1.3.3+dfsg-3_all.deb qbs-doc-html_1.3.3+dfsg-3_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1y9d7b-0003tj...@franck.debian.org
qbs_1.3.3+dfsg-3_amd64.changes ACCEPTED into unstable
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 09 Jan 2015 19:46:15 +0300
Source: qbs
Binary: qbs libqbscore1 libqbsqtprofilesetup1 qbs-dev qbs-dbg qbs-examples
qbs-doc qbs-doc-html
Architecture: source all
Version: 1.3.3+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers
Changed-By: Dmitry Shachnev
Description:
libqbscore1 - Qt Build Suite core library
libqbsqtprofilesetup1 - Qt Build Suite profile setup library
qbs- Qt Build Suite
qbs-dbg- Qt Build Suite debugging symbols
qbs-dev- Qt Build Suite development files
qbs-doc- Qt Build Suite documentation
qbs-doc-html - Qt Build Suite HTML documentation
qbs-examples - Qt Build Suite examples
Closes: 774974
Changes:
qbs (1.3.3+dfsg-3) unstable; urgency=medium
.
[ Pino Toscano ]
* Add ${misc:Pre-Depends} to Pre-Depends for qbs, libqbscore1, and
libqbsqtprofilesetup1.
.
[ Adam Majer ]
* Remove rpath from project include files used by 3rd party
software. On Debian, rpath should not be set when referencing
system installed libraries.
.
[ Dmitry Shachnev ]
* Add increase_timeout.diff from Dejan Latinovic to make tests pass
on mips (closes: #774974).
* Update debian/watch for new downloads server name.
Checksums-Sha1:
e438e400599f973d5d71cefdfc6ab0d79ecf184a 2426 qbs_1.3.3+dfsg-3.dsc
e7e5efac6c5fe3296865b0d9ceecb4e192728934 11404 qbs_1.3.3+dfsg-3.debian.tar.xz
82687c6c70e3614d90bbab90d1dcb88837fd7f85 39368
qbs-examples_1.3.3+dfsg-3_all.deb
18b4aa1417f2562286e7b8f06eee3bc30d04564e 123720 qbs-doc_1.3.3+dfsg-3_all.deb
40de9a0285ad9fe6bd2045628d5643fba1129aac 60858
qbs-doc-html_1.3.3+dfsg-3_all.deb
Checksums-Sha256:
7601720f836b2249f70dfb552102abed16fcb7a6ee7bcc078abb221e7bc43e45 2426
qbs_1.3.3+dfsg-3.dsc
c001c241b6f52cf91d0d38623a8b29f2006550ad9ddb271992ef025f58893d61 11404
qbs_1.3.3+dfsg-3.debian.tar.xz
c1992d15d06423ea55be96a5ce0cc44e0714f662ac1df25c70c4a288e41a0dfb 39368
qbs-examples_1.3.3+dfsg-3_all.deb
69bda14477716cbb970fdcec86fd8d6dec3903f5d0d25cf6461fcf34a7cd0622 123720
qbs-doc_1.3.3+dfsg-3_all.deb
77574b640daef5bafa117b5585a293dfbade9dca4e65d9c047ad92f47a09d677 60858
qbs-doc-html_1.3.3+dfsg-3_all.deb
Files:
fbd5ae458b419f3c118ffbc9d619c400 2426 devel optional qbs_1.3.3+dfsg-3.dsc
0ee142be61bff30a4822170afdf00300 11404 devel optional
qbs_1.3.3+dfsg-3.debian.tar.xz
f95aafcbb529941314719d8d66581d6f 39368 doc optional
qbs-examples_1.3.3+dfsg-3_all.deb
7fa55faed91bd294e7c10b74ef1fff92 123720 doc optional
qbs-doc_1.3.3+dfsg-3_all.deb
3131e4e2dd207a022e7f0984936b426e 60858 doc optional
qbs-doc-html_1.3.3+dfsg-3_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQIcBAEBAgAGBQJUsAv7AAoJENb+cQNj+F3TcB0P/0hl/1azJsepPVjzCdJsnGPe
YgP6zGQaP01VAUVYeXGwSts/3ZJcNn5QwnLfNGiq6sdml37/ufmf6xDn2MRUoauN
QB0LWo8o5nzRSrlHdHmOIGr5JOYbvsr4KNExGIlAu7h08sbvmBK20z69143nk7et
T1q7SyZQn5T0Jaty0PDJxYIH5M5xG6kKeh7cv0G+RQgmUwBFwRCIDL77pPE+S/ze
33ui5P/H0d7cJIummgtuhYPmyKMqWKCxkzUF5YSV3jYYpAlmaLd3DQ8hqAo1SXJt
iALwD9PhIw6nXZTBhxTjKsVL2CntVeEZaNr1a2czrh91OOWnqo9It50JriwA17Ys
+BrS2dYvfUi7CCb4+aDLqZAw2uPRDOzqvvlKDeuljcP6iubrkZXGRfYJB1exfblO
EbjhqT4bakv64wUbW4hcnVTyjYmiQVZZyV+9PC+TPRp0ksTbCGpMySYx3qsiHjkq
UqPVwXKr1JOQGysxpW9HbLglNp+6p53P3iQRg/ALgbzcGqXG4Ul3sgfWof58OSG6
wo+cRXEVt8YzeG3j3XuK0oVsXBYhPkz1H0GII2kGXYt5zSvg+XpDFsadTBfOrABD
+wTrffahICczaeAENaEdu46bo1XjHhj2+Tvzkf1RvZWld3dXuh31Bf9WFTfOWTl8
3an78hy5uo9//NVoV+c9
=sHOt
-END PGP SIGNATURE-
Thank you for your contribution to Debian.
--
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/e1y9dcc-0004pk...@franck.debian.org
Bug#755359: [kdm] systemd seem to fail to start display-manager.service
Il 09/01/2015 15:45, John Paul Adrian Glaubitz ha scritto: After that finished, I rebooted the machine and it booted right into kdm without any issues or error messages. Whatever I did, I could*NOT* reproduce your problem - at all. it means if you type the command # journalctl --no-pager | grep display-manager no output is printed ?
Bug#755359: [kdm] systemd seem to fail to start display-manager.service
Control: tags -1 -unreproducible Control: tags -1 patch Control: retitle -1 kdm: Please add a systemd service file On 01/09/2015 08:14 PM, Francesco Muzio wrote: > it means if you type the command > > # journalctl --no-pager | grep display-manager > > no output is printed ? Ok, I actually understand now what your problem is. What you are seeing there is a mere *warning* by the systemd generator for the display manager unit that there is no service file for kdm present and that systemd used different means like a sysvinit LSB script or similar to start kdm. root@vs76:~# journalctl --no-pager |grep display-manager Jan 09 22:39:09 vs76 systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. root@vs76:~# And, in fact, when you look at the output of "systemctl status kdm.service", you see that systemd used the kdm sysvinit script to start kdm which is indicated by the prefix "LSB:": root@vs76:~# systemctl status kdm.service ● kdm.service - LSB: X display manager for KDE Loaded: loaded (/etc/init.d/kdm) Drop-In: /run/systemd/generator/kdm.service.d └─50-kdm-$x-display-manager.conf Active: active (running) since Fri 2015-01-09 22:39:10 CET; 31s ago Process: 443 ExecStart=/etc/init.d/kdm start (code=exited, status=0/SUCCESS) CGroup: /system.slice/kdm.service ├─492 /usr/bin/kdm ├─497 /usr/bin/X :0 vt7 -br -nolisten tcp -auth /var/run/xauth/A:0-a7npvc ├─716 -:0 └─717 /usr/lib/kde4/libexec/kdm_greet Jan 09 22:39:10 vs76 kdm[443]: Starting K Display Manager: kdm. Jan 09 22:39:11 vs76 kdm_greet[717]: Cannot load /usr/share/kde4/apps/kdm/faces/.default.face: No such file...ctory Hint: Some lines were ellipsized, use -l to show in full. root@vs76:~# This isn't an error or a serious bug, it's just an information, nothing else. And to fix it, you can simply drop the attached service file "kdm.service" into /lib/systemd/system. This is a service file I derived from the kdm.service provided for kdm in Fedora. I tested it and it works without any problems and the warning message in the journal vanishes and "systemctl status kdm.service" lists a native systemd service: root@vs76:~# journalctl --no-pager |grep display-manager root@vs76:~# systemctl status kdm.service ● kdm.service - KDE Display Manager Loaded: loaded (/lib/systemd/system/kdm.service; enabled) Drop-In: /run/systemd/generator/kdm.service.d └─50-kdm-$x-display-manager.conf Active: active (running) since Fri 2015-01-09 22:41:39 CET; 19s ago Docs: man:kdm(1) Process: 489 ExecStartPre=/bin/sh -c [ "$(cat /etc/X11/default-display-manager 2>/dev/null)" = "/usr/bin/kdm" ] (code=exited, status=0/SUCCESS) Main PID: 497 (kdm) CGroup: /system.slice/kdm.service ├─497 /usr/bin/kdm ├─520 /usr/bin/X :0 vt7 -br -nolisten tcp -auth /var/run/xauth/A:0-rQr9Ab ├─710 -:0 └─711 /usr/lib/kde4/libexec/kdm_greet Jan 09 22:41:40 vs76 kdm_greet[711]: Cannot load /usr/share/kde4/apps/kdm/faces/.default.face: No such file...ctory Hint: Some lines were ellipsized, use -l to show in full. root@vs76:~# So my initial approach to fix the issue was right, the service file was just not correct. As a reference, I am attaching the service files for lightdm and kdm which are shipped with Fedora. Note that the kdm.service file from Fedora does *not* specify a BusName unlike the one for lightdm. Adding a BusName would result in systemd misinterpreting the exec status and leaving the activation state as "Activating". I will ask the release team for a possible pre-approval of a patched kdm package. Cheers, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 [Unit] Description=KDE Display Manager Documentation=man:kdm(1) After=systemd-user-sessions.service [Service] ExecStartPre=/bin/sh -c '[ "$(cat /etc/X11/default-display-manager 2>/dev/null)" = "/usr/bin/kdm" ]' ExecStart=/usr/bin/kdm Restart=always IgnoreSIGPIPE=no [Unit] Description=Light Display Manager Documentation=man:lightdm(1) Conflicts=getty@tty1.service After=systemd-user-sessions.service getty@tty1.service plymouth-quit.service livesys-late.service [Service] ExecStart=/usr/sbin/lightdm Restart=always IgnoreSIGPIPE=no BusName=org.freedesktop.DisplayManager [Install] Alias=display-manager.service [Unit] Description=The KDE login manager Conflicts=getty@tty1.service After=systemd-user-sessions.service getty@tty1.service plymouth-quit.service Conflicts=plymouth-quit.service [Service] ExecStart=/usr/bin/kdm vt1 Restart=always IgnoreSIGPIPE=no [Install] Alias=display-manager.service
Processed: Re: [kdm] systemd seem to fail to start display-manager.service
Processing control commands: > tags -1 -unreproducible Bug #755359 [kdm] [kdm] systemd seem to fail to start display-manager.service Removed tag(s) unreproducible. > tags -1 patch Bug #755359 [kdm] [kdm] systemd seem to fail to start display-manager.service Added tag(s) patch. > retitle -1 kdm: Please add a systemd service file Bug #755359 [kdm] [kdm] systemd seem to fail to start display-manager.service Changed Bug title to 'kdm: Please add a systemd service file' from '[kdm] systemd seem to fail to start display-manager.service' -- 755359: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b755359.142083991212103.transcr...@bugs.debian.org
Bug#755359: [kdm] systemd seem to fail to start display-manager.service
Il 09/01/2015 22:45, John Paul Adrian Glaubitz ha scritto: Ok, I actually understand now what your problem is. What you are seeing there is a mere *warning* by the systemd generator for the display manager unit that there is no service file for kdm present and that systemd used different means like a sysvinit LSB script or similar to start kdm. root@vs76:~# journalctl --no-pager |grep display-manager Jan 09 22:39:09 vs76 systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. root@vs76:~# it was a troubled birth, but we are arrived at the problem This isn't an error or a serious bug, it's just an information, nothing else. for this I have open the bug as a minor bug And to fix it, you can simply drop the attached service file "kdm.service" into /lib/systemd/system. This is a service file I derived from the kdm.service provided for kdm in Fedora. I tested it and it works without any problems and the warning message in the journal vanishes and "systemctl status kdm.service" lists a native systemd service: root@vs76:~# journalctl --no-pager |grep display-manager root@vs76:~# systemctl status kdm.service ● kdm.service - KDE Display Manager Loaded: loaded (/lib/systemd/system/kdm.service; enabled) Drop-In: /run/systemd/generator/kdm.service.d └─50-kdm-$x-display-manager.conf Active: active (running) since Fri 2015-01-09 22:41:39 CET; 19s ago Docs: man:kdm(1) Process: 489 ExecStartPre=/bin/sh -c [ "$(cat /etc/X11/default-display-manager 2>/dev/null)" = "/usr/bin/kdm" ] (code=exited, status=0/SUCCESS) Main PID: 497 (kdm) CGroup: /system.slice/kdm.service ├─497 /usr/bin/kdm ├─520 /usr/bin/X :0 vt7 -br -nolisten tcp -auth /var/run/xauth/A:0-rQr9Ab ├─710 -:0 └─711 /usr/lib/kde4/libexec/kdm_greet Jan 09 22:41:40 vs76 kdm_greet[711]: Cannot load /usr/share/kde4/apps/kdm/faces/.default.face: No such file...ctory Hint: Some lines were ellipsized, use -l to show in full. root@vs76:~# I have tried this new kdm.service file, but the solution isn't working for me. The kdm service can be started manually and seems to run without problems, but if I reboot the machine systemd ignores the kdm service with the same behaviour showed in previous tests I have tried the kdm.service file in my real Debian environment and in the VM that I have shared with you, in both cases KDM will not start at boot -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54b05769.8050...@gmail.com
Bug#755359: [kdm] systemd seem to fail to start display-manager.service
On 01/09/2015 11:34 PM, Francesco Muzio wrote: > I have tried the kdm.service file in my real Debian environment and in > the VM that I have shared with you, in both cases KDM will not start at > boot Is kdm actually configured to be your default display manager? root@vs76:~> cat /etc/X11/default-display-manager /usr/bin/kdm root@vs76:~> What do systemctl status kdm.service and journalctl -u kdm.service tell you? Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54b05861.4020...@physik.fu-berlin.de
Bug#755359: [kdm] systemd seem to fail to start display-manager.service
On 01/09/2015 11:38 PM, John Paul Adrian Glaubitz wrote: > On 01/09/2015 11:34 PM, Francesco Muzio wrote: >> I have tried the kdm.service file in my real Debian environment and in >> the VM that I have shared with you, in both cases KDM will not start at >> boot > > Is kdm actually configured to be your default display manager? Ok, I thoroughly analyzed your qemu image and eventually found out that the symbolic link /etc/systemd/system/display-manager.service which points to /lib/systemd/system/kdm.service was missing. A simple ln -s /lib/systemd/system/kdm.service /etc/systemd/system/display-manager.service fixed it for me. Don't ask me why, but it was missing on your installation but not on mine. I have to figure that out and I have to read up on the documentation again to understand where this symlink comes from, I did *not* create it manually in my case. Also, the kdm.service that you put under /lib/systemd/system/ has a completely messed up formatting because you somehow messed it up during copy and paste. Try looking at the file with "cat /lib/systemd/system/kdm.service" and you understand what I mean. I don't know whether this had any impact though. PS: Next time you share such a qemu image, please don't set the locale and the keyboard layout to Italian. It makes it easier for non-Italian-speaking folk to help you. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54b06799.4000...@physik.fu-berlin.de
Bug#755359: [kdm] systemd seem to fail to start display-manager.service
Il 10/01/2015 00:43, John Paul Adrian Glaubitz ha scritto: Ok, I thoroughly analyzed your qemu image and eventually found out that the symbolic link /etc/systemd/system/display-manager.service which points to /lib/systemd/system/kdm.service was missing. A simple ln -s /lib/systemd/system/kdm.service /etc/systemd/system/display-manager.service fixed it for me. I've no /etc/systemd/system/display-manager.service on my machines, very interesting Don't ask me why, but it was missing on your installation but not on mine. I have to figure that out and I have to read up on the documentation again to understand where this symlink comes from, I did *not* create it manually in my case. how many display managers are installed on your systems? if I install slim a soft link /etc/systemd/system/display-manager.service is created and it points to slim service you're saying that after a clean installation when only one display-manager (KDM) is installed a soft link /etc/systemd/system/display-manager.service is created for it ? right ? if you run a dpkg-reconfigure kdm to change the default DM and choose gdm3/slim the /etc/systemd/system/display-manager.service link is updated automatically? And if you re-choose KDM as default /etc/systemd/system/display-manager.service point again to kdm.service ? Also, the kdm.service that you put under /lib/systemd/system/ has a completely messed up formatting because you somehow messed it up during copy and paste. Try looking at the file with "cat /lib/systemd/system/kdm.service" and you understand what I mean. I don't know whether this had any impact though. It has been caused by a quick and dirty HTTP transfer PS: Next time you share such a qemu image, please don't set the locale and the keyboard layout to Italian. It makes it easier for non-Italian-speaking folk to help you. I will consider the advice. -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54b06ff3.1040...@gmail.com
Bug#755359: [kdm] systemd seem to fail to start display-manager.service
also I think it's impossible that a soft-link /etc/systemd/system/display-manager.service is created on a fresh install who only installs KDM as display-manager.service. Otherwise on the system there would be a /etc/systemd/system/display-manager.service who not point to no service. -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54b073fc.7030...@gmail.com
Bug#755359: [kdm] systemd seem to fail to start display-manager.service
On Sat, Jan 10, 2015 at 01:18:59AM +0100, Francesco Muzio wrote: > how many display managers are installed on your systems? As I said, that was a test system and there was only KDM installed, nothing else. I have to poke around a bit more. However, it seems ... > if I install slim a soft link > /etc/systemd/system/display-manager.service is created and it points > to slim service that this symlink is actually always created by the postinst script of the display manager (on Debian, Fedora uses the [Install] section of the .service file for that by setting an alias to display-manager.service) and looking at the source code of the kdm Debian package, this particular part is actually missing in the kdm package while it is present in the lightdm package. So it's actually a bit surprising that the link was installed on my test system. > if you run a dpkg-reconfigure kdm to change the default DM and > choose gdm3/slim the /etc/systemd/system/display-manager.service > link is updated automatically? Yes, this is actually the basic idea. > And if you re-choose KDM as default > /etc/systemd/system/display-manager.service point again to > kdm.service ? It actually depends on which package you reconfigure. So, if you run "dpkg-reconfigure lightdm" (provided that lightdm is installed) and choose "kdm as your default DM, it should work. However, if you do that with "dpkg-reconfigure kdm" and choose "kdm" or any other DM for that matter, it shouldn't work. > >PS: Next time you share such a qemu image, please don't set the > > locale and the keyboard layout to Italian. It makes it easier > > for non-Italian-speaking folk to help you. > I will consider the advice. Thanks! I will dig a bit more into the source code of the kdm Debian package and see if I can provide an updated version which should finally provide 100% compatibility. However, just to be sure I'm asking again: When you do a fresh installation and don't use a service file for kdm, kdm works and "systemctl status kdm.service" shows that it's running however you get the warning in the journal about the display-manager service, right? Cheers, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150110011807.ga29...@physik.fu-berlin.de
