Sorry, misunderstanding. I restored the previous tags, which seem to be
correct.
** Tags removed: verification-done
** Tags added: verification-done-trusty verification-needed-utopic
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm
Trusty SRU uploaded to SRU review queue.
** Changed in: systemd (Ubuntu Trusty)
Status: Fix Released => In Progress
** Changed in: systemd (Ubuntu Trusty)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
D
This also affects 14.04 LTS, although to a slightly lesser degree. In
14.04 we have a patch which does the modprobing for the "cpu" subsystem;
but reportedly this also affects drivers of other platforms, so let's
just backport that more generic upstream fix to cover all cases.
This can potentially
Thanks for confirming, so this is indeed the case: Your /home has a max
mount count of 35, but all other partitions have -1.
The config file is /etc/mke2fs.conf, as visible in the commit diff. It
was just typo'ed in the commit description.
This was a deliberate behaviour change, so I'm closing th
** Tags removed: verification-done-trusty verification-needed-utopic
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/678421
Title:
Error message for a f
Jamie, Daniel, did you ever get this after the fix in bug 1302264? This
is the typical symptom of logind not working, so if you have that
situation can you please check for a logind crash /var/crash?
** Changed in: compiz
Status: Confirmed => Invalid
** Changed in: unity
Status: Con
Reopening the kernel task here. We've carried the "temporary" udev rule
workaround for three releases now; it seems we all agree that it's wrong
(unconditional "unbreak my kernel rule") and makes things even worse
under memory pressure. Is there any better solution in sight? Thanks!
** Changed in:
According to the dpkg terminal log, the first package that failed was
cgmanager:
Setting up cgmanager (0.32-4ubuntu1.2) ...
Failed to get D-Bus connection: No connection to service manager.
Failed to get D-Bus connection: No connection to service manager.
invoke-rc.d: initscript cgmanager, action
I committed a patch to enable this with a configure option:
http://cgit.freedesktop.org/udisks/commit/?id=ae2a5ff1e
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1020759
Title:
/run/
Public bug reported:
Boot the current live system with systemd: Go to gfxboot, select F6,
press Esc twice, stay in gfxboot, and append init=/bin/systemd to the
command line. The live system will come up, but degraded:
● systemd-machine-id-commit.service - Commit a transient machine-id on disk
GI transitions can't be
decoupled from each other. pygtkcompat might help quite a bit, but
it's also just a crutch. I think it's preferable to just port programs
all the way to clean GTK3+GI.
Thanks,
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Develop
Oh, and pygtkcompat's purpose is to provide a pygtk like compat wrapper
for PyGI + GTK 3. :-) If you have to use GTK 2 still, use the
corresponding real pygtk. (But as I said, none of that is supported any
more).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bug
This is a case of "just don't do that", I'm afraid. GTK 2 is very old
and hasn't been maintained for like 5 years. At the time when gobject
introspection came up we already had GTK 3, so any introspection stuff
which happens to work with GTK 2 is pure luck.
** Information type changed from Private
Can you please check if "getfacl /dev/dri/card0" shows an ACL? (Just
copy&paste the whole output). I suppose at some point early in the boot
process you might even have a second one, but ubuntu-drivers-common's
selection between multiple graphics cards might just disable the second
one and thus thi
Setting up libpam-systemd:amd64 (204-5ubuntu20.9) ...
debconf: kann Oberfläche nicht initialisieren: Passthrough
debconf: (Can't locate Debconf/Element.pm in @INC (you may need to install the
Debconf::Element module) (@INC contains: /etc/perl /usr/local/lib/perl/5.18.2
/usr/local/share/perl/5.18.
While that's good for your system :-) I'm afraid I still understand what
went wrong initially in the first place. Calling the postinsts manually
should be very close to what actually happens during apt-get. It seems
reasonably clear that it was invoke-rc.d complaining about symlinks, so
it seems at
*** This bug is a duplicate of bug 1407757 ***
https://bugs.launchpad.net/bugs/1407757
** This bug is no longer a duplicate of bug 1394199
package libsystemd-login0:amd64 208-8ubuntu8.1 failed to install/upgrade:
package libsystemd-login0:amd64 is already installed and configured
** This b
No further response in two months, closing. I'll reopen once there is
some more information. Thanks!
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubunt
To confirm, do you actually need the "udevadm control --reload", or is
unplugging/replugging the keyboard enough after changing the keymaps?
** Summary changed:
- Custom keymap in hwdb not working
+ changing hwdb requires calling udevadm control --reload
** Changed in: udev (Ubuntu)
Importanc
Can you please give me the output of
sudo /lib/udev/cdrom_id --debug /dev/sr0
while the blank DVD is in the drive?
** Package changed: udev (Ubuntu) => systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a m
** Changed in: systemd (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1389201
Title:
Error calling EVIOCSKEYCODE on device node: Invalid argu
That looks very similar to bug 1404143 which got fixed in that version.
** Package changed: udev (Ubuntu) => systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscr
Fixed in https://launchpad.net/ubuntu/+source/systemd/218-3ubuntu1
** Changed in: systemd (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.
Ah, that's not an udevd bug then. Reassigning to XFCE.
** Package changed: systemd (Ubuntu) => xfce4-settings (Ubuntu)
** Changed in: xfce4-settings (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscrib
I'll fix this in udisks2's test suite instead.
** Package changed: systemd (Ubuntu) => udisks2 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1398859
Title:
unmounting NT
This caused bug 1404143 so I reverted this change.
** Changed in: systemd (Ubuntu)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1398859
Added an utopic task for SRUing this. Fix:
http://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?h=experimental&id=c8b099c992
** Also affects: systemd (Ubuntu Utopic)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Utopic)
Status: New => Triaged
--
Y
Regression introduced in
https://launchpad.net/ubuntu/+source/systemd/218-2ubuntu3 . Downgrading
the udev binary package to 218-2ubuntu2 fixes this.
** Package changed: cryptsetup (Ubuntu) => systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt
Fixed with https://launchpad.net/ubuntu/+source/systemd/218-2ubuntu3
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.
upower 0.99 (in Ubuntu 15.04) drops suspend handling, so this is
obsolete.
** Changed in: upower (Ubuntu)
Status: Confirmed => Invalid
** No longer affects: gnome-power-manager (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscr
** No longer affects: udisks2 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/1372978
Title:
SMART info window uncomfortable to use
To manage notifications abou
That's odd, now the error messages are gone entirely, even though the
only change is to add "set -x" to the resume premount script to show
debug output. I have a gut feeling that the update-initramfs -u (which
rebuilds the initramfs) somehow "fixed" this. Unfortunately we now lost
the evidence what
** Changed in: gvfs (Ubuntu)
Assignee: Martin Pitt (pitti) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/657609
Title:
music players w
Considering again, I'd rather provide the dependency in systemd itself
as a shim until we enable systemd-vgconsole properly (if ever). This
will at least not break dependencies of third-party packages.
** Package changed: plymouth (Ubuntu Vivid) => systemd (Ubuntu Vivid)
** Changed in: systemd (U
I got u-desktop-next to boot, and confirm that starting cgmanager fixes
app startup.
** Package changed: systemd (Ubuntu) => cgmanager (Ubuntu)
** Changed in: cgmanager (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bug
onfirmed => Triaged
** Changed in: console-setup (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1400393
Title:
wrong k
** Package changed: udev (Ubuntu) => systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1398025
Title:
Errors messages like "error: /dev/sdb: No medium found" on booti
This was discussed upstream a while ago:
http://lists.freedesktop.org/archives/systemd-
devel/2014-April/018378.html
A simple "debug" indeed enables debugging for everything. If you want
only systemd debugging, use systemd.log_level=debug, if you want only
kernel debugging, use "loglevel=debug". S
Ah, our rsyslog has a delta, so let's stick a matching tmpfiles.d/
snippet into rsyslog.
** Package changed: systemd (Ubuntu) => rsyslog (Ubuntu)
** Changed in: rsyslog (Ubuntu)
Status: New => In Progress
** Changed in: rsyslog (Ubuntu)
Assignee: (unassigned) => Mart
rsyslog's postinst seems fine. I have a gut feeling that this is due to
/usr/lib/tmpfiles.d/var.conf changing it back to 0755, the permissions
are wrong there.
** Package changed: rsyslog (Ubuntu) => systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Deskto
Done in https://launchpad.net/ubuntu/+source/xdiagnose/3.7.1
Thanks Didier!
** Package changed: systemd (Ubuntu) => xdiagnose (Ubuntu)
** Changed in: xdiagnose (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
For 15.04 we plan to change to systemd by default, at which point this
will work. For 14.10 making systemctl "invisible" is not an important
enough issue to warrant a stable release update; plus, some people
actually want to boot 14.10 with systemd for experimentation (note that
this is not officia
Pushed. Thanks!
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1401099
Title:
display-manager autopkgtests for s
ged in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Summary changed:
- [regression] unmounting NTFS causes mount.ntfs process to get stuck in
eternal kernel deep sleep
+ [udev regression] unmounting NTFS causes mount.ntfs process to get stuck in
eternal kernel deep sleep
*
This is all UI, not timedatectl. timedated does nothing which is related
to this, as ubuntu touch uses ntpdate (which isn't really configurable,
it always runs in the DHCP hook). Please also see bug 1390120 which is
the inverse of this.
** Package changed: systemd (Ubuntu) => ubuntu-system-setting
What kind of systemd interface is system-settings calling to
enable/disable automatic time? At the moment we install ntpdate, which
hooks itself into /etc/dhcp/dhclient-exit-hooks.d which isn't
configurable. timedatectl's set-ntp command is for a local NTP server
like ntpd or chronyd, but we don't
** Package changed: systemd (Ubuntu) => dpkg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1396708
Title:
package libudev1:i386 204-5ubuntu20.9 failed to install/upgrade:
Should have looked at the current dmesg output earlier:
[ 1197.540523] traps: dpkg-divert[6140] general protection ip:8050cc3
sp:bfdcf25c error:42a in dpkg-divert[8048000+1e000]
so dpkg itself seems to crash here :-( reassigning.
** Summary changed:
- package udev 204-5ubuntu20.7 failed to inst
** Package changed: systemd (Ubuntu) => debconf (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1396968
Title:
package libpam-systemd:amd64 204-5ubuntu20.8 failed to
inst
** Package changed: systemd (Ubuntu) => plymouth (Ubuntu)
** Changed in: plymouth (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1392970
Title
We ship /lib/firmware/iwlwifi-6000-4.ucode in linux-firmware, which is
also what the module advertises:
$ modinfo iwlwifi|grep 6000
firmware: iwlwifi-6000g2b-6.ucode
firmware: iwlwifi-6000g2a-5.ucode
firmware: iwlwifi-6000-4.ucode
This is what udev's userspace helper is looking
** Bug watch added: Novell/SUSE Bugzilla #891645
https://bugzilla.novell.com/show_bug.cgi?id=891645
** Also affects: systemd (openSUSE) via
https://bugzilla.novell.com/show_bug.cgi?id=891645
Importance: Unknown
Status: Unknown
** Package changed: systemd (openSUSE) => opensuse
--
** Tags removed: block-proposed
** Changed in: systemd (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1397344
Title:
Give 217
: New => In Progress
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1397361
Title:
Failed
Undecided
Assignee: Martin Pitt (pitti)
Status: In Progress
** Tags: block-proposed
** Changed in: systemd (Ubuntu)
Status: New => In Progress
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Tags added: block-proposed
--
You r
** Also affects: pygobject (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: pygobject (Ubuntu)
Status: New => Fix Released
** Changed in: pygobject (Ubuntu Precise)
Status: New => Triaged
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1396270 ***
https://bugs.launchpad.net/bugs/1396270
Profile changing in units works quite well now in current vivid (bug
1396270). So unless there is further information about what's still
missing I'm considering this a duplicate.
** This bug has been marked
I created a per-user container "t1", and confirm that it does start
under upstart/cgmanger and doesn't under systemd. I now have a
preliminary patch for putting the user slices into all cgroup
controllers, plus some hand-crafted "chown ubuntu" for all the
user-1000.slice cgroup directories so that
Seems irda-utils has an invalid init.d script:
insserv: warning: script 'irda-setup' missing LSB tags and overrides
insserv: There is a loop between service watchdog and irda-setup if stopped
insserv: loop involving service irda-setup at depth 2
insserv: loop involving service watchdog at depth
Oh sorry, this is actually on purpose -- The source package itself
builds systemd-dbg which has all the debug symbols of all libs.
** Changed in: systemd (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is sub
/usr/bin/pkg_create_dbgsym: nothing in
/build/buildd/systemd-215/debian/libudev1-dbgsym and no dbgdepends, ignoring
and consequently we stopped getting libudev1-dbgsym.
** Affects: systemd (Ubuntu)
Importance: Medium
Assignee: Martin Pitt (pitti)
Status: Triaged
** Changed in:
Hah, nice! Works for me, too.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/678421
Title:
Error message for a faulty ~/.profile script
To manage notifications about this bug go to:
h
Thanks, so as the KEY_BRIGHTNESS{UP/DOWN} evdev events are correctly
generated this isn't an udev regression. Thus reassigning to settings-
daemon for now, as this is the component that is supposed to react to
these keys. This might likely be fallout from the upower 0.9 → 0.99
transition.
** Pack
> . "$CONFIG_FILE" 2>"$ERR"
> OTOH, I suppose that switching to bash wouldn't be approved just like that. ;)
Bash's input redirection simply is way more powerful. Granted, bash
takes a tad longer to start up, but any tee or other external program
which you call in addition will probably hurt perf
gtest (Ubuntu)
Status: New => Fix Committed
** Changed in: autopkgtest (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1
** Package changed: keystone (Ubuntu) => systemd-shim (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1393474
Title:
su call in postinst fails with "Killed" when not r
Removing package for now, as it's not at all clear how to design this
(at least udev is way too low in the stack to even potentially ask the
user anything).
I'm very sceptical of these approaches. Experience shows that popping up
dialog boxes with security related questions à la "are you sure that
The most prominent cause of breakage in trusty was bug 1382510, which is
fixed in trusty-updates now. Do people still encounter this with
204-5ubuntu20.8? If so, we need to debug what else breaks in the init
script (adding some "set -x", etc.)
** Also affects: systemd (Ubuntu Trusty)
Importance
systemd (in the sense of pid 1) doesn't do that. I. e. if you boot with
init=/bin/systemd the only cgroup controller it puts tasks into (by
default) is the "systemd" one, for that very reason. But if you boot
with upstart (Ubuntu's default still), cgmanager creates cgroups.
cgmanager puts tasks int
w off to
finding the fix in the history..
** Changed in: systemd (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: systemd (Ubuntu Utopic)
Status: Confirmed => Triaged
** Changed in: systemd (Ubuntu Utopic)
Assignee: (unassigned) => Martin Pitt (pitt
For comparison I downloaded/booted current trusty, and I get the "can
not connect to iSCSI daemon" error there, too. But I do get a PATH_ID:
lrwxrwxrwx 1 root root 9 Nov 13 11:52 /dev/disk/by-path/ip-10.0.2.2:3260
-iscsi-trusty-daily-maas-amd64-lun-1 -> ../../sda
ubuntu@ubuntu:~$ sudo udevadm -d
Does this actually need to be fixed on the kernel side in Trusty? I'm a
bit confused by the "fix released" status of linux in utopic, as far as
I know most issues can be fixed in udev's keymaps alone?
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affec
Actually, option 1 would be to keep util-linux as-is and instead patch
systemd to read the "is hwclock local?" from /etc/default/rcS instead of
/etc/adjtime.
slangasek | pitti: again, my concern is that reinstating /etc/adjtime is going
to cause people to start misusing hwclock --adjust
slangasek
Oh, I expect us to upgrade to 3.14 ASAP. We just had 3.12 prepared for
quite some time, and as you say for 3.14 we need to upgrade vte first,
so we wanted to land this in two smaller steps.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
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 /etc/sy
No response to comment #2 in 6 weeks, and no explanation where the
"hvc0" thing comes from, so I close this. If you have more information,
I'm happy to reopen. Thanks!
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a mem
.
** Also affects: rfkill (Ubuntu)
Importance: Undecided
Status: New
** Changed in: rfkill (Ubuntu)
Status: New => Triaged
** Changed in: rfkill (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of
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
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 Ubuntu
Desktop Bugs, which is subscribed to gnome-applets in Ubuntu.
https://bugs.launchpad.net/bugs/1330037
Title:
upower 0.99.1 transition
I checked sugar-0.98, and the only usage seems to be in
./extensions/deviceicon/battery.py which only reads battery properties.
This looks fine for upower 0.99.
** Changed in: sugar-0.98 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubun
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
This looks like your apt sources are out of date and you have an
incomplete upgrade? Please try "sudo apt-get update" and then "sudo apt-
get -f install" to clean up. If that still does not work, please
copy&paste the output of "apt-cache policy udev libudev1".
** Changed in: systemd (Ubuntu)
*** This bug is a duplicate of bug 1365095 ***
https://bugs.launchpad.net/bugs/1365095
** This bug has been marked a duplicate of bug 1365095
Greeter not asking for pin code in image 11 (krillin)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
*** This bug is a duplicate of bug 1382510 ***
https://bugs.launchpad.net/bugs/1382510
** This bug has been marked a duplicate of bug 1382510
systemd-logind upstart script breaks if libpam-systemd is installed for more
than one arch
--
You received this bug notification because you are a
** Changed in: ubuntu-system-settings (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-applets in Ubuntu.
https://bugs.launchpad.net/bugs/1330037
Title:
upower 0.99.1 transition
** Summary changed:
- [FFe] upower 0.99.1 transition
+ upower 0.99.1 transition
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-applets in Ubuntu.
https://bugs.launchpad.net/bugs/1330037
Title:
upower 0.99.1 transition
To ma
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 Ubuntu
Desktop Bugs, which is subscribed to gnome-applets in Ubuntu.
https://bugs.launchpad.net/bu
Hmm, bluez looks fine at first sight. Reassigning this back, apparently
the bluetooth.target behaviour changed.
** Package changed: bluez (Ubuntu) => systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Status: Triaged => Confirmed
** Changed in: systemd (Ubuntu)
Assignee: Marti
** Changed in: bluez (Ubuntu)
Status: New => Triaged
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Summary changed:
- Bluetooth is not activated
+ bluetooth.service not started automatically
--
You received this bug notification because you are
m-settings/upower0.99/+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
** Changed in: gnome-session (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-applets in Ubuntu.
https://bugs.launchpad.net/bugs/1330037
Title:
[FFe] upower 0.99.1 transitio
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 Ubuntu
Deskto
I extracted Tim's powerd patch and created an upstream MP for this.
** Changed in: powerd (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-applets in Ubuntu.
https://bugs.launchpad.net/b
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 n
** 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 Ubuntu
Desktop Bugs, which is subscribed to gnome-applets in U
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 notific
** Changed in: gnome-shell (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-applets in Ubuntu.
https://bugs.launchpad.net/bugs/1330037
Title:
[FFe] upower 0.99.1 transition
** Changed in: gnome-shell-pomodoro (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-applets in Ubuntu.
https://bugs.launchpad.net/bugs/1330037
Title:
[FFe] upower 0.99.1 transition
** Changed in: wmbattery (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-applets in Ubuntu.
https://bugs.launchpad.net/bugs/1330037
Title:
[FFe] upower 0.99.1 transition
To manage
** 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 Ubuntu
Desktop Bugs, which is subscribed to gnome-applets in Ubuntu.
https:
801 - 900 of 7892 matches
Mail list logo
