Am 11.05.2014 18:14, schrieb Zack Weinberg:
Well, this is frustrating: now I can't reproduce the problem either.
(Reverted /etc/fstab to its previous state, rebooted several times
with no problems.)
To me this suggests some sort of race condition inside udev, and
perhaps I should just file
Am 13.05.2014 22:57, schrieb Nikita Pichugin:
Package: systemd
Version: 204-10
Severity: important
Dear Maintainer,
I use a dualboot machine with Debian and Windows 8. I want the windows
partition to automount on boot, so I added it to the /etc/fstab. The problem
is
that I can't boot
The following assumes you run policykit 0.105
Am 13.05.2014 09:57, schrieb Martin Steigerwald:
merkaba:/etc/polkit-1 cat
./localauthority/50-local.d/org.freedesktop.upower.pkla
[Suspend/hibernate permissions]
Identity=unix-group:sudo
Am 19.05.2014 15:02, schrieb Martin Steigerwald:
Am Dienstag, 13. Mai 2014, 22:13:09 schrieb Michael Biebl:
Am 13.05.2014 09:57, schrieb Martin Steigerwald:
org.freedesktop.login1.hibernate-multiple-sessions
This also needs the according suspend action to be a full work-around:
merkaba
Hi,
Am 26.05.2014 13:03, schrieb Michael Meskes:
Hi,
I'm currently updating quota for quite a bit of things. But I'm at a loss as
to
what to do with /etc/init.d/quota. It seems, correct me if I'm wrong, that
systemd comes with its own binary for quotacheck, which does not implement
most
Am 26.05.2014 10:38, schrieb Martin-Éric Racine:
2014-05-25 17:01 GMT+03:00 Michael Stapelberg stapelb...@debian.org:
Martin-Éric Racine martin-eric.rac...@iki.fi writes:
The output from init.d scripts is printed to console 3 consecutive times
when systemd is pid 1.
Can you provide a
Am 26.05.2014 20:50, schrieb Patrick Häcker:
I guess the value dirty_writeback_centisecs defaults to 500. Other values
defined via sysctl have their (suspected) default value, too.
Which other values?
--
Why is it that all of the instruments seeking intelligent life in the
universe are
Hi Jonathan,
On Sat, May 10, 2014 at 02:16:25PM +0100, Jonathan Wiltshire wrote:
Control: severity -1 serious
Hi,
On Wed, May 07, 2014 at 06:20:02PM +0100, Jakub Warmuz wrote:
Unfortunately, I'm *unable to boot* the system with
netfilter-persistent systemd service enabled!
Package: dh-systemd
Version: 1.18
Severity: important
dh_systemd_start --restart-after-upgrade generates the following code in
postinst
if [ -d /run/systemd/system ]; then
systemctl --system daemon-reload /dev/null || true
deb-systemd-invoke try-restart ModemManager.service
Hi,
Am 04.06.2014 09:34, schrieb Martin Pitt:
brltty's systemd unit unconditionally starts the service. This
mis-matches the behaviour of the init.d file which checks
RUN_BRLTTY in /etc/default/brltty. The attached debdiff adjusts the
unit to do the same. It's not pretty, but seems to work
Am 05.06.2014 18:42, schrieb Ed Swierk:
Package: systemd
Version: 208-1
Severity: normal
X-Debbugs-CC: pkg-systemd-maintainers@lists.alioth.debian.org
Dear Maintainer,
During boot, certain services with Type=oneshot are started more than
once. The set of affected services varies
Am 14.06.2014 16:04, schrieb Michael Gold:
Package: systemd
Version: 204-10
Severity: critical
After installing systemd today and rebooting, I saw a few lines (not
errors) about systemd-fsck on xfs filesystems, and then I was prompted
for dm-crypt passwords for 4 disks that are not
Am 14.06.2014 16:59, schrieb Michael Gold:
On Sat, Jun 14, 2014 at 16:27:36 +0200, Michael Biebl wrote:
Am 14.06.2014 16:04, schrieb Michael Gold:
Package: systemd
Version: 204-10
Severity: critical
After installing systemd today and rebooting, I saw a few lines (not
errors) about systemd
Am 14.06.2014 17:15, schrieb Sven Joachim:
This is not going to happen as this conflicts with #748355.
#748355 is about the conflict with sysvinit, not with sysvinit-core.
Fair enough. Using Conflicts: sysvinit-core in systemd-sysv would have
been the correct thing to do anyway, i.e. the fix
Am 15.06.2014 00:02, schrieb Michael Biebl:
tags 751623 + fixed-upstream
thanks
Am 14.06.2014 22:51, schrieb Debian Bug Tracking System:
retitle -2 systemd: should print reason for starting emergency shell
Bug #751623 [systemd] systemd: opens emergency shell after prompting
Am 21.06.2014 17:41, schrieb Peter Gervai:
Reboot resulted an interesting view: endless rapid (10s per second) messages
about
[SKIP] ordering cycle found: D-Bus System Message Bus Socket
and that's all. Obviously nothing can be done, Ctrl-Alt-Del not yet
functioning, no further messages,
tags 752266 + moreinfo
thanks
Am 21.06.2014 23:32, schrieb Brainslug:
Package: systemd
Version: 204-8
Severity: important
I'm running jessie on a Dell M4800 laptop. I modified
/etc/systemd/logind.conf to suspend when either the power or suspend key
is pressed.
This part is working, but
forcemerge 751845 752104
thanks
Am 19.06.2014 18:18, schrieb Lionel Elie Mamane:
Package: systemd
Version: 204-8
Severity: normal
Just switched to systemd (installed systemd-sysv), on an up-to-date
jessie system.
On reboot, I notice:
Jun 19 17:53:02 fort systemd-fsck[959]:
Am 16.04.2014 22:06, schrieb Tollef Fog Heen:
]] Michael Biebl
I remember that we had a few issues in the past. One being that the
journal file was blown up incredibly causing important log data to be
rotated away
We might want to make it configurable whether to use
Am 25.06.2014 14:41, schrieb Christoph Anton Mitterer:
Package: systemd
Version: 204-11
Severity: important
Hey.
Not sure whether this is an issue of systemd or udev (probably even the
later) but since both are in the same source package anyway... ;)
Since 204-11 my system doesn't
reassign 752765 src:systemd
forcemerge 717491 752765
thanks
Am 26.06.2014 14:02, schrieb Tomas Janousek:
Package: systemd
Version: 204-8
Severity: normal
The manpage for systemd-suspend.service(8) advises users to put scripts in
/usr/lib/systemd/system-sleep/, but these are ignored.
reassign 752744 xfce4-session
thanks
Am 26.06.2014 09:22, schrieb Norbert Preining:
Package: systemd
Version: 204-12
Severity: normal
HI systemd maintainers,
everytime there is an upgrade of systemd, the suspend/reboot
functionality in XFCE is just gone. No reaction, no change.
I
Am 18.02.2014 23:25, schrieb Michael Biebl:
Package: systemd
Version: 204-7
Severity: wishlist
Since dracut enables systemd support in its initramfs, we should
probably trigger and update of the initramfs whenever systemd is
installed/updated/removed.
I don't know dracut enough, so
Am 27.11.2013 11:27, schrieb Alessandro Ghedini:
To reproduce the issue, one can follow those steps:
- Make sure rsyslog is installed and running.
status: step1.txt
- rm -f /etc/systemd/system/syslog.service
- systemctl daemon-reload
status: step2.txt
- re-create symlink: systemctl
Am 28.06.2014 18:32, schrieb Andrew Shadura:
Hello,
On Fri, 27 Jun 2014 21:13:40 +0200
Michael Biebl bi...@debian.org wrote:
the udev package ships a udev rule [1], which runs ifup $INTERFACE via
the net.agent helper.
This seems to create a race with the networking SysV init script
Hi there,
Am 29.06.2014 09:50, schrieb Michael Meskes:
Looking more closely, it seems the quota package only suggests the
rpcbind package, yet the quotarpc.service contains:
Requires=rpcbind.service
After=rpcbind.service
Requires means, the service will fail to start if the dependency is
Am 29.06.2014 13:39, schrieb Michael Meskes:
Btw, I noticed that quotarpc is not enabled by default. Instead
dh_systemd creates two sections for quota.service
# ls debian/*.service
debian/quota.quotarpc.service debian/quota.service
This seems to be the result of a recent change to
Hi Steve,
this is a heads-up that we intend to upload 208 from experimental to
unstable as soon as 204-14 has migrated to testing.
This should happen within the next week.
I guess this will make this bug sort-of RC, but I'll leave it up to you
to bump it accordingly.
Will notify you again, once
Am 01.07.2014 21:20, schrieb Steve Langasek:
Hi Michael,
On Tue, Jul 01, 2014 at 05:37:55PM +0200, Michael Biebl wrote:
Am 01.07.2014 17:20, schrieb Thomas Weber:
Or, taking a different perspective: now that the issue is known, what is
done to prevent another user from hitting the very same
.
reassign 751589 systemd 204-6
Bug #751589 {Done: Michael Biebl bi...@debian.org}
[sysvinit-core,systemd-sysv] sysvinit-core: /sbin/init missing after
switching from systemd to sysvinit
Bug reassigned from package 'sysvinit-core,systemd-sysv' to 'systemd'.
No longer marked as found
Am 02.07.2014 16:15, schrieb VALETTE Eric OLNC/OLPS:
So we are probably hunting a kernel/systemd dependency that is not
listed in the page I indicated.
Or I should go back to school and take a reading course :-(
CONFIG_FHANDLE was not set on my Kernel (in the meantime I also upgraded
from
reassign 753379 udev
forcemerge 713877 753379
thanks
Am 02.07.2014 16:30, schrieb Holger Levsen:
On Dienstag, 1. Juli 2014, Francewhoa wrote:
What led up to the situation?
• Steps to reproduce bug
1. Insert any CD or DVD
2. The CD or DVD is not automatically detected by the system
What
Am 02.07.2014 17:23, schrieb VALETTE Eric OLNC/OLPS:
On 07/02/2014 05:01 PM, Michael Biebl wrote:
Never saw a warning and never failed to install anything! I checked the
test is there in 208 too and it is.
I even did extract the code and tested it:
needed_symbols='inotify_init signalfd
Am 03.07.2014 11:16, schrieb Sam Morris:
Package: systemd
Version: 204-8~bpo70+1
Severity: normal
My desktop has been up for 31 days. Today I noticed I could no longer connect
Am 03.07.2014 09:09, schrieb VALETTE Eric OLNC/OLPS:
Sorry this was not clear, I have just checked the scripts works and I did on
kernel that had the CONFIG_FHANDLE already. So I do not understand why I
never
saw a warning.
Most likely the version you installed did not have this check.
It
Am 03.07.2014 12:33, schrieb Michael Biebl:
Am 03.07.2014 09:09, schrieb VALETTE Eric OLNC/OLPS:
Sorry this was not clear, I have just checked the scripts works and I did on
kernel that had the CONFIG_FHANDLE already. So I do not understand why I
never
saw a warning.
Most likely
Am 03.07.2014 12:55, schrieb Matthias Urlichs:
Package: systemd
Version: 208-5
Severity: normal
While updating, systemd was updated before glibc.
Needless to say, this does not work at all.
# aptitude(wd: ~)
Reading changelogs...
apt-listchanges: Mailing
Am 03.07.2014 13:03, schrieb Sam Morris:
On Thu, Jul 03, 2014 at 12:30:14PM +0200, Michael Biebl wrote:
If dbus is running (and it apparently is), then it should be the process
listening on /var/run/dbus/system_bus_socket.
I'm not sure about that... on another system where dbus is currently
Am 03.07.2014 13:56, schrieb Jakub Wilk:
systemd-sysv was unpacked, but not configured yet. At this point, its
dependencies were not required to be satisfied. So from POV of the
package manager everything is in order here.
Perhaps a Pre-Depends is missing somewhere; but it's hard to tell
Am 03.07.2014 14:26, schrieb Ansgar Burchardt:
Most essential packages should have this problem. I checked bash and it
indeed has
Pre-Depends: dash (= 0.5.5.1-2.2), libc6 (= 2.15), libtinfo5
which comes from
Pre-Depends: dash (= 0.5.5.1-2.2), ${shlibs:Pre-Depends}, ${misc:Depends}
Am 03.07.2014 16:17, schrieb Michael Biebl:
Attached is a proposed patch.
feedback on the patch would be appreciated.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
Hi Gerrit,
Am 04.07.2014 13:50, schrieb Gerrit Pape:
I hereby ask for help to add systemd support to these packages.
We (pkg-systemd team) can help you with that.
Let's follow up on the pkg-systemd mailing list.
In most cases adding a .service file is pretty simple.
If it's only about
Am 04.07.2014 14:34, schrieb Michael Biebl:
Hi Gerrit,
Am 04.07.2014 13:50, schrieb Gerrit Pape:
I hereby ask for help to add systemd support to these packages.
We (pkg-systemd team) can help you with that.
Let's follow up on the pkg-systemd mailing list.
In most cases adding
Package: libselinux1
Version: 2.3-1
Severity: important
Tags: patch
The current version of libselinux1.postint runs telinit u to tell init
to re-exec itself. This was added so the system can shutdown cleanly when
sysvinit is the active PID 1.
Under systemd this is not necessary since systemd
Package: libsepol1
Version: 2.3-1
Severity: important
Tags: patch
The current version of libselinux1.postint runs telinit u to tell init
to re-exec itself. This was added so the system can shutdown cleanly
when sysvinit is the active PID 1.
Under systemd this is not necessary since systemd uses
Am 05.07.2014 04:40, schrieb Michael Biebl:
I'm not convinced that a package-individual trigger is the right answer
for this (we also discussed this possibility within the team). Every
package providing a long running system service would have to provide
such a trigger and every library would
Am 05.07.2014 04:57, schrieb Russell Coker:
On Sat, 5 Jul 2014 04:40:33 Michael Biebl wrote:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753726
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753727
The above bugs concern the ability of library packages to request that
systemd use
Am 05.07.2014 04:57, schrieb Russell Coker:
On Sat, 5 Jul 2014 04:40:33 Michael Biebl wrote:
So I still kindly ask you to apply the patches in #753726 and #753727
OK I think we should do that next time we update them. I don't think it's
worth doing a special update for that.
Thank you
Am 05.07.2014 15:57, schrieb Michael Biebl:
Can you also attach the output of
grep snd_hda /etc/modprobe.d/* /lib/modprobe.d/* and a complete
make that
grep snd /etc/modprobe.d/* /lib/modprobe.d/*
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed
Am 05.07.2014 15:47, schrieb Antonio Marcos López Alonso:
El 05/07/14 13:33, Michael Biebl escribió:
Am 05.07.2014 14:16, schrieb Antonio Marcos López Alonso:
Package: systemd
Version: 204-14
Severity: important
--- Please enter the report below this line. ---
After upgrading to systemd
Am 05.07.2014 16:09, schrieb Antonio Marcos López Alonso:
Attaching.
grep_snd.log
/etc/modprobe.d/alsa-base-blacklist.conf:# blacklist snd-atiixp-modem
/etc/modprobe.d/alsa-base-blacklist.conf:# blacklist snd-intel8x0m
/etc/modprobe.d/alsa-base-blacklist.conf:# blacklist
Am 07.11.2013 12:08, schrieb Emmanuel Hainry:
Package: libsystemd-login0
Version: 204-5
Severity: important
Dear Maintainer,
Login is taking something like 20 seconds (while the rest of the boot
was done after 9 seconds). Looking into dmesg, it does not report
anything being done before
Am 22.02.2014 00:16, schrieb John Paul Adrian Glaubitz:
On 02/22/2014 12:10 AM, Michael Biebl wrote:
Just tried again (with two VMs):
The NFS server being a wheezy system, the client system is an up-to-date
SID system. Worked like a charm.
Ok, it seems to be a local configuration issue
Am 06.07.2014 10:39, schrieb Antonio Marcos López Alonso:
El 06/07/14 05:34, Ben Hutchings escribió:
I think the usual workaround is to add 'index=1' to the snd-aloop line
in /etc/modules. It is probably possible to do something more
sophisticated in an ALSA configuration file.
Adding
Am 06.07.2014 15:46, schrieb Michael Meskes:
Package: systemd
Version: 204-14
Severity: normal
TTBOMK the quota package now provides all the logic in these service files and
then some, so please remove these from systemd and let quota handle the quota
stuff.
How does the quota package
[dropping the debian-kernel CC]
Am 06.07.2014 21:11, schrieb Bjørn Mork:
Michael Biebl bi...@debian.org writes:
Be aware that systemd-modules-load does *not* read module parameters
from /etc/modules. You'll need to set them via a /etc/modprobe.d/ file.
Hmm... Is that considered a bug
Am 06.07.2014 16:39, schrieb Michael Meskes:
How does the quota package ensure it is run when an actual device shows
up and is mounted? Afaics it is only run once during boot.
Argh, you're right, that it doesn't do. But it should. How does systemd make
sure its quotaon service is run in that
Am 07.07.2014 11:20, schrieb Michael Meskes:
On Mon, Jul 07, 2014 at 03:00:47AM +0200, Michael Biebl wrote:
Wouldn't be a better idea to simply get the additional functionality the
Debian quota scripts provide moved into the quotaon and quotacheck
binaries upstream?
I don't think so
Am 08.07.2014 15:01, schrieb Łukasz Stelmach:
Package: systemd
Version: 204-14~bpo70+1
Severity: normal
Dear Maintainer,
I want to run systemd in a container on my desktop. I installed a
minimal debian system in a directory (debootstrap) and started a
container in it. Much to my
Am 08.07.2014 22:50, schrieb Stefano Zacchiroli:
Now the questions/comments:
- I've had that script since ever, basically, and it used to work fine
in the past, both before and after switching to systemd as init. I'm
not sure why/when it stopped working.
- As a mere user, the above
Am 09.07.2014 01:14, schrieb Michael Biebl:
Am 08.07.2014 22:50, schrieb Stefano Zacchiroli:
Now the questions/comments:
- I've had that script since ever, basically, and it used to work fine
in the past, both before and after switching to systemd as init. I'm
not sure why/when
Am 09.07.2014 01:28, schrieb Michael Biebl:
Running within the context of an if-up.d hook you make an explicit
assumption that $network is already provided, which is probably reasonable.
Strictly speaking though, the LSB $network facility is defined in
/etc/insserv.conf when the networking
Am 09.07.2014 10:20, schrieb Łukasz Stelmach:
It was 2014-07-08 wto 21:34, when Michael Biebl wrote:
Am 08.07.2014 17:50, schrieb Łukasz Stelmach:
It was 2014-07-08 wto 16:29, when Michael Biebl wrote:
Am 08.07.2014 16:03, schrieb Michael Biebl:
I can not reproduce this but I have to add
reassign 754404 systemd-sysv
thanks
Am 10.07.2014 22:32, schrieb 積丹尼 Dan Jacobson:
MB == Michael Biebl bi...@debian.org writes:
MB Please provide a complete apt log.
Start-Date: 2014-07-11 01:47:04
Install: systemd-sysv:i386 (208-5)
Upgrade: libsystemd-daemon0:i386 (208-3, 208-5
Am 10.07.2014 22:51, schrieb Michael Biebl:
The /sbin/runlevel utility is shipped by both sysvinit-core and
systemd-sysv. That's why they Conflict/Replace each other.
...
We could drop the Conflicts: sysvinit-core from systemd-sysv and only
keep the Replaces, but that has it's downsides
Am 12.07.2014 00:34, schrieb Bas Wijnen:
When fsck failed with this message before, I could do:
mount / -o remount,ro
fsck /
Now, and I'm guessing this is a change on the part of systemd, that
first command (remount read-only) fails with the message that the file
system is busy. Having no
I really don't think what your doing in rc.local is sensible, but at
least there is a simpler workaround then your messing around with the
getty config:
# mkdir /etc/systemd/system/rc-local.service.d/
# echo -e
[Service]\nStandardInput=tty-force\nStandardOutput=journal+console\n
Am 13.07.2014 22:17, schrieb Bas Wijnen:
On Sat, Jul 12, 2014 at 12:59:04AM +0200, Michael Biebl wrote:
Am 12.07.2014 00:34, schrieb Bas Wijnen:
When fsck failed with this message before, I could do:
mount / -o remount,ro
fsck /
Now, and I'm guessing this is a change on the part of systemd
reassign 755194 plymouth
thanks
Am 18.07.2014 19:14, schrieb Gilles Mocellin:
Package: systemd
Version: 208-6
Severity: normal
Dear Maintainer,
My syslog is full of message like that one :
Jul 18 18:54:16 guitare systemd[1]: Cannot add dependency job for unit
Am 18.07.2014 13:56, schrieb Christoph Berg:
Package: systemd
Version: 204-14
Severity: normal
Hi,
my host system is jessie. In my sid-amd64 chroot which I entered using
systemd-nspawn, I tried to start a new systemd --system instance:
$ sudo systemd-nspawn -D
Hi,
Am 20.07.2014 11:28, schrieb Peter Palfrader:
On Mon, 07 Jul 2014, Peter Palfrader wrote:
} weasel@valiant:~$ cat /etc/crypttab
} sda3_crypt UUID=81402c7d-3819-4860-b71f-ff0f808f599e none luks
} sda6_crypt UUID=4385f6be-9584-4fd9-a3b8-92a2826311a5 /etc/luks/sda6.key
luks
}
} aux1
Am 20.07.2014 15:42, schrieb Peter Palfrader:
On Sun, 20 Jul 2014, Michael Biebl wrote:
Hi,
Am 20.07.2014 11:28, schrieb Peter Palfrader:
On Mon, 07 Jul 2014, Peter Palfrader wrote:
} weasel@valiant:~$ cat /etc/crypttab
} sda3_crypt UUID=81402c7d-3819-4860-b71f-ff0f808f599e none luks
reassign 755436 aptitude
thanks
Am 20.07.2014 20:52, schrieb Stefan:
Package: libpam-systemd
Version: 204-8
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Trying to hit 'B'
Am 21.07.2014 09:57, schrieb Erwan David:
It is
then uimpossible to check that the boot works correctly.
It's certainly possible. Contrary to sysvinit, you can query the
complete state of the system at any time.
Simply run systemctl (or systemctl status) to get an overview of the
running
reassign 755516 plymouth
forcmerge 755194 755516
affects 755194 systemd
thanks
Am 21.07.2014 17:54, schrieb Martin-Éric Racine:
Package: systemd
Version: 208-6
Severity: normal
Syslog reports that:
[13140.364123] systemd[1]: Cannot add dependency job for unit
reassign 755512 systemd
forcemerge 755373 755512
thanks
Hi,
Am 21.07.2014 15:45, schrieb John Wong:
Package: systemd-sysv
Version: 208-6
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
Recently(over 2 weeks), I
Am 21.07.2014 14:39, schrieb Martin Steigerwald:
Package: systemd
Version: 208-1
Severity: important
Dear Maintainer,
after booting with systemd 208-1 the more important one of two NFS exports
is not mounted. /home (on NetApp FAS) is not mounted, while /somenfs
(on Linux NFS server) is:
Am 21.07.2014 14:39, schrieb Martin Steigerwald:
Package: systemd
Version: 208-1
Severity: important
Dear Maintainer,
after booting with systemd 208-1 the more important one of two NFS exports
is not mounted. /home (on NetApp FAS) is not mounted, while /somenfs
(on Linux NFS server) is:
Hi,
Am 24.07.2014 14:10, schrieb Benoit Friry:
Package: libpam-systemd
Version: 208-6
Severity: minor
Dear Maintainer,
After upgrade, I get lots of error in auth.log:
Jul 24 11:45:17 host sshd[23128]: pam_systemd(sshd:session): Failed to create
session: Invalid argument
Is
Am 24.07.2014 22:59, schrieb Benoit Friry:
After a reboot your problem will be gone.
No more error in log after reboot. Bug report can be closed.
Is there any other way to fix that without rebooting?
Unfortunately not. The new logind requires systemd as PID 1, which
means you need to
Am 25.07.2014 04:06, schrieb Marco d'Itri:
On Jul 24, Michal Suchanek michal.sucha...@ruk.cuni.cz wrote:
Apparently there are two versions of libudev linked in.
Upgrading libudev-dev so it references libudev.so.1 resolves the
problem.
I am not sure if linking symbols from two different
Am 26.07.2014 18:52, schrieb Martin Pitt:
Hello Michael,
Michael Biebl [2014-07-26 13:25 +0200]:
Hm, that seems to be a recent change in the linux kernel headers afaics.
It seems to be an incompatibility between recent glibc and libattr.
My guess was linux-libc-dev, since
Am 26.07.2014 20:10, schrieb Brian Julin:
I just went through this ordeal myself. Here are some observations.
1) The problem causing the OP to enter emergency mode in the first place
is likely because systemd does not seem to (with current packages) want
to do anything with swap or
Am 26.07.2014 21:12, schrieb Michael Biebl:
I completely forgot that we defer the actual start/stop/restart to
invoke-rc.d in most cases (i.e. if there is a matching .service and SysV
init script).
So, yeah, we'd actually need to special case .socket units here or we
change invoke-rc.d
Am 26.07.2014 23:59, schrieb Henrique de Moraes Holschuh:
On Sat, 26 Jul 2014, Michael Biebl wrote:
If invoke-rc.d by default stops both .socket and .service, the package
maintainer no longer has this option.
This is incorrect.
You can extend invoke-rc.d stop with a --option that quiesces
Am 22.07.2014 23:54, schrieb Julian Gilbey:
For me, this is a killer, as I still do not know how to solve the
problem I asked a while back on debian-user
(https://lists.debian.org/debian-user/2014/04/msg01286.html): in
summary, I need to unlock an encrypted filesystem during boot time by
Control: severity -1 normal
Control: reassign -1 wpasupplicant
Control: retitle -1 if-up.d hook fails with exit code 1
Am 27.07.2014 22:52, schrieb Sergio Mendoza:
Package: systemd-sysv
Version: 208-6
Severity: grave
Justification: renders package unusable
Since gnome and its dependent
Am 27.07.2014 23:55, schrieb Nikolaus Rath:
Package: systemd
Version: 208-6
Severity: normal
I am using systemd as pid 1. After a dist-upgrade on July 21st for testing,
I was unable to resume from hibernation anymore. The resume image would
be loaded, but then the system would reboot.
Am 26.07.2014 15:21, schrieb Gerrit Pape:
On Tue, Jul 22, 2014 at 03:03:02PM +0200, Michael Biebl wrote:
Am 22.07.2014 14:34, schrieb Gerrit Pape:
On Fri, Jul 18, 2014 at 12:03:41PM +, Gerrit Pape wrote:
I'm really not keen to add a dependency to daemontools-run, esp. not to
the runit
Am 28.07.2014 15:34, schrieb Michael Biebl:
Am 28.07.2014 15:00, schrieb Elimar Riesebieter:
Users don't have any chance to choose an initsystem other than
systemd when they want to use packages which are rdepend on
libpam-systemd. And these are many many. I don't see any progress to
find
Control: -1 important
Am 28.07.2014 15:53, schrieb Marc Glisse:
makes unrelated software on the system (or the whole system) break,
pretty much what I am seeing here. The recent upgrades pulled in systemd
(it is very hard to avoid currently) and made the system unbootable. The
workaround I
Hi,
Am 28.07.2014 01:54, schrieb Christian Hofstaedtler:
* Michael Biebl bi...@debian.org [140727 23:09]:
Am 22.07.2014 23:54, schrieb Julian Gilbey:
For me, this is a killer, as I still do not know how to solve the
problem I asked a while back on debian-user
(https://lists.debian.org/debian
Am 28.07.2014 16:53, schrieb Michael Biebl:
--8---
[Unit]
Description=Unlock EncFS
DefaultDependencies=no
After=local-fs.target
Before=display-manager.service getty@tty1.service
[Service]
Type=oneshot
RemainAfterExit=true
Environment=RootDir=/home/.encfs/crypt
Environment
Am 28.07.2014 17:23, schrieb Marc Glisse:
The output of systemctl list-jobs and journalctl -alb would be
helpful for a start.
The first only listed:
497 systemd-logind.service start running
The second is:
http://geometrica.saclay.inria.fr/team/Marc.Glisse/tmp/systemd
It seems that the
Am 28.07.2014 18:06, schrieb Corcodel Marian:
Package: systemd
Version: 208-6
Severity: normal
Hi
When run systemctl stop boot.mount fail to execute.
What is the exact error message you get on
systemctl stop boot.mount
Do you get any error message in the journal?
--
Why is it that all
reassign 756760 systemd-shim
thanks
Am 01.08.2014 um 14:50 schrieb Martin Steigerwald:
Package: systemd
Version: 208-1
Severity: important
Dear Maintainer,
I tried to hibernate but got same annoying authorization requester
*after* KDE locked its desktop as described in bug #747939.
Am 05.08.2014 10:32, schrieb shirish शिरीष:
Package: systemd
Version: 208-6
Severity: normal
Dear Maintainer,
When I give the command for shutting off the system :-
#halt
halt does not switch off the system, this is expected.
OR
#poweroff
poweroff does switch off the system.
Am 22.07.2014 11:11, schrieb Samuel Thibault:
Package: systemd-sysv
Version: 208-6
Severity: important
Hello,
First boot with systemd-sysv failed. The base reason is that I had
a bogus line in fstab which sysvinit was fine with, but systemd is
not (FTR, /var/tmp/d-i/debian.iso
Am 06.08.2014 16:37, schrieb Mike Gabriel:
Hi Brian,
On Mi 06 Aug 2014 00:28:40 CEST, brian m. carlson wrote:
On Tue, Aug 05, 2014 at 03:14:34PM +, Mike Gabriel wrote:
Is is possible that your machine has systemd _and_ consolekit installed?
That would explain the
Am 07.08.2014 01:16, schrieb Michael Biebl:
Am 06.08.2014 16:37, schrieb Mike Gabriel:
Yes. It's a dependency of mate-power-manager.
can you rebuild mate-power-manager from sources and test this:
1) Downgrade consolekit from Depends: to Recommends: in debian/control
2) Build
1 - 100 of 2086 matches
Mail list logo
