Processing control commands:
> close -1
Bug #771653 [systemd] systemd 217 breaks X11 (not more kdm and loggin and using
startx gives me no mouse)
Marked Bug as done
> forcemerge 771739 -1
Bug #771739 {Done: Martin Pitt } [systemd] could not start
nodm with systemd 217-1 or 217-2
Bug #771653 {Don
Control: close -1
Control: forcemerge 771739 -1
Eric Valette [2014-12-03 8:40 +0100]:
> Confirmed fixed. Thanks for your time and work.
Thanks for confirming! Duplicating to #771739 then.
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | D
On 03/12/2014 07:41, Didier Roche wrote:
However, I've committed a patch with 217-3 which incidentally will fix
as well your issue (which is basically "don't touch if the default dm !=
systemd native services". Keep me posted once you download that one
which should land shortly in experimental.
Le 02/12/2014 19:03, Eric Valette a écrit :
On 02/12/2014 09:32, Didier Roche wrote:
Ok, everything looks fine. I doubt about the /usr separation to be the
cause for that one as the generator doesn't use any file there.
Last try before sending you a debug binary:
cat -e /etc/X11/default-displa
Processing commands for cont...@bugs.debian.org:
> retitle 771830 generator doesn't find python at boot if /usr is a separate
> mount
Bug #771830 [systemd-cron] Fails to execute at all
Changed Bug title to 'generator doesn't find python at boot if /usr is a
separate mount' from 'Fails to execute
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/12/2014 15:11, Michael Biebl wrote:
> Am 02.12.2014 um 14:58 schrieb Vincent Danjean:
>> If you need more information, please ask.
>
> wicd seems to ship SysV init script only. I assume you haven't created your
> own native wicd.service file
On 2014-12-01 16:32, Michael Biebl wrote:
Does the system itself boot correctly?
Yes.
How does your /etc/network/interfaces look like?
Default configuration. Like Stefano Zacchiroli's, without last two IPv6
lines:
https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=15;filename=interfaces;att=
>[ 21.520730] systemd[1]: /usr appears to be on its own filesytem
> and is not already mounted. This is not a supported setup.
You could maybe also mount /usr in your initramfs, before systemd is started.
___
Pkg-systemd-maintainers mailing list
Pkg-
control: tag -1 + wontfix
control: severity -1 normal
Hi,
The generator must follow a special set of rules defined here:
http://www.freedesktop.org/wiki/Software/systemd/Generators/
One of those is that they are the first thing run by systemd; even before /usr
is mounted.
This can't be changed
Processing control commands:
> tag -1 + wontfix
Bug #771830 [systemd-cron] Fails to execute at all
Added tag(s) wontfix.
> severity -1 normal
Bug #771830 [systemd-cron] Fails to execute at all
Severity set to 'normal' from 'grave'
--
771830: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=77183
On 02/12/2014 09:32, Didier Roche wrote:
Ok, everything looks fine. I doubt about the /usr separation to be the
cause for that one as the generator doesn't use any file there.
Last try before sending you a debug binary:
cat -e /etc/X11/default-display-manager
(even if I treat trailing spaces,
Package: systemd-cron
Version: 1.3.1+ds1-2
Severity: grave
Here are relevant lines from output of dmesg-command:
[ 21.059257] EXT4-fs (sdb1): mounted filesystem with ordered data
mode. Opts: (null)
[ 21.520730] systemd[1]: /usr appears to be on its own filesytem
and is not already mount
systemd_217-3_amd64.changes uploaded successfully to localhost
along with the files:
systemd_217-3.dsc
systemd_217-3.debian.tar.xz
systemd_217-3_amd64.deb
systemd-sysv_217-3_amd64.deb
libpam-systemd_217-3_amd64.deb
libsystemd0_217-3_amd64.deb
libsystemd-dev_217-3_amd64.deb
libsystem
Michael Biebl [2014-12-02 14:33 +0100]:
> Those are bugs in the lxdm and slim packages and need to be fixed there.
That'd be my preference too, TBH, but it was already n'acked by the
RT. Maybe we can reopen this, though.
> Trying to workaround that in systemd looks like the wrong approach.
The w
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 02 Dec 2014 16:53:36 +0100
Source: systemd
Binary: systemd systemd-sysv libpam-systemd libsystemd0 libsystemd-dev
libsystemd-login0 libsystemd-login-dev libsystemd-daemon0 libsystemd-daemon-dev
libsystemd-journal
Your message dated Tue, 02 Dec 2014 16:19:59 +
with message-id
and subject line Bug#771739: fixed in systemd 217-3
has caused the Debian Bug report #771739,
regarding could not start nodm with systemd 217-1 or 217-2
to be marked as done.
This means that you claim that the problem has been dea
Your message dated Tue, 02 Dec 2014 16:19:59 +
with message-id
and subject line Bug#771498: fixed in systemd 217-3
has caused the Debian Bug report #771498,
regarding systemd: please sprinkle debian/systemd.bug-script with "2>&1"s
to be marked as done.
This means that you claim that the probl
Processing commands for cont...@bugs.debian.org:
> tags 771739 + pending
Bug #771739 [systemd] could not start nodm with systemd 217-1 or 217-2
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
771739: http://bugs.debian.org/cgi-bin/bugreport.c
Am 02.12.2014 um 14:58 schrieb Vincent Danjean:
> Package: systemd
> Version: 215-6
> Severity: important
>
> On my laptop, I've both network-manager and wicd installed.
> I know that both cannot be used at the same time. I've both installed
> because, in one environment (in the house of my pare
Le 02/12/2014 14:33, Michael Biebl a écrit :
Am 02.12.2014 um 14:17 schrieb Didier Roche:
Le 02/12/2014 13:44, Michael Biebl a écrit :
Am 02.12.2014 um 13:06 schrieb Didier Roche:
This is to fix multiple bug reports where people don't have (or have
multiple) dm services starting.
Can you prov
Am 02.12.2014 um 14:17 schrieb Didier Roche:
> Le 02/12/2014 13:44, Michael Biebl a écrit :
>> Am 02.12.2014 um 13:06 schrieb Didier Roche:
>>> This is to fix multiple bug reports where people don't have (or have
>>> multiple) dm services starting.
>> Can you provide links to such bug reports so we
Le 02/12/2014 13:44, Michael Biebl a écrit :
Am 02.12.2014 um 13:06 schrieb Didier Roche:
This is to fix multiple bug reports where people don't have (or have
multiple) dm services starting.
Can you provide links to such bug reports so we have a bit of a context?
Sure:
https://bugs.debian.org
Am 02.12.2014 um 13:06 schrieb Didier Roche:
> This is to fix multiple bug reports where people don't have (or have
> multiple) dm services starting.
Can you provide links to such bug reports so we have a bit of a context?
--
Why is it that all of the instruments seeking intelligent life in t
Le 02/12/2014 12:28, Michael Biebl a écrit :
Am 02.12.2014 um 06:48 schrieb Martin Pitt:
積丹尼 Dan Jacobson [2014-12-02 13:36 +0800]:
# cat /etc/X11/default-display-manager
cat: /etc/X11/default-display-manager: No such file or directory
Indeed, nodm doesn't use this file at all, nor does it con
Am 02.12.2014 um 06:48 schrieb Martin Pitt:
> 積丹尼 Dan Jacobson [2014-12-02 13:36 +0800]:
>> # cat /etc/X11/default-display-manager
>> cat: /etc/X11/default-display-manager: No such file or directory
>
> Indeed, nodm doesn't use this file at all, nor does it conflict with
> any other window manager
Am 01.12.2014 um 23:10 schrieb Felipe Sateler:
>> I'm interested how you managed to install kmod < 14, given that udev has
>> a Breaks: kmod < 14.
>
> Turns out udev was not upgraded alongside systemd:
>
> % apt-cache policy udev
> udev:
> Installed: 175-7.2
> Candidate: 175-7.2
> Version
Processing commands for cont...@bugs.debian.org:
> notfound 771739 215-7
Bug #771739 [systemd] could not start nodm with systemd 217-1 or 217-2
Ignoring request to alter found versions of bug #771739 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you ne
On 12/02/2014 09:32 AM, Didier Roche wrote:
> Ok, everything looks fine. I doubt about the /usr separation to be the
> cause for that one as the generator doesn't use any file there.
>
> Last try before sending you a debug binary:
> cat -e /etc/X11/default-display-manager
>
> (even if I treat tr
Le 02/12/2014 09:17, Eric Valette a écrit :
On 02/12/2014 09:13, Didier Roche wrote:
anks!
Are you really sure that /etc/X11/default-display-manager exists on this
machine (you didn't paste from any other) and points to a kdm binary?
Yes. Double checked!
cat /etc/X11/default-display-manager
Le 02/12/2014 09:13, Eric Valette a écrit :
On 02/12/2014 09:01, Eric Valette wrote:
On 02/12/2014 08:55, Didier Roche wrote:
This isn't the logs we asked for though to debug your issue. Can you
paste them please? (after running as root):
systemctl status kdm.service
systemctl status display-m
On 02/12/2014 09:13, Didier Roche wrote:
anks!
Are you really sure that /etc/X11/default-display-manager exists on this
machine (you didn't paste from any other) and points to a kdm binary?
Yes. Double checked!
cat /etc/X11/default-display-manager
/usr/bin/kdm
valette@tri-yann4:~$ type /usr/b
Le 02/12/2014 09:01, Eric Valette a écrit :
On 02/12/2014 08:55, Didier Roche wrote:
This isn't the logs we asked for though to debug your issue. Can you
paste them please? (after running as root):
systemctl status kdm.service
systemctl status display-manager.service
Here they are (making the
On 02/12/2014 09:01, Eric Valette wrote:
On 02/12/2014 08:55, Didier Roche wrote:
This isn't the logs we asked for though to debug your issue. Can you
paste them please? (after running as root):
systemctl status kdm.service
systemctl status display-manager.service
Here they are (making them f
On 02/12/2014 08:55, Didier Roche wrote:
This isn't the logs we asked for though to debug your issue. Can you
paste them please? (after running as root):
systemctl status kdm.service
systemctl status display-manager.service
Here they are (making them from console :-()
-- eric
● kdm.ser
34 matches
Mail list logo
