** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1367241
Title:
Incorrect
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) = Dariusz Gadomski (dgadomski)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1367241
Title:
Incorrect udev
Thanks Martin for taking a look.
In my precise (12.04.5) install the default kernel is 3.13.0-32-generic, which
is affected by the issue:
$ grep FB_VESA /boot/config-3.13.0-32-generic
CONFIG_FB_VESA=y
In fact initially this has been reported by a CTS customer for precise.
--
You received this
Actually I think the second approach would be better, since the error
comes not from the message (which is redirected to upstart logs anyway),
but from the return code of the script.
Unfortunately, according to my knowledge, the upstart scripts are
executed with the -e switch making it stop with
I have uploaded new patches updated as agreed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1367241
Title:
Incorrect udev-fallback-graphics.conf
Status in “systemd”
Adding new SRU proposal for Precise.
** Patch removed: systemd_204-5ubuntu20.7.debdiff
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1367241/+attachment/4201485/+files/systemd_204-5ubuntu20.7.debdiff
** Patch removed: udev_175-0ubuntu9.7.debdiff
Adding new SRU proposal for Trusty.
** Patch added: systemd_204-5ubuntu20.7.debdiff
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1367241/+attachment/4202154/+files/systemd_204-5ubuntu20.7.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I have investigated the possibility to backport the fix for this issue
from trusty (14.04). There has been a major refactoring of the locking
all over lvm between versions shipped with precise (2.02.66 patched to
2.02.72) and trusty (2.02.98).
The scope of backporting makes this operation risky
Assuming that:
* vg0 is the volume group in question
* lv0 is the logical volume
* sdc is the physical volume that needs to be freed
there is a workaround possible:
1. lvconvert --mirrorlog core -m 1 /dev/vg0/lv0
2. lvconvert --mirrorlog core -m 0 vg0/lv0 /dev/sdc
3. vgreduce vg0 /dev/sdc
--
I have verified this on my machines, although I still wait for a
verification from a user.
I will update this issue after getting the confirmation.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
SRU proposal for utopic (gtk+2.0)
** Description changed:
- i am printing from my ubuntu karmic to a windows box. everytime i print
- i get asked to input username and password to windows box, then the
- document gets printed. there is a remember password checkbox, but it
- keeps asking me when
SRU proposal for utopic (gtk+3.0)
** Patch added: gtk+3.0_3.12.2-0ubuntu8.debdiff
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/445333/+attachment/4214816/+files/gtk%2B3.0_3.12.2-0ubuntu8.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
@TWC Service Thank you for checking this.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1367241
@Marco
I am thinking about a fix for this:
* Add a setting to change the current behavior (e.g. Remember viewport focus)
* Before changing viewport save the currently focused window
* When coming back to a viewport instead of focusing the default window do:
i) if the new setting is enabled try to
TWC Service verified trusty. Adding correct tag.
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1367241
Title:
Incorrect
While I was working on a packport of this feature I have discovered a
bug in the gtk printing backends (affects series 2 and 3) that may cause
random crashes due to buffer overflow.
I have reported the issue upstream and am working on backports to utopic
and trusty (gtk2 and gtk3).
SRU proposal for trusty.
Contains feature backport along with a fix for
https://bugzilla.gnome.org/show_bug.cgi?id=73.
** Patch added: trusty_gtk+2.0_2.24.23-0ubuntu1.2.debdiff
SRU proposal for utopic
Contains the feature backport along with a fix for
https://bugzilla.gnome.org/show_bug.cgi?id=73.
** Patch added: utopic_gtk+2.0_2.24.24-0ubuntu2.debdiff
SRU proposal for Utopic
(https://bugzilla.gnome.org/show_bug.cgi?id=73)
** Patch added: utopic_gtk+3.0_3.12.2-0ubuntu11.debdiff
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/445333/+attachment/4222403/+files/utopic_gtk%2B3.0_3.12.2-0ubuntu11.debdiff
--
You received this bug
SRU proposal for trusty.
Contains feature backport along with a fix for
https://bugzilla.gnome.org/show_bug.cgi?id=73.
** Patch added: trusty_gtk+3.0_3.10.8-0ubuntu1.3.debdiff
** Tags added: cts
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1367241
Title:
Incorrect udev-fallback-graphics.conf
Status in “systemd” package in Ubuntu:
Fix
** Tags added: cts
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/445333
Title:
remember password on printing to windows printers does not work
Status in GTK+ GUI
SRU proposal for precise
** Description changed:
+ [Impact]
+
+ * This bug is likely to cause a crash with a SEGV in multithreading
+ applications doing many memory deallocations with ATOMIC_FASTBINS
+ feature enabled.
+
+ [Test Case]
+
+ * Since this is a race condition issue there is no
** Description changed:
[Impact]
- * This bug is likely to cause a crash with a SEGV in multithreading
+ * This bug is likely to cause a crash with a SEGV in multithreading
applications doing many memory deallocations with ATOMIC_FASTBINS
feature enabled.
[Test Case]
- * Since
SRU proposal for utopic (gtk2)
** Patch removed: utopic_gtk+2.0_2.24.24-0ubuntu2.debdiff
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/445333/+attachment/4222404/+files/utopic_gtk%2B2.0_2.24.24-0ubuntu2.debdiff
** Patch removed: trusty_gtk+2.0_2.24.23-0ubuntu1.2.debdiff
SRU proposal for trusty (gtk2).
** Patch added: trusty_gtk+2.0_2.24.23-0ubuntu1.2.debdiff
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/445333/+attachment/4265156/+files/trusty_gtk%2B2.0_2.24.23-0ubuntu1.2.debdiff
--
You received this bug notification because you are a member of
Sebastien, please find the attached debdiffs with the
gtk_print_backend_set_password version bumped.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/445333
Title:
SRU proposal for trusty (gtk3).
** Patch added: trusty_gtk+3.0_3.10.8-0ubuntu1.3.debdiff
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/445333/+attachment/4265155/+files/trusty_gtk%2B3.0_3.10.8-0ubuntu1.3.debdiff
--
You received this bug notification because you are a member of
Sebastien, I have prepared a debdiff for gtk2 vivid. I hope it will be
of any use for you. Thanks!
** Patch added: vivid_gtk+2.0_2.24.25-0ubuntu2.debdiff
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/445333/+attachment/4266693/+files/vivid_gtk%2B2.0_2.24.25-0ubuntu2.debdiff
--
You
The upstream gtk is considering backporting this change to gtk2: [1]
What I find most important in the description is:
With regards to the importance of having this only fixed in GTK 3. To be
honest, as long as firefox still uses GTK 2 in most distributions this fix is
more important for our
Updated debdiff against eglibc_2.15-0ubuntu10.9.
** Patch added: precise_eglibc_2.15-0ubuntu10.10.debdiff
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1020210/+attachment/4299972/+files/precise_eglibc_2.15-0ubuntu10.10.debdiff
** Patch removed:
Adding syslog with enhannced debugging information from bluetoothd.
** Attachment added: Syslog with -d passed to bluetoothd
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1410779/+attachment/4298384/+files/syslog
--
You received this bug notification because you are a member of
Thanks Victor for your report.
I am aware that you were trying:
sudo rfkill unblock 3
[sudo] password for vestival:
vestival@vestival01:~$ sudo rfkill list
0: tpacpi_wwan_sw: Wireless WAN
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
3: hci0:
Chris, please find the updated debdiff.
** Patch removed: precise_eglibc_2.15-0ubuntu10.11.debdiff
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1020210/+attachment/4317996/+files/precise_eglibc_2.15-0ubuntu10.11.debdiff
** Patch added: precise_eglibc_2.15-0ubuntu10.11.debdiff
Chris, please find the updated debdiff.
** Patch added: precise_eglibc_2.15-0ubuntu10.11.debdiff
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1020210/+attachment/4317996/+files/precise_eglibc_2.15-0ubuntu10.11.debdiff
--
You received this bug notification because you are a member
** Bug watch added: Debian Bug tracker #781007
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781007
** Also affects: network-manager (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781007
Importance: Unknown
Status: Unknown
--
You received this bug notification
** Bug watch added: GNOME Bug Tracker #752481
https://bugzilla.gnome.org/show_bug.cgi?id=752481
** Also affects: network-manager via
https://bugzilla.gnome.org/show_bug.cgi?id=752481
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
Adding SRU proposal for wily.
** Description changed:
+ [Impact]
+
+ * A lack of proper synchronization in ifupdown causes a race condition
+ resulting in occasional incorrect network interface initialization (e.g.
+ in bonding case - wrong bonding settings, network unavailable because
+
Adding SRU proposal for Vivid.
** Patch added: "vivid_ifupdown_0.7.48.1ubuntu11.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1337873/+attachment/4501798/+files/vivid_ifupdown_0.7.48.1ubuntu11.debdiff
--
You received this bug notification because you are a member of
Adding SRU proposal for Trusty (to make ifenslave compatible with
ifupdown changes).
** Patch added: "trusty_ifenslave_2.4ubuntu1.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1337873/+attachment/4501800/+files/trusty_ifenslave_2.4ubuntu1.2.debdiff
--
You received this
Adding SRU proposal for Trusty.
** Patch added: "trusty_ifupdown_0.7.47.2ubuntu4.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1337873/+attachment/4501799/+files/trusty_ifupdown_0.7.47.2ubuntu4.2.debdiff
--
You received this bug notification because you are a member of
** Description changed:
[Impact]
- * A lack of proper synchronization in ifupdown causes a race condition
+ * Lack of proper synchronization in ifupdown causes a race condition
resulting in occasional incorrect network interface initialization (e.g.
in bonding case - wrong bonding
** Description changed:
There is an error observed when Ubuntu is configured to perform
authentication via pam_vas (Vintela Authentication Services by Dell) in
a disconnected mode (using cached authentication).
Steps to reproduce:
1. Configure pam_vas client authenticating to a
Public bug reported:
There is an error observed when Ubuntu is configured to perform
authentication via pam_vas (Vintela Authentication Services by Dell) in
a disconnected mode (using cached authentication).
Steps to reproduce:
1. Configure pam_vas client authenticating to a remote server.
2.
** Changed in: policykit-1 (Ubuntu)
Assignee: (unassigned) => Dariusz Gadomski (dgadomski)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1510824
Ti
** Summary changed:
- PolkitAgentSession ignores multiline output (with pam_vas)
+ PolkitAgentSession incorrectly handles multiline output (with pam_vas)
** Description changed:
There is an error observed when Ubuntu is configured to perform
authentication via pam_vas (Vintela
** Bug watch added: freedesktop.org Bugzilla #92886
https://bugs.freedesktop.org/show_bug.cgi?id=92886
** Also affects: policykit-1 via
https://bugs.freedesktop.org/show_bug.cgi?id=92886
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
Adding SRU proposal for Xenial.
** Patch added: "xenial_ifupdown_0.7.54ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1337873/+attachment/4515989/+files/xenial_ifupdown_0.7.54ubuntu2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Typo, what I've meant in the above comment is that I wanted to avoid
doing 2 different actions in the same commit.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1510824
Miroslav, thanks for taking a look.
Sure, I can improve the patch. I'll attach the new version as soon as
it's done.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-1 in Ubuntu.
Created attachment 119643
Refactoring to use send_to_helper
I have refactored the code to make use of send_to_helper instead of
duplicating the code.
I've chosen to apply it on top of the previous change to keep 2
different actions (escaping PAM_TEXT_INFO and refactoring) on the same
step.
I
I have debugged the network-manager daemon (src/settings/nm-
settings.c:234 impl_settings_list_connections) and nmcli
(cli/src/connections.c:8633 get_connections_cb).
It looks that a correct number of connections is sent from the daemon
and a limited number is received in the nmcli. Maybe it's
Public bug reported:
If a large number of networks is configured it may be impossible to
connect to some of them as a regular user, because they are not listed.
It affects all the versions I tested: trusty, utopic, vivid and wily.
Steps to reproduce:
1. Configure a large number of networks (in
I have been playing with copying some limit values from
/etc/dbus-1/session.conf to system.conf and by bisection I found out that
adding the following settings:
limit name=max_replies_per_connection5/limit
makes the problem disappear.
--
You received this bug notification because you are a
** Changed in: ifupdown (Ubuntu)
Assignee: (unassigned) => Dariusz Gadomski (dgadomski)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1337873
Title:
Prec
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1375821
Title:
ifupdown doesn't bring loopback to state up
Status in ifupdown package in Ubuntu:
Fix
I have backported the fix to trusty in my ppa.
Unfortunately I was not able to reproduce this issue (although my tests
are ongoing). With that being said I would really appreciate anyone that
is affected by this issue to give it a try and let me know whether the
backport fixed that for them.
The
I have prepared a 'broken' pam_unix version printing a multiline text info if
it detects the PAM_SERVICE name is polkit-1.
This allows to reproduce the issue and verify the fix.
I've made this broken version available for Vivid and Wily in
ppa:dgadomski/lp1510824 and performed the verification
Created attachment 119702
Refactoring to use send_to_helper
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1510824
Title:
PolkitAgentSession incorrectly handles
Added SRU proposal for trusty.
** Patch added: "trusty_policykit-1_0.105-4ubuntu3.14.04.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1510824/+attachment/4522626/+files/trusty_policykit-1_0.105-4ubuntu3.14.04.1.debdiff
--
You received this bug notification because
Added SRU proposal for vivid.
** Patch added: "vivid_policykit-1_0.105-8ubuntu5.debdiff"
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1510824/+attachment/4522625/+files/vivid_policykit-1_0.105-8ubuntu5.debdiff
--
You received this bug notification because you are a member of
Added SRU proposal for Xenial.
** Description changed:
+ [Impact]
+
+ * An explanation of the effects of the bug on users and
+
+ * justification for backporting the fix to the stable release.
+
+ * In addition, it is helpful, but not required, to include an
+explanation of how the
Added SRU proposal for wily.
** Patch added: "wily_policykit-1_0.105-11ubuntu3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1510824/+attachment/4522624/+files/wily_policykit-1_0.105-11ubuntu3.debdiff
--
You received this bug notification because you are a member of
** Patch removed: "wily_ifupdown_0.7.54ubuntu3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1337873/+attachment/4548423/+files/wily_ifupdown_0.7.54ubuntu3.debdiff
** Patch removed: "trusty_ifupdown_0.7.47.2ubuntu4.3.debdiff"
SRU proposal for Wily (extended with fix to bug #1532722)
** Patch added: "wily_ifupdown_0.7.54ubuntu3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1337873/+attachment/4548423/+files/wily_ifupdown_0.7.54ubuntu3.debdiff
--
You received this bug notification because you
SRU proposal for Trusty (extended with fix to bug #1532722)
** Patch added: "trusty_ifupdown_0.7.47.2ubuntu4.3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1337873/+attachment/4548422/+files/trusty_ifupdown_0.7.47.2ubuntu4.3.debdiff
--
You received this bug notification
Updated SRU proposal for Trusty (fix to bug #1532722)
** Patch added: "trusty_ifupdown_0.7.47.2ubuntu4.3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1337873/+attachment/4548430/+files/trusty_ifupdown_0.7.47.2ubuntu4.3.debdiff
--
You received this bug notification
New SRU proposal for Wily (with fix to bug #1532722)
** Patch added: "wily_ifupdown_0.7.54ubuntu1.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1337873/+attachment/4548431/+files/wily_ifupdown_0.7.54ubuntu1.2.debdiff
--
You received this bug notification because you are
I have verified both Trusty and Wily. The verification was automated
cyclic rebooting of a VM containing 3 NICs - 2 of them were used in
bonding in active-backup. Before the fix has been implemented this test
failed with some interfaces uninitialized or the bonding mode being
wrong (the default
Since I've added the fix to bug 1532722 and after several days of
testing I did not observe any other issues on Trusty and Wily I'm
tagging this as verified.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of
Hello Max,
My guess (supported by a test I made in a test environment) is the cause of the
problem are those lines under iface bond0:
pre-ip ifup eth2
pre-up ifup eth3
Those are most probably causing a deadlock, since the new release aims to fix
the race condition causing the
That's right Andrew, it's backported from Debian so no forwarding
needed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1545302
Title:
wpa-roam broken by fix for ifupdown
@Paul: glad it works for you. Thank you for reporting the issue and the
feedback.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1545302
Title:
wpa-roam broken by fix for
Thank you for the report sirswa.
I have analyzed your config and came to some conclusions. You may want to
consider using one of the approaches below:
* giving up on bonding and replacing it with bridging in STP mode (please
consult the man pages at
Hello Paul,
The locking mechanism was implemented to avoid race conditions in ifupdown
(such as the one reported as bug #1337873). Unsetting the variable may lead to
unexpected consequences. I belive a proper solution would be to modify wpa-roam
implementation to play along with ifupdown.
Paul, I think that the real cause here is that (by looking into
debian/ifupdown/functions.sh) wpasupplicant depends on the previous single-file
ifstate.
Currently, for the sake of the locking mechanism, it has been split into an
individual ifstate.$IFACE per interface, while wpasupplicant still
Paul, I have finally managed to reproduce this on Trusty. The ifstate
looks to be a false trail.
However, please note that with 0.8.10ubuntu1 on Xenial this problem does
not occur.
I am investigating which change needs to be backported. I will keep you
updated.
--
You received this bug
Hello Paul,
I have identified the cause of the problem and prepared a fix.
My tests show that it solves the issue for Trusty and Wily (while Xenial does
not require a fix since it's ifupdown has been synced with Debian to a version
containing a fix already).
Could you please revert your
Paul, the patch looks good.
It's better than making those scripts compatible with new style of
ifstate. Fixing ifstate-based implementation would not cover replacing
one logical iface with another, while your implementation does it.
Good luck with pushing this to Debian.
--
You received this
Adding SRU proposal for Trusty.
** Description changed:
+ [Impact]
+
+ * In some configurations recurrent ifup/down calls are broken due to a
+ false-positive recursion detection.
+
+ * In certain situations it leaves interfaces unconfigured (in this
+ case: WLAN interface connected to WiFi
Adding SRU proposal for Wily.
** Attachment added: "wily_ifupdown_0.7.54ubuntu1.3.dsc"
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1545302/+attachment/4574280/+files/wily_ifupdown_0.7.54ubuntu1.3.dsc
--
You received this bug notification because you are a member of Ubuntu
Touch
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1545302
Title:
wpa-roam broken by fix for ifupdown #1337873
Status in wpa package in Ubuntu:
Confirmed
@Mike, @DavidS: thank you for feedback. I'm glad it's working for you.
The official fix will be on it's way.
@Robert: please confirm that your wpa-roam settings below "iface wlan0 inet
manual" is in fact pointing to the right file as DavidS noticed. If it is
please check:
sudo wpa_cli status
@sirswa I tried to reproduce this in my environment - unsuccessfully.
I created a similar config - please take a look at my it for reference:
http://paste.ubuntu.com/15129899/
Maybe you could spot a difference that I overlooked.
This could mean that this change may be interfering with something
Stack trace:
#0 0x7f70f7618227 in __GI_raise (sig=sig@entry=6)
at ../sysdeps/unix/sysv/linux/raise.c:55
#1 0x7f70f7619e8a in __GI_abort () at abort.c:89
#2 0x7f70f79bc48f in isc_assertion_failed (
file=file@entry=0x7f70f7a06350 "../../../../lib/isc/unix/socket.c",
Hello,
Do you have an ifupdown crash saved in /var/crash after this incident?
If so, please attach it do this bug.
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
** Description changed:
- [Impact]
+ [Impact]
There are some unlinked calls to libGL.so.1 undetected in the build process
because of using libepoxy. Running an application that does not depend on
libgl1 (directly or indirectly) may lead to aborting the process with an
undefined reference to
Yakkety SRU proposal with fixed version number.
** Patch removed: "yakkety_gtk+3.0_3.20.9-1ubuntu3.debdiff"
https://bugs.launchpad.net/hundredpapercuts/+bug/1550983/+attachment/4808140/+files/gtk+3.0_3.20.9-1ubuntu3.debdiff
** Patch added: "yakkety_gtk+3.0_3.20.9-1ubuntu2.1.debdiff"
** Changed in: gtk+3.0 (Ubuntu)
Assignee: (unassigned) => Dariusz Gadomski (dgadomski)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1550983
Title:
Fails to st
SRU proposal for Xenial - backport from Zesty.
** Patch added: "xenial_gtk+3.0_3.18.9-1ubuntu3.2.debdiff"
https://bugs.launchpad.net/hundredpapercuts/+bug/1550983/+attachment/4808141/+files/xenial_gtk+3.0_3.18.9-1ubuntu3.2.debdiff
** Tags added: sts-sru
--
You received this bug
SRU proposal for Yakkety - backport from Zesty.
** Patch added: "gtk+3.0_3.20.9-1ubuntu3.debdiff"
https://bugs.launchpad.net/hundredpapercuts/+bug/1550983/+attachment/4808140/+files/gtk+3.0_3.20.9-1ubuntu3.debdiff
--
You received this bug notification because you are a member of Ubuntu
This bug is fixed in Zesty by latest sync with Debian (gtk+3.0
(3.22.7-2)).
** Changed in: gtk+3.0 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1550983
Title:
Fails to start with "Couldn't open libGL.so.1" (missing dependency?)
Status in One
** Description changed:
+ [Impact]
+ There are some unlinked calls to libGL.so.1 undetected in the build process
because of using libepoxy. Running an application that does not depend on
libgl1 (directly or indirectly) may lead to aborting the process with an
undefined reference to
** Tags removed: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1665018
Title:
client tools ignore -h option without port number
Status in cups package in
Thanks Till & Brian.
In the same environment that served as a reproducer the new version
fixes the issue.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I have just verified it for Trusty and Yakkety on the same images that
were used earlier to reproduce it.
The issue is gone.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
SRU proposal for Trusty.
** Patch added: "trusty_cups_1.7.2-0ubuntu1.8.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1665018/+attachment/4819939/+files/trusty_cups_1.7.2-0ubuntu1.8.debdiff
** Tags added: sts-sponsor
--
You received this bug notification because you are a
of the one given by -h option).
If a port number is given (e.g. server2:631) the commands work as
expected.
** Affects: cups (Ubuntu)
Importance: Medium
Assignee: Dariusz Gadomski (dgadomski)
Status: New
** Tags: sts
** Changed in: cups (Ubuntu)
Importance: Undecided => Med
Of course I meant Xenial and Yakkety. Thanks for noticing that Robie.
The versions I tested:
* Xenial
libgtk-3-0:
Installed: 3.18.9-1ubuntu3.2
* Yakkety:
libgtk-3-0:
Installed: 3.20.9-1ubuntu2.1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
1 - 100 of 241 matches
Mail list logo
