** Changed in: systemd-shim (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1359439
Title:
[7.287663] systemd-logind[1057]: Failed to st
I'm on ubuntu 16.04.1, doesn't work for me
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1359439
Title:
[7.287663] systemd-logind[1057]: Failed to start unit
user@126.service:
solution from geek.de.nz worked perfectly for me, i'm on ubuntu 16.04
upgraded from 14.04
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1359439
Title:
[7.287663] systemd-logind[1
sudo apt-get install systemd-sysv
seems to be an easy fix/work-around for now. It will remove the package
that causes this error.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1359439
I am getting same error like @pavel-petrovic in Ubuntu 15.10. I am not
able to get into the desktop. During boot up I am stuck in a console
screen where these error message comes in. What's the solution here?
--
You received this bug notification because you are a member of DX
Packages, which is
I am getting this in 16.04 development version.
[ 87.068463] systemd-logind[2155]: Failed to start user service:
Unknown unit: user@1000.service
(could be because this is a fresh upgrade from earlier version, but yes,
it is still here)
** Description changed:
- ATTENTION: This bug is fully u
Same error in Ubuntu 15.04
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1359439
Title:
[7.287663] systemd-logind[1057]: Failed to start unit
user@126.service: Unknown unit: us
This bug only affected utopic, which is EOL now, so closing.
** Changed in: systemd (Ubuntu Utopic)
Status: Triaged => Won't Fix
** Changed in: null-and-void
Status: New => Invalid
** Changed in: systemd-shim (Ubuntu)
Assignee: Martin Pitt (pitti) => (unassigned)
** Changed i
New install of 14.10
Worked fine on Nvidia GTX 760 with nomodeset in grub
Installed latest 352 x64 Nvidia driver and rebooted
Lightdm did not start and "systemd-logind[969]: Failed to start unit
user@1000.service: Unknown unit: user@1000.service" was displayed twice.
After starting lightdm, it cyc
is there a ppa with the right package systemd-shim , or systemd?? I
upgraded from Trusty to Utopic and I didn't understand how to resolve
this bug.
I have read this page, but I'm sorry I'm unable to dowload source, compile with
a patch, etc. It would help to have a binary package.
Thanks in adva
The "vivid" Launchpad project has nothing to do with Ubuntu vivid, for
the record. This bug doesn't affect Ubuntu 15.04 as that uses systemd
for booting now, and systemd-shim isn't necessary any more (and inert if
installed).
** Project changed: vivid => null-and-void
--
You received this bug no
I also was hit by this bug when updating my utopic (14.10) amd64 system
to vivid (15.04). Deinstalling systemd-shim also worked for me.
** Also affects: vivid
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of DX
Packages, which is subsc
Hi Martin, and thanks for answering.
I've tried again skipping running tests, but unfortunately had another error:
...
./.libs/libsystemd-core.a(libsystemd_core_la-job.o):(.debug_info+0x198e):
undefined reference to `x21'
collect2: error: ld returned 1 exit status
Makefile:8486: set di istruzion
Giuseppe, you can run "env DEB_BUILD_OPTIONS=nocheck debuild ..." (or
sbuild, etc.) to disable running the tests. (The test works fine in a
clean schroot, not sure what's wrong in your environment)
--
You received this bug notification because you are a member of DX
Packages, which is subscribed
Hello everybody.
I've tried to recompile systemd applying Nathan Rennie-Waldock's patch, but I
get this error:
...
/lib/systemd/system/rsyslog.service = enabled
systemd not booted skipping 'test_install_printf()'
test-utf8.log
goo goo goo
��
debian/rules:233: recipe for target 'ove
** Changed in: systemd-shim (Ubuntu)
Importance: High => Medium
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1359439
Title:
[7.287663] systemd-logind[1057]: Failed to start u
Hi Marko,
I meant tty-1, when I said "From my terminal".
But you are right, my retry was not after the first login after a boot. I am
not wuth the computer now, I will try again. If the Problem still comes (ie.
these Problems are not related), then I will create a report for gnome.
--
You rece
Hi Romain,
Thanks for interesting observation and analysis, but I believe these two
problems are not related. As a test, try restarting the computer and
then logging in via one of the tty2-tty6 (Ctrl-Alt-F2 - Ctrl-Alt-F6).
I'm getting that line with user@1000.service only on first tty login
after
I might come after the war has ended but after a lot of investigation
about my problem, I found something which might be interesting for you.
First of all:
Ubuntu gnome 14.10 (clean install)
What was my problem:
Since today (1st of March : date is important here) GDM did not show up (black
scree
I also had this problem and uninstalling fglrx drivers fixed this issue
(display driver for AMD graphics cards)
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1359439
Title:
[7.28
That patch looks okay for an utopic SRU. Thanks!
** Also affects: systemd (Ubuntu Utopic)
Importance: Undecided
Status: New
** Also affects: systemd-shim (Ubuntu Utopic)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Utopic)
Status: New => Triaged
**
The attachment "logind-check-booted-with-systemd.patch" seems to be a
patch. If it isn't, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are a member of the ~ubuntu-
reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad use
This is actually in systemd, not systemd-shim.
I patched systemd-shim to ignore unknown unit warning, so then I get a warning
from systemd-logind: systemd-logind[1414]: Failed to start user service:
Message did not receive a reply (timeout by message bus)
So it's being started by the login manage
** Changed in: systemd-shim (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1359439
Title:
[7.287663] systemd-logind[1057]: Failed to start u
** Changed in: systemd-shim (Ubuntu)
Status: Triaged => New
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1359439
Title:
[7.287663] systemd-logind[1057]: Failed to start u
** Changed in: systemd-shim (Ubuntu)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1359439
Title:
[7.287663] systemd-logind[1057]: Failed to
Sorry, network is up. By pattient :)
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1359439
Title:
[7.287663] systemd-logind[1057]: Failed to start unit
user@126.service: Unknow
i find this
https://github.com/desrt/systemd-shim/commit/729b958d9d97
may be it can help?\
my server network is down. i lose money(
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/135943
Mauricio Faria de Oliveira [2015-01-26 18:44 -]:
> Would you have any update on the process of resolving this (maybe someone/I
> can help?)
Sure, anyone who wants to look into this is welcome of course. It just
turned out to be much less trivial than I originally thought.
> or its severity (
@pitti
Hi, Martin.
Would you have any update on the process of resolving this (maybe someone/I can
help?), or its severity (what's the impact?)
Thanks a lot.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bu
I also got bitten by this bug after updating from ubuntu gnome 14.04 to
14.10. I tried switching to the systemd init system but this did not
work either so I reverted to upstart. However using the last kernel from
14.04 works and the system becomes usable again. I am only mentioning it
because it h
** Description changed:
+ ATTENTION: This bug is fully understood, there is *no need* to add even
+ more comments about "me too" here.
+
[7.287663] systemd-logind[1057]: Failed to start unit user@126.service:
Unknown unit: user@126.service
[7.287677] systemd-logind[1057]: Failed to s
Same issue for me on my Thinkpad W530. After the upgrade from 14.04 to
14.10 the PC was working with the Intel integrated graphics card but not
with the discrete Nvidia one (as usual after any kernel update...). When
reinstalling the Nvidia drivers the problem appeared. Subsequently, I
can login gr
Ohh...
Got workaround for this issue which was mentioned by Dexuan Cui (decui) for
GNOME.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1359439
Title:
[7.287663] systemd-logind
Is there any workaround for this issue?
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1359439
Title:
[7.287663] systemd-logind[1057]: Failed to start unit
user@126.service: Unk
Got this (for user@1000.service) on new installs of Lubuntu 14.10 64-bit
on one machine, and Ubuntu Server 14.10 32-bit on another. On the
Lubuntu machine, I had other issues with the on-motherboard video, so I
put another video board in it and re-installed Lubuntu, and this time
this bug did not
when will this be fixed???
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1359439
Title:
[7.287663] systemd-logind[1057]: Failed to start unit
user@126.service: Unknown unit: us
it occurs to me that simply switching to systemd-sysv then back again, without
the in between kde stuff, might have fixed it, but now i'll only know if i
reinstall it and try that lol.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-
this hit me on a new install of kubuntu 14.10 and its subsequent upgrades. i
used the workaround of installing systemd-sysv as others have done, but at that
point my graphical desktop (KDE) still would not start. i installed midnight
commander to go look at the Xsession errors in my home folde
I have the same problem as described initially (as the title of this bug
report) after a clean install of Ubuntu Server 14.10.
I used sudo -i t become the root and then ran the following command:
* apt-get install systemd-sysv
After rebooting and logging in, I did not have the message/problem a
Got it after installing openssh-server on UbuntuGnome utopic. No way to
boot in graphic mode till now.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1359439
Title:
[7.287663] sys
This bug hits me every time apt-get upgrades to a new release of the
kernel. The first reboot after upgrading would always fail. A 2nd reboot
would always work. This time, after upgrading to 3.16.0-28-generic
x86_64, subsequent reboots end up in the same state. If I open a
console, it says the netw
The problem is still here, fix hasn't landed on my machine yet ...
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1359439
Title:
[7.287663] systemd-logind[1057]: Failed to start u
Occured for me after a new install of Ubuntu Server 14.10 64-bit to an
ext4 FS on a RAID-1 on SSDs.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1359439
Title:
[7.287663] system
Affects me after nautilus reinstallation on Ubuntu Studio 14.10
systemd-logind 1116 failed to start unit user@1000.service
... unknown unit
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bug
I have the same problem.
After install ubuntu 14.10, on start i get a black screen;
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1359439
Title:
[7.287663] systemd-logind[1057]:
Affects Ubuntu Gnome after upgrading to 14.10.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1359439
Title:
[7.287663] systemd-logind[1057]: Failed to start unit
user@126.servi
Affects Kubuntu 14.10 too. Both updated and fresh.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1359439
Title:
[7.287663] systemd-logind[1057]: Failed to start unit
user@126.s
** Changed in: systemd-shim (Debian)
Status: Fix Committed => New
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1359439
Title:
[7.287663] systemd-logind[1057]: Failed to s
** Changed in: systemd-shim (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1359439
Title:
[7.287663] systemd-logind[1057]: Failed to star
Sorry, that fix was broken, I reverted it.
** Changed in: systemd-shim (Ubuntu)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1359439
Title
** Changed in: systemd-shim (Debian)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1359439
Title:
[7.287663] systemd-logind[1057]: Fail
https://github.com/desrt/systemd-shim/commit/729b958d9d97
** Changed in: systemd-shim (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs
** Changed in: systemd-shim (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: systemd-shim (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https:/
I think it's imortant to note that https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=756247#58 warns on the workaround on the grounds
that it involves the installation of sytemd. systemd is an alternative
to the current default upstart manager (see
https://wiki.ubuntu.com/systemd#systemd_-_An_al
After upgrade to Kubuntu 14.10:
[ 33.150498] systemd-logind[1197]: Failed to start unit user@109.service:
Unknown unit: user@109.service
[ 33.150504] systemd-logind[1197]: Failed to start user service: Unknown
unit: user@109.service
[ 33.155503] systemd-logind[1197]: New session c1 of user
I think https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756247#53 gave
the root cause and a workaround(see comment #58 at the same link...)
And,
root@decui-VM:~# systemctl
Failed to get D-Bus connection: No connection to service manager.
root@decui-VM:~#
--
You received this bug notification b
I'm suffering from the same issue with Ubuntu 14.10 guest on Hyper-V.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1359439
Title:
[7.287663] systemd-logind[1057]: Failed to star
Not sure if it's the underlying cause, but uninstalling my fglrx
packages, rebooting, then reinstalling them fixed the issue for me. (AMD
graphics driver for anyone not familiar)
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in
Same issue after upgrading from 14.04 to 14.10
[Wed Oct 29 07:41:17 2014] systemd-logind[2243]: Failed to start unit
user@109.service: Unknown unit: user@109.service
[Wed Oct 29 07:41:17 2014] systemd-logind[2243]: Failed to start user service:
Unknown unit: user@109.service
[Wed Oct 29 07:41:3
Same issue here. Just upgrade from Ubuntu GNOME 14.04 to Ubuntu GNOME
14.10
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1359439
Title:
[7.287663] systemd-logind[1057]: Failed t
Same issue here. Just updated from Ubuntu GNOME 14.04 to Ubuntu GNOME
14.10 and it doesn't log into gnome; just a black screen. When I switch
to the terminal it shows the following error:
systemd-logind[1148]: Failed to start unit user@1000.service: Unknown
unit: user@1000.service
--
You receiv
Same thing - installed Ubuntu 14.10 server (x86_64). Base Install + SSH
Server. On first boot, saw the errors just after logging in.
[ 93.892769] systemd-logind[1148]: Failed to start unit user@1000.service:
Unknown unit: user@1000.service
[ 93.892864] systemd-logind[1148]: failed to start user
Same here while running Ubuntu 14.10 server in a VirtualBox VM:
[ 62.851445] systemd-logind[1191]: Failed to start unit user@1000.service:
Unknown unit: user@1000.service
[ 62.854044] systemd-logind[1191]: failed to start user service: Unknown
unit: user@1000.service
This happens after a cl
Just updated to Ubuntu 14.10 and got a similar error:
[ 14.070781] systemd-logind[969]: Failed to start unit user@1000.service:
Unknown unit: user@1000.service
[ 14.070789] systemd-logind[969]: Failed to start user service: Unknown unit:
user@1000.service
--
You received this bug notificat
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1359439
** Tags added: iso-testing
--
You received this bug notification because you are a member of DX
Packages, which is s
** Package changed: systemd (Ubuntu) => systemd-shim (Ubuntu)
** Changed in: systemd-shim (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1359439
67 matches
Mail list logo
