[Ubuntu-translations-coordinators] [Bug 1380702] Re: No keyboards shortcuts in QT apps
** Changed in: qtbase-opensource-src (Ubuntu Yakkety) Status: Confirmed => Won't Fix ** Changed in: canonical-devices-system-image Status: In Progress => Fix Released ** Changed in: appmenu-qt5 Status: In Progress => Fix Released ** Changed in: qtbase-opensource-src (Ubuntu) Importance: Undecided => Medium ** Changed in: qtbase-opensource-src (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: qtbase-opensource-src (Ubuntu Yakkety) Importance: Undecided => Medium ** Project changed: sni-qt => ubuntu-translations ** No longer affects: ubuntu-translations -- You received this bug notification because you are a member of Ubuntu Translations Coordinators, which is subscribed to Ubuntu Translations. Matching subscriptions: Ubuntu Translations bug mail https://bugs.launchpad.net/bugs/1380702 Title: No keyboards shortcuts in QT apps Status in appmenu-qt5: Fix Released Status in Canonical System Image: Fix Released Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Xenial: Fix Released Status in qtbase-opensource-src source package in Yakkety: Won't Fix Bug description: Impact == This affects all Qt applications on Unity and other desktops which use global menu, either via appmenu-qt5 or via native implementation on Yakkety. Any shortcut is not working if the corresponding action is attached only to the menubar (i.e. and not also to the toolbar). It can be reproduced with almost any application by removing the toolbar (right- clicking on it and deselecting it). Test Case = * Open Qt Assistant; * Press Ctrl+T (this action is not on the toolbar). Expected: a new tab should be opened. Current result: nothing happens. In Yakkety the fix should work both with and without appmenu-qt5. Proposed Fix The proposed fix is a backport of the upstream fix at https://code.qt.io/cgit/qt/qtbase.git/commit/?id=287f548d4c7cc594. Actually just the qshortcut.cpp part would be sufficient, but the other parts make sure it plays fine together with https://cgit.kde.org /plasma-integration.git/commit/?id=aef74e97e2ed462a. Regression Potential The fix is in Zesty for 1½ months now (in upstream even longer), and so far nobody complained. People have verified that the fix works (see comment #63). To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-translations-coordinators Post to : ubuntu-translations-coordinators@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators More help : https://help.launchpad.net/ListHelp
[Ubuntu-translations-coordinators] [Bug 1600136] Re: App indicator does not show icon for Qt apps or with custom icons
** No longer affects: snapd (Ubuntu) ** No longer affects: snapd (Ubuntu Xenial) ** Project changed: snappy => ubuntu-translations ** No longer affects: ubuntu-translations ** Project changed: qt => ubuntu-translations ** No longer affects: ubuntu-translations -- You received this bug notification because you are a member of Ubuntu Translations Coordinators, which is subscribed to Ubuntu Translations. Matching subscriptions: Ubuntu Translations bug mail https://bugs.launchpad.net/bugs/1600136 Title: App indicator does not show icon for Qt apps or with custom icons Status in appmenu-qt5 package in Ubuntu: Fix Released Status in libappindicator package in Ubuntu: Fix Released Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in sni-qt package in Ubuntu: Fix Released Status in appmenu-qt5 source package in Xenial: Fix Released Status in libappindicator source package in Xenial: Fix Released Status in qtbase-opensource-src source package in Xenial: Confirmed Status in sni-qt source package in Xenial: Fix Released Bug description: Snaps that use the app indicator area via Qt can't display their icon there. Steps to reproduce and screenshot: https://github.com/nuttyartist/notes/pull/77 Some research: - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html - The indicator icon is created under /tmp under a randomly generated directory name didrocks mentions also: 1. The application says "this is my menu, and here is my icon at that address", the address being /tmp/blablabla 2. appindicator receives the bus messages 3. and says "let's have a look at this icon at that address" 4. BUT! /tmp in the snap is different form system /tmp SRU bug for libappindicator: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/FpEvQYGN and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run gtk3-appindicator An indicator should open (with proper icon), then if you select "Set icon with Full Path" and/or "Enable Local Theme" from its menu, you should see a proper icon. When snaps are generated in non updated systems, the icon will be still missing. [Regression potential] If $SNAP is defined for an app not running in snap confinement the icons couldn't be properly visible SRU bug for appmenu-qt5: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/KeZ1udjW and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run qt5-systray An indicator should open, with the proper icon showin. From the window you can change the icon type, and all the types should work. When snaps are generated in non updated systems, the icons (except the Themed one) will be still missing. [Regression potential] If $SNAP env variable is defined for an app not running in snap confinement the icons couldn't be properly visible SRU bug for sni-qt: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/EZjQS5CH and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run qt4-systray An indicator should open, with the proper icon showin. From the window you can change the icon type, and all the types should work. When snaps are generated in non updated systems, the icons (except the Themed one) will be still missing. [Regression potential] If $SNAP env variable is defined for an app not running in snap confinement the icons couldn't be properly visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1600136/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-translations-coordinators Post to : ubuntu-translations-coordinators@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators More help : https://help.launchpad.net/ListHelp
[Ubuntu-translations-coordinators] [Bug 1380702] [NEW] No keyboards shortcuts in QT apps
You have been subscribed to a public bug: Impact == This affects all Qt applications on Unity and other desktops which use global menu, either via appmenu-qt5 or via native implementation on Yakkety. Any shortcut is not working if the corresponding action is attached only to the menubar (i.e. and not also to the toolbar). It can be reproduced with almost any application by removing the toolbar (right-clicking on it and deselecting it). Test Case = * Open Qt Assistant; * Press Ctrl+T (this action is not on the toolbar). Expected: a new tab should be opened. Current result: nothing happens. In Yakkety the fix should work both with and without appmenu-qt5. Proposed Fix The proposed fix is a backport of the upstream fix at https://code.qt.io/cgit/qt/qtbase.git/commit/?id=287f548d4c7cc594. Actually just the qshortcut.cpp part would be sufficient, but the other parts make sure it plays fine together with https://cgit.kde.org/plasma- integration.git/commit/?id=aef74e97e2ed462a. Regression Potential The fix is in Zesty for 1½ months now (in upstream even longer), and so far nobody complained. People have verified that the fix works (see comment #63). ** Affects: appmenu-qt5 Importance: High Assignee: Łukasz Zemczak (sil2100) Status: Fix Released ** Affects: canonical-devices-system-image Importance: High Assignee: Łukasz Zemczak (sil2100) Status: Fix Released ** Affects: ubuntu-translations Importance: Undecided Status: New ** Affects: qtbase-opensource-src (Ubuntu) Importance: Medium Assignee: Dmitry Shachnev (mitya57) Status: Fix Released ** Affects: qtbase-opensource-src (Ubuntu Xenial) Importance: Medium Status: Fix Released ** Affects: qtbase-opensource-src (Ubuntu Yakkety) Importance: Medium Status: Won't Fix ** Tags: a11y qt4 qt5 unity8-desktop verification-done-xenial -- No keyboards shortcuts in QT apps https://bugs.launchpad.net/bugs/1380702 You received this bug notification because you are a member of Ubuntu Translations Coordinators, which is subscribed to Ubuntu Translations. ___ Mailing list: https://launchpad.net/~ubuntu-translations-coordinators Post to : ubuntu-translations-coordinators@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators More help : https://help.launchpad.net/ListHelp
[Ubuntu-translations-coordinators] [Bug 1600136] [NEW] App indicator does not show icon for Qt apps or with custom icons
You have been subscribed to a public bug: Snaps that use the app indicator area via Qt can't display their icon there. Steps to reproduce and screenshot: https://github.com/nuttyartist/notes/pull/77 Some research: - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html - The indicator icon is created under /tmp under a randomly generated directory name didrocks mentions also: 1. The application says "this is my menu, and here is my icon at that address", the address being /tmp/blablabla 2. appindicator receives the bus messages 3. and says "let's have a look at this icon at that address" 4. BUT! /tmp in the snap is different form system /tmp SRU bug for libappindicator: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/FpEvQYGN and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run gtk3-appindicator An indicator should open (with proper icon), then if you select "Set icon with Full Path" and/or "Enable Local Theme" from its menu, you should see a proper icon. When snaps are generated in non updated systems, the icon will be still missing. [Regression potential] If $SNAP is defined for an app not running in snap confinement the icons couldn't be properly visible SRU bug for appmenu-qt5: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/KeZ1udjW and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run qt5-systray An indicator should open, with the proper icon showin. From the window you can change the icon type, and all the types should work. When snaps are generated in non updated systems, the icons (except the Themed one) will be still missing. [Regression potential] If $SNAP env variable is defined for an app not running in snap confinement the icons couldn't be properly visible SRU bug for sni-qt: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/EZjQS5CH and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run qt4-systray An indicator should open, with the proper icon showin. From the window you can change the icon type, and all the types should work. When snaps are generated in non updated systems, the icons (except the Themed one) will be still missing. [Regression potential] If $SNAP env variable is defined for an app not running in snap confinement the icons couldn't be properly visible ** Affects: ubuntu-translations Importance: Undecided Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Affects: appmenu-qt5 (Ubuntu) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Released ** Affects: libappindicator (Ubuntu) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Released ** Affects: qtbase-opensource-src (Ubuntu) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Released ** Affects: sni-qt (Ubuntu) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Released ** Affects: appmenu-qt5 (Ubuntu Xenial) Importance: High Status: Fix Released ** Affects: libappindicator (Ubuntu Xenial) Importance: High Status: Fix Released ** Affects: qtbase-opensource-src (Ubuntu Xenial) Importance: High Status: Confirmed ** Affects: sni-qt (Ubuntu Xenial) Importance: High Status: Fix Released ** Tags: isv patch snap-desktop-issue verification-done -- App indicator does not show icon for Qt apps or with custom icons https://bugs.launchpad.net/bugs/1600136 You received this bug notification because you are a member of Ubuntu Translations Coordinators, which is subscribed to Ubuntu Translations. ___ Mailing list: https://launchpad.net/~ubuntu-translations-coordinators Post to : ubuntu-translations-coordinators@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators More help : https://help.launchpad.net/ListHelp
[Ubuntu-translations-coordinators] [Bug 1600136] [NEW] App indicator does not show icon for Qt apps or with custom icons
You have been subscribed to a public bug: Snaps that use the app indicator area via Qt can't display their icon there. Steps to reproduce and screenshot: https://github.com/nuttyartist/notes/pull/77 Some research: - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html - The indicator icon is created under /tmp under a randomly generated directory name didrocks mentions also: 1. The application says "this is my menu, and here is my icon at that address", the address being /tmp/blablabla 2. appindicator receives the bus messages 3. and says "let's have a look at this icon at that address" 4. BUT! /tmp in the snap is different form system /tmp SRU bug for libappindicator: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/FpEvQYGN and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run gtk3-appindicator An indicator should open (with proper icon), then if you select "Set icon with Full Path" and/or "Enable Local Theme" from its menu, you should see a proper icon. When snaps are generated in non updated systems, the icon will be still missing. [Regression potential] If $SNAP is defined for an app not running in snap confinement the icons couldn't be properly visible SRU bug for appmenu-qt5: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/KeZ1udjW and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run qt5-systray An indicator should open, with the proper icon showin. From the window you can change the icon type, and all the types should work. When snaps are generated in non updated systems, the icons (except the Themed one) will be still missing. [Regression potential] If $SNAP env variable is defined for an app not running in snap confinement the icons couldn't be properly visible SRU bug for sni-qt: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/EZjQS5CH and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run qt4-systray An indicator should open, with the proper icon showin. From the window you can change the icon type, and all the types should work. When snaps are generated in non updated systems, the icons (except the Themed one) will be still missing. [Regression potential] If $SNAP env variable is defined for an app not running in snap confinement the icons couldn't be properly visible ** Affects: qt Importance: Undecided Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Affects: ubuntu-translations Importance: Undecided Status: New ** Affects: appmenu-qt5 (Ubuntu) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Released ** Affects: libappindicator (Ubuntu) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Released ** Affects: qtbase-opensource-src (Ubuntu) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Released ** Affects: sni-qt (Ubuntu) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Released ** Affects: appmenu-qt5 (Ubuntu Xenial) Importance: High Status: Fix Released ** Affects: libappindicator (Ubuntu Xenial) Importance: High Status: Fix Released ** Affects: qtbase-opensource-src (Ubuntu Xenial) Importance: High Status: Confirmed ** Affects: sni-qt (Ubuntu Xenial) Importance: High Status: Fix Released ** Tags: isv patch snap-desktop-issue verification-done -- App indicator does not show icon for Qt apps or with custom icons https://bugs.launchpad.net/bugs/1600136 You received this bug notification because you are a member of Ubuntu Translations Coordinators, which is subscribed to Ubuntu Translations. ___ Mailing list: https://launchpad.net/~ubuntu-translations-coordinators Post to : ubuntu-translations-coordinators@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators More help : https://help.launchpad.net/ListHelp
[Ubuntu-translations-coordinators] [Bug 1755061] Re: HAProxyContext on Ubuntu 14.04 generates config that fails to start on boot
** Project changed: charm-helpers => ubuntu-translations
** No longer affects: ubuntu-translations
** Project changed: charm-swift-proxy => ubuntu-translations
** No longer affects: ubuntu-translations
** Project changed: charm-neutron-api => ubuntu-translations
** No longer affects: ubuntu-translations
** Project changed: charm-keystone => ubuntu-translations
** No longer affects: ubuntu-translations
** Project changed: charm-cinder => ubuntu-translations
** No longer affects: ubuntu-translations
** Project changed: charm-glance => ubuntu-translations
** No longer affects: ubuntu-translations
** Project changed: charm-nova-cloud-controller => ubuntu-translations
** No longer affects: ubuntu-translations
--
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1755061
Title:
HAProxyContext on Ubuntu 14.04 generates config that fails to start on
boot
Status in haproxy package in Ubuntu:
Fix Released
Status in haproxy source package in Trusty:
Fix Committed
Bug description:
[Impact]
Valid haproxy configuration directives don't work on trusty as /run/haproxy
does not survive reboots and is not-recreated on daemon start.
[Test Case]
sudo apt install haproxy
configure /etc/haproxy.cfg with a admin socket in /run/haproxy:
global
log /var/lib/haproxy/dev/log local0
log /var/lib/haproxy/dev/log local1 notice
maxconn 2
user haproxy
group haproxy
spread-checks 0
stats socket /var/run/haproxy/admin.sock mode 600 level admin
stats timeout 2m
Restart haproxy (will fail as /{,var/}run/haproxy does not exist)
[Regression Potential]
Minimal - same fix is in later package revisions
[Original Bug Report]
While testing upgrades of an Ubuntu 14.04 deployment of OpenStack from ~15.04
to 17.11 charms, I noticed that a number of the OpenStack charmed services
failed to start haproxy when I rebooted their units: cinder, glance, keystone,
neutron-api, nova-cloud-controller, and swift-proxy.
The following was in /var/log/boot.log:
[ALERT] 069/225906 (1100) : cannot bind socket for UNIX listener
(/var/run/haproxy/admin.sock). Aborting.
[ALERT] 069/225906 (1100) : [/usr/sbin/haproxy.main()] Some protocols failed
to start their listeners! Exiting.
* Starting haproxy haproxy
[fail]
The charm created /var/run/haproxy, but since /var/run (really /run)
is a tmpfs, this did not survive the reboot and so haproxy could not
create the socket.
I compared the haproxy.cfg the charm creates with the default config
shipped by the Ubuntu 16.04 haproxy package, and it seems that
charmhelpers/contrib/openstack/templates/haproxy.cfg is closely based
on the package, including the admin.sock directive. However, on
Ubuntu 16.04, /etc/init.d/haproxy ensures that /var/run/haproxy exists
before it starts haproxy:
[agnew(work)] diff -u haproxy-1.4.24/debian/haproxy.init
haproxy-1.6.3/debian/haproxy.init
--- haproxy-1.4.24/debian/haproxy.init 2015-12-16 03:55:29.0 +1300
+++ haproxy-1.6.3/debian/haproxy.init 2015-12-31 20:10:38.0 +1300
[...]
@@ -50,6 +41,10 @@
haproxy_start()
{
+ [ -d "$RUNDIR" ] || mkdir "$RUNDIR"
+ chown haproxy:haproxy "$RUNDIR"
+ chmod 2775 "$RUNDIR"
+
check_haproxy_config
start-stop-daemon --quiet --oknodo --start --pidfile "$PIDFILE" \
[...]
charm-helpers or the OpenStack charms or both should be updated so
that haproxy will start on boot when running on Ubuntu 14.04.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1755061/+subscriptions
___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help : https://help.launchpad.net/ListHelp
[Ubuntu-translations-coordinators] [Bug 1755061] [NEW] HAProxyContext on Ubuntu 14.04 generates config that fails to start on boot
You have been subscribed to a public bug:
[Impact]
Valid haproxy configuration directives don't work on trusty as /run/haproxy
does not survive reboots and is not-recreated on daemon start.
[Test Case]
sudo apt install haproxy
configure /etc/haproxy.cfg with a admin socket in /run/haproxy:
global
log /var/lib/haproxy/dev/log local0
log /var/lib/haproxy/dev/log local1 notice
maxconn 2
user haproxy
group haproxy
spread-checks 0
stats socket /var/run/haproxy/admin.sock mode 600 level admin
stats timeout 2m
Restart haproxy (will fail as /{,var/}run/haproxy does not exist)
[Regression Potential]
Minimal - same fix is in later package revisions
[Original Bug Report]
While testing upgrades of an Ubuntu 14.04 deployment of OpenStack from ~15.04
to 17.11 charms, I noticed that a number of the OpenStack charmed services
failed to start haproxy when I rebooted their units: cinder, glance, keystone,
neutron-api, nova-cloud-controller, and swift-proxy.
The following was in /var/log/boot.log:
[ALERT] 069/225906 (1100) : cannot bind socket for UNIX listener
(/var/run/haproxy/admin.sock). Aborting.
[ALERT] 069/225906 (1100) : [/usr/sbin/haproxy.main()] Some protocols failed to
start their listeners! Exiting.
* Starting haproxy haproxy [fail]
The charm created /var/run/haproxy, but since /var/run (really /run) is
a tmpfs, this did not survive the reboot and so haproxy could not create
the socket.
I compared the haproxy.cfg the charm creates with the default config
shipped by the Ubuntu 16.04 haproxy package, and it seems that
charmhelpers/contrib/openstack/templates/haproxy.cfg is closely based on
the package, including the admin.sock directive. However, on Ubuntu
16.04, /etc/init.d/haproxy ensures that /var/run/haproxy exists before
it starts haproxy:
[agnew(work)] diff -u haproxy-1.4.24/debian/haproxy.init
haproxy-1.6.3/debian/haproxy.init
--- haproxy-1.4.24/debian/haproxy.init 2015-12-16 03:55:29.0 +1300
+++ haproxy-1.6.3/debian/haproxy.init 2015-12-31 20:10:38.0 +1300
[...]
@@ -50,6 +41,10 @@
haproxy_start()
{
+ [ -d "$RUNDIR" ] || mkdir "$RUNDIR"
+ chown haproxy:haproxy "$RUNDIR"
+ chmod 2775 "$RUNDIR"
+
check_haproxy_config
start-stop-daemon --quiet --oknodo --start --pidfile "$PIDFILE" \
[...]
charm-helpers or the OpenStack charms or both should be updated so that
haproxy will start on boot when running on Ubuntu 14.04.
** Affects: ubuntu-translations
Importance: High
Status: Invalid
** Affects: haproxy (Ubuntu)
Importance: High
Status: Fix Released
** Affects: haproxy (Ubuntu Trusty)
Importance: High
Assignee: James Page (james-page)
Status: Fix Committed
** Tags: canonical-is-ps45-1711-upgrade verification-needed
verification-needed-trusty
--
HAProxyContext on Ubuntu 14.04 generates config that fails to start on boot
https://bugs.launchpad.net/bugs/1755061
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help : https://help.launchpad.net/ListHelp
[Ubuntu-translations-coordinators] [Bug 1755061] [NEW] HAProxyContext on Ubuntu 14.04 generates config that fails to start on boot
You have been subscribed to a public bug:
[Impact]
Valid haproxy configuration directives don't work on trusty as /run/haproxy
does not survive reboots and is not-recreated on daemon start.
[Test Case]
sudo apt install haproxy
configure /etc/haproxy.cfg with a admin socket in /run/haproxy:
global
log /var/lib/haproxy/dev/log local0
log /var/lib/haproxy/dev/log local1 notice
maxconn 2
user haproxy
group haproxy
spread-checks 0
stats socket /var/run/haproxy/admin.sock mode 600 level admin
stats timeout 2m
Restart haproxy (will fail as /{,var/}run/haproxy does not exist)
[Regression Potential]
Minimal - same fix is in later package revisions
[Original Bug Report]
While testing upgrades of an Ubuntu 14.04 deployment of OpenStack from ~15.04
to 17.11 charms, I noticed that a number of the OpenStack charmed services
failed to start haproxy when I rebooted their units: cinder, glance, keystone,
neutron-api, nova-cloud-controller, and swift-proxy.
The following was in /var/log/boot.log:
[ALERT] 069/225906 (1100) : cannot bind socket for UNIX listener
(/var/run/haproxy/admin.sock). Aborting.
[ALERT] 069/225906 (1100) : [/usr/sbin/haproxy.main()] Some protocols failed to
start their listeners! Exiting.
* Starting haproxy haproxy [fail]
The charm created /var/run/haproxy, but since /var/run (really /run) is
a tmpfs, this did not survive the reboot and so haproxy could not create
the socket.
I compared the haproxy.cfg the charm creates with the default config
shipped by the Ubuntu 16.04 haproxy package, and it seems that
charmhelpers/contrib/openstack/templates/haproxy.cfg is closely based on
the package, including the admin.sock directive. However, on Ubuntu
16.04, /etc/init.d/haproxy ensures that /var/run/haproxy exists before
it starts haproxy:
[agnew(work)] diff -u haproxy-1.4.24/debian/haproxy.init
haproxy-1.6.3/debian/haproxy.init
--- haproxy-1.4.24/debian/haproxy.init 2015-12-16 03:55:29.0 +1300
+++ haproxy-1.6.3/debian/haproxy.init 2015-12-31 20:10:38.0 +1300
[...]
@@ -50,6 +41,10 @@
haproxy_start()
{
+ [ -d "$RUNDIR" ] || mkdir "$RUNDIR"
+ chown haproxy:haproxy "$RUNDIR"
+ chmod 2775 "$RUNDIR"
+
check_haproxy_config
start-stop-daemon --quiet --oknodo --start --pidfile "$PIDFILE" \
[...]
charm-helpers or the OpenStack charms or both should be updated so that
haproxy will start on boot when running on Ubuntu 14.04.
** Affects: ubuntu-translations
Importance: High
Status: Invalid
** Affects: charm-nova-cloud-controller
Importance: High
Status: Invalid
** Affects: haproxy (Ubuntu)
Importance: High
Status: Fix Released
** Affects: haproxy (Ubuntu Trusty)
Importance: High
Assignee: James Page (james-page)
Status: Fix Committed
** Tags: canonical-is-ps45-1711-upgrade verification-needed
verification-needed-trusty
--
HAProxyContext on Ubuntu 14.04 generates config that fails to start on boot
https://bugs.launchpad.net/bugs/1755061
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help : https://help.launchpad.net/ListHelp
[Ubuntu-translations-coordinators] [Bug 1755061] [NEW] HAProxyContext on Ubuntu 14.04 generates config that fails to start on boot
You have been subscribed to a public bug:
[Impact]
Valid haproxy configuration directives don't work on trusty as /run/haproxy
does not survive reboots and is not-recreated on daemon start.
[Test Case]
sudo apt install haproxy
configure /etc/haproxy.cfg with a admin socket in /run/haproxy:
global
log /var/lib/haproxy/dev/log local0
log /var/lib/haproxy/dev/log local1 notice
maxconn 2
user haproxy
group haproxy
spread-checks 0
stats socket /var/run/haproxy/admin.sock mode 600 level admin
stats timeout 2m
Restart haproxy (will fail as /{,var/}run/haproxy does not exist)
[Regression Potential]
Minimal - same fix is in later package revisions
[Original Bug Report]
While testing upgrades of an Ubuntu 14.04 deployment of OpenStack from ~15.04
to 17.11 charms, I noticed that a number of the OpenStack charmed services
failed to start haproxy when I rebooted their units: cinder, glance, keystone,
neutron-api, nova-cloud-controller, and swift-proxy.
The following was in /var/log/boot.log:
[ALERT] 069/225906 (1100) : cannot bind socket for UNIX listener
(/var/run/haproxy/admin.sock). Aborting.
[ALERT] 069/225906 (1100) : [/usr/sbin/haproxy.main()] Some protocols failed to
start their listeners! Exiting.
* Starting haproxy haproxy [fail]
The charm created /var/run/haproxy, but since /var/run (really /run) is
a tmpfs, this did not survive the reboot and so haproxy could not create
the socket.
I compared the haproxy.cfg the charm creates with the default config
shipped by the Ubuntu 16.04 haproxy package, and it seems that
charmhelpers/contrib/openstack/templates/haproxy.cfg is closely based on
the package, including the admin.sock directive. However, on Ubuntu
16.04, /etc/init.d/haproxy ensures that /var/run/haproxy exists before
it starts haproxy:
[agnew(work)] diff -u haproxy-1.4.24/debian/haproxy.init
haproxy-1.6.3/debian/haproxy.init
--- haproxy-1.4.24/debian/haproxy.init 2015-12-16 03:55:29.0 +1300
+++ haproxy-1.6.3/debian/haproxy.init 2015-12-31 20:10:38.0 +1300
[...]
@@ -50,6 +41,10 @@
haproxy_start()
{
+ [ -d "$RUNDIR" ] || mkdir "$RUNDIR"
+ chown haproxy:haproxy "$RUNDIR"
+ chmod 2775 "$RUNDIR"
+
check_haproxy_config
start-stop-daemon --quiet --oknodo --start --pidfile "$PIDFILE" \
[...]
charm-helpers or the OpenStack charms or both should be updated so that
haproxy will start on boot when running on Ubuntu 14.04.
** Affects: charm-cinder
Importance: High
Status: Invalid
** Affects: charm-glance
Importance: High
Status: Invalid
** Affects: ubuntu-translations
Importance: High
Status: Invalid
** Affects: charm-nova-cloud-controller
Importance: High
Status: Invalid
** Affects: haproxy (Ubuntu)
Importance: High
Status: Fix Released
** Affects: haproxy (Ubuntu Trusty)
Importance: High
Assignee: James Page (james-page)
Status: Fix Committed
** Tags: canonical-is-ps45-1711-upgrade verification-needed
verification-needed-trusty
--
HAProxyContext on Ubuntu 14.04 generates config that fails to start on boot
https://bugs.launchpad.net/bugs/1755061
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help : https://help.launchpad.net/ListHelp
[Ubuntu-translations-coordinators] [Bug 1755061] [NEW] HAProxyContext on Ubuntu 14.04 generates config that fails to start on boot
You have been subscribed to a public bug:
[Impact]
Valid haproxy configuration directives don't work on trusty as /run/haproxy
does not survive reboots and is not-recreated on daemon start.
[Test Case]
sudo apt install haproxy
configure /etc/haproxy.cfg with a admin socket in /run/haproxy:
global
log /var/lib/haproxy/dev/log local0
log /var/lib/haproxy/dev/log local1 notice
maxconn 2
user haproxy
group haproxy
spread-checks 0
stats socket /var/run/haproxy/admin.sock mode 600 level admin
stats timeout 2m
Restart haproxy (will fail as /{,var/}run/haproxy does not exist)
[Regression Potential]
Minimal - same fix is in later package revisions
[Original Bug Report]
While testing upgrades of an Ubuntu 14.04 deployment of OpenStack from ~15.04
to 17.11 charms, I noticed that a number of the OpenStack charmed services
failed to start haproxy when I rebooted their units: cinder, glance, keystone,
neutron-api, nova-cloud-controller, and swift-proxy.
The following was in /var/log/boot.log:
[ALERT] 069/225906 (1100) : cannot bind socket for UNIX listener
(/var/run/haproxy/admin.sock). Aborting.
[ALERT] 069/225906 (1100) : [/usr/sbin/haproxy.main()] Some protocols failed to
start their listeners! Exiting.
* Starting haproxy haproxy [fail]
The charm created /var/run/haproxy, but since /var/run (really /run) is
a tmpfs, this did not survive the reboot and so haproxy could not create
the socket.
I compared the haproxy.cfg the charm creates with the default config
shipped by the Ubuntu 16.04 haproxy package, and it seems that
charmhelpers/contrib/openstack/templates/haproxy.cfg is closely based on
the package, including the admin.sock directive. However, on Ubuntu
16.04, /etc/init.d/haproxy ensures that /var/run/haproxy exists before
it starts haproxy:
[agnew(work)] diff -u haproxy-1.4.24/debian/haproxy.init
haproxy-1.6.3/debian/haproxy.init
--- haproxy-1.4.24/debian/haproxy.init 2015-12-16 03:55:29.0 +1300
+++ haproxy-1.6.3/debian/haproxy.init 2015-12-31 20:10:38.0 +1300
[...]
@@ -50,6 +41,10 @@
haproxy_start()
{
+ [ -d "$RUNDIR" ] || mkdir "$RUNDIR"
+ chown haproxy:haproxy "$RUNDIR"
+ chmod 2775 "$RUNDIR"
+
check_haproxy_config
start-stop-daemon --quiet --oknodo --start --pidfile "$PIDFILE" \
[...]
charm-helpers or the OpenStack charms or both should be updated so that
haproxy will start on boot when running on Ubuntu 14.04.
** Affects: ubuntu-translations
Importance: High
Status: Invalid
** Affects: charm-glance
Importance: High
Status: Invalid
** Affects: charm-nova-cloud-controller
Importance: High
Status: Invalid
** Affects: haproxy (Ubuntu)
Importance: High
Status: Fix Released
** Affects: haproxy (Ubuntu Trusty)
Importance: High
Assignee: James Page (james-page)
Status: Fix Committed
** Tags: canonical-is-ps45-1711-upgrade verification-needed
verification-needed-trusty
--
HAProxyContext on Ubuntu 14.04 generates config that fails to start on boot
https://bugs.launchpad.net/bugs/1755061
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help : https://help.launchpad.net/ListHelp
[Ubuntu-translations-coordinators] [Bug 1755061] [NEW] HAProxyContext on Ubuntu 14.04 generates config that fails to start on boot
You have been subscribed to a public bug:
[Impact]
Valid haproxy configuration directives don't work on trusty as /run/haproxy
does not survive reboots and is not-recreated on daemon start.
[Test Case]
sudo apt install haproxy
configure /etc/haproxy.cfg with a admin socket in /run/haproxy:
global
log /var/lib/haproxy/dev/log local0
log /var/lib/haproxy/dev/log local1 notice
maxconn 2
user haproxy
group haproxy
spread-checks 0
stats socket /var/run/haproxy/admin.sock mode 600 level admin
stats timeout 2m
Restart haproxy (will fail as /{,var/}run/haproxy does not exist)
[Regression Potential]
Minimal - same fix is in later package revisions
[Original Bug Report]
While testing upgrades of an Ubuntu 14.04 deployment of OpenStack from ~15.04
to 17.11 charms, I noticed that a number of the OpenStack charmed services
failed to start haproxy when I rebooted their units: cinder, glance, keystone,
neutron-api, nova-cloud-controller, and swift-proxy.
The following was in /var/log/boot.log:
[ALERT] 069/225906 (1100) : cannot bind socket for UNIX listener
(/var/run/haproxy/admin.sock). Aborting.
[ALERT] 069/225906 (1100) : [/usr/sbin/haproxy.main()] Some protocols failed to
start their listeners! Exiting.
* Starting haproxy haproxy [fail]
The charm created /var/run/haproxy, but since /var/run (really /run) is
a tmpfs, this did not survive the reboot and so haproxy could not create
the socket.
I compared the haproxy.cfg the charm creates with the default config
shipped by the Ubuntu 16.04 haproxy package, and it seems that
charmhelpers/contrib/openstack/templates/haproxy.cfg is closely based on
the package, including the admin.sock directive. However, on Ubuntu
16.04, /etc/init.d/haproxy ensures that /var/run/haproxy exists before
it starts haproxy:
[agnew(work)] diff -u haproxy-1.4.24/debian/haproxy.init
haproxy-1.6.3/debian/haproxy.init
--- haproxy-1.4.24/debian/haproxy.init 2015-12-16 03:55:29.0 +1300
+++ haproxy-1.6.3/debian/haproxy.init 2015-12-31 20:10:38.0 +1300
[...]
@@ -50,6 +41,10 @@
haproxy_start()
{
+ [ -d "$RUNDIR" ] || mkdir "$RUNDIR"
+ chown haproxy:haproxy "$RUNDIR"
+ chmod 2775 "$RUNDIR"
+
check_haproxy_config
start-stop-daemon --quiet --oknodo --start --pidfile "$PIDFILE" \
[...]
charm-helpers or the OpenStack charms or both should be updated so that
haproxy will start on boot when running on Ubuntu 14.04.
** Affects: charm-cinder
Importance: High
Status: Invalid
** Affects: charm-glance
Importance: High
Status: Invalid
** Affects: charm-keystone
Importance: High
Status: Invalid
** Affects: charm-neutron-api
Importance: High
Status: Invalid
** Affects: charm-nova-cloud-controller
Importance: High
Status: Invalid
** Affects: ubuntu-translations
Importance: High
Status: Invalid
** Affects: haproxy (Ubuntu)
Importance: High
Status: Fix Released
** Affects: haproxy (Ubuntu Trusty)
Importance: High
Assignee: James Page (james-page)
Status: Fix Committed
** Tags: canonical-is-ps45-1711-upgrade verification-needed
verification-needed-trusty
--
HAProxyContext on Ubuntu 14.04 generates config that fails to start on boot
https://bugs.launchpad.net/bugs/1755061
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help : https://help.launchpad.net/ListHelp
[Ubuntu-translations-coordinators] [Bug 1755061] [NEW] HAProxyContext on Ubuntu 14.04 generates config that fails to start on boot
You have been subscribed to a public bug:
[Impact]
Valid haproxy configuration directives don't work on trusty as /run/haproxy
does not survive reboots and is not-recreated on daemon start.
[Test Case]
sudo apt install haproxy
configure /etc/haproxy.cfg with a admin socket in /run/haproxy:
global
log /var/lib/haproxy/dev/log local0
log /var/lib/haproxy/dev/log local1 notice
maxconn 2
user haproxy
group haproxy
spread-checks 0
stats socket /var/run/haproxy/admin.sock mode 600 level admin
stats timeout 2m
Restart haproxy (will fail as /{,var/}run/haproxy does not exist)
[Regression Potential]
Minimal - same fix is in later package revisions
[Original Bug Report]
While testing upgrades of an Ubuntu 14.04 deployment of OpenStack from ~15.04
to 17.11 charms, I noticed that a number of the OpenStack charmed services
failed to start haproxy when I rebooted their units: cinder, glance, keystone,
neutron-api, nova-cloud-controller, and swift-proxy.
The following was in /var/log/boot.log:
[ALERT] 069/225906 (1100) : cannot bind socket for UNIX listener
(/var/run/haproxy/admin.sock). Aborting.
[ALERT] 069/225906 (1100) : [/usr/sbin/haproxy.main()] Some protocols failed to
start their listeners! Exiting.
* Starting haproxy haproxy [fail]
The charm created /var/run/haproxy, but since /var/run (really /run) is
a tmpfs, this did not survive the reboot and so haproxy could not create
the socket.
I compared the haproxy.cfg the charm creates with the default config
shipped by the Ubuntu 16.04 haproxy package, and it seems that
charmhelpers/contrib/openstack/templates/haproxy.cfg is closely based on
the package, including the admin.sock directive. However, on Ubuntu
16.04, /etc/init.d/haproxy ensures that /var/run/haproxy exists before
it starts haproxy:
[agnew(work)] diff -u haproxy-1.4.24/debian/haproxy.init
haproxy-1.6.3/debian/haproxy.init
--- haproxy-1.4.24/debian/haproxy.init 2015-12-16 03:55:29.0 +1300
+++ haproxy-1.6.3/debian/haproxy.init 2015-12-31 20:10:38.0 +1300
[...]
@@ -50,6 +41,10 @@
haproxy_start()
{
+ [ -d "$RUNDIR" ] || mkdir "$RUNDIR"
+ chown haproxy:haproxy "$RUNDIR"
+ chmod 2775 "$RUNDIR"
+
check_haproxy_config
start-stop-daemon --quiet --oknodo --start --pidfile "$PIDFILE" \
[...]
charm-helpers or the OpenStack charms or both should be updated so that
haproxy will start on boot when running on Ubuntu 14.04.
** Affects: charm-cinder
Importance: High
Status: Invalid
** Affects: charm-glance
Importance: High
Status: Invalid
** Affects: charm-keystone
Importance: High
Status: Invalid
** Affects: ubuntu-translations
Importance: High
Status: Invalid
** Affects: charm-nova-cloud-controller
Importance: High
Status: Invalid
** Affects: haproxy (Ubuntu)
Importance: High
Status: Fix Released
** Affects: haproxy (Ubuntu Trusty)
Importance: High
Assignee: James Page (james-page)
Status: Fix Committed
** Tags: canonical-is-ps45-1711-upgrade verification-needed
verification-needed-trusty
--
HAProxyContext on Ubuntu 14.04 generates config that fails to start on boot
https://bugs.launchpad.net/bugs/1755061
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help : https://help.launchpad.net/ListHelp
[Ubuntu-translations-coordinators] [Bug 1755061] [NEW] HAProxyContext on Ubuntu 14.04 generates config that fails to start on boot
You have been subscribed to a public bug:
[Impact]
Valid haproxy configuration directives don't work on trusty as /run/haproxy
does not survive reboots and is not-recreated on daemon start.
[Test Case]
sudo apt install haproxy
configure /etc/haproxy.cfg with a admin socket in /run/haproxy:
global
log /var/lib/haproxy/dev/log local0
log /var/lib/haproxy/dev/log local1 notice
maxconn 2
user haproxy
group haproxy
spread-checks 0
stats socket /var/run/haproxy/admin.sock mode 600 level admin
stats timeout 2m
Restart haproxy (will fail as /{,var/}run/haproxy does not exist)
[Regression Potential]
Minimal - same fix is in later package revisions
[Original Bug Report]
While testing upgrades of an Ubuntu 14.04 deployment of OpenStack from ~15.04
to 17.11 charms, I noticed that a number of the OpenStack charmed services
failed to start haproxy when I rebooted their units: cinder, glance, keystone,
neutron-api, nova-cloud-controller, and swift-proxy.
The following was in /var/log/boot.log:
[ALERT] 069/225906 (1100) : cannot bind socket for UNIX listener
(/var/run/haproxy/admin.sock). Aborting.
[ALERT] 069/225906 (1100) : [/usr/sbin/haproxy.main()] Some protocols failed to
start their listeners! Exiting.
* Starting haproxy haproxy [fail]
The charm created /var/run/haproxy, but since /var/run (really /run) is
a tmpfs, this did not survive the reboot and so haproxy could not create
the socket.
I compared the haproxy.cfg the charm creates with the default config
shipped by the Ubuntu 16.04 haproxy package, and it seems that
charmhelpers/contrib/openstack/templates/haproxy.cfg is closely based on
the package, including the admin.sock directive. However, on Ubuntu
16.04, /etc/init.d/haproxy ensures that /var/run/haproxy exists before
it starts haproxy:
[agnew(work)] diff -u haproxy-1.4.24/debian/haproxy.init
haproxy-1.6.3/debian/haproxy.init
--- haproxy-1.4.24/debian/haproxy.init 2015-12-16 03:55:29.0 +1300
+++ haproxy-1.6.3/debian/haproxy.init 2015-12-31 20:10:38.0 +1300
[...]
@@ -50,6 +41,10 @@
haproxy_start()
{
+ [ -d "$RUNDIR" ] || mkdir "$RUNDIR"
+ chown haproxy:haproxy "$RUNDIR"
+ chmod 2775 "$RUNDIR"
+
check_haproxy_config
start-stop-daemon --quiet --oknodo --start --pidfile "$PIDFILE" \
[...]
charm-helpers or the OpenStack charms or both should be updated so that
haproxy will start on boot when running on Ubuntu 14.04.
** Affects: charm-cinder
Importance: High
Status: Invalid
** Affects: charm-glance
Importance: High
Status: Invalid
** Affects: ubuntu-translations
Importance: High
Status: Invalid
** Affects: charm-keystone
Importance: High
Status: Invalid
** Affects: charm-neutron-api
Importance: High
Status: Invalid
** Affects: charm-nova-cloud-controller
Importance: High
Status: Invalid
** Affects: charm-swift-proxy
Importance: High
Status: Invalid
** Affects: haproxy (Ubuntu)
Importance: High
Status: Fix Released
** Affects: haproxy (Ubuntu Trusty)
Importance: High
Assignee: James Page (james-page)
Status: Fix Committed
** Tags: canonical-is-ps45-1711-upgrade verification-needed
verification-needed-trusty
--
HAProxyContext on Ubuntu 14.04 generates config that fails to start on boot
https://bugs.launchpad.net/bugs/1755061
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help : https://help.launchpad.net/ListHelp
[Ubuntu-translations-coordinators] [Bug 1415880] Re: 14e4:4365 bcmwl-kernel source: fix for null pointer crash
** Project changed: dell-sputnik => ubuntu-translations ** No longer affects: ubuntu-translations -- You received this bug notification because you are a member of Ubuntu Translations Coordinators, which is subscribed to Ubuntu Translations. Matching subscriptions: Ubuntu Translations bug mail https://bugs.launchpad.net/bugs/1415880 Title: 14e4:4365 bcmwl-kernel source: fix for null pointer crash Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Precise: Won't Fix Status in bcmwl source package in Trusty: Fix Committed Status in bcmwl source package in Vivid: Won't Fix Status in bcmwl source package in Wily: Fix Released Bug description: [Impact] * bcmwl does not compile on new kernels (or HWE kernels) * bcmwl suffers from null reference bug [Test Case] * public PPA provided to community and feedback * based on patch available to other distros * comment #42 [Regression Potential] * for changes on kernel support it may not compile (tested with 3.2, 3.13, 3.18 and 4.2) * for the null reference change -> proved to fix problem for community based on feedback [Other Info] Original bug description: The bcmwl package as of now misses one patch for a bug that occurs with BCM43142 and possibly other broadcom chipsets that will look like random disconnects, poor wifi signal and kernel warnings, See also #1379524. Adding the patch is a fairly simple process: * put the patch file in /usr/src/bcmwl-6.30.223.248+bdcom/patches * add the following line to /usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf PATCH[7]="0014-null-pointer-crash.patch" * run: /usr/lib/dkms/common.postinst bcmwl 6.30.223.248+bdcom /usr/share/bcmwl x86_64 $(uname -r) This has fixed the issue for me. Edit: I just wanted to add that I did not write the patch; I merely downloaded it from a paste that was linked from the respective AUR package. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 [modified: usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf] ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: LXDE Date: Thu Jan 29 13:15:17 2015 InstallationDate: Installed on 2015-01-26 (3 days ago) InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1415880/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-translations-coordinators Post to : ubuntu-translations-coordinators@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators More help : https://help.launchpad.net/ListHelp
[Ubuntu-translations-coordinators] [Bug 1415880] [NEW] 14e4:4365 bcmwl-kernel source: fix for null pointer crash
You have been subscribed to a public bug: [Impact] * bcmwl does not compile on new kernels (or HWE kernels) * bcmwl suffers from null reference bug [Test Case] * public PPA provided to community and feedback * based on patch available to other distros * comment #42 [Regression Potential] * for changes on kernel support it may not compile (tested with 3.2, 3.13, 3.18 and 4.2) * for the null reference change -> proved to fix problem for community based on feedback [Other Info] Original bug description: The bcmwl package as of now misses one patch for a bug that occurs with BCM43142 and possibly other broadcom chipsets that will look like random disconnects, poor wifi signal and kernel warnings, See also #1379524. Adding the patch is a fairly simple process: * put the patch file in /usr/src/bcmwl-6.30.223.248+bdcom/patches * add the following line to /usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf PATCH[7]="0014-null-pointer-crash.patch" * run: /usr/lib/dkms/common.postinst bcmwl 6.30.223.248+bdcom /usr/share/bcmwl x86_64 $(uname -r) This has fixed the issue for me. Edit: I just wanted to add that I did not write the patch; I merely downloaded it from a paste that was linked from the respective AUR package. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu1 [modified: usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf] ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CurrentDesktop: LXDE Date: Thu Jan 29 13:15:17 2015 InstallationDate: Installed on 2015-01-26 (3 days ago) InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-translations Importance: Undecided Status: Confirmed ** Affects: bcmwl (Ubuntu) Importance: High Assignee: Rafael David Tinoco (inaddy) Status: Fix Released ** Affects: bcmwl (Ubuntu Precise) Importance: High Assignee: Rafael David Tinoco (inaddy) Status: Won't Fix ** Affects: bcmwl (Ubuntu Trusty) Importance: High Status: Fix Committed ** Affects: bcmwl (Ubuntu Vivid) Importance: High Assignee: Rafael David Tinoco (inaddy) Status: Won't Fix ** Affects: bcmwl (Ubuntu Wily) Importance: High Assignee: Rafael David Tinoco (inaddy) Status: Fix Released ** Tags: amd64 apport-bug iso-testing latest-bios-8dcn40ww patch removal-candidate utopic verification-needed vivid -- 14e4:4365 bcmwl-kernel source: fix for null pointer crash https://bugs.launchpad.net/bugs/1415880 You received this bug notification because you are a member of Ubuntu Translations Coordinators, which is subscribed to Ubuntu Translations. ___ Mailing list: https://launchpad.net/~ubuntu-translations-coordinators Post to : ubuntu-translations-coordinators@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators More help : https://help.launchpad.net/ListHelp
[Ubuntu-translations-coordinators] [Bug 1173761] Re: 14e4:43b1 Broadcom Corporation Device 43b1 (rev 03) - not supported
** No longer affects: broadcom-sta (Ubuntu) ** Project changed: broadcom => ubuntu-translations ** No longer affects: ubuntu-translations -- You received this bug notification because you are a member of Ubuntu Translations Coordinators, which is subscribed to Ubuntu Translations. Matching subscriptions: Ubuntu Translations bug mail https://bugs.launchpad.net/bugs/1173761 Title: 14e4:43b1 Broadcom Corporation Device 43b1 (rev 03) - not supported Status in bcmwl package in Ubuntu: Fix Released Status in bcmwl source package in Trusty: Fix Committed Bug description: Both during and after installation, 13.04 doesn't support the Broadcom-based 802.11ac wifi chipsets. lspci reports it as "Network controller: Broadcom Corporation Device 43b1 (rev 03)". WORKAROUND: 6_30_223_95 driver in http://people.canonical.com/~ypwong/drivers/broadcom/ , install an old version: https://launchpad.net/ubuntu/saucy/amd64/bcmwl-kernel- source/6.30.223.30+bdcom-0ubuntu3 (found at http://gaspuu.blogspot.no/2014/05/dell-precision-m4800-with-ubuntu- linux.html), or simply replace the wifi module with another one with better driver support (if laptop has no whitelist for modules). --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes InstallationDate: Installed on 2013-04-27 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) Tags: raring Uname: Linux 3.9.0-030900rc8-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: atrauzzi 2141 F pulseaudio /dev/snd/controlC0: atrauzzi 2141 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: [ 176.287266] atl1c :04:00.0: vpd r/w failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update. DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=90e84f80-b3fc-4480-b4cd-21d15e3abc6d InstallationDate: Installed on 2013-04-27 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: ASUSTeK COMPUTER INC. G75VX MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=b0911040-5a49-4581-9a7a-bac9d830a0ba ro nomodeset quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 StagingDrivers: r8712u Tags: raring staging Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 10/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G75VX.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G75VX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG75VX.203:bd10/23/2012:svnASUSTeKCOMPUTERINC.:pnG75VX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG75VX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: G75VX dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1173761/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-translations-coordinators Post to : ubuntu-translations-coordinators@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators More help : https://help.launchpad.net/ListHelp
[Ubuntu-translations-coordinators] [Bug 1173761] [NEW] 14e4:43b1 Broadcom Corporation Device 43b1 (rev 03) - not supported
You have been subscribed to a public bug: Both during and after installation, 13.04 doesn't support the Broadcom- based 802.11ac wifi chipsets. lspci reports it as "Network controller: Broadcom Corporation Device 43b1 (rev 03)". WORKAROUND: 6_30_223_95 driver in http://people.canonical.com/~ypwong/drivers/broadcom/ , install an old version: https://launchpad.net/ubuntu/saucy/amd64/bcmwl-kernel- source/6.30.223.30+bdcom-0ubuntu3 (found at http://gaspuu.blogspot.no/2014/05/dell-precision-m4800-with-ubuntu- linux.html), or simply replace the wifi module with another one with better driver support (if laptop has no whitelist for modules). --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes InstallationDate: Installed on 2013-04-27 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) Tags: raring Uname: Linux 3.9.0-030900rc8-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo --- ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: atrauzzi 2141 F pulseaudio /dev/snd/controlC0: atrauzzi 2141 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: [ 176.287266] atl1c :04:00.0: vpd r/w failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update. DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=90e84f80-b3fc-4480-b4cd-21d15e3abc6d InstallationDate: Installed on 2013-04-27 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: ASUSTeK COMPUTER INC. G75VX MarkForUpload: True NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=b0911040-5a49-4581-9a7a-bac9d830a0ba ro nomodeset quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 StagingDrivers: r8712u Tags: raring staging Uname: Linux 3.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 10/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G75VX.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G75VX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG75VX.203:bd10/23/2012:svnASUSTeKCOMPUTERINC.:pnG75VX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG75VX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: G75VX dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: ubuntu-translations Importance: Undecided Status: New ** Affects: bcmwl (Ubuntu) Importance: Wishlist Status: Fix Released ** Affects: bcmwl (Ubuntu Trusty) Importance: Wishlist Status: Fix Committed ** Tags: apport-collected bios-outdated-206 bot-comment metabug raring removal-candidate staging verification-needed -- 14e4:43b1 Broadcom Corporation Device 43b1 (rev 03) - not supported https://bugs.launchpad.net/bugs/1173761 You received this bug notification because you are a member of Ubuntu Translations Coordinators, which is subscribed to Ubuntu Translations. ___ Mailing list: https://launchpad.net/~ubuntu-translations-coordinators Post to : ubuntu-translations-coordinators@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators More help : https://help.launchpad.net/ListHelp
