** 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: 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: 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
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 Ubuntu
Desktop Bugs, which is subscribed to gnome-applets in
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
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.
You actually need to boot with systemd for systemctl to work. But NB
that in Ubuntu 14.10 this isn't officially supported yet, and many stuff
is still broken. But you can append init=/bin/systemd to the command
line to play with it; a normal desktop works very well.
** Changed in: systemd
That systemd error message is unrelated, mostly cosmetic, and fairly
harmless. reassigning back
** Package changed: systemd (Ubuntu) = xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
Gunnar,
Running it through sh -n is definitively a good way how to test a
shell script. It of course will miss a lot of errors (variable typos,
failing programs in a set -e script, etc.), but it at least will catch
obvious syntax errors. So ignoring faulty scripts and showing some error
message
** Changed in: systemd (Ubuntu)
Status: New = Fix Released
** Changed in: systemd (Ubuntu Trusty)
Status: New = Triaged
** Changed in: systemd (Ubuntu Trusty)
Importance: Undecided = High
** Changed in: systemd (Ubuntu Trusty)
Assignee: (unassigned) = Martin Pitt (pitti
This is a debconf failure in pam-auth-update, reassigning.
** Package changed: systemd (Ubuntu) = pam (Ubuntu)
** Summary changed:
- package libpam-systemd:amd64 208-8ubuntu5 failed to install/upgrade:
subprocess installed post-installation script returned error exit status 128
+ package
That description is a bit vague. Maybe for someone familiar with libvirt
it's enough, but can you please precisely describe the steps that you
did and the output? Thanks!
Confirming, that is with init=/bin/systemd or systemd-sysv, not with
booting with upstart (the only supported init system in
Patch sent upstream (rejected though), and applied to our gnome-terminal
packaging bzr.
** Changed in: gnome-terminal (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in
Egmont Koblinger [2014-10-15 9:18 -]:
I guess it's way too late for Utopic, but will make it into VV, correct?
Right. Utopic releases next week, and shipping and outdated
g-terminal is far from being release-critical. So it will land as soon
as V opens.
--
You received this bug
** Changed in: gnome-terminal (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1132700
Title:
gnome-terminal = 3.7
Cheers, thanks for the research! That explains where my ~/.bashrc got
that PROMPT_COMMAND from.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1132700
Title:
gnome-terminal
Please let's not do this madness in Ubuntu. Setting the initial dir
doesn't require any of this $PS1 hackery, and it's outright impossible
to inject it for any existing home dir (i. e. majority of cases).
Running the login shell executable in the desired directory is the
direct, clean, and
Followed up upstream at
https://bugzilla.gnome.org/show_bug.cgi?id=697475#c43 ff., and discussed
in #ubuntu-desktop. To unblock the update to 3.14 we'll revert
https://git.gnome.org/browse/gnome-terminal/commit/?id=cf3cad876 (i. e.
short-circuit the env var hack and putting back cwd_of_pid() to
** Summary changed:
- gnome-terminal requires sourcing of vte.sh login script -- go back to reading
/proc/pid/cwd
+ gnome-terminal = 3.7 requires sourcing of vte.sh login script -- go back to
reading /proc/pid/cwd
--
You received this bug notification because you are a member of Ubuntu
For being sure that we get the full output, can you please run this
python3 -c 'from gi.repository import Click'
and copypaste the whole output? This looks like your glib is out of
date (2.41.3-1), can you please upgrade to the current 14.10 version and
check if it works then? If so, I'll bump
OK, then we need to figure out the scope of how many people will likely
set $PROMPT_COMMAND in their ~/.bashrc (i. e. which older releases had
that in their /etc/skel/, or perhaps it was just added there manually).
If that's reasonably small or has never been in /etc/skel/, we can
revisit what's
)
** Changed in: libgphoto2 (Ubuntu)
Importance: Undecided = Low
** Changed in: libgphoto2 (Ubuntu)
Status: New = Triaged
** Changed in: libgphoto2 (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
** Also affects: libmtp (Ubuntu)
Importance: Undecided
Status: New
Further discussion in the upstream bug showed a better compromise:
- Let's use vte.sh for the cases where ~/.bashrc doesn't overwrite
$PROMPT_COMMAND
- Add back cwd_from_pid() as a fallback for the other cases, to avoid
regressions.
--
You received this bug notification because you are a
Egmont Koblinger [2014-10-07 10:16 -]:
Indeed it could be crucial to know if PROMPT_COMMAND was ever present in
/etc/skel. I think it's fair game if users who have once touched their
configs will need to touch that again.
Yes, I agree.
OSC stands for operating system command, this is
Right, if you boot 14.10 with systemd this should already work. But that
job doesn't run under upstart. So either we wait until systemd becomes
the init in Ubuntu, or we write a corresponding upstart job that calls
/lib/systemd/systemd-backlight.
** Changed in: sysvinit (Ubuntu)
Importance:
I'm afraid I don't have an idea what could cause a SIGILL in
dbus_message_new_error (), since like that we don't see the real error
message which caused dbus_bus_get_unix_user() to fail. Is this
reproducible on your system, i. e. does it crash on every boot (or at
least more than once)? If so, I
This happens in the pam-auth-update call, reassigning to PAM.
** Summary changed:
- package libpam-systemd:amd64 208-8ubuntu4 failed to install/upgrade:
subprocess installed post-installation script returned error exit status 128
+ package libpam-systemd:amd64 208-8ubuntu4 failed to
** Changed in: gnome-control-center (Ubuntu)
Status: New = Fix Committed
** Changed in: gnome-settings-daemon (Ubuntu)
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in
*** This bug is a duplicate of bug 1348039 ***
https://bugs.launchpad.net/bugs/1348039
** This bug has been marked a duplicate of bug 1348039
shim does not implement 'Subscribe' method called by logind
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Ubuntu does not yet install a systemd-ask-password agent. It seems
openvpn went too much ahead and is relying on this without checking
whether a password agent is running.
** Package changed: systemd (Ubuntu) = openvpn (Ubuntu)
** Summary changed:
- OpenVPN doesnt ask for pkcs12 password
+
** Also affects: libgweather (Ubuntu Utopic)
Importance: Undecided
Status: Confirmed
** Also affects: libgweather (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Utopic fix merged and uploaded, thanks!
** Changed in: libgweather (Ubuntu Utopic)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to libgweather in Ubuntu.
Trusty SRU uploaded to SRU team review queue. Unsubscribing sponsors
now.
** Changed in: libgweather (Ubuntu Trusty)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to libgweather in Ubuntu.
ifup@.service works as intended. The idea is that /etc/init.d/networking
brings up all auto interfaces, and that unit takes care of the
hotplugged interfaces only.
The problem is that /etc/init.d/networking (or something it calls)
doesn't work if / is read-only. I'll investigate what it's trying
So for some reason your system configuration causes
/etc/init.d/networking to be run before the kernel detects eth0
(journalctl shows this quite nicely).
** Package changed: ifupdown (Ubuntu) = systemd (Ubuntu)
** Summary changed:
- auto interfaces do not come up with r/o images
+
Ben, I uploaded both of them. The previous systemd version is still in
trusty-proposed, so accepting that will still take a few days. The
precise one can be reviewed/accepted by the SRU team right now.
** Also affects: udev (Ubuntu)
Importance: Undecided
Status: New
** No longer
** Summary changed:
- systemd boot hangs - sysv:networking - ifup - tinc
+ tinc needs systemd integration
** No longer affects: systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
Public bug reported:
Installing systemd-sysv replaces upstart's reboot, poweroff and
friends. systemd's binaries currently don't know how to talk to upstart
to forward the request to upstart. This breaks a transition to systemd
as default init which doesn't just change the boot= kernel parameter
Thanks Brian for spotting this! Closing bug then.
** Changed in: systemd (Ubuntu)
Status: New = Invalid
** Summary changed:
- package libpam-systemd 204-5ubuntu20.5 failed to install/upgrade: subprocess
new pre-removal script returned error exit status 102
+ package libpam-systemd
Utopic fix committed to git, thanks! I keep this open for trusty, but as
it's neither a data loss nor critical bug and just a cosmetical corner
case I keep it as low importance.
You say since 3.13.0-16.36 which is trusty -- i. e. precise's kernel
still has it as a module? So it seems to me that
Ah indeed. But this has worked by sheer accident, not by design. udev
rules aren't supposed for this, and if they write any files it should be
into /dev/ or /run. They can race in both ways: before the file system
becomes available, or they run too late when the display manager is
already starting
I suppose you at least want this for 14.04 LTS. Do you still need this
for 12.04 LTS too, or is 14.04 sufficient?
** Package changed: udev (Ubuntu) = systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a member
Utopic fix committed to packaging git: http://anonscm.debian.org/cgit
/pkg-systemd/systemd.git/commit/?id=37f4673cf
** Changed in: systemd (Ubuntu)
Status: In Progress = Fix Committed
** Also affects: systemd (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in:
The systemd side of this is fixed in utopic, closing. The kernel (and
main) side keeps open.
** 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
This is fixed in utopic.
** 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/1247676
Title:
[keymap] high
*** This bug is a duplicate of bug 1301846 ***
https://bugs.launchpad.net/bugs/1301846
** This bug has been marked a duplicate of bug 1301846
loginctl crashed with SIGABRT
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
I am on an UEFI system. I'm not sure what you mean by the same bug,
that bug was fixed by above systemd upload. If you have trouble with
booting, can you please open a new bug? Preferably by submitting a crash
report through Apport if you have any crash report; if you don't have
crashes, please
Crash in py3clean, reassigning.
** Package changed: pygobject (Ubuntu) = python3-defaults (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1360642
Title:
package
Not a bug in apport or pygobject. It seems your system has python-
minimal not installed, which is fairly essential. Please put it back.
** Changed in: pygobject (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** 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 Ubuntu
Desktop Bugs, which is subscribed to systemd-shim in Ubuntu.
Fixed in https://git.gnome.org/browse/pygobject/commit/?id=92f0d6ebf
** Package changed: virt-manager (Ubuntu) = pygobject (Ubuntu)
** Changed in: pygobject (Ubuntu)
Importance: Medium = High
** Changed in: pygobject (Ubuntu)
Status: Confirmed = Triaged
** Also affects: pygobject via
** Changed in: pygobject (Ubuntu)
Status: Triaged = Fix Committed
** Changed in: pygobject (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygobject in Ubuntu.
https
** Package changed: ubuntu = systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Status: Confirmed = 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/1361272
Title:
** Also affects: udev (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: udev (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Trusty)
Public bug reported:
We currently ship an early development release of pygobject in utopic
(3.13.3). GNOME 3.13.90 was released, so we should update pygobject.
I'm filing this with block-proposed, so that we can stage and test
everything in -proposed and then release after TRAINCON-0 has been
** Tags removed: block-proposed
** Changed in: pygobject (Ubuntu)
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1359671
Title:
New upstream
** 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 Ubuntu
Desktop Bugs, which is subscribed to systemd-shim in Ubuntu.
** Package changed: systemd-shim (Ubuntu) = poppler (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/1254851
Title:
qpdfview renders black pages after poppler update
To
** Package changed: systemd-shim (Ubuntu) = network-manager (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/1296372
Title:
network disabled 14.04 trusty
To manage
** Bug watch added: Debian Bug tracker #756076
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756076
** Also affects: systemd-shim (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756076
Importance: Unknown
Status: Unknown
** Changed in: systemd-shim (Ubuntu)
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 Ubuntu
** Package changed: udev (Ubuntu) = systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Importance: Undecided = Low
** Changed in: systemd (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Right, we don't build static libraries (in quite a lot of packages), as
there's really no need for them and they just encourage code duplication
and hard to maintain systems.
** Summary changed:
- libudev1 does not include static library
+ libudev-dev does not include static library
** Changed
*** This bug is a duplicate of bug 1012081 ***
https://bugs.launchpad.net/bugs/1012081
** This bug has been marked a duplicate of bug 1012081
util-linux needs updating to 2.24.2
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
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
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
Added kernel task for the lack of evdev events.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
+ Summary:
+ - The joystick evdev device for the pedals doesn't get proper permissions
(in udev/systemd)
+ - The pedal evdev device sometimes
** 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/1353595
Title:
[proposed] upgrade fails due to missing new
Applied in systemd packaging git, thanks!
** Package changed: udev (Ubuntu) = systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
This is fixed in utopic, the upstart script went away completely in
favor of D-BUS activation.
** Changed in: systemd (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
Closing. Adrian as the original reporter said it's fixed for him in
final 14.04, and I didn't get an answer from akete in 2 months. Please
reopen if you are still experiencing this. Thanks!
** Changed in: systemd (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug
Ah, nevermind, this just rang a bell. This was fixed a while ago
already, but hasn't found its way into Ubuntu yet:
http://cgit.freedesktop.org/systemd/systemd/commit/?id=2658624399b
** Changed in: systemd (Ubuntu)
Status: Incomplete = Fix Committed
** Bug watch added: freedesktop.org
However, sudo su - does not result in the creation of
XDG_RUNTIME_DIR for the root user, hence UPSTART_SESSION is set to the
null value.
That's correct, and intended. This was explicitly done in
https://launchpad.net/ubuntu/+source/systemd/204-0ubuntu19.1 for bug
1197395. $XDG_RUNTIME_DIR must
Fixed in current udev packages, the udevadm.upgrade diversion was
dropped.
** 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
Fixed upstream:
http://cgit.freedesktop.org/systemd/systemd/commit/?id=efb4bf4e
** Package changed: udev (Ubuntu) = systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Status: New = Fix Committed
** Summary changed:
- two udev EV_KEY when hit a hotkey like enable/disable wireless. hp
This is coming from dh_python3's autogenerated pyclean call:
Preparing to replace python3-gi 3.4.0-1 (using
.../python3-gi_3.4.0-1ubuntu0.1_amd64.deb) ...
Fatal Python error: Py_Initialize: Unable to get the locale encoding
EOFError: EOF read where not expected
Can you please give the output of
This is for consideration of the server team, who enabled biosdevname.
** Package changed: systemd (Ubuntu) = ubuntu-meta (Ubuntu)
** Changed in: ubuntu-meta (Ubuntu)
Status: Opinion = New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
The debug output does appear in /var/log/syslog after sudo udevadm
control --log-priority=debug at least in Ubuntu 14.04 LTS and 14.10, so
this apparently got fixed.
** Changed in: systemd (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member
Thanks. Reassigning to kernel then.
** Summary changed:
- [keymap] Brightness keys Fn+F5 and Fn+F6 don't work for Asus UX32LN
+ Asus UX32LN: Brightness keys Fn+F5 and Fn+F6 don't generate evdev event
** Package changed: systemd (Ubuntu) = linux (Ubuntu)
** Changed in: linux (Ubuntu)
Not a bug in systemd itself; (unity|gnome)-control-center need to start
depending on libnss-myhostname, like in Debian.
** Package changed: systemd (Debian) = gnome-control-center (Debian)
** Package changed: systemd (Ubuntu) = unity-control-center (Ubuntu)
--
You received this bug
Actually, in the MIR bug there is still some dispute, so reassigning
back to systemd for now.
** Package changed: unity-control-center (Ubuntu) = systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center
Indeed, lots of USB port resets in
https://launchpadlibrarian.net/176813239/CurrentDmesg.txt. I suppose the
port that the hub is connected to is simply unable to provide enough
power for all devices on the hub, or there is a bad USB cable or other
hardware problem. Please try the USB device on a
** 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 Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
Ah sorry, I thought you meant the empty product name of the graphics
card (which also didn't exist yet in 14.04).
Indeed udev hwdb doesn't have data for ssb: devices.
** Changed in: systemd (Ubuntu)
Status: Fix Released = Triaged
** Summary changed:
- [hwdb] No vendor/product name for
This is fixed in utopic's systemd, its hwdb now has
pci:v10DEd08A0*
ID_MODEL_FROM_DATABASE=MCP89 [GeForce 320M]
** Changed in: systemd (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Thanks for your report! However, I'm afraid there's not much that we can
do about it: There is no useful stack trace at all, no duplicates on
Launchpad or https://errors.ubuntu.com/?package=systemdperiod=month
Looks like it crashed somewhere between libkmod and glibc, even before
udev started. If
Bug 1289608 looks very similar, and has a full (although not fully
symbolic) stack trace:
https://launchpadlibrarian.net/168647144/Stacktrace.txt There are no
other duplicates on LP, and none on
https://errors.ubuntu.com/?package=systemdperiod=month
Looks like it crashed somewhere between libkmod
This is fixed in utopic, as the init script went away completely, in
favor of always using D-BUS activation.
** Also affects: systemd (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Utopic)
Importance: High
Status: Confirmed
** Changed in:
208 is in utopic now, so this can be closed.
** 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/1335369
** Changed in: metacity (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/1347992
Title:
Update to 3.12
To manage notifications
This bug was fixed in the package harfbuzz - 0.9.33-1
Sponsored for أحمد المحمودي (Ahmed El-Mahmoudy) (aelmahmoudy)
---
harfbuzz (0.9.33-1) unstable; urgency=medium
* New upstream release.
* Upload to unstable.
* Added unbreak_abi.diff patch to Re-add hb_version_check to
So it seems the originally reported problem was fixed. There's a
multitude of insufficiently described and hard to understand other
problems here. If you have particular issues under systemd, can you
please report one bug for each issue with a precise description, and
include the output of
Can you please install the evtest package and check with sudo evtest
that you actually get brightness keycodes every time you press these
keys? I suppose that is true as you write Changing the shortcut to
execute xfce4-terminal seems to make the hotkey 100% consistent, so
the evdev events seem to
Fixed upstream now:
http://cgit.freedesktop.org/systemd/systemd/commit/?id=1f6d36f
Thanks Wang!
** Package changed: linux (Ubuntu) = systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
** Bug watch added: Debian Bug tracker #674755
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674755
** Also affects: systemd (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674755
Importance: Unknown
Status: Unknown
--
You received this bug notification because
I believe this has been sufficiently tested now. We are out of
traincon-0 for the touch images too, so let's unleash this.
** 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
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
-
** Package changed: ubuntu = systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Status: New = In Progress
** Also affects: systemd (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Utopic)
Importance: Undecided
Status: In Progress
--
901 - 1000 of 7748 matches
Mail list logo
