> Was there anything else related to systemd done to this system?
No, I didn't even properly realize systemd was pulled in as a
dependency...
In any case I fixed the problem here and you can probably close this if
it's not reproducible
--
You received this bug notification because you are
Well, I was upgrading from an older sssd-common package...
Maybe the problem was with on of the previous sssd-common versions.
IIRC it first occurred when I tried to upgrade from 1.11.8-0ubuntu0.5 to
1.11.8-0ubuntu0.6
In any case it was definitely trying to stop the service via systemd
which
updated the description with more details
** Description changed:
- ubuntu-core-launcher and hence snapd and hence systemd is installed from
- the official repo...
+ If you have the `systemd` package installed, the upgrade of sssd-common
+ fails because it thinks systemd is used and the
Public bug reported:
ubuntu-core-launcher and hence snapd and hence systemd is installed from
the official repo...
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: sssd-common 1.11.8-0ubuntu0.6
ProcVersionSignature: Ubuntu 4.4.0-79.100~14.04.1-generic 4.4.67
Uname: Linux
So will this actually be released for yakkety and zesty as well??
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652945
Title:
dpkg-parsechangelog intolerant of unfinalised changelogs
To manage
Public bug reported:
Building some packages for yakkety and zesty fails with:
Can't call method "epoch" on an undefined value at
/usr/share/perl5/Dpkg/Changelog.pm line 498.
dpkg-buildpackage: error: dpkg-genchanges gave error exit status 25
Due to this bug [1], some packages don't build on
So can someone with appropriate rights please propose an SRU for xenial?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573234
Title:
unable to link: cannot find libvtkproj4
To manage
Public bug reported:
On 16.04 lablgtk2 (version 2.18.3+dfsg-1build1) reports it's version as 2.16
instead of the correct 2.18:
$ ocamlfind query -format '%v' lablgtk2
2.16.0
This prevents correct builds of software that has to distinguish between
some API changes between 2.16 and 2.18
See also
Public bug reported:
When using an additional external monitor, the reveal of the global
application menu on the laptop (left) monitor only works for the first
menu entry if the two screens are bottom aligned.
The menu only appears when mousing over the first menu entry or the empty area
of the
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1042898
Title:
reveal of global menu not working on primary monitor in dual setup
To manage notifications about this bug go to:
** Description changed:
When using an additional external monitor, the reveal of the global
application menu on the laptop (left) monitor only works for the first
- menu entry.
+ menu entry if the two screens are bottom aligned.
The menu only appears when mousing over the first menu
** Tags added: oneiric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/705267
Title:
Applications that remain running in notification area get relaunched
To manage notifications about this bug go
Still the case in 11.10 with sni-qt and sni-qt:i386 installed. The skype
indicator does not change this, as soon as skype is hidden to the tray
the dash doesn't pick it up anymore.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I still have the problem that unity doesn't recognize xchat as already running
with 11.10 if xchat was hidden/minimized to the tray.
With xchat-indicator installed it at least recognized it as still running there
and correctly alerts in case of new messages.
Seems to be related to bug #705267 as
14 matches
Mail list logo
