Bug#774841: qtbase-opensource-src: Please provide qtconfig-qt5
Source: qtbase-opensource-src Severity: normal Dear Maintainer, the Qt4 source package provides a qt4-qtconfig package to configure various aspects of Qt4 applications. Qt5 in Debian currently doesn't ship with this application, although it seems to be part of the Qt5 repository. There's no way to configure Qt5 application, except by hand-editing the appropriate settings in the appropriate files (I guess?), which is sub-optimal. Can you please provide the qtconfig application for the Qt5 plateform? Thanks, Jonathan -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/4 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) -- 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/20150108102504.29762.29921.report...@danio.home
Bug#774841: qtbase-opensource-src: Please provide qtconfig-qt5
reassign 774841 src:qttools-opensource-src severity 774841 wishlist close 774841 thanks Hi, On 2015-01-08 11:25, Jonathan Ballet wrote: Qt5 in Debian currently doesn't ship with this application, although it seems to be part of the Qt5 repository. There's no way to configure Qt5 application, except by hand-editing the appropriate settings in the appropriate files (I guess?), which is sub-optimal. Can you please provide the qtconfig application for the Qt5 plateform? qtconfig there is not built by default, and I'm not sure whether it would even compile OOTB. It has been even removed upstream [1][2][3], so it makes no sense to provide a dead tool in Debian. [1] http://lists.qt-project.org/pipermail/development/2014-December/019544.html [2] https://codereview.qt-project.org/#/c/102626/ [3] https://qt.gitorious.org/qt/qttools/commit/9eb989dee3b7add23d83f2d0c40b2843f6a832a7 Thanks for your report, -- Pino Toscano -- 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/22a8f8c8f6acf4c2f4da4c4c9dd5d...@pino.toscano.name
Processed: Re: Bug#774841: qtbase-opensource-src: Please provide qtconfig-qt5
Processing commands for cont...@bugs.debian.org: > reassign 774841 src:qttools-opensource-src Bug #774841 [src:qtbase-opensource-src] qtbase-opensource-src: Please provide qtconfig-qt5 Bug reassigned from package 'src:qtbase-opensource-src' to 'src:qttools-opensource-src'. Ignoring request to alter found versions of bug #774841 to the same values previously set Ignoring request to alter fixed versions of bug #774841 to the same values previously set > severity 774841 wishlist Bug #774841 [src:qttools-opensource-src] qtbase-opensource-src: Please provide qtconfig-qt5 Severity set to 'wishlist' from 'normal' > close 774841 Bug #774841 [src:qttools-opensource-src] qtbase-opensource-src: Please provide qtconfig-qt5 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 774841: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774841 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.c.142071546012146.transcr...@bugs.debian.org
Bug#766349: marked as done (Kmail: Some times sign with S/MIME failed)
Your message dated Thu, 08 Jan 2015 10:14:41 -0300 with message-id <3589668.7htoikuX1d@luna> and subject line Unreproducible and lack of more info has caused the Debian Bug report #766349, regarding Kmail: Some times sign with S/MIME failed 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.) -- 766349: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766349 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kmail Version: 4:4.14.1-1 Severity: critical -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16-2-amd64 (SMP w/6 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kmail depends on: ii kde-runtime 4:4.14.1-1+b1 ii kdepim-runtime4:4.14.1-1 ii kdepimlibs-kio-plugins4:4.14.1-1 ii libakonadi-calendar4 4:4.14.1-1 ii libakonadi-contact4 4:4.14.1-1 ii libakonadi-kde4 4:4.14.1-1 ii libakonadi-kmime4 4:4.14.1-1 ii libakonadiprotocolinternals1 1.13.0-2 ii libc6 2.19-11 ii libcalendarsupport4 4:4.14.1-1 ii libfollowupreminder4 4:4.14.1-1 ii libgcc1 1:4.9.1-16 ii libgpgme++2 4:4.14.1-1 ii libgrantlee-core0 0.4.0-2 ii libincidenceeditorsng44:4.14.1-1 ii libkabc4 4:4.14.1-1 ii libkalarmcal2 4:4.14.1-1 ii libkcalcore4 4:4.14.1-1 ii libkcalutils4 4:4.14.1-1 ii libkcmutils4 4:4.14.1-1+b1 ii libkdecore5 4:4.14.1-1+b1 ii libkdepim44:4.14.1-1 ii libkdeui5 4:4.14.1-1+b1 ii libkio5 4:4.14.1-1+b1 ii libkleo4 4:4.14.1-1 ii libkmanagesieve4 4:4.14.1-1 ii libkmime4 4:4.14.1-1 ii libknewstuff3-4 4:4.14.1-1+b1 ii libknotifyconfig4 4:4.14.1-1+b1 ii libkontactinterface4a 4:4.14.1-1 ii libkparts44:4.14.1-1+b1 ii libkpgp4 4:4.14.1-1 ii libkpimidentities44:4.14.1-1 ii libkpimtextedit4 4:4.14.1-1 ii libkpimutils4 4:4.14.1-1 ii libkprintutils4 4:4.14.1-1+b1 ii libksieveui4 4:4.14.1-1 ii libktnef4 4:4.14.1-1 ii libmailcommon44:4.14.1-1 ii libmailimporter4 4:4.14.1-1 ii libmailtransport4 4:4.14.1-1 ii libmessagecomposer4 4:4.14.1-1 ii libmessagecore4 4:4.14.1-1 ii libmessagelist4 4:4.14.1-1 ii libmessageviewer4 4:4.14.1-1 ii libpimcommon4 4:4.14.1-1 ii libqt4-dbus 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-network4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-xml4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtwebkit4 2.3.4.dfsg-2 ii libsendlater4 4:4.14.1-1 ii libsolid4 4:4.14.1-1+b1 ii libstdc++64.9.1-16 ii libtemplateparser44:4.14.1-1 ii perl 5.20.1-1 Versions of packages kmail recommends: ii gnupg-agent 2.0.26-3 ii gnupg22.0.26-3 ii pinentry-gtk2 [pinentry-x11] 0.8.3-2 Versions of packages kmail suggests: ii bogofilter 1.2.4+dfsg1-3 pn clamav | f-prot-installer ii kaddressbook 4:4.14.1-1 ii kleopatra 4:4.14.1-1 ii procmail 3.22-22 -- no debconf information --- End Message --- --- Begin Message --- Hi! Diane has asked if you could reproduce this bug on November, and as no reply has arrived and we can't reproduce the bug anymore, I'm closing this bug. Of course if you can still reproduce it and can give us the data Diane asked for then do not heasitate to reopen this bug attaching the necessary info. Thanks, Lisandro. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part. --- End Message ---
Bug#763365: marked as done (qtcreator and qbs: error when trying to install together)
Your message dated Thu, 08 Jan 2015 13:51:53 - with message-id <20150108135153.4369.38...@mitya57.me> and subject line Re: qtcreator and qbs: error when trying to install together has caused the Debian Bug report #763365, regarding qtcreator and qbs: error when trying to install together 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.) -- 763365: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763365 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: qbs,qtcreator Version: qbs/1.2.2+dfsg-1 Version: qtcreator/3.2.1+dfsg-3 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2014-09-29 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Extracting templates from packages: 20% Extracting templates from packages: 41% Extracting templates from packages: 62% Extracting templates from packages: 82% Extracting templates from packages: 100% Preconfiguring packages ... Selecting previously unselected package gcc-4.9-base:amd64. (Reading database ... 10878 files and directories currently installed.) Preparing to unpack .../gcc-4.9-base_4.9.1-15_amd64.deb ... Unpacking gcc-4.9-base:amd64 (4.9.1-15) ... Setting up gcc-4.9-base:amd64 (4.9.1-15) ... (Reading database ... 10885 files and directories currently installed.) Preparing to unpack .../libstdc++6_4.9.1-15_amd64.deb ... Unpacking libstdc++6:amd64 (4.9.1-15) over (4.8.2-19) ... Setting up libstdc++6:amd64 (4.9.1-15) ... Processing triggers for libc-bin (2.19-11) ... Selecting previously unselected package libgcrypt20:amd64. (Reading database ... 10898 files and directories currently installed.) Preparing to unpack .../libgcrypt20_1.6.2-4_amd64.deb ... Unpacking libgcrypt20:amd64 (1.6.2-4) ... Selecting previously unselected package libgmp10:amd64. Preparing to unpack .../libgmp10_2%3a6.0.0+dfsg-6_amd64.deb ... Unpacking libgmp10:amd64 (2:6.0.0+dfsg-6) ... Selecting previously unselected package libnettle4:amd64. Preparing to unpack .../libnettle4_2.7.1-3_amd64.deb ... Unpacking libnettle4:amd64 (2.7.1-3) ... Selecting previously unselected package libhogweed2:amd64. Preparing to unpack .../libhogweed2_2.7.1-3_amd64.deb ... Unpacking libhogweed2:amd64 (2.7.1-3) ... Selecting previously unselected package libffi6:amd64. Preparing to unpack .../libffi6_3.1-2_amd64.deb ... Unpacking libffi6:amd64 (3.1-2) ... Preparing to unpack .../libp11-kit0_0.20.7-1_amd64.deb ... Unpacking libp11-kit0:amd64 (0.20.7-1) over (0.18.5-3) ... Selecting previously unselected package libtasn1-6:amd64. Preparing to unpack .../libtasn1-6_4.2-1_amd64.deb ... Unpacking libtasn1-6:amd64 (4.2-1) ... Selecting previously unselected package libgnutls-deb0-28:amd64. Preparing to unpack .../libgnutls-deb0-28_3.3.8-2_amd64.deb ... Unpacking libgnutls-deb0-28:amd64 (3.3.8-2) ... Selecting previously unselected package libkeyutils1:amd64. Preparing to unpack .../libkeyutils1_1.5.9-5_amd64.deb ... Unpacking libkeyutils1:amd64 (1.5.9-5) ... Selecting previously unselected package libkrb5support0:amd64. Preparing to unpack .../libkrb5support0_1.12.1+dfsg-10_amd64.deb ... Unpacking libkrb5support0:amd64 (1.12.1+dfsg-10) ... Selecting previously unselected package libk5crypto3:amd64. Preparing to unpack .../libk5crypto3_1.12.1+dfsg-10_amd64.deb ... Unpacking libk5crypto3:amd64 (1.12.1+dfsg-10) ... Selecting previously unselected package libkrb5-3:amd64. Preparing to unpack .../libkrb5-3_1.12.1+dfsg-10_amd64.deb ... Unpacking libkrb5-3:amd64 (1.12.1+dfsg-10) ... Selecting previously unselected package libgssapi-krb5-2:amd64. Preparing to unpack .../libgssapi-krb5-2_1.12.1+dfsg-10_amd64.deb ... Unpacking libgssapi-krb5-2:amd64 (1.12.1+dfsg-10) ... Selecting previously unselected package libxml2:amd64. Preparing to unpack .../libxml2_2.9.1+dfsg1-4_amd64.deb ... Unpacking libxml2:amd64 (2.9.1+dfsg1-4) ... Selecting previously unselected package libglib2.0-0:amd64. Preparing to unpack .../libglib2.0-0_2.42.0-1_amd64.deb ... Unpacking libglib2.0-0:amd64 (2.42.0-1) ... Selecting previously unselected package libatk1.0-data. Preparing to unpack .../libatk1.0-data_2.14.0-1_all.deb ... Unpacking libatk1.0-data (2.14.0-1) ... Selecting previously unselected package libatk1.0-0:amd64. Preparing to unpack .../libatk1.0-0_2.14.0-1_amd64.deb ... Unpacking libatk1.0-0:amd64 (2.14.0-1) ... Selecting previously unselected package libavahi-common-data:amd64. Preparing to unpack .../libavahi-common-data_0.6
Processed: [bts-link] source package kmix
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package kmix > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). > # remote status report for #772318 (http://bugs.debian.org/772318) > # Bug title: kmix: bashism in /bin/sh script > # * http://bugs.kde.org/show_bug.cgi?id=341640 > # * remote status changed: UNCONFIRMED -> RESOLVED > # * remote resolution changed: (?) -> FIXED > # * closed upstream > tags 772318 + fixed-upstream Bug #772318 [kmix] kmix: bashism in /bin/sh script Added tag(s) fixed-upstream. > usertags 772318 - status-UNCONFIRMED Usertags were: status-UNCONFIRMED. Usertags are now: . > usertags 772318 + status-RESOLVED resolution-FIXED There were no usertags set. Usertags are now: status-RESOLVED resolution-FIXED. > thanks Stopping processing here. Please contact me if you need assistance. -- 772318: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772318 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.c.14207361572472.transcr...@bugs.debian.org
Bug#774884: kmail: Cannot choose my smime cert in KMail
Package: kmail Version: 4:4.14.1-1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I imported my certs and could not choose it for signing my emails. * What exactly did you do (or not do) that was effective (or ineffective)? I tried to choose a cert and then i choosed a key in the dialog * What was the outcome of this action? The key-icon in front of the line got a red-cross and the "OK"-Button is grey and disabled * What outcome did you expect instead? the cert should be useable, as in evolution where it works like a charm *** End of the template - remove these template lines *** -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages kmail depends on: ii kde-runtime 4:4.14.2-2 ii kdepim-runtime4:4.14.2-2 ii kdepimlibs-kio-plugins4:4.14.2-2+b1 ii libakonadi-calendar4 4:4.14.2-2+b1 ii libakonadi-contact4 4:4.14.2-2+b1 ii libakonadi-kde4 4:4.14.2-2+b1 ii libakonadi-kmime4 4:4.14.2-2+b1 ii libakonadiprotocolinternals1 1.13.0-2 ii libc6 2.19-13 ii libcalendarsupport4 4:4.14.1-1 ii libfollowupreminder4 4:4.14.1-1 ii libgcc1 1:4.9.1-19 ii libgpgme++2 4:4.14.2-2+b1 ii libgrantlee-core0 0.4.0-2 ii libincidenceeditorsng44:4.14.1-1 ii libkabc4 4:4.14.2-2+b1 ii libkalarmcal2 4:4.14.2-2+b1 ii libkcalcore4 4:4.14.2-2+b1 ii libkcalutils4 4:4.14.2-2+b1 ii libkcmutils4 4:4.14.2-4 ii libkdecore5 4:4.14.2-4 ii libkdepim44:4.14.1-1 ii libkdeui5 4:4.14.2-4 ii libkio5 4:4.14.2-4 ii libkleo4 4:4.14.1-1 ii libkmanagesieve4 4:4.14.1-1 ii libkmime4 4:4.14.2-2+b1 ii libknewstuff3-4 4:4.14.2-4 ii libknotifyconfig4 4:4.14.2-4 ii libkontactinterface4a 4:4.14.2-2+b1 ii libkparts44:4.14.2-4 ii libkpgp4 4:4.14.1-1 ii libkpimidentities44:4.14.2-2+b1 ii libkpimtextedit4 4:4.14.2-2+b1 ii libkpimutils4 4:4.14.2-2+b1 ii libkprintutils4 4:4.14.2-4 ii libksieveui4 4:4.14.1-1 ii libktnef4 4:4.14.2-2+b1 ii libmailcommon44:4.14.1-1 ii libmailimporter4 4:4.14.1-1 ii libmailtransport4 4:4.14.2-2+b1 ii libmessagecomposer4 4:4.14.1-1 ii libmessagecore4 4:4.14.1-1 ii libmessagelist4 4:4.14.1-1 ii libmessageviewer4 4:4.14.1-1 ii libpimcommon4 4:4.14.1-1 ii libqt4-dbus 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-network4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-xml4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqtwebkit4 2.3.4.dfsg-3 ii libsendlater4 4:4.14.1-1 ii libsolid4 4:4.14.2-4 ii libstdc++64.9.1-19 ii libtemplateparser44:4.14.1-1 ii perl 5.20.1-4 Versions of packages kmail recommends: ii gnupg-agent 2.0.26-3 ii gnupg22.0.26-3 ii pinentry-gtk2 [pinentry-x11] 0.8.3-2 Versions of packages kmail suggests: ii bogofilter 1.2.4+dfsg1-3 pn clamav | f-prot-installer ii kaddressbook 4:4.14.1-1 ii kleopatra 4:4.14.1-1 ii procmail 3.22-22 -- no debconf information -- 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/20150108164421.18775.42456.report...@toaster.home.hamich.net
Bug#755359: [kdm] systemd seem to fail to start display-manager.service
I have done a test with a new installation of Debian. Yesterday I have created a minimal installation of Debian for i386 architecture with qemu. I have downloaded the latest weekly build of debian-testing-i386-netinst.iso image and I have installed it on a qcow2 image of 4GB I have installed kde-plasma-desktop and kdm. I have put the correct kdm.service in the /lib/systemd/system/ directory I have rebooted the system and the result is the same as on my real machines. kdm it's not executed. If I delete kdm.service file at the next reboot kdm works as expected. You can download the disk image of my VM from this link https://www.dropbox.com/s/nrcwkmbbbqlf5em/HDD4GB.7z?dl=0 I have run it with this command qemu-system-i386 -m 512 -enable-kvm -cpu athlon -hda HDD4GB.qcow2 I hope it helps you to understand where is the problem. -- 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/54aef5df.1030...@gmail.com
Bug#755359: [kdm] systemd seem to fail to start display-manager.service
On 01/08/2015 10:25 PM, Francesco Muzio wrote: > I have downloaded the latest weekly build of > debian-testing-i386-netinst.iso image and I have installed it on a qcow2 > image of 4GB > > I have installed kde-plasma-desktop and kdm. > I have put the correct kdm.service in the /lib/systemd/system/ directory Why did you copy the extra kdm.service file into the systemd directory? This file isn't actually necessary as the systemd generator for the display-manager unit takes care of that. It creates a unit file on-the-fly and puts it into /run/systemd/generator/kdm.service.d. > I have rebooted the system and the result is the same as on my real > machines. kdm it's not executed. > If I delete kdm.service file at the next reboot kdm works as expected. It works for me. I did an absolute clean installation with the netinst image (beta2). I chose KDE during the desktop installation dialog and got a working KDE with KDM setup right away, no additional work necessary. There is something that you are fundamentally doing wrong. I assume you do a minimal installation without using tasksel during the installation and then install the packages manually instead of using meta packages and apparently some essential package is missing? > I have run it with this command > qemu-system-i386 -m 512 -enable-kvm -cpu athlon -hda HDD4GB.qcow2 Thanks, I will look into it when I find the time. Here is a summary how I installed Debian Jessie and got a working system: 1. Download Debian Jessie Netinst Beta 2 ISO (amd64) 2. Create a new VMWare Virtual Machine and mount the Netinst ISO 3. Install everything with the defaults 4. At the tasksel selection screen, select "Desktop->KDE" plus "SSH server" and "base system" 5. Finish installation and reboot 6. Upon reboot, my system boots right into KDM; no strings attached So, the only difference I see is that you are using i386 (as opposed to amd64 here) and you apparently don't use tasksel. 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/54aef83a.9030...@physik.fu-berlin.de
Bug#755359: [kdm] systemd seem to fail to start display-manager.service
Why did you copy the extra kdm.service file into the systemd directory? Because you have told me to do it. see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755359#10 There is something that you are fundamentally doing wrong. I assume you do a minimal installation without using tasksel during the installation and then install the packages manually instead of using meta packages and apparently some essential package is missing? Because I had to recreate my problem with an image as small as possible. But don't digress anymore. I have explained my problem in the first message In journald log I see this message systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. See system logs and 'systemctl status display-manager.service' for details. And your proposed solution was you could add the attached kdm.service file and add it to /lib/systemd/system and see if that fixes your problem. this test hasn't solved my problem has caused me a fail of KDM to start at the reboot. probably you have missed my premise at the top of the first message Dear maintainers, My machine (updated debian testing) has only KDM as display manager, it starts without problem after upgrading/trasition to systemd. -- 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/54af025e.4080...@gmail.com
Bug#755359: [kdm] systemd seem to fail to start display-manager.service
On 01/08/2015 11:19 PM, Francesco Muzio wrote: > Because I had to recreate my problem with an image as small as possible. It was a suggestion, a guess out of the dark. I didn't tell you to do it, I merely asked whether this might help in this case. I didn't know about the systemd generators at the time then. > But don't digress anymore. I have explained my problem in the first message > >> In journald log I see this message >> >> systemd[1]: Cannot add dependency job for unit display-manager.service, >> ignoring: Unit display-manager.service failed to load: No such file or >> directory. See system logs and 'systemctl status >> display-manager.service' for details. > > > And your proposed solution was > >> you could add the attached kdm.service >> file and add it to /lib/systemd/system and see if that fixes your >> problem. I am not denying that. But that applied to the case of your installed system, not for a fresh installation. As I pointed out earlier, I did a clean and fresh unmodified installation and used the defaults and KDM worked out-of-the-box. Again, either the image you are using is broken or you are doing something fundamentally wrong as it worked for me. > this test hasn't solved my problem has caused me a fail of KDM to start > at the reboot. It was a _suggestion_, I was not saying _at all_ that this was the guaranteed solution. And, if you read further, I did my own experiments and could not reproduce your problem on a clean installation. > probably you have missed my premise at the top of the first message No, I did not miss anything at all since I said previously that I did a fresh and clean install with just KDM installed using tasksel and it worked. I can, btw, not examine your qemu image since you did not provide me with any passwords. I would have mount it manually now and modify the passwd database but you could have just told me the password. 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/54af043b.10...@physik.fu-berlin.de
Bug#755359: [kdm] systemd seem to fail to start display-manager.service
Il 08/01/2015 23:27, John Paul Adrian Glaubitz ha scritto: I can, btw, not examine your qemu image since you did not provide me with any passwords. I would have mount it manually now and modify the passwd database but you could have just told me the password. Oops... I have forget to tell you the credentials user: root pass: password user: debian pass: password in the image you have downloaded the kdm.service is stored in /lib/systemd/system/ directory if you delete it and reboot you can expirienced the error in journalctl log 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 -- 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/54af0975.8030...@gmail.com
