** 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
** 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
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
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
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:
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
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
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
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
--
** 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
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
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
@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 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
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
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.
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
** 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
201 - 241 of 241 matches
Mail list logo
