As xenial-release and yakkety-release have the same ido version, I
forward-copied the xenial SRU to yakkety. This needs to be verified too,
so that both can eventually be released. Otherwise x would have a higher
version than y.
** Also affects: ido (Ubuntu Yakkety)
Importance: Undecided
The version of indicator-power in the proposed pocket of Xenial that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
** Changed in: indicator-power (Ubuntu Xenial)
Status: Fix
The version of indicator-power in the proposed pocket of Xenial that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
--
You received this bug notification because you are a member of DX
Hello errors.ubuntu.com, or anyone else affected,
Accepted ido into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/ido/13.10.0+16.04.20161028-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
Iain Lane [2016-10-01 19:26 -]:
> Hmm. Maybe this is saying that we should bind ubuntu-session.target to
> something else - like unity7? You can't log in again with an active
> unity7, so in theory (if stop is propagated down to graphical-session
> and graphical-session-pre) there wouldn't be
> If you ever end up stopping gnome-keyring from within a new session
then its ExecStopPost kills the upstart session of this new one that we
are starting up, *not* the previous one that it was started up under.
I assume you meant to say "gnome-session.service" here, not keyring (as
its
> To fix that, something like comment #3 is needed. Such as looping over
all 'active' units that are PartOf graphical-session.target and stopping
them all.
I think we would only need to "systemctl stop graphical-session.target"
for this, otherwise a unit forgets the PartOf= and that loop would
** Changed in: gnome-session (Ubuntu)
Status: In Progress => Won't Fix
** Changed in: gnome-session (Ubuntu)
Status: Won't Fix => Fix Committed
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity-gtk-module in Ubuntu.
** Changed in: upstart (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity-gtk-module in Ubuntu.
https://bugs.launchpad.net/bugs/1618886
Title:
unity-gtk-module.service is racy;
start (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity-gtk-module in Ubuntu.
https://bugs.launchpad.net/bugs/1618886
Title:
unity-gtk-module.service is racy; session services don't s
> sudo killall -9 Xorg
This causes some havoc -- as this does not actually stop anything in the
session, random services just start failing the next time they try to
talk to X. Due to our Restart=on-failure, these units then try to
restart a few times until they hit the restart limit and go to
Argh!
if [ "$(systemctl --user show -p PartOf --value)" = "graphical-
session.target" ]; then
The systemctl --user call is missing a $unit argument, so this loop
never actually worked.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to
** Changed in: gnome-session (Ubuntu)
Status: Triaged => In Progress
** Changed in: gnome-session (Ubuntu)
Milestone: None => ubuntu-16.09
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity-gtk-module in Ubuntu.
** Changed in: unity-gtk-module (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity-gtk-module in Ubuntu.
https://bugs.launchpad.net/bugs/1618886
Title:
unity-gtk-module.service is
uot; issue.
** Also affects: gnome-session (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-session (Ubuntu)
Status: New => Triaged
** Changed in: gnome-session (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Summary changed:
- unity-gtk-module
** Changed in: unity-gtk-module (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity-gtk-module in Ubuntu.
https://bugs.launchpad.net/bugs/1618886
Title:
unity-gtk-module.service is racy
Without the PPA this is because upstart runs unity and there is no
synchronization between unity-gtk-module.service and unity7.conf.
With the PPA (i. e. converted services) this happens because unity-gtk-
module.service stays running after killing X (systemctl restart lightdm)
if there is another
: High
Assignee: Martin Pitt (pitti)
Status: Triaged
** Changed in: unity-gtk-module (Ubuntu)
Status: New => Triaged
** Changed in: unity-gtk-module (Ubuntu)
Importance: Undecided => Medium
** Changed in: unity-gtk-module (Ubuntu)
Assignee: (unassigned) => Ma
Hello Omer, or anyone else affected,
Accepted indicator-power into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/indicator-
power/12.10.6+16.04.20160708-0ubuntu1 in a few hours, and then in the
-proposed repository.
Please help us by testing
Hello Cerberus, or anyone else affected,
Accepted gnome-menus into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
menus/3.13.3-6ubuntu3.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
The verification of the Stable Release Update for accountsservice has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
Hello Huck-bernhard, or anyone else affected,
Accepted unity-control-center into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unity-control-center/15.04.0+16.04.20160413-0ubuntu2 in a few hours,
and then in the -proposed repository.
Please
Hello Sebastien, or anyone else affected,
Accepted accountsservice into xenial-proposed. The package will build
now and be available at
https://launchpad.net/ubuntu/+source/accountsservice/0.6.40-2ubuntu11.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
The verification of the Stable Release Update for accountsservice has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
The version of appmenu-gtk in the proposed pocket of Precise that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
** Changed in: appmenu-gtk (Ubuntu Precise)
Status: In Progress =>
The version of appmenu-gtk in the proposed pocket of Precise that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
--
You received this bug notification because you are a member of DX
I removed indicator-appmenu from precise-proposed, I has been sitting
there for four years.
** Package changed: update-manager (Ubuntu) => indicator-appmenu
(Ubuntu)
** Changed in: indicator-appmenu (Ubuntu Precise)
Status: In Progress => Won't Fix
--
You received this bug notification
Hello brainsail, or anyone else affected,
Accepted accountsservice into xenial-proposed. The package will build
now and be available at
https://launchpad.net/ubuntu/+source/accountsservice/0.6.40-2ubuntu11 in
a few hours, and then in the -proposed repository.
Please help us by testing this new
Hello danimo, or anyone else affected,
Accepted owncloud-client into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/owncloud-
client/2.1.1+dfsg-1ubuntu1.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this
For the record, our SABDFL requested this change, so this FFE/UIFE will
go in by way of the ultimate power.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to hud in Ubuntu.
https://bugs.launchpad.net/bugs/1551986
Title:
[FFe][UIFe] HUD
> @pitti, sorry for doing this without consulting you
Please don't apologize for doing great work :-) I haven't really worked
on pygobject for two years now. Thanks for fixing this!
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to libunity in
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)
*
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
It's very unlikely that this is related to systemd, as it's got nothing
at all to do with handling the user session and screen locking. This is
handled by unity. The most probable reason is that unity crashes when
it's trying to lock the screen. When this happens, do you get a crash
notification?
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
** 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
** Package changed: systemd (Ubuntu) = systemd-shim (Ubuntu)
--
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/1426362
Title:
logind session files fill up /run space
Status in
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
**
** 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
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
** 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
** Package changed: keystone (Ubuntu) = systemd-shim (Ubuntu)
--
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/1393474
Title:
su call in postinst fails with Killed when not running
: New = Fix Committed
** Changed in: autopkgtest (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
--
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/1393474
Title:
su call
** Tags removed: systemd-boot
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/922129
Title:
notify-osd crashed with signal 5 in _XReply()
Status in
** 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
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.
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
This is not Debian bug #756076. That is about cleaning up closing
loginctl sessions after logging out (which I implemented in upstream git
now). But this bug is about actually killing the leftover background
processes in the cgroup and the logind session if KillUserProcesses=yes
is set in
powerd and system-settings landed in -proposed now, too.
** Changed in: powerd (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-power in Ubuntu.
** Summary changed:
- [FFe] upower 0.99.1 transition
+ upower 0.99.1 transition
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-power in Ubuntu.
https://bugs.launchpad.net/bugs/1330037
Title:
upower 0.99.1 transition
Status in
** Changed in: ubuntu-system-settings (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-power in Ubuntu.
https://bugs.launchpad.net/bugs/1330037
Title:
upower 0.99.1 transition
Closing the tasks which are done in vivid now, but whose changelogs
don't have a bug ref.
** Changed in: upower (Ubuntu)
Status: Fix Committed = Fix Released
** Changed in: gnome-applets (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because
Same with sugar-0.96.
** Changed in: sugar-0.96 (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-power in Ubuntu.
https://bugs.launchpad.net/bugs/1330037
Title:
upower 0.99.1 transition
razorqt also has a SystemdProvider class which can do the suspend/resume
things. It's also not that important, see Debian bug #752442. So we can
ignore this for this transition.
** Changed in: razorqt (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a
gnome-session moved to systemd in https://code.launchpad.net/~darkxst
/gnome-session/3.14/+merge/240212, thus dropping the upower dep.
** Changed in: gnome-session (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of DX
Packages,
** Changed in: gnome-session (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-power in Ubuntu.
https://bugs.launchpad.net/bugs/1330037
Title:
[FFe] upower 0.99.1 transition
/+merge/230988
Everything else should be ready in -proposed now.
** Changed in: gnome-settings-daemon (Ubuntu)
Status: In Progress = Fix Committed
** Changed in: gnome-settings-daemon (Ubuntu)
Assignee: Tim (darkxst) = Martin Pitt (pitti)
--
You received this bug notification
I uploaded a fakesync for gnome-applets, reverting build-dep back to
0.99.
** Changed in: gnome-applets (Ubuntu)
Status: In Progress = Fix Committed
** Changed in: gnome-applets (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
--
You received this bug notification because you
upower 0.99 synced from Debian.
** Changed in: upower (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-power in Ubuntu.
https://bugs.launchpad.net/bugs/1330037
Title:
[FFe]
gnome-control-center changes committed to packaging bzr and uploaded.
** Changed in: gnome-control-center (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-power in Ubuntu.
** Changed in: cinnamon-control-center (Ubuntu)
Status: New = Fix Committed
** Changed in: cinnamon-session (Ubuntu)
Status: New = Fix Committed
** Changed in: cinnamon-settings-daemon (Ubuntu)
Status: New = Fix Committed
--
You received this bug notification because you
** Changed in: xfce4-power-manager (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-power in Ubuntu.
https://bugs.launchpad.net/bugs/1330037
Title:
[FFe] upower 0.99.1
** Changed in: xfce4-settings (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-power in Ubuntu.
https://bugs.launchpad.net/bugs/1330037
Title:
[FFe] upower 0.99.1 transition
** Changed in: mutter (Ubuntu)
Status: In Progress = Fix Committed
** Also affects: wmbattery (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-power in Ubuntu.
** Changed in: wmbattery (Ubuntu)
Status: New = Fix Committed
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-power in Ubuntu.
https://bugs.launchpad.net/bugs/1330037
Title:
[FFe] upower 0.99.1 transition
Status in
** Changed in: gnome-shell-pomodoro (Ubuntu)
Status: New = Fix Committed
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-power in Ubuntu.
https://bugs.launchpad.net/bugs/1330037
Title:
[FFe] upower 0.99.1 transition
** Changed in: gnome-shell (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-power in Ubuntu.
https://bugs.launchpad.net/bugs/1330037
Title:
[FFe] upower 0.99.1 transition
Status
The mate packages still need to get rebuilt against the new libupower-
glib3. I'll upload those.
** Changed in: mate-power-manager (Ubuntu)
Status: Fix Released = In Progress
** Changed in: mate-applets (Ubuntu)
Status: Fix Released = In Progress
--
You received this bug
** Changed in: mate-applets (Ubuntu)
Status: In Progress = Fix Committed
** Changed in: mate-power-manager (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-power in Ubuntu.
I ported Tim's patches to current unity-{settings-daemon,control-
center}, comitted to bzr, and uploaded.
** Changed in: unity-control-center (Ubuntu)
Status: New = Fix Committed
** Changed in: unity-settings-daemon (Ubuntu)
Status: New = Fix Committed
--
You received this bug
Confirmed. I did a fresh utopic daily install yesterday, and setting
switch off screen to 1 min and lock screen to 30 s doesn't do
anything at least for my account. This is with my ancient config, but I
also confirmed this with a fresh user account.
** Changed in: unity (Ubuntu)
Importance:
** Changed in: unity
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1351306
Title:
Cannot uninstall upstart
)
Assignee: (unassigned) = Martin Pitt (pitti)
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1365401
Title:
indicator-sound.mo not in language
*** This bug is a duplicate of bug 1365336 ***
https://bugs.launchpad.net/bugs/1365336
Wile systemd-shim 7-1 → 7-2 is essentially a no-op (i. e. harmless), you
really shouldn't have gotten that version automatically yet -- it's
still in proposed. Pretty pretty please do *not* run
** Also affects: unity (Ubuntu)
Importance: Undecided
Status: New
** Also affects: unity-lens-applications (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Sorry, this doesn't actually affect unity-lens-applications, this is
just a transitive dep.
** Changed in: unity-lens-applications (Ubuntu)
Status: New = Invalid
** Changed in: unity (Ubuntu)
Status: New = In Progress
** Also affects: pay-service (Ubuntu)
Importance: Undecided
** Changed in: pay-service (Ubuntu)
Status: New = In Progress
** Also affects: hockeypuck (Ubuntu)
Importance: Undecided
Status: New
** Changed in: hockeypuck (Ubuntu)
Status: New = Fix Committed
** Changed in: hockeypuck (Ubuntu)
Assignee: (unassigned) = Martin
** Also affects: dovecot (Ubuntu)
Importance: Undecided
Status: New
** Changed in: dovecot (Ubuntu)
Status: New = In Progress
** Changed in: dovecot (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
--
You received this bug notification because you are a member of DX
** Also affects: ubuntu-app-launch (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1351306
Title:
** Changed in: ubuntu-app-launch (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1351306
Title:
Cannot uninstall
Debian exp now has 214, so to build this more conveniently I added a
conditional upstream:
https://github.com/desrt/systemd-shim/commit/4c6af921
With that shim just needs to be rebuilt.
** Changed in: systemd-shim (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug
** Changed in: systemd-shim (Ubuntu)
Status: New = Invalid
** Changed in: ubuntu-app-launch
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
** 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
*** This bug is a duplicate of bug 1252121 ***
https://bugs.launchpad.net/bugs/1252121
** This bug has been marked a duplicate of bug 1252121
missing PrepareForSleep signal after resuming, causing networking to stay
disabled
--
You received this bug notification because you are a member
** Package changed: systemd-shim (Ubuntu) = network-manager (Ubuntu)
--
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/1296372
Title:
network disabled 14.04 trusty
Status in
** Package changed: systemd-shim (Ubuntu) = poppler (Ubuntu)
--
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/1254851
Title:
qpdfview renders black pages after poppler update
Status
Fixed in https://github.com/desrt/systemd-shim/commit/21210f7fd
Thanks for the report!
** Changed in: systemd-shim (Ubuntu)
Status: New = Triaged
** Changed in: systemd-shim (Ubuntu)
Importance: Undecided = Low
** Changed in: systemd-shim (Ubuntu)
Status: Triaged = Fix
This was fixed a while ago already:
Changes in version 5
=
- write a sendsigs.omit.d file to prevent upstart from killing us
during shutdown. This should fix the suspend-when-shutting-down
issue once and for all.
** Changed in: systemd-shim (Ubuntu)
Status:
Please attach a screenshot with the crash, it should show a traceback or
other error. Thanks!
** Package changed: systemd-shim (Ubuntu) = linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of DX
** Information type changed from Private to Public
--
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/1234482
Title:
systemd-shim crashed with SIGSEGV in power_unit_start()
Status in
I'm afraid this stack trace does not make any sense. It crashes in
if (pu-action == POWER_SUSPEND)
but the pu pointer is clearly initialized (as seen in the Stacktrace),
and the very same pu-action is being used before already (and not
modified in between). So I'm afraid with the current
I committed https://github.com/desrt/systemd-shim/commit/b4f1dc0ca to
advertise both APIs.
** Changed in: systemd-shim (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
Meh, that doesn't actually work, logind complains about a signature
mismatch. So indeed this will have to wait until we update systemd.
** Changed in: systemd-shim (Ubuntu)
Status: Fix Committed = Triaged
--
You received this bug notification because you are a member of DX
Packages,
I don't see this message; what do you do to trigger it? Anyway, I'll
just test this with d-feet.
--
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/1348039
Title:
shim does not implement
Your dmesg talks about plymouth-upstart-bridge, which only exists under
upstart. So I'm still convinced you were running upstart here, with
systemd-shim.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to systemd-shim in Ubuntu.
Missing API in systemd-shim.
** Package changed: systemd (Ubuntu) = systemd-shim (Ubuntu)
** Changed in: systemd-shim (Ubuntu)
Status: Confirmed = Triaged
** Summary changed:
- systemd failure messages pop up on console as well as seen in dmesg
+ Errors on cleaning up cgroups
--
You
Bug 1348039 already exists about the missing Subscribe(), retitling for
the other issues.
** Bug watch added: Debian Bug tracker #756076
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756076
** Also affects: systemd-shim (Debian) via
** Changed in: systemd (Ubuntu)
Status: Triaged = Invalid
** Changed in: systemd (Ubuntu Trusty)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-session in Ubuntu.
Matching subscriptions:
This package is handled by the automatic CI train machinery, so I can't
just sponsor it.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to overlay-scrollbar in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1262022
I suppose you were not actually running systemd for this, but upstart (I
see this here as well). systemd-shim apparently does not implement that
stub. Reassigning and dropping systemd-boot tag.
** Description changed:
Get that error logged at the end of the dmesg file. That error seems to
-
1 - 100 of 152 matches
Mail list logo
