[Desktop-packages] [Bug 1833322] Comment bridged from LTC Bugzilla
Now? CPUs are faster; if you disable irqtune, you can observe in /proc/interrupts that various device interrupts are still sent to CPUs other than CPU0, they just don't go ping-ponging around between all of them like they do with irqtune. A big difference compared to the early days, for example for ethernet a lot of the work that was done in the interrupt handler back then, the interrupt handler now does the bare minimum and does the rest of the work with a kernel thread (same for wifi, which tends to be a bit of an interrupt and CPU hog). Meaning the actual interrupts take much less time to run now than they did then. The total CPU time could still add up to more than 1 core can handle if you had, say, 10gbps ethernet. But the kernel threads can be scheduled to any CPU core just like any other thread even if the interrupts are tied to one CPU. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Please consider no more having irqbalance enabled by default (per image/use-case/TBD) Status in Ubuntu on IBM z Systems: Confirmed Status in irqbalance package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop"; SUPPORT_URL="http://support.system76.com"; BUG_REPORT_URL="https://github.com/pop-os/pop/issues"; PRIVACY_POLICY_URL="https://system76.com/privacy"; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1833322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833322] Comment bridged from LTC Bugzilla
--- Comment From cborn...@de.ibm.com 2024-01-15 06:46 EDT--- Just a statement from s390x/IBM Z. For our platform irqbalance makes no sense as our interrupt handling works differently. So we do not need it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Consider removing irqbalance from default install on desktop images Status in Ubuntu on IBM z Systems: New Status in irqbalance package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop"; SUPPORT_URL="http://support.system76.com"; BUG_REPORT_URL="https://github.com/pop-os/pop/issues"; PRIVACY_POLICY_URL="https://system76.com/privacy"; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1833322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images
** Tags added: architecture-s39064 bugnameltc-204586 severity-medium targetmilestone-inin2404 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Consider removing irqbalance from default install on desktop images Status in Ubuntu on IBM z Systems: New Status in irqbalance package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop"; SUPPORT_URL="http://support.system76.com"; BUG_REPORT_URL="https://github.com/pop-os/pop/issues"; PRIVACY_POLICY_URL="https://system76.com/privacy"; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1833322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037569] Re: udev issues with mantic beta
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin2310 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libblockdev in Ubuntu. https://bugs.launchpad.net/bugs/2037569 Title: udev issues with mantic beta Status in Ubuntu on IBM z Systems: Fix Released Status in libblockdev package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Status in udisks2 package in Ubuntu: Fix Released Bug description: While installing mantic beta (on s390x, LPAR and z/VM - but this might not be architecture specific) I faced issues with udev. In my installation I've updated the installer to "edge/lp-2009141" (subiquity 22.02.2+git1762.1b1ee6f4 5164). During my installations I first noticed bad response times in case of dealing with devices (like enabling new devices with chzdev). chzdev is used during the installation, hence the installation procedure is also affected by this. (I mainly notice this issue in case of DASD ECKD disk enablements.) But even after after a successful (but due to this issue less snappier) installation, means after the post-install reboot, in the installed system I can find several udev related processes, like: 69448 root 20 0 31280 11944 2560 S 39.2 0.0 2:51.67 (udev-worker) 509 root 20 0 31276 13812 4600 S 20.6 0.0 2:07.76 systemd-udevd 893 root 20 0 469016 13544 10496 R 17.3 0.0 1:43.53 udisksd 1 root 20 0 168664 12748 8396 S 16.3 0.0 1:40.47 systemd which is not only unusual, but (as one can see) they consume quite some resources. Even the remote ssh into that system is impacted by this high load. So far I only see this in mantic. I tried 20.04.3 as well as lunar, but both do not seem to be affected by this udev problem. I neither face the bad response on device enablement, nor can see any udev related processes still running after post-install-reboot in the installed system. (Sometimes I could also see a growing log file 'syslog'). I cannot say yet what is causing this, but since I see 'systemd-udevd' as prominent process in top, I'll first of all mark this as affecting systemd-udevd (or systemd). I've attached the outcome of some more investigations I did ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2037569/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037569] Re: udev issues with mantic beta
** Tags added: architecture-s39064 bugnameltc-203787 severity-high targetmilestone-inin--- -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libblockdev in Ubuntu. https://bugs.launchpad.net/bugs/2037569 Title: udev issues with mantic beta Status in Ubuntu on IBM z Systems: Fix Released Status in libblockdev package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Status in udisks2 package in Ubuntu: Fix Released Bug description: While installing mantic beta (on s390x, LPAR and z/VM - but this might not be architecture specific) I faced issues with udev. In my installation I've updated the installer to "edge/lp-2009141" (subiquity 22.02.2+git1762.1b1ee6f4 5164). During my installations I first noticed bad response times in case of dealing with devices (like enabling new devices with chzdev). chzdev is used during the installation, hence the installation procedure is also affected by this. (I mainly notice this issue in case of DASD ECKD disk enablements.) But even after after a successful (but due to this issue less snappier) installation, means after the post-install reboot, in the installed system I can find several udev related processes, like: 69448 root 20 0 31280 11944 2560 S 39.2 0.0 2:51.67 (udev-worker) 509 root 20 0 31276 13812 4600 S 20.6 0.0 2:07.76 systemd-udevd 893 root 20 0 469016 13544 10496 R 17.3 0.0 1:43.53 udisksd 1 root 20 0 168664 12748 8396 S 16.3 0.0 1:40.47 systemd which is not only unusual, but (as one can see) they consume quite some resources. Even the remote ssh into that system is impacted by this high load. So far I only see this in mantic. I tried 20.04.3 as well as lunar, but both do not seem to be affected by this udev problem. I neither face the bad response on device enablement, nor can see any udev related processes still running after post-install-reboot in the installed system. (Sometimes I could also see a growing log file 'syslog'). I cannot say yet what is causing this, but since I see 'systemd-udevd' as prominent process in top, I'll first of all mark this as affecting systemd-udevd (or systemd). I've attached the outcome of some more investigations I did ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2037569/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959469] Comment bridged from LTC Bugzilla
An updated test package was created for kinetic and build with the help of this PPA: https://launchpad.net/~fheimes/+archive/ubuntu/lp1959469 for the major architectures. This incl. building and executing the testsuite too, which results in all tests passed: ... All 112 tests passed ... PASS: rsa-sign PASS: rsa-verify PASS: rsa-encrypt == All 3 tests passed == -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nettle in Ubuntu. https://bugs.launchpad.net/bugs/1959469 Title: [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto) Status in Ubuntu on IBM z Systems: New Status in nettle package in Ubuntu: New Bug description: Upgrade nettle to latest version >= 3.7.4 (crypto) Description Upgrade nettle to latest version >= 3.7.4 to provide CPACF Support for Crypto Libraries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959469/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913388] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2021-02-11 03:27 EDT--- IBM Bugzilla status->closed, Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to clucene-core in Ubuntu. https://bugs.launchpad.net/bugs/1913388 Title: clucene-core: please pull in patch to stabilize API on s390x during upgrade to glibc 2.33 Status in Ubuntu on IBM z Systems: Fix Released Status in clucene-core package in Ubuntu: Fix Released Bug description: On s390x, the type float_t has historically been defined as double for no good reason, yet with unexpected and unnecessary impact on performance in some scenarios. The upcoming glibc release 2.33 will be a first step towards cleaning that up, which will change float_t to become float on s390x when compiling C++ code, such as in clucene- core. That would break the ABI of clucene-core on s390x for existing binaries. Today, clucene-core uses float_t for some parameters in its API; that type is defined as double on s390x today. Together with gcc's default behavior, that contradicts the C standard. To get to a more sane combination, the upcoming glibc release 2.33 will change float_t to become float on s390x (with some exceptions when compiling C code, which do not apply for clucene-core). To my knowledge, glibc 2.33 is a candidate for inclusion in Ubuntu 21.04. To avoid breaking the API of clucene-core in the process, I have prepared a trivial patch that fixes clucene-core's API to always use double instead of float_t on s390x. That patch effectively persists the current de-facto API on s390x, without changes for other architectures. Note that using float_t in an API is generally "not a great idea", because that type can have different definitions even with the same compiler and glibc version on the same system (e.g., on 32-bit x86, when switching between SSE and x87 FP ops). Patch submitted in https://sourceforge.net/p/clucene/bugs/233/ and https://sourceforge.net/p/clucene/mailman/message/37153930/ yet upstream clucene is effectively unmaintained. If Ubuntu 21.04 adopts glibc 2.33, please consider pulling in this patch in clucene-core. Related request for ImageMagick: https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1913268 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1913388/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913388] Comment bridged from LTC Bugzilla
--- Comment From marius.hillenbr...@ibm.com 2021-01-27 05:05 EDT--- The clucene packages are built and shipped on s390x as part of the "main" repository (just verified in an Ubuntu 20.04 -- http://ports.ubuntu.com/pool/main/c/clucene-core/). I do not know how what role the grouping into Ubuntu Desktop plays. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to clucene-core in Ubuntu. https://bugs.launchpad.net/bugs/1913388 Title: clucene-core: please pull in patch to stabilize API on s390x during upgrade to glibc 2.33 Status in Ubuntu on IBM z Systems: Triaged Status in clucene-core package in Ubuntu: Incomplete Bug description: On s390x, the type float_t has historically been defined as double for no good reason, yet with unexpected and unnecessary impact on performance in some scenarios. The upcoming glibc release 2.33 will be a first step towards cleaning that up, which will change float_t to become float on s390x when compiling C++ code, such as in clucene- core. That would break the ABI of clucene-core on s390x for existing binaries. Today, clucene-core uses float_t for some parameters in its API; that type is defined as double on s390x today. Together with gcc's default behavior, that contradicts the C standard. To get to a more sane combination, the upcoming glibc release 2.33 will change float_t to become float on s390x (with some exceptions when compiling C code, which do not apply for clucene-core). To my knowledge, glibc 2.33 is a candidate for inclusion in Ubuntu 21.04. To avoid breaking the API of clucene-core in the process, I have prepared a trivial patch that fixes clucene-core's API to always use double instead of float_t on s390x. That patch effectively persists the current de-facto API on s390x, without changes for other architectures. Note that using float_t in an API is generally "not a great idea", because that type can have different definitions even with the same compiler and glibc version on the same system (e.g., on 32-bit x86, when switching between SSE and x87 FP ops). Patch submitted in https://sourceforge.net/p/clucene/bugs/233/ and https://sourceforge.net/p/clucene/mailman/message/37153930/ yet upstream clucene is effectively unmaintained. If Ubuntu 21.04 adopts glibc 2.33, please consider pulling in this patch in clucene-core. Related request for ImageMagick: https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1913268 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1913388/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794478] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-03-12 06:07 EDT--- IBM Bugzilla status-> closed, delivered by the distro -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Fix Released Bug description: [Impact] In case creating bond interface, IPv4 address is not automatically assigned when IPv6 has manual setting. [Test Case] 1. create 18.04.4 instance, network-manager version is 1.10.6-2ubuntu.1.2 as original description. 2. ipv6 manual, ipv4 auto ## sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup; sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0"; sudo nmcli con mod bond0 ipv6.method manual ipv6.addresses fe81::ff:fe97:a27f/64; sudo nmcli con mod bond0 ipv4.method auto; sudo nmcli con add type bond-slave ifname ens34 master bond0; sudo nmcli con add type bond-slave ifname ens35 master bond0; sudo nmcli con mod bond0 +bond.options mii=100 sleep 5 sudo nmcli con up bond-slave-ens34 sudo nmcli con up bond-slave-ens35 sudo nmcli con up bond0; sleep 5; sudo nmcli c s bond0 ## 3. ipv6 auto, ipv4 auto ## sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup; sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0"; sudo nmcli con mod bond0 ipv6.method auto; sudo nmcli con mod bond0 ipv4.method auto; sudo nmcli con add type bond-slave ifname ens34 master bond0; sudo nmcli con add type bond-slave ifname ens35 master bond0; sudo nmcli con mod bond0 +bond.options mii=100 sleep 5 sudo nmcli con up bond-slave-ens34 sudo nmcli con up bond-slave-ens35 sudo nmcli con up bond0; sleep 5 sudo nmcli c s bond0 ## when run #3, it is working, but with #2, it is not working. [Potential Regression] Actually nothing special. fix just remove if statement. but it needs Network Manager restarted. [Other informations] After upstream fix, it is working fine with #2 and #3 above. * Upstream bug and fix: https://bugzilla.redhat.com/show_bug.cgi?id=1575944 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35 * Only affecting Bionic: $ git describe --contains f03ae35 1.10.8~2 $ rmadison network-manager ==> network-manager | 1.10.6-2ubuntu1.2 | bionic-updates network-manager | 1.20.4-2ubuntu2.2 | eoan-updates network-manager | 1.22.4-1ubuntu2 | focal [Original description] ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto From /var/log/syslog, we can see ip got assigned: Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.
[Desktop-packages] [Bug 1794478] Comment bridged from LTC Bugzilla
--- Comment From abhir...@in.ibm.com 2020-03-04 08:55 EDT--- The network manager fix provided is working fine. The version on the tested machine is as below: root@NetworkTest:/usr/local/zACI/test/suites/net/web# dpkg -l | grep 1.10.6-2ubuntu1.4 ii libnm0:s390x 1.10.6-2ubuntu1.4 s390xGObject-based client library for NetworkManager ii network-manager 1.10.6-2ubuntu1.4 s390xnetwork management framework (daemon and userspace tools) root@ABHIRAM:/usr/local/zACI/test/suites/net/web# Ok with changing the tag from verification-needed-bionic to verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Fix Committed Bug description: [Impact] In case creating bond interface, IPv4 address is not automatically assigned when IPv6 has manual setting. [Test Case] 1. create 18.04.4 instance, network-manager version is 1.10.6-2ubuntu.1.2 as original description. 2. ipv6 manual, ipv4 auto ## sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup; sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0"; sudo nmcli con mod bond0 ipv6.method manual ipv6.addresses fe81::ff:fe97:a27f/64; sudo nmcli con mod bond0 ipv4.method auto; sudo nmcli con add type bond-slave ifname ens34 master bond0; sudo nmcli con add type bond-slave ifname ens35 master bond0; sudo nmcli con mod bond0 +bond.options mii=100 sleep 5 sudo nmcli con up bond-slave-ens34 sudo nmcli con up bond-slave-ens35 sudo nmcli con up bond0; sleep 5; sudo nmcli c s bond0 ## 3. ipv6 auto, ipv4 auto ## sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup; sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0"; sudo nmcli con mod bond0 ipv6.method auto; sudo nmcli con mod bond0 ipv4.method auto; sudo nmcli con add type bond-slave ifname ens34 master bond0; sudo nmcli con add type bond-slave ifname ens35 master bond0; sudo nmcli con mod bond0 +bond.options mii=100 sleep 5 sudo nmcli con up bond-slave-ens34 sudo nmcli con up bond-slave-ens35 sudo nmcli con up bond0; sleep 5 sudo nmcli c s bond0 ## when run #3, it is working, but with #2, it is not working. [Potential Regression] Actually nothing special. fix just remove if statement. but it needs Network Manager restarted. [Other informations] After upstream fix, it is working fine with #2 and #3 above. * Upstream bug and fix: https://bugzilla.redhat.com/show_bug.cgi?id=1575944 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35 * Only affecting Bionic: $ git describe --contains f03ae35 1.10.8~2 $ rmadison network-manager ==> network-manager | 1.10.6-2ubuntu1.2 | bionic-updates network-manager | 1.20.4-2ubuntu2.2 | eoan-updates network-manager | 1.22.4-1ubuntu2 | focal [Original description] ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=n
[Desktop-packages] [Bug 1794478] lp1794478_bionic.debdiff
Default Comment by Bridge ** Attachment added: "lp1794478_bionic.debdiff" https://bugs.launchpad.net/bugs/1794478/+attachment/5330008/+files/lp1794478_bionic.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Confirmed Bug description: [Impact] In case creating bond interface, IPv4 address is not automatically assigned when IPv6 has manual setting. [Test Case] 1. create 18.04.4 instance, network-manager version is 1.10.6-2ubuntu.1.2 as original description. 2. ipv6 manual, ipv4 auto ## sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup; sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0"; sudo nmcli con mod bond0 ipv6.method manual ipv6.addresses fe81::ff:fe97:a27f/64; sudo nmcli con mod bond0 ipv4.method auto; sudo nmcli con add type bond-slave ifname ens34 master bond0; sudo nmcli con add type bond-slave ifname ens35 master bond0; sudo nmcli con mod bond0 +bond.options mii=100 sleep 5 sudo nmcli con up bond-slave-ens34 sudo nmcli con up bond-slave-ens35 sudo nmcli con up bond0; sleep 5; sudo nmcli c s bond0 ## 3. ipv6 auto, ipv4 auto ## sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup; sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0"; sudo nmcli con mod bond0 ipv6.method auto; sudo nmcli con mod bond0 ipv4.method auto; sudo nmcli con add type bond-slave ifname ens34 master bond0; sudo nmcli con add type bond-slave ifname ens35 master bond0; sudo nmcli con mod bond0 +bond.options mii=100 sleep 5 sudo nmcli con up bond-slave-ens34 sudo nmcli con up bond-slave-ens35 sudo nmcli con up bond0; sleep 5 sudo nmcli c s bond0 ## when run #3, it is working, but with #2, it is not working. [Potential Regression] Actually nothing special. fix just remove if statement. but it needs Network Manager restarted. [Other informations] After upstream fix, it is working fine with #2 and #3 above. * Upstream bug and fix: https://bugzilla.redhat.com/show_bug.cgi?id=1575944 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35 * Only affecting Bionic: $ git describe --contains f03ae35 1.10.8~2 $ rmadison network-manager ==> network-manager | 1.10.6-2ubuntu1.2 | bionic-updates network-manager | 1.20.4-2ubuntu2.2 | eoan-updates network-manager | 1.22.4-1ubuntu2 | focal [Original description] ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto From /var/log/syslog, we can see ip got assigned: Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTe
[Desktop-packages] [Bug 1794478] lp1794478_bionic.debdiff
Default Comment by Bridge ** Attachment added: "lp1794478_bionic.debdiff" https://bugs.launchpad.net/bugs/1794478/+attachment/5329626/+files/lp1794478_bionic.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Confirmed Bug description: [Impact] [Test Case] [Potential Regression] [Other informations] * Upstream bug and fix: https://bugzilla.redhat.com/show_bug.cgi?id=1575944 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35 * Only affecting Bionic: $ git describe --contains f03ae35 1.10.8~2 $ rmadison network-manager ==> network-manager | 1.10.6-2ubuntu1.2 | bionic-updates network-manager | 1.20.4-2ubuntu2.2 | eoan-updates network-manager | 1.22.4-1ubuntu2 | focal [Original description] ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto From /var/log/syslog, we can see ip got assigned: Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 10.2.3.1 Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1 root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 28: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute test_bond valid_lft 353sec preferred_lft 353sec inet6 fe80::ff:feb3:b522/64 scope link valid_lft forever preferred_lft forever +++ Bond interface, ipv4 automatic mode and ipv6 manual mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab type=bond interface-name=test_bond permissions= timestamp=1537943300 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy address1=fe81::32a5:bc5f:287f:8db8/64 dns-search= method=manual No automatic ip assigned to ipv4 and no requests to dhcp server seen in /var/log/syslog root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 29: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute valid_lft forever preferred_lft forever ==> Correct LP-Package need to be assigned...! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1794478/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists
[Desktop-packages] [Bug 1794478] Comment bridged from LTC Bugzilla
--- Comment From abhir...@in.ibm.com 2020-02-14 12:51 EDT--- Eric, network-manager 1.10.6-2ubuntu1.3+testpkg20201202b1 fix provided is Working good. Network connection with auto ipv4 mode and manual ipv6 mode is NOW rightly setting ipv4 from server and manual ipv6. Deactivated and Activated the network connection to see both ips are still retained. No issues seen here. restart of network manager also the ips are retained. --- Comment From abhir...@in.ibm.com 2020-02-14 12:59 EDT--- nmcli c s for bond device , the output parameters being watched are now as expected ipv4.method:auto ipv6.method:manual ipv6.addresses: fe81::ff:fe97:a27f/64 GENERAL.STATE: activated IP4.ADDRESS[1]: 10.2.3.60/24 IP6.ADDRESS[1]: fe81::ff:fe97:a27f/64 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Confirmed Bug description: ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto From /var/log/syslog, we can see ip got assigned: Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 10.2.3.1 Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1 root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 28: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute test_bond valid_lft 353sec preferred_lft 353sec inet6 fe80::ff:feb3:b522/64 scope link valid_lft forever preferred_lft forever +++ Bond interface, ipv4 automatic mode and ipv6 manual mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab type=bond interface-name=test_bond permissions= timestamp=1537943300 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy address1=fe81::32a5:bc5f:287f:8db8/64 dns-search= method=manual No automatic ip assigned to ipv4 and no requests to dhcp server seen in /var/log/syslog root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 29: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute valid_lft forever preferred_lft forever ==> Correct LP-Package need to be a
[Desktop-packages] [Bug 1790098] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-02-11 04:54 EDT--- IBM Bugzilla status -> closed, Fix Released with bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1790098 Title: vlan created on bond fails auto activation on updating parent network bond Status in Ubuntu on IBM z Systems: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Fix Released Bug description: Auto activation of Vlan created over network-bond fails if bond is deactivated and reactivated. Contact Information = Abhiram Kulkarni(abhir...@in.ibm.com), Mandar Deshpande(manda...@in.ibm.com) ---uname output--- Linux S36MANDAR 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:23 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Created a network bond with static IP address (and no IPv6 address); active backup mode; ARP polling; single slave. 2. Created a VLAN using said network bond with static IPv4 address (and no IPv6 address). 3. Can ping from the appliance to a target on both links (the parent bond and the VLAN). 4. Switched to another slave for the created bond 5. Can still ping from the appliance to a target via the parent bond; however, cannot ping to the target via the VLAN. = Detailed steps: 1. Initial setup: root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 2. Create Netwrok-bond with one slave: root@S36MANDAR:~# nmcli c add type bond con-name mybond1 ifname mybond1 ipv4.method disabled ipv6.method ignore Connection 'mybond1' (4b918a65-43a6-4ec3-b3c4-388ed52b116d) successfully added. root@S36MANDAR:~# nmcli con add type ethernet ifname enc1d40 master mybond1 Connection 'bond-slave-enc1d40' (cfe4b245-3dda-4f45-b7b4-6d40d144a02f) successfully added. root@S36MANDAR:~# nmcli con up bond-slave-enc1d40 Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/18) root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE bond-slave-enc1d40 cfe4b245-3dda-4f45-b7b4-6d40d144a02f ethernet enc1d40 enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d bond mybond1 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 3. Create vlan over mybond1: === root@S36MANDAR:~# nmcli con add type vlan con-name vlanbond.100 ifname vlanbond.100 dev mybond1 id 100 ipv4.method disabled ipv6.method ignore Connection 'vlanbond.100' (e054df42-97a0-492b-b2c9-b9571077493e) successfully added. root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE bond-slave-enc1d40 cfe4b245-3dda-4f45-b7b4-6d40d144a02f ethernet enc1d40 enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d bond mybond1 vlanbond.100e054df42-97a0-492b-b2c9-b9571077493e vlan vlanbond.100 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 4. Reactivate bond : = root@S36MANDAR:~# nmcli con up mybond1 Connection successfully activated (master waiting for slaves) (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/30) root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet enc1d40 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d bond mybond1 bond-slave-enc1d40 cfe4b245-3dda-4f45-b7b4-6d40d144a02f ethernet -- encw18104ddeb38e-d5f7-3814-abb7-be50b8da874e ethernet -- vlanbond.100e054df42-97a0-492b-b2c9-b9571077493e vlan -- As is seen, vlan(vlanbond.100) did not get activated Now, i
[Desktop-packages] [Bug 1794478] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2019-12-10 10:31 EDT--- Re-opened bugzilla, problem still not fixed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: Fix Released Status in network-manager package in Ubuntu: New Status in network-manager source package in Bionic: Fix Released Bug description: ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto From /var/log/syslog, we can see ip got assigned: Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 10.2.3.1 Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1 root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 28: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute test_bond valid_lft 353sec preferred_lft 353sec inet6 fe80::ff:feb3:b522/64 scope link valid_lft forever preferred_lft forever +++ Bond interface, ipv4 automatic mode and ipv6 manual mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab type=bond interface-name=test_bond permissions= timestamp=1537943300 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy address1=fe81::32a5:bc5f:287f:8db8/64 dns-search= method=manual No automatic ip assigned to ipv4 and no requests to dhcp server seen in /var/log/syslog root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 29: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute valid_lft forever preferred_lft forever ==> Correct LP-Package need to be assigned...! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1794478/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1790098] Comment bridged from LTC Bugzilla
--- Comment From abhir...@in.ibm.com 2019-10-29 03:59 EDT--- Tested below scenario: 1)Create a bond network device 2)Create a vlan on top of above bond network device 3)Deactivate the bond 4)VLAN DEVICE ALSO GOES INTO DEACTIVATED state automatically 5)Activate bond 6)With the fix in, VLAN ALSO NOW GETS ACTIVATED AUTOMATICALLY This defect fix is verified -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1790098 Title: vlan created on bond fails auto activation on updating parent network bond Status in Ubuntu on IBM z Systems: Won't Fix Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Fix Committed Bug description: Auto activation of Vlan created over network-bond fails if bond is deactivated and reactivated. Contact Information = Abhiram Kulkarni(abhir...@in.ibm.com), Mandar Deshpande(manda...@in.ibm.com) ---uname output--- Linux S36MANDAR 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:23 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Created a network bond with static IP address (and no IPv6 address); active backup mode; ARP polling; single slave. 2. Created a VLAN using said network bond with static IPv4 address (and no IPv6 address). 3. Can ping from the appliance to a target on both links (the parent bond and the VLAN). 4. Switched to another slave for the created bond 5. Can still ping from the appliance to a target via the parent bond; however, cannot ping to the target via the VLAN. = Detailed steps: 1. Initial setup: root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 2. Create Netwrok-bond with one slave: root@S36MANDAR:~# nmcli c add type bond con-name mybond1 ifname mybond1 ipv4.method disabled ipv6.method ignore Connection 'mybond1' (4b918a65-43a6-4ec3-b3c4-388ed52b116d) successfully added. root@S36MANDAR:~# nmcli con add type ethernet ifname enc1d40 master mybond1 Connection 'bond-slave-enc1d40' (cfe4b245-3dda-4f45-b7b4-6d40d144a02f) successfully added. root@S36MANDAR:~# nmcli con up bond-slave-enc1d40 Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/18) root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE bond-slave-enc1d40 cfe4b245-3dda-4f45-b7b4-6d40d144a02f ethernet enc1d40 enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d bond mybond1 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 3. Create vlan over mybond1: === root@S36MANDAR:~# nmcli con add type vlan con-name vlanbond.100 ifname vlanbond.100 dev mybond1 id 100 ipv4.method disabled ipv6.method ignore Connection 'vlanbond.100' (e054df42-97a0-492b-b2c9-b9571077493e) successfully added. root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE bond-slave-enc1d40 cfe4b245-3dda-4f45-b7b4-6d40d144a02f ethernet enc1d40 enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d bond mybond1 vlanbond.100e054df42-97a0-492b-b2c9-b9571077493e vlan vlanbond.100 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 4. Reactivate bond : = root@S36MANDAR:~# nmcli con up mybond1 Connection successfully activated (master waiting for slaves) (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/30) root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet enc1d40 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d bond mybond1 bond-slave-enc1d40 cfe4b245-3dda-4f45-b7b4-6d40d144a02f ethernet --
[Desktop-packages] [Bug 1790098] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2019-06-19 03:47 EDT--- IBM Bugzilla status -> closed, Will not be fixed by Canonical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1790098 Title: vlan created on bond fails auto activation on updating parent network bond Status in Ubuntu on IBM z Systems: Won't Fix Status in network-manager package in Ubuntu: Won't Fix Bug description: Auto activation of Vlan created over network-bond fails if bond is deactivated and reactivated. Contact Information = Abhiram Kulkarni(abhir...@in.ibm.com), Mandar Deshpande(manda...@in.ibm.com) ---uname output--- Linux S36MANDAR 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:23 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Created a network bond with static IP address (and no IPv6 address); active backup mode; ARP polling; single slave. 2. Created a VLAN using said network bond with static IPv4 address (and no IPv6 address). 3. Can ping from the appliance to a target on both links (the parent bond and the VLAN). 4. Switched to another slave for the created bond 5. Can still ping from the appliance to a target via the parent bond; however, cannot ping to the target via the VLAN. = Detailed steps: 1. Initial setup: root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 2. Create Netwrok-bond with one slave: root@S36MANDAR:~# nmcli c add type bond con-name mybond1 ifname mybond1 ipv4.method disabled ipv6.method ignore Connection 'mybond1' (4b918a65-43a6-4ec3-b3c4-388ed52b116d) successfully added. root@S36MANDAR:~# nmcli con add type ethernet ifname enc1d40 master mybond1 Connection 'bond-slave-enc1d40' (cfe4b245-3dda-4f45-b7b4-6d40d144a02f) successfully added. root@S36MANDAR:~# nmcli con up bond-slave-enc1d40 Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/18) root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE bond-slave-enc1d40 cfe4b245-3dda-4f45-b7b4-6d40d144a02f ethernet enc1d40 enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d bond mybond1 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 3. Create vlan over mybond1: === root@S36MANDAR:~# nmcli con add type vlan con-name vlanbond.100 ifname vlanbond.100 dev mybond1 id 100 ipv4.method disabled ipv6.method ignore Connection 'vlanbond.100' (e054df42-97a0-492b-b2c9-b9571077493e) successfully added. root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE bond-slave-enc1d40 cfe4b245-3dda-4f45-b7b4-6d40d144a02f ethernet enc1d40 enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d bond mybond1 vlanbond.100e054df42-97a0-492b-b2c9-b9571077493e vlan vlanbond.100 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 4. Reactivate bond : = root@S36MANDAR:~# nmcli con up mybond1 Connection successfully activated (master waiting for slaves) (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/30) root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet enc1d40 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d bond mybond1 bond-slave-enc1d40 cfe4b245-3dda-4f45-b7b4-6d40d144a02f ethernet -- encw18104ddeb38e-d5f7-3814-abb7-be50b8da874e ethernet -- vlanbond.100e054df42-97a0-492b-b2c9-b9571077493e vlan -- As is seen, vlan(vlanbond.100) did not get activated Now, if manually I make vlan connection up, it gets activated: root@S3
[Desktop-packages] [Bug 1794478] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2019-05-14 11:09 EDT--- IBM bugzilla status -> closed, Fix Released with Bionic.. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Fix Released Bug description: ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto From /var/log/syslog, we can see ip got assigned: Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 10.2.3.1 Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1 root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 28: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute test_bond valid_lft 353sec preferred_lft 353sec inet6 fe80::ff:feb3:b522/64 scope link valid_lft forever preferred_lft forever +++ Bond interface, ipv4 automatic mode and ipv6 manual mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab type=bond interface-name=test_bond permissions= timestamp=1537943300 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy address1=fe81::32a5:bc5f:287f:8db8/64 dns-search= method=manual No automatic ip assigned to ipv4 and no requests to dhcp server seen in /var/log/syslog root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 29: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute valid_lft forever preferred_lft forever ==> Correct LP-Package need to be assigned...! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1794478/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794478] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2019-04-23 04:08 EDT--- The fix has worked , tested and we did not notice any other issues during the test. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: Fix Committed Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Fix Committed Bug description: ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto From /var/log/syslog, we can see ip got assigned: Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 10.2.3.1 Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1 root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 28: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute test_bond valid_lft 353sec preferred_lft 353sec inet6 fe80::ff:feb3:b522/64 scope link valid_lft forever preferred_lft forever +++ Bond interface, ipv4 automatic mode and ipv6 manual mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab type=bond interface-name=test_bond permissions= timestamp=1537943300 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy address1=fe81::32a5:bc5f:287f:8db8/64 dns-search= method=manual No automatic ip assigned to ipv4 and no requests to dhcp server seen in /var/log/syslog root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 29: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute valid_lft forever preferred_lft forever ==> Correct LP-Package need to be assigned...! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1794478/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794478] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2019-04-04 09:01 EDT--- Basic testing is done on the image and it looks good. Will be doing more testing and get back if any issues. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: Fix Committed Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Fix Committed Bug description: ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto From /var/log/syslog, we can see ip got assigned: Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 10.2.3.1 Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1 root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 28: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute test_bond valid_lft 353sec preferred_lft 353sec inet6 fe80::ff:feb3:b522/64 scope link valid_lft forever preferred_lft forever +++ Bond interface, ipv4 automatic mode and ipv6 manual mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab type=bond interface-name=test_bond permissions= timestamp=1537943300 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy address1=fe81::32a5:bc5f:287f:8db8/64 dns-search= method=manual No automatic ip assigned to ipv4 and no requests to dhcp server seen in /var/log/syslog root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 29: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute valid_lft forever preferred_lft forever ==> Correct LP-Package need to be assigned...! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1794478/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1642965] Comment bridged from LTC Bugzilla
--- Comment From jac...@de.ibm.com 2018-12-13 06:13 EDT---
And the next version comes in:
Package: firefox
Status: install ok installed
Priority: optional
Section: web
Installed-Size: 168434
Maintainer: Ubuntu Mozilla Team
Architecture: s390x
Version: 64.0+build3-0ubuntu0.16.04.1
Replaces: kubuntu-firefox-installer
Provides: gnome-www-browser, iceweasel, www-browser
Depends: lsb-release, libatk1.0-0 (>= 1.12.4), libc6 (>= 2.18),
libcairo-gobject2 (>= 1.10.0), libcairo2 (>= 1.10.0), libdbus-1-3 (>= 1.9.14),
libdbus-glib-1-2 (>= 0.78), libffi6 (>= 3.0.4), libfontconfig1 (>= 2.11.94),
libfreetype6 (>= 2.3.5), libgcc1 (>= 1:4.2), libgdk-pixbuf2.0-0 (>= 2.22.0),
libglib2.0-0 (>= 2.30.0), libgtk-3-0 (>= 3.4), libpango-1.0-0 (>= 1.22.0),
libpangocairo-1.0-0 (>= 1.14.0), libstartup-notification0 (>= 0.8), libstdc++6
(>= 4.6), libx11-6, libx11-xcb1, libxcb-shm0, libxcb1, libxext6, libxrender1,
libxt6
Recommends: xul-ext-ubufox, libcanberra0, libdbusmenu-glib4, libdbusmenu-gtk3-4
Suggests: fonts-lyx
Conffiles:
/etc/apparmor.d/usr.bin.firefox 2c5033f33fe1c0e5b9f27ecbbb6ff74f
/etc/apport/blacklist.d/firefox d41d8cd98f00b204e9800998ecf8427e
/etc/apport/native-origins.d/firefox 7c26b75c7c2b715c89cc6d85338252a4
/etc/firefox/syspref.js 09e457e65435a1a043521f2bd19cd2a1
/etc/firefox/firefox.js a49602f3ce5871da8a5c58579411e971 obsolete
Description: Safe and easy web browser from Mozilla
Firefox delivers safe, easy web browsing. A familiar user interface,
enhanced security features including protection from online identity theft,
and integrated search let you get the most out of the web.
Xul-Appid: {ec8030f7-c20a-464f-9b0e-13a3a9e97384}
firefox:
Installed: 64.0+build3-0ubuntu0.16.04.1
Candidate: 64.0+build3-0ubuntu0.16.04.1
Version table:
*** 64.0+build3-0ubuntu0.16.04.1 500
500 http://de.ports.ubuntu.com/ubuntu-ports xenial-updates/main s390x Packages
500 http://ports.ubuntu.com/ubuntu-ports xenial-security/main s390x Packages
But alas, still crashing:
Thread 1 "firefox" received signal SIGSEGV, Segmentation fault.
NS_ABORT_OOM (aSize=) at
/build/firefox-cC5WSS/firefox-64.0+build3/xpcom/base/nsDebugImpl.cpp:628
628 /build/firefox-cC5WSS/firefox-64.0+build3/xpcom/base/nsDebugImpl.cpp:
No such file or directory.
(gdb) info stack
#0 NS_ABORT_OOM (aSize=) at
/build/firefox-cC5WSS/firefox-64.0+build3/xpcom/base/nsDebugImpl.cpp:628
#1 0x03fff41bf24c in nsTSubstring::AllocFailed (aLength=, this=0x3ffdb30)
at /build/firefox-cC5WSS/firefox-64.0+build3/xpcom/string/nsTSubstring.h:1172
#2 nsTString::ReplaceSubstring (this=this@entry=0x3ffdb30,
aTarget=..., aNewValue=...)
at
/build/firefox-cC5WSS/firefox-64.0+build3/xpcom/string/nsTStringObsolete.cpp:275
#3 0x03fff41bf2f6 in nsTString::ReplaceSubstring
(this=this@entry=0x3ffdb30,
aTarget=aTarget@entry=0x3fff831482e ";",
aNewValue=aNewValue@entry=0x3fff805c8e0 "%3b")
at
/build/firefox-cC5WSS/firefox-64.0+build3/xpcom/string/nsTStringObsolete.cpp:252
#4 0x03fff42bda3c in net_GetURLSpecFromActualFile (aFile=,
result=...)
at /build/firefox-cC5WSS/firefox-64.0+build3/netwerk/base/nsURLHelperUnix.cpp:45
#5 0x03fff42829ea in mozilla::FileLocation::GetURIString
(this=this@entry=0x3fffd6ed5f0, aResult=...)
at /build/firefox-cC5WSS/firefox-64.0+build3/xpcom/build/FileLocation.cpp:118
#6 0x03fff49c2988 in nsZipArchive::OpenArchive
(this=this@entry=0x3fffd6fa000, aZipHandle=0x3fffd6ed5e0, aFd=aFd@entry=0x0)
at /build/firefox-cC5WSS/firefox-64.0+build3/modules/libjar/nsZipArchive.cpp:359
#7 0x03fff49c2ac6 in nsZipArchive::OpenArchive
(this=this@entry=0x3fffd6fa000, aFile=)
at /build/firefox-cC5WSS/firefox-64.0+build3/modules/libjar/nsZipArchive.cpp:380
#8 0x03fff428626a in mozilla::Omnijar::InitOne (aPath=aPath@entry=0x0,
aType=aType@entry=mozilla::Omnijar::GRE)
at /build/firefox-cC5WSS/firefox-64.0+build3/xpcom/build/Omnijar.cpp:87
#9 0x03fff4287c3a in mozilla::Omnijar::Init (aAppPath=0x0, aGrePath=0x0)
at /build/firefox-cC5WSS/firefox-64.0+build3/xpcom/build/Omnijar.cpp:111
#10 NS_InitXPCOM2 (aResult=0x3fffd685a38, aBinDirectory=,
aAppFileLocationProvider=)
at /build/firefox-cC5WSS/firefox-64.0+build3/xpcom/build/XPCOMInit.cpp:612
#11 0x03fff428800c in NS_InitXPCOM2 (aResult=aResult@entry=0x3fffd685a38,
aBinDirectory=,
aAppFileLocationProvider=) at
/build/firefox-cC5WSS/firefox-64.0+build3/xpcom/build/XPCOMInit.cpp:748
#12 0x03fff70b6808 in ScopedXPCOMStartup::Initialize (this=0x3fffd685a38)
at /build/firefox-cC5WSS/firefox-64.0+build3/toolkit/xre/nsAppRunner.cpp:1484
#13 0x03fff70be23e in XREMain::XRE_main (this=this@entry=0x3ffe278,
argc=argc@entry=1, argv=argv@entry=0x3fff7a8,
aConfig=...) at
/build/firefox-cC5WSS/firefox-64.0+build3/toolkit/xre/nsAppRunner.cpp:4918
#14 0x03fff70be5ca in XRE_main (argc=, argv=0x3fff7a8,
aConfig=...)
at /build/firefox-cC5WSS/firefox-64.0+build3/toolkit/xre/nsAppRunner.cpp:5014
#15 0x00016cb8 in do_main (argc=, argv=0x3fff7a8,
[Desktop-packages] [Bug 1642965] Comment bridged from LTC Bugzilla
--- Comment From jac...@de.ibm.com 2018-11-27 08:10 EDT---
Ok, I know what the problem with the missing libraries is -> you don't put the
Shared-Object into the appropriate search pathes so that ld.so can find them.
But though, also with hand written search pathes the firefox package is
still broken:
milliadm@mclint:~$
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:/usr/lib/firefox:/usr/lib/gcc-mozilla/lib
firefox
Segmentation fault (core dumped)
milliadm@mclint:~$ echo $?
139
For completeness, here is the stack breakdown:
#0 NS_ABORT_OOM (aSize=) at
/build/firefox-VVCewt/firefox-63.0.3+build1/xpcom/base/nsDebugImpl.cpp:628
#1 0x03fff457a1e4 in nsTSubstring::AllocFailed (aLength=, this=0x3ffdb38)
at /build/firefox-VVCewt/firefox-63.0.3+build1/xpcom/string/nsTSubstring.h:1165
#2 nsTString::ReplaceSubstring (this=this@entry=0x3ffdb38,
aTarget=..., aNewValue=...)
at
/build/firefox-VVCewt/firefox-63.0.3+build1/xpcom/string/nsTStringObsolete.cpp:275
#3 0x03fff457a28e in nsTString::ReplaceSubstring
(this=this@entry=0x3ffdb38,
aTarget=aTarget@entry=0x3fff832e126 ";",
aNewValue=aNewValue@entry=0x3fff807a438 "%3b")
at
/build/firefox-VVCewt/firefox-63.0.3+build1/xpcom/string/nsTStringObsolete.cpp:252
#4 0x03fff4674cb4 in net_GetURLSpecFromActualFile (aFile=,
result=...)
at
/build/firefox-VVCewt/firefox-63.0.3+build1/netwerk/base/nsURLHelperUnix.cpp:45
#5 0x03fff463caaa in mozilla::FileLocation::GetURIString
(this=this@entry=0x3fffd6ed5f0, aResult=...)
at /build/firefox-VVCewt/firefox-63.0.3+build1/xpcom/build/FileLocation.cpp:118
#6 0x03fff4d65a80 in nsZipArchive::OpenArchive
(this=this@entry=0x3fffd6fa000, aZipHandle=0x3fffd6ed5e0, aFd=aFd@entry=0x0)
at
/build/firefox-VVCewt/firefox-63.0.3+build1/modules/libjar/nsZipArchive.cpp:359
#7 0x03fff4d65bbe in nsZipArchive::OpenArchive
(this=this@entry=0x3fffd6fa000, aFile=)
at
/build/firefox-VVCewt/firefox-63.0.3+build1/modules/libjar/nsZipArchive.cpp:380
#8 0x03fff4640352 in mozilla::Omnijar::InitOne (aPath=aPath@entry=0x0,
aType=aType@entry=mozilla::Omnijar::GRE)
at /build/firefox-VVCewt/firefox-63.0.3+build1/xpcom/build/Omnijar.cpp:87
#9 0x03fff4641dfa in mozilla::Omnijar::Init (aAppPath=0x0, aGrePath=0x0)
at /build/firefox-VVCewt/firefox-63.0.3+build1/xpcom/build/Omnijar.cpp:111
#10 NS_InitXPCOM2 (aResult=0x3fffd685a30, aBinDirectory=,
aAppFileLocationProvider=)
at /build/firefox-VVCewt/firefox-63.0.3+build1/xpcom/build/XPCOMInit.cpp:609
#11 0x03fff46421cc in NS_InitXPCOM2 (aResult=aResult@entry=0x3fffd685a30,
aBinDirectory=,
aAppFileLocationProvider=) at
/build/firefox-VVCewt/firefox-63.0.3+build1/xpcom/build/XPCOMInit.cpp:747
#12 0x03fff74153d8 in ScopedXPCOMStartup::Initialize (this=0x3fffd685a30)
at /build/firefox-VVCewt/firefox-63.0.3+build1/toolkit/xre/nsAppRunner.cpp:1490
#13 0x03fff741cf16 in XREMain::XRE_main (this=this@entry=0x3ffe280,
argc=argc@entry=1, argv=argv@entry=0x3fff7a8,
aConfig=...) at
/build/firefox-VVCewt/firefox-63.0.3+build1/toolkit/xre/nsAppRunner.cpp:4923
#14 0x03fff741d2aa in XRE_main (argc=, argv=0x3fff7a8,
aConfig=...)
at /build/firefox-VVCewt/firefox-63.0.3+build1/toolkit/xre/nsAppRunner.cpp:5019
#15 0x00016c48 in do_main (argc=, argv=0x3fff7a8,
envp=)
at /build/firefox-VVCewt/firefox-63.0.3+build1/browser/app/nsBrowserApp.cpp:233
#16 0x00016468 in main (argc=, argv=0x3fff7a8,
envp=0x3fff7b8)
at /build/firefox-VVCewt/firefox-63.0.3+build1/browser/app/nsBrowserApp.cpp:315
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1642965
Title:
Firefox crashes - Error loading theme icon
Status in firefox package in Ubuntu:
Won't Fix
Bug description:
Linux lnx 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:14:35 UTC 2016 s390x
s390x s390x GNU/Linux
Firefox:
firefox 47.0+build3-0ubuntu0.16.04.1
Description:
Firefox crashes when trying to start it on the server and display on the
local client.
Other X application can be displayed.
Reproduction:
Login to the server: ssh -X lnxserver
Start firefox: firefox --no-remote
Error Message:
(firefox:39655): Gtk-WARNING **: Error loading theme icon 'list-add' for
stock: Icon 'list-add' not present in theme System
Segmentation fault (core dumped)
== Comment: #6 - Thorsten Diehl - 2016-11-16
11:50:35 ==
I can confirm this.
I installed Ubuntu 16.04.1 on s390x (z13 machine) and installed updates, then
x11-apps, which were working fine (xclock, xeyes).
I installed firefox and started it:
firefox --no-remote
it created tons of messages, all complaing about an unknown image format.
Any subsequent start does not create that many messages. But even with
--safe-mode I can't get it started:
root@s8330009:~# firefox --no-remote --safe-mode
(firefox:1487): Gtk-WARNING **: Locale not supported by C library.
Us
[Desktop-packages] [Bug 1642965] Comment bridged from LTC Bugzilla
--- Comment From jac...@de.ibm.com 2018-11-26 04:54 EDT--- Next package version is out, but still no better: milliadm@mclint:~$ ldd /usr/lib/firefox/libxul.so | grep -v \(0x /usr/lib/firefox/libxul.so: /usr/lib/s390x-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by /usr/lib/firefox/libxul.so) /usr/lib/firefox/libxul.so: /usr/lib/s390x-linux-gnu/libnss3.so: version `NSS_3.30' not found (required by /usr/lib/firefox/libxul.so) liblgpllibs.so => not found libmozsqlite3.so => not found libmozgtk.so => not found milliadm@mclint:~$ apt policy firefox firefox: Installed: 63.0.3+build1-0ubuntu0.16.04.1 Candidate: 63.0.3+build1-0ubuntu0.16.04.1 Version table: *** 63.0.3+build1-0ubuntu0.16.04.1 500 500 http://de.ports.ubuntu.com/ubuntu-ports xenial-updates/main s390x Packages 500 http://ports.ubuntu.com/ubuntu-ports xenial-security/main s390x Packages 100 /var/lib/dpkg/status Where can I get your version of "GLIBCXX_3.4.22", "NSS_3.30", liblgpllibs.so, libmozsqlite3.so and libmozgtk.so for xenial s390x from? They must have been available on that very environment that built this s390x-firefox package! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1642965 Title: Firefox crashes - Error loading theme icon Status in firefox package in Ubuntu: Won't Fix Bug description: Linux lnx 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:14:35 UTC 2016 s390x s390x s390x GNU/Linux Firefox: firefox 47.0+build3-0ubuntu0.16.04.1 Description: Firefox crashes when trying to start it on the server and display on the local client. Other X application can be displayed. Reproduction: Login to the server: ssh -X lnxserver Start firefox: firefox --no-remote Error Message: (firefox:39655): Gtk-WARNING **: Error loading theme icon 'list-add' for stock: Icon 'list-add' not present in theme System Segmentation fault (core dumped) == Comment: #6 - Thorsten Diehl - 2016-11-16 11:50:35 == I can confirm this. I installed Ubuntu 16.04.1 on s390x (z13 machine) and installed updates, then x11-apps, which were working fine (xclock, xeyes). I installed firefox and started it: firefox --no-remote it created tons of messages, all complaing about an unknown image format. Any subsequent start does not create that many messages. But even with --safe-mode I can't get it started: root@s8330009:~# firefox --no-remote --safe-mode (firefox:1487): Gtk-WARNING **: Locale not supported by C library. Using the fallback 'C' locale. Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknown image format 1 (t=0.627128) [GFX1]: Unknown image format 1 Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknown image format 1 (t=0.627128) |[1][GFX1]: Unknown image format 0 (t=0.631695) [GFX1]: Unknown image format 0 [1487] ###!!! ABORT: X_ShmAttach: BadAccess (attempt to access private resource denied); 3 requests ago: file /build/firefox-xMihVX/firefox-47.0+build3/toolkit/xre/nsX11ErrorHandler.cpp, line 157 [1487] ###!!! ABORT: X_ShmAttach: BadAccess (attempt to access private resource denied); 3 requests ago: file /build/firefox-xMihVX/firefox-47.0+build3/toolkit/xre/nsX11ErrorHandler.cpp, line 157 Perhaps a graphics library (gtklib?) has a problem? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1642965/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1642965] Comment bridged from LTC Bugzilla
--- Comment From jac...@de.ibm.com 2018-11-08 05:29 EDT---
Hello and sorry, you're right ... I haven't posted the package details. Here
they come:
root@mclint:~# dpkg --status firefox
Package: firefox
Status: install ok installed
Priority: optional
Section: web
Installed-Size: 164686
Maintainer: Ubuntu Mozilla Team
Architecture: s390x
Version: 63.0+build2-0ubuntu0.16.04.2
Replaces: kubuntu-firefox-installer
Provides: gnome-www-browser, iceweasel, www-browser
Depends: lsb-release, libatk1.0-0 (>= 1.12.4), libc6 (>= 2.18),
libcairo-gobject2 (>= 1.10.0), libcairo2 (>= 1.10.0), libdbus-1-3 (>= 1.9.14),
libdbus-glib-1-2 (>= 0.78), libffi6 (>= 3.0.4), libfontconfig1 (>= 2.11.94),
libfreetype6 (>= 2.3.5), libgcc1 (>= 1:4.2), libgdk-pixbuf2.0-0 (>= 2.22.0),
libglib2.0-0 (>= 2.30.0), libgtk-3-0 (>= 3.4), libpango-1.0-0 (>= 1.22.0),
libpangocairo-1.0-0 (>= 1.14.0), libstartup-notification0 (>= 0.8), libstdc++6
(>= 4.6), libx11-6, libx11-xcb1, libxcb-shm0, libxcb1, libxext6, libxrender1,
libxt6
Recommends: xul-ext-ubufox, libcanberra0, libdbusmenu-glib4, libdbusmenu-gtk3-4
Suggests: fonts-lyx
Conffiles:
/etc/apparmor.d/usr.bin.firefox 2c5033f33fe1c0e5b9f27ecbbb6ff74f
/etc/apport/blacklist.d/firefox d41d8cd98f00b204e9800998ecf8427e
/etc/apport/native-origins.d/firefox 7c26b75c7c2b715c89cc6d85338252a4
/etc/firefox/syspref.js 09e457e65435a1a043521f2bd19cd2a1
/etc/firefox/firefox.js a49602f3ce5871da8a5c58579411e971 obsolete
Description: Safe and easy web browser from Mozilla
Firefox delivers safe, easy web browsing. A familiar user interface,
enhanced security features including protection from online identity theft,
and integrated search let you get the most out of the web.
Xul-Appid: {ec8030f7-c20a-464f-9b0e-13a3a9e97384}
root@mclint:~# apt policy firefox
firefox:
Installiert: 63.0+build2-0ubuntu0.16.04.2
Installationskandidat: 63.0+build2-0ubuntu0.16.04.2
Versionstabelle:
*** 63.0+build2-0ubuntu0.16.04.2 500
500 http://de.ports.ubuntu.com/ubuntu-ports xenial-updates/main s390x Packages
500 http://ports.ubuntu.com/ubuntu-ports xenial-security/main s390x Packages
100 /var/lib/dpkg/status
So, this is the most current firefox package that is available in "main"
from xenial-updates and xenial-security for the s390x platform.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1642965
Title:
Firefox crashes - Error loading theme icon
Status in firefox package in Ubuntu:
Won't Fix
Bug description:
Linux lnx 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:14:35 UTC 2016 s390x
s390x s390x GNU/Linux
Firefox:
firefox 47.0+build3-0ubuntu0.16.04.1
Description:
Firefox crashes when trying to start it on the server and display on the
local client.
Other X application can be displayed.
Reproduction:
Login to the server: ssh -X lnxserver
Start firefox: firefox --no-remote
Error Message:
(firefox:39655): Gtk-WARNING **: Error loading theme icon 'list-add' for
stock: Icon 'list-add' not present in theme System
Segmentation fault (core dumped)
== Comment: #6 - Thorsten Diehl - 2016-11-16
11:50:35 ==
I can confirm this.
I installed Ubuntu 16.04.1 on s390x (z13 machine) and installed updates, then
x11-apps, which were working fine (xclock, xeyes).
I installed firefox and started it:
firefox --no-remote
it created tons of messages, all complaing about an unknown image format.
Any subsequent start does not create that many messages. But even with
--safe-mode I can't get it started:
root@s8330009:~# firefox --no-remote --safe-mode
(firefox:1487): Gtk-WARNING **: Locale not supported by C library.
Using the fallback 'C' locale.
Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknown image format 1
(t=0.627128) [GFX1]: Unknown image format 1
Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknown image format 1
(t=0.627128) |[1][GFX1]: Unknown image format 0 (t=0.631695) [GFX1]: Unknown
image format 0
[1487] ###!!! ABORT: X_ShmAttach: BadAccess (attempt to access private
resource denied); 3 requests ago: file
/build/firefox-xMihVX/firefox-47.0+build3/toolkit/xre/nsX11ErrorHandler.cpp,
line 157
[1487] ###!!! ABORT: X_ShmAttach: BadAccess (attempt to access private
resource denied); 3 requests ago: file
/build/firefox-xMihVX/firefox-47.0+build3/toolkit/xre/nsX11ErrorHandler.cpp,
line 157
Perhaps a graphics library (gtklib?) has a problem?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1642965/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1642965] Comment bridged from LTC Bugzilla
--- Comment From jac...@de.ibm.com 2018-11-07 05:41 EDT--- Wow, I see a new build ... but it still doesn't work: milliadm@mclint:~$ ldd /usr/lib/firefox/libxul.so | grep -v \(0x /usr/lib/firefox/libxul.so: /usr/lib/s390x-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by /usr/lib/firefox/libxul.so) /usr/lib/firefox/libxul.so: /usr/lib/s390x-linux-gnu/libnss3.so: version `NSS_3.30' not found (required by /usr/lib/firefox/libxul.so) liblgpllibs.so => not found libmozsqlite3.so => not found libmozgtk.so => not found Where can I get those shared libraries from? They don't come from the usual Xenial-Update repositories for s390x! How did you build that firefox package at all (the libraries must exist in your build environment)? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1642965 Title: Firefox crashes - Error loading theme icon Status in firefox package in Ubuntu: Won't Fix Bug description: Linux lnx 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:14:35 UTC 2016 s390x s390x s390x GNU/Linux Firefox: firefox 47.0+build3-0ubuntu0.16.04.1 Description: Firefox crashes when trying to start it on the server and display on the local client. Other X application can be displayed. Reproduction: Login to the server: ssh -X lnxserver Start firefox: firefox --no-remote Error Message: (firefox:39655): Gtk-WARNING **: Error loading theme icon 'list-add' for stock: Icon 'list-add' not present in theme System Segmentation fault (core dumped) == Comment: #6 - Thorsten Diehl - 2016-11-16 11:50:35 == I can confirm this. I installed Ubuntu 16.04.1 on s390x (z13 machine) and installed updates, then x11-apps, which were working fine (xclock, xeyes). I installed firefox and started it: firefox --no-remote it created tons of messages, all complaing about an unknown image format. Any subsequent start does not create that many messages. But even with --safe-mode I can't get it started: root@s8330009:~# firefox --no-remote --safe-mode (firefox:1487): Gtk-WARNING **: Locale not supported by C library. Using the fallback 'C' locale. Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknown image format 1 (t=0.627128) [GFX1]: Unknown image format 1 Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknown image format 1 (t=0.627128) |[1][GFX1]: Unknown image format 0 (t=0.631695) [GFX1]: Unknown image format 0 [1487] ###!!! ABORT: X_ShmAttach: BadAccess (attempt to access private resource denied); 3 requests ago: file /build/firefox-xMihVX/firefox-47.0+build3/toolkit/xre/nsX11ErrorHandler.cpp, line 157 [1487] ###!!! ABORT: X_ShmAttach: BadAccess (attempt to access private resource denied); 3 requests ago: file /build/firefox-xMihVX/firefox-47.0+build3/toolkit/xre/nsX11ErrorHandler.cpp, line 157 Perhaps a graphics library (gtklib?) has a problem? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1642965/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1796839] [NEW] Only 64 Memory regions or dimms supported for Hotplug.
Public bug reported: == Comment: #0 - HARIHARAN T. SUNDARESH REDDY - 2018-10-03 01:29:59 == Description : Hotplug is supported only for 64 dimms and the same is controlled by the sysfs parameter # cat /sys/module/vhost/parameters/max_mem_regions 64 However qemu supports 256 slots max. In my opinion max_mem_regions must be >= 256. log : 63 Device attached successfully<--- 63 times devices attached successfully, later all attach failed. 64 error: Failed to attach device from hp_mem.xml error: internal error: unable to execute QEMU command 'device_add': a used vhost backend has no free memory slots left 65 error: Failed to attach device from hp_mem.xml error: internal error: unable to execute QEMU command 'device_add': a used vhost backend has no free memory slots left 66 error: Failed to attach device from hp_mem.xml error: internal error: unable to execute QEMU command 'device_add': a used vhost backend has no free memory slots left System Details : uname -a Linux ltc-fvttest 4.18.5-custom #1 SMP Wed Sep 26 12:11:51 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux root@ltc-fvttest:/home/hariharan# cat /etc/os-release NAME="Ubuntu" VERSION="18.10 (Cosmic Cuttlefish)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu Cosmic Cuttlefish (development branch)" VERSION_ID="18.10" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=cosmic UBUNTU_CODENAME=cosmic ** Affects: sysfsutils (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64le bugnameltc-171919 severity-medium targetmilestone-inin--- ** Tags added: architecture-ppc64le bugnameltc-171919 severity-medium targetmilestone-inin--- ** Changed in: ubuntu Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** Package changed: ubuntu => sysfsutils (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sysfsutils in Ubuntu. https://bugs.launchpad.net/bugs/1796839 Title: Only 64 Memory regions or dimms supported for Hotplug. Status in sysfsutils package in Ubuntu: New Bug description: == Comment: #0 - HARIHARAN T. SUNDARESH REDDY - 2018-10-03 01:29:59 == Description : Hotplug is supported only for 64 dimms and the same is controlled by the sysfs parameter # cat /sys/module/vhost/parameters/max_mem_regions 64 However qemu supports 256 slots max. In my opinion max_mem_regions must be >= 256. log : 63 Device attached successfully<--- 63 times devices attached successfully, later all attach failed. 64 error: Failed to attach device from hp_mem.xml error: internal error: unable to execute QEMU command 'device_add': a used vhost backend has no free memory slots left 65 error: Failed to attach device from hp_mem.xml error: internal error: unable to execute QEMU command 'device_add': a used vhost backend has no free memory slots left 66 error: Failed to attach device from hp_mem.xml error: internal error: unable to execute QEMU command 'device_add': a used vhost backend has no free memory slots left System Details : uname -a Linux ltc-fvttest 4.18.5-custom #1 SMP Wed Sep 26 12:11:51 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux root@ltc-fvttest:/home/hariharan# cat /etc/os-release NAME="Ubuntu" VERSION="18.10 (Cosmic Cuttlefish)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu Cosmic Cuttlefish (development branch)" VERSION_ID="18.10" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=cosmic UBUNTU_CODENAME=cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysfsutils/+bug/1796839/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794478] Comment bridged from LTC Bugzilla
--- Comment From abhir...@in.ibm.com 2018-10-04 05:03 EDT--- Vorlon, Yes i agree that nmcli is being used by me for managing the interfaces. The issue is not seen with ETHERNET and VLAN type of interfaces. This is happening only with BOND interfaces (auto ipv4 and manual ipv6 assigned.) Is is possible for you to try with this configuration and check? If its not happening then probably its a nmcli bug? I have to yet work on netplan tool and see if i can reproduce. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: Incomplete Status in network-manager package in Ubuntu: Incomplete Bug description: ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto From /var/log/syslog, we can see ip got assigned: Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 10.2.3.1 Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1 root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 28: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute test_bond valid_lft 353sec preferred_lft 353sec inet6 fe80::ff:feb3:b522/64 scope link valid_lft forever preferred_lft forever +++ Bond interface, ipv4 automatic mode and ipv6 manual mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab type=bond interface-name=test_bond permissions= timestamp=1537943300 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy address1=fe81::32a5:bc5f:287f:8db8/64 dns-search= method=manual No automatic ip assigned to ipv4 and no requests to dhcp server seen in /var/log/syslog root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 29: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute valid_lft forever preferred_lft forever ==> Correct LP-Package need to be assigned...! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1794478/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1790098] Comment bridged from LTC Bugzilla
--- Comment From abhir...@in.ibm.com 2018-09-12 05:05 EDT--- Vorlon, On investigation, comparing steps , behaviour with Ubuntu and Other distros, adding below data. Other distros, nmcli behaviour Deactivation of bond steps via our script/code: +++ 1)Deactivate slaves [nmcli c down ] 2)Deactivate bond [nmcli c down ] Result : All slaves , bond get deactivated. VLANs created on top of bond automatically get deactivated. Activation of bond steps via our script/code: +++ 1)Activate slaves [nmcli c up ] 2)Activate bond [nmcli c up ] Result : All slaves , bond get activated . VLANs created on top of bond automatically get activated. In Ubuntu + nmcli : Deactivation of bond: 1)Deactivate slaves [nmcli c down ] 2)Deactivate bond [nmcli c down ] Result : All slaves , bond get deactivated. VLANs created on top of bond automatically get deactivated. Activation of bond: 1)Activate slaves [nmcli c up ] 2)Activate bond [nmcli c up ] Result : All slaves , bond get activated . VLANs created on top of bond ##FAILED## to activate. Workaround to make autoactivation for vlan work is as follows: Deactivation of bond: 1)Deactivate bond [nmcli c down ] Result : Bond get deactivated. Slaves part of bond and VLANs created on top of bond automatically get deactivated. Activation of bond: 1)Activate bond [nmcli c up ] Result : Bond gets activated . Slaves part of bond and VLANs created on top of bond automatically get activated. But this workaround will not work in other distros. Other distros explicitly needed the slaves to be activated. I am not sure how could i simulate above steps behaviour with other utility like ip commands. Any suggestions there? I thought of using "ip link set bond_device down " as equivalent to "nmcli c down " but they differ. "ip link set bond_device down" only brings the link down for bond where as "nmcli c down " brings the bond device down and also detaches slave from bond. I also notice "nmcli c up " behaviour is different in Ubuntu and Other distros. In ubuntu , it probably assumes all slaves attached to bond, bond device itself and vlans created on top of bond as one entity and activated all. In other distros , it assumes slave as not part of it , hence only bond device is active. Slave and VLANs remain inactive. So this is probably bug in one of the distros or probably expected behaviour of nmcli component in different distros. Any suggestions/inputs here ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1790098 Title: vlan created on bond fails auto activation on updating parent network bond Status in Ubuntu on IBM z Systems: Incomplete Status in network-manager package in Ubuntu: Incomplete Bug description: Auto activation of Vlan created over network-bond fails if bond is deactivated and reactivated. Contact Information = Abhiram Kulkarni(abhir...@in.ibm.com), Mandar Deshpande(manda...@in.ibm.com) ---uname output--- Linux S36MANDAR 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:23 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Created a network bond with static IP address (and no IPv6 address); active backup mode; ARP polling; single slave. 2. Created a VLAN using said network bond with static IPv4 address (and no IPv6 address). 3. Can ping from the appliance to a target on both links (the parent bond and the VLAN). 4. Switched to another slave for the created bond 5. Can still ping from the appliance to a target via the parent bond; however, cannot ping to the target via the VLAN. = Detailed steps: 1. Initial setup: root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 2. Create Netwrok-bond with one slave: root@S36MANDAR:~# nmcli c add type bond con-name mybond1 ifname mybond1 ipv4.method disabled ipv6.method ignore Connection 'mybond1' (4b918a65-43a6-4ec3-b3c4-388ed52b116d) successfully added. root@S36MANDAR:~# nmcli con add type ethernet ifname enc1d40 master mybond1 Connection 'bond-slave-enc1d40' (cfe4b245-3dda-4f45-b7b4-6d40d144a02f) successfully added. root@S36MANDAR:~# nmcli con up bond-slave-enc1d40 Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/18) root@S36MANDAR:
[Desktop-packages] [Bug 1790098] Comment bridged from LTC Bugzilla
--- Comment From abhir...@in.ibm.com 2018-09-10 05:16 EDT--- Vorlon, In the detailed steps , the commands have been simplified. Let me put simple use case for ease to avoid confusion. 1)Create bond using nmcli utility with below attributes set: one slave (eth0) , mode = active_backup , ipv4 is assigned to bond say 30.1.2.100/24 2)Create VLAN on top of bond created in above step 1. ipv4 is assigned to vlan say 30.1.3.100/24 3)Ping operation under test works for 30.1.2.1 and 30.1.3.1 4)Deactivate bond. Vlan also gets deactivated. Both 30.1.2.1 and 30.1.3.1 are not reachable. Because ip routes no more exists on deactivation of bond. #This is expected as per my understanding 5)Activate bond. VLAN DOES NOT GET ACTIVATED AUTOMATICALLY. Only 30.1.2.1 is reachable. Route for VLAN is not created. #This was working in combination with nmcli + other distros automatically, and as a end user need not do any operation with respect to VLAN. 6)For nmcli + Ubuntu, we are forced to Manually Activate VLAN, route is then created for VLAN. 30.1.3.1 is now reachable. Above steps can be repeated 1)Without assiging ip to bond as well 2)For some reasons if we want to add a new slave or delete a slave from bond OR change any attributes of bond say primary, primary_reselect etc, bond is deactivated, attributes of bond are modified and activated. In this process VLAN gets deactivated autmatically but not gets auto - activated resulting in loss of traffic So either i suspect one of the two issues here 1)nmcli was internally handling this in case of other distros. i.e deactivated the vlan, when bond is deactivated and activate the vlan , when bond is activated. OR 2)network kernel underlying module takes care of these notifications between bond and vlan. I suspected this because, as i did not see any log updates with respect to nmcli tool for automatically deactivating and activating VLAN -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1790098 Title: vlan created on bond fails auto activation on updating parent network bond Status in Ubuntu on IBM z Systems: Incomplete Status in network-manager package in Ubuntu: Incomplete Bug description: Auto activation of Vlan created over network-bond fails if bond is deactivated and reactivated. Contact Information = Abhiram Kulkarni(abhir...@in.ibm.com), Mandar Deshpande(manda...@in.ibm.com) ---uname output--- Linux S36MANDAR 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:23 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Created a network bond with static IP address (and no IPv6 address); active backup mode; ARP polling; single slave. 2. Created a VLAN using said network bond with static IPv4 address (and no IPv6 address). 3. Can ping from the appliance to a target on both links (the parent bond and the VLAN). 4. Switched to another slave for the created bond 5. Can still ping from the appliance to a target via the parent bond; however, cannot ping to the target via the VLAN. = Detailed steps: 1. Initial setup: root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 2. Create Netwrok-bond with one slave: root@S36MANDAR:~# nmcli c add type bond con-name mybond1 ifname mybond1 ipv4.method disabled ipv6.method ignore Connection 'mybond1' (4b918a65-43a6-4ec3-b3c4-388ed52b116d) successfully added. root@S36MANDAR:~# nmcli con add type ethernet ifname enc1d40 master mybond1 Connection 'bond-slave-enc1d40' (cfe4b245-3dda-4f45-b7b4-6d40d144a02f) successfully added. root@S36MANDAR:~# nmcli con up bond-slave-enc1d40 Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/18) root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE bond-slave-enc1d40 cfe4b245-3dda-4f45-b7b4-6d40d144a02f ethernet enc1d40 enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d bond mybond1 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 3. Create vlan over mybond1: === root@S36MANDAR:~# nmcli con add type vlan con-name vlanbond.100 ifname vlanbond.100 dev myb
[Desktop-packages] [Bug 1790098] Comment bridged from LTC Bugzilla
--- Comment From abhir...@in.ibm.com 2018-09-07 05:39 EDT--- I agree that we need to switch to netplan, but that is currently not feasible approach for us. We will keep you updated once we have anything concrete on it. We expect nmcli also to work as we get the rpm from ubuntu repo. While i was investigating the below case between RHEL and Ubuntu, i noticed the below behaviour. Test case : 1)Create bond 2)Create vlan 3)Deactivate bond #routes for both bond and vlan gets deleted## Hence vlan also gets deactivated 4)Activate bond #Routes get created for bond and not for vlan. ## Hence vlan continues to be in deactivated state? Where in case of RHEL, the route for vlan also was created in step 4, hence the vlan was in activated state. I monitored the system logs during above execution, i did not notice nmcli doing any explicit activation/deactivation logs for vlan when bond was deactivated or activated. So with this i suspect, its underlying kernel taking care of some sort of notification events which is black box to me. Could you please help us inspect on same lines and review the case? What is the expected behaviour with netplan for the above test case? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1790098 Title: vlan created on bond fails auto activation on updating parent network bond Status in Ubuntu on IBM z Systems: Incomplete Status in network-manager package in Ubuntu: Incomplete Bug description: Auto activation of Vlan created over network-bond fails if bond is deactivated and reactivated. Contact Information = Abhiram Kulkarni(abhir...@in.ibm.com), Mandar Deshpande(manda...@in.ibm.com) ---uname output--- Linux S36MANDAR 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:23 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Created a network bond with static IP address (and no IPv6 address); active backup mode; ARP polling; single slave. 2. Created a VLAN using said network bond with static IPv4 address (and no IPv6 address). 3. Can ping from the appliance to a target on both links (the parent bond and the VLAN). 4. Switched to another slave for the created bond 5. Can still ping from the appliance to a target via the parent bond; however, cannot ping to the target via the VLAN. = Detailed steps: 1. Initial setup: root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 2. Create Netwrok-bond with one slave: root@S36MANDAR:~# nmcli c add type bond con-name mybond1 ifname mybond1 ipv4.method disabled ipv6.method ignore Connection 'mybond1' (4b918a65-43a6-4ec3-b3c4-388ed52b116d) successfully added. root@S36MANDAR:~# nmcli con add type ethernet ifname enc1d40 master mybond1 Connection 'bond-slave-enc1d40' (cfe4b245-3dda-4f45-b7b4-6d40d144a02f) successfully added. root@S36MANDAR:~# nmcli con up bond-slave-enc1d40 Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/18) root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE bond-slave-enc1d40 cfe4b245-3dda-4f45-b7b4-6d40d144a02f ethernet enc1d40 enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d bond mybond1 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 3. Create vlan over mybond1: === root@S36MANDAR:~# nmcli con add type vlan con-name vlanbond.100 ifname vlanbond.100 dev mybond1 id 100 ipv4.method disabled ipv6.method ignore Connection 'vlanbond.100' (e054df42-97a0-492b-b2c9-b9571077493e) successfully added. root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE bond-slave-enc1d40 cfe4b245-3dda-4f45-b7b4-6d40d144a02f ethernet enc1d40 enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d bond mybond1 vlanbond.100e054df42-97a0-492b-b2c9-b9571077493e vlan vlanbond.100 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07
[Desktop-packages] [Bug 1772859] Re: Network Manager is not able to manage the devices on Ubuntu 18.04
--- Comment From heinz-werner_se...@de.ibm.com 2018-07-19 07:30 EDT--- IBM bugzilla status -> closed, Problem solved. ** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin1804 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1772859 Title: Network Manager is not able to manage the devices on Ubuntu 18.04 Status in Ubuntu on IBM z Systems: Invalid Status in network-manager package in Ubuntu: Invalid Bug description: NetworkManager is not able to manage the devices on latest Ubuntu(18.04) ---uname output--- Linux (none) 4.15.0-12-generic #13-Ubuntu SMP Wed Mar 7 21:36:36 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = z14 s390 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Install the latest Ubuntu(18.04) with Network Manager(1.10.4). 2. Configure a network device and login to the partition through ssh. 3. Now you can see the following output root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- Userspace tool common name: 1.10.6-2ubuntu1: amd64 arm64 armhf i386 ppc64el s390x The userspace tool has the following bit modes: 64-bit Userspace rpm: NetworkManager --version 1.10.4 Userspace tool obtained from project website: na Some more information about the issue: Network device has been configured manually after the image is up from Support Element(SE): - znetconf -a - cat /sys/bus/ccwgroup/drivers/qeth//if_name - ifconfig netmask 255.255.255.0 - route add default gw - SSH service has been configured This helped us to login to the Lpar. In Lpar - output of znetconf -c Device IDs TypeCard Type CHPID Drv. Name State - 0.0.1a80,0.0.1a81,0.0.1a82 1731/01 OSD_10GIG A8 qeth eth0 online 0.0.1810,0.0.1811,0.0.1812 1731/01 OSD_1000 D0 qeth eth1 online - output of nmcli c s root@(none):~# nmcli c s NAME UUID TYPE DEVICE - output of nmcli d s root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- * The above output shows that devices are not managed by nmcli After some investigation we found couple of suggestions like 1. Ubuntu(version <17.04): Creating an empty file(/etc/NetworkManager/conf.d/10-globally-managed-devices.conf) and restarting NM, solved the issue. 2. Ubuntu(version 17.10): Copying the said file(10-globally-managed-devices.conf) from /usr/lib to /etc/ and modifying the "unmanaged-devices" to none, resolved the issue. * link for reference: https://bugs.launchpad.net/ubuntu/+source /network-manager/+bug/1638842 For the latest version(18.04), none of the above solutions worked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1772859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1642965] Comment bridged from LTC Bugzilla
--- Comment From jac...@de.ibm.com 2018-06-18 04:53 EDT--- Still crashing: Thread 1 "firefox" received signal SIGSEGV, Segmentation fault. MOZ_CrashOOL (aLine=672, aReason=0x3fff85c5fac "u_init() failed") at /build/firefox-p64FVO/firefox-60.0.2+build1/mfbt/Assertions.cpp:33 33 /build/firefox-p64FVO/firefox-60.0.2+build1/mfbt/Assertions.cpp: No such file or directory. (gdb) info stack #0 MOZ_CrashOOL (aLine=672, aReason=0x3fff85c5fac "u_init() failed") at /build/firefox-p64FVO/firefox-60.0.2+build1/mfbt/Assertions.cpp:33 #1 0x03fff489f3e6 in NS_InitXPCOM2 (aResult=0x3fffd687a20, aBinDirectory=, aAppFileLocationProvider=) at /build/firefox-p64FVO/firefox-60.0.2+build1/xpcom/build/XPCOMInit.cpp:672 #2 0x03fff489f404 in NS_InitXPCOM2 (aResult=aResult@entry=0x3fffd687a20, aBinDirectory=, aAppFileLocationProvider=) at /build/firefox-p64FVO/firefox-60.0.2+build1/xpcom/build/XPCOMInit.cpp:736 #3 0x03fff7657c20 in ScopedXPCOMStartup::Initialize (this=0x3fffd687a20) at /build/firefox-p64FVO/firefox-60.0.2+build1/toolkit/xre/nsAppRunner.cpp:1572 #4 0x03fff765e358 in XREMain::XRE_main (this=this@entry=0x3ffe2b0, argc=argc@entry=1, argv=argv@entry=0x3fff7d8, aConfig=...) at /build/firefox-p64FVO/firefox-60.0.2+build1/toolkit/xre/nsAppRunner.cpp:4966 #5 0x03fff765e772 in XRE_main (argc=, argv=0x3fff7d8, aConfig=...) at /build/firefox-p64FVO/firefox-60.0.2+build1/toolkit/xre/nsAppRunner.cpp:5062 #6 0x00016140 in do_main (argc=, argv=0x3fff7d8, envp=) at /build/firefox-p64FVO/firefox-60.0.2+build1/browser/app/nsBrowserApp.cpp:231 #7 0x00015960 in main (argc=, argv=0x3fff7d8, envp=0x3fff7e8) at /build/firefox-p64FVO/firefox-60.0.2+build1/browser/app/nsBrowserApp.cpp:304 ... at least we have build, but we also need something that actually "works"! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1642965 Title: Firefox crashes - Error loading theme icon Status in firefox package in Ubuntu: Won't Fix Bug description: Linux lnx 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:14:35 UTC 2016 s390x s390x s390x GNU/Linux Firefox: firefox 47.0+build3-0ubuntu0.16.04.1 Description: Firefox crashes when trying to start it on the server and display on the local client. Other X application can be displayed. Reproduction: Login to the server: ssh -X lnxserver Start firefox: firefox --no-remote Error Message: (firefox:39655): Gtk-WARNING **: Error loading theme icon 'list-add' for stock: Icon 'list-add' not present in theme System Segmentation fault (core dumped) == Comment: #6 - Thorsten Diehl - 2016-11-16 11:50:35 == I can confirm this. I installed Ubuntu 16.04.1 on s390x (z13 machine) and installed updates, then x11-apps, which were working fine (xclock, xeyes). I installed firefox and started it: firefox --no-remote it created tons of messages, all complaing about an unknown image format. Any subsequent start does not create that many messages. But even with --safe-mode I can't get it started: root@s8330009:~# firefox --no-remote --safe-mode (firefox:1487): Gtk-WARNING **: Locale not supported by C library. Using the fallback 'C' locale. Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknown image format 1 (t=0.627128) [GFX1]: Unknown image format 1 Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknown image format 1 (t=0.627128) |[1][GFX1]: Unknown image format 0 (t=0.631695) [GFX1]: Unknown image format 0 [1487] ###!!! ABORT: X_ShmAttach: BadAccess (attempt to access private resource denied); 3 requests ago: file /build/firefox-xMihVX/firefox-47.0+build3/toolkit/xre/nsX11ErrorHandler.cpp, line 157 [1487] ###!!! ABORT: X_ShmAttach: BadAccess (attempt to access private resource denied); 3 requests ago: file /build/firefox-xMihVX/firefox-47.0+build3/toolkit/xre/nsX11ErrorHandler.cpp, line 157 Perhaps a graphics library (gtklib?) has a problem? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1642965/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772859] Comment bridged from LTC Bugzilla
--- Comment From sankar...@in.ibm.com 2018-06-07 06:47 EDT--- Hi there, Now Network Manager(NM) is able to manage the devices with the following changes. Change the contents of the file /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf to [keyfile] unmanaged-devices=none from [keyfile] unmanaged-devices=*,except:type:wifi,except:type:wwan and restart NM(service network-manager restart) did the trick. Why it didn't work earlier: We added interfaces to the file /etc/network/interfaces. So NM is not able to manage the interfaces updated in the said file. When we removed the interfaces from the above file, It started working. Is this approach correct ?? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1772859 Title: Network Manager is not able to manage the devices on Ubuntu 18.04 Status in Ubuntu on IBM z Systems: Invalid Status in network-manager package in Ubuntu: Invalid Bug description: NetworkManager is not able to manage the devices on latest Ubuntu(18.04) ---uname output--- Linux (none) 4.15.0-12-generic #13-Ubuntu SMP Wed Mar 7 21:36:36 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = z14 s390 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Install the latest Ubuntu(18.04) with Network Manager(1.10.4). 2. Configure a network device and login to the partition through ssh. 3. Now you can see the following output root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- Userspace tool common name: 1.10.6-2ubuntu1: amd64 arm64 armhf i386 ppc64el s390x The userspace tool has the following bit modes: 64-bit Userspace rpm: NetworkManager --version 1.10.4 Userspace tool obtained from project website: na Some more information about the issue: Network device has been configured manually after the image is up from Support Element(SE): - znetconf -a - cat /sys/bus/ccwgroup/drivers/qeth//if_name - ifconfig netmask 255.255.255.0 - route add default gw - SSH service has been configured This helped us to login to the Lpar. In Lpar - output of znetconf -c Device IDs TypeCard Type CHPID Drv. Name State - 0.0.1a80,0.0.1a81,0.0.1a82 1731/01 OSD_10GIG A8 qeth eth0 online 0.0.1810,0.0.1811,0.0.1812 1731/01 OSD_1000 D0 qeth eth1 online - output of nmcli c s root@(none):~# nmcli c s NAME UUID TYPE DEVICE - output of nmcli d s root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- * The above output shows that devices are not managed by nmcli After some investigation we found couple of suggestions like 1. Ubuntu(version <17.04): Creating an empty file(/etc/NetworkManager/conf.d/10-globally-managed-devices.conf) and restarting NM, solved the issue. 2. Ubuntu(version 17.10): Copying the said file(10-globally-managed-devices.conf) from /usr/lib to /etc/ and modifying the "unmanaged-devices" to none, resolved the issue. * link for reference: https://bugs.launchpad.net/ubuntu/+source /network-manager/+bug/1638842 For the latest version(18.04), none of the above solutions worked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1772859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772859] Comment bridged from LTC Bugzilla
--- Comment From kieni...@de.ibm.com 2018-06-07 03:18 EDT--- "So your system is obviously not an 18.04 default installation from scratch" This is correct. We are not using a standard installation but build an appliance with a minimal footprint. Our build process builds the appliance using debootstrap and we are using a local apt repository with the deb packages from UBUNTU 18.04 as input for debootstrap. So we are basically controlling what packages are installed in our appliances and right now netplan is not included. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1772859 Title: Network Manager is not able to manage the devices on Ubuntu 18.04 Status in Ubuntu on IBM z Systems: Invalid Status in network-manager package in Ubuntu: Invalid Bug description: NetworkManager is not able to manage the devices on latest Ubuntu(18.04) ---uname output--- Linux (none) 4.15.0-12-generic #13-Ubuntu SMP Wed Mar 7 21:36:36 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = z14 s390 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Install the latest Ubuntu(18.04) with Network Manager(1.10.4). 2. Configure a network device and login to the partition through ssh. 3. Now you can see the following output root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- Userspace tool common name: 1.10.6-2ubuntu1: amd64 arm64 armhf i386 ppc64el s390x The userspace tool has the following bit modes: 64-bit Userspace rpm: NetworkManager --version 1.10.4 Userspace tool obtained from project website: na Some more information about the issue: Network device has been configured manually after the image is up from Support Element(SE): - znetconf -a - cat /sys/bus/ccwgroup/drivers/qeth//if_name - ifconfig netmask 255.255.255.0 - route add default gw - SSH service has been configured This helped us to login to the Lpar. In Lpar - output of znetconf -c Device IDs TypeCard Type CHPID Drv. Name State - 0.0.1a80,0.0.1a81,0.0.1a82 1731/01 OSD_10GIG A8 qeth eth0 online 0.0.1810,0.0.1811,0.0.1812 1731/01 OSD_1000 D0 qeth eth1 online - output of nmcli c s root@(none):~# nmcli c s NAME UUID TYPE DEVICE - output of nmcli d s root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- * The above output shows that devices are not managed by nmcli After some investigation we found couple of suggestions like 1. Ubuntu(version <17.04): Creating an empty file(/etc/NetworkManager/conf.d/10-globally-managed-devices.conf) and restarting NM, solved the issue. 2. Ubuntu(version 17.10): Copying the said file(10-globally-managed-devices.conf) from /usr/lib to /etc/ and modifying the "unmanaged-devices" to none, resolved the issue. * link for reference: https://bugs.launchpad.net/ubuntu/+source /network-manager/+bug/1638842 For the latest version(18.04), none of the above solutions worked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1772859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772859] Comment bridged from LTC Bugzilla
--- Comment From abhir...@in.ibm.com 2018-06-06 14:43 EDT--- Team, We understand Network Manager is good for desktop but not servers. But given the stability NetworkManager is bringing in and ease of use across different operating systems, i assume users are not restricted not to use NetworkManager for servers. The reason being we going with network manager as explained is to reuse the code for all distros. Note : Netplan is not present/installed in our ubuntu. So by default we are expecting network manager to work. root@57fb2571ae8a:~# ls -l /etc | grep netplan root@57fb2571ae8a:~# If we need to start using netplan, probably we have to re-write the code to configure yaml files which can be understood by netplan. So as a workaround, we would like to understand why network manager is failing to manage the devices? This is definitely to do with open issue, https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842 Let me know if more data is needed for analysis, Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1772859 Title: Network Manager is not able to manage the devices on Ubuntu 18.04 Status in Ubuntu on IBM z Systems: Invalid Status in network-manager package in Ubuntu: Invalid Bug description: NetworkManager is not able to manage the devices on latest Ubuntu(18.04) ---uname output--- Linux (none) 4.15.0-12-generic #13-Ubuntu SMP Wed Mar 7 21:36:36 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = z14 s390 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Install the latest Ubuntu(18.04) with Network Manager(1.10.4). 2. Configure a network device and login to the partition through ssh. 3. Now you can see the following output root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- Userspace tool common name: 1.10.6-2ubuntu1: amd64 arm64 armhf i386 ppc64el s390x The userspace tool has the following bit modes: 64-bit Userspace rpm: NetworkManager --version 1.10.4 Userspace tool obtained from project website: na Some more information about the issue: Network device has been configured manually after the image is up from Support Element(SE): - znetconf -a - cat /sys/bus/ccwgroup/drivers/qeth//if_name - ifconfig netmask 255.255.255.0 - route add default gw - SSH service has been configured This helped us to login to the Lpar. In Lpar - output of znetconf -c Device IDs TypeCard Type CHPID Drv. Name State - 0.0.1a80,0.0.1a81,0.0.1a82 1731/01 OSD_10GIG A8 qeth eth0 online 0.0.1810,0.0.1811,0.0.1812 1731/01 OSD_1000 D0 qeth eth1 online - output of nmcli c s root@(none):~# nmcli c s NAME UUID TYPE DEVICE - output of nmcli d s root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- * The above output shows that devices are not managed by nmcli After some investigation we found couple of suggestions like 1. Ubuntu(version <17.04): Creating an empty file(/etc/NetworkManager/conf.d/10-globally-managed-devices.conf) and restarting NM, solved the issue. 2. Ubuntu(version 17.10): Copying the said file(10-globally-managed-devices.conf) from /usr/lib to /etc/ and modifying the "unmanaged-devices" to none, resolved the issue. * link for reference: https://bugs.launchpad.net/ubuntu/+source /network-manager/+bug/1638842 For the latest version(18.04), none of the above solutions worked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1772859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772859] Comment bridged from LTC Bugzilla
--- Comment From abhir...@in.ibm.com 2018-06-06 03:26 EDT--- Team, We understand Network Manager is good for desktop but not servers. But given the stability NetworkManager is bringing in and ease of use across different operating systems, i assume users are not restricted not to use NetworkManager for servers. The reason being we going with network manager as explained is to reuse the code for all distros. Note : Netplan is not present/installed in our ubuntu. So by default we are expecting network manager to work. root@57fb2571ae8a:~# ls -l /etc | grep netplan root@57fb2571ae8a:~# If we need to start using netplan, probably we have to re-write the code to configure yaml files which can be understood by netplan. So as a workaround, we would like to understand why network manager is failing to manage the devices? This is definitely to do with open issue, https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842 Let me know if more data is needed for analysis, Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1772859 Title: Network Manager is not able to manage the devices on Ubuntu 18.04 Status in Ubuntu on IBM z Systems: Invalid Status in network-manager package in Ubuntu: Invalid Bug description: NetworkManager is not able to manage the devices on latest Ubuntu(18.04) ---uname output--- Linux (none) 4.15.0-12-generic #13-Ubuntu SMP Wed Mar 7 21:36:36 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = z14 s390 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Install the latest Ubuntu(18.04) with Network Manager(1.10.4). 2. Configure a network device and login to the partition through ssh. 3. Now you can see the following output root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- Userspace tool common name: 1.10.6-2ubuntu1: amd64 arm64 armhf i386 ppc64el s390x The userspace tool has the following bit modes: 64-bit Userspace rpm: NetworkManager --version 1.10.4 Userspace tool obtained from project website: na Some more information about the issue: Network device has been configured manually after the image is up from Support Element(SE): - znetconf -a - cat /sys/bus/ccwgroup/drivers/qeth//if_name - ifconfig netmask 255.255.255.0 - route add default gw - SSH service has been configured This helped us to login to the Lpar. In Lpar - output of znetconf -c Device IDs TypeCard Type CHPID Drv. Name State - 0.0.1a80,0.0.1a81,0.0.1a82 1731/01 OSD_10GIG A8 qeth eth0 online 0.0.1810,0.0.1811,0.0.1812 1731/01 OSD_1000 D0 qeth eth1 online - output of nmcli c s root@(none):~# nmcli c s NAME UUID TYPE DEVICE - output of nmcli d s root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- * The above output shows that devices are not managed by nmcli After some investigation we found couple of suggestions like 1. Ubuntu(version <17.04): Creating an empty file(/etc/NetworkManager/conf.d/10-globally-managed-devices.conf) and restarting NM, solved the issue. 2. Ubuntu(version 17.10): Copying the said file(10-globally-managed-devices.conf) from /usr/lib to /etc/ and modifying the "unmanaged-devices" to none, resolved the issue. * link for reference: https://bugs.launchpad.net/ubuntu/+source /network-manager/+bug/1638842 For the latest version(18.04), none of the above solutions worked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1772859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772859] Comment bridged from LTC Bugzilla
--- Comment From abhir...@in.ibm.com 2018-06-01 03:11 EDT--- Team, Any update on this issue? This is blocking our experimentation of Network Manager on Ubuntu platform. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1772859 Title: Network Manager is not able to manage the devices on Ubuntu 18.04 Status in Ubuntu on IBM z Systems: New Status in network-manager package in Ubuntu: New Bug description: NetworkManager is not able to manage the devices on latest Ubuntu(18.04) ---uname output--- Linux (none) 4.15.0-12-generic #13-Ubuntu SMP Wed Mar 7 21:36:36 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = z14 s390 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Install the latest Ubuntu(18.04) with Network Manager(1.10.4). 2. Configure a network device and login to the partition through ssh. 3. Now you can see the following output root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- Userspace tool common name: 1.10.6-2ubuntu1: amd64 arm64 armhf i386 ppc64el s390x The userspace tool has the following bit modes: 64-bit Userspace rpm: NetworkManager --version 1.10.4 Userspace tool obtained from project website: na Some more information about the issue: Network device has been configured manually after the image is up from Support Element(SE): - znetconf -a - cat /sys/bus/ccwgroup/drivers/qeth//if_name - ifconfig netmask 255.255.255.0 - route add default gw - SSH service has been configured This helped us to login to the Lpar. In Lpar - output of znetconf -c Device IDs TypeCard Type CHPID Drv. Name State - 0.0.1a80,0.0.1a81,0.0.1a82 1731/01 OSD_10GIG A8 qeth eth0 online 0.0.1810,0.0.1811,0.0.1812 1731/01 OSD_1000 D0 qeth eth1 online - output of nmcli c s root@(none):~# nmcli c s NAME UUID TYPE DEVICE - output of nmcli d s root@(none):~# nmcli d s DEVICE TYPE STATE CONNECTION eth0ethernet unmanaged -- eth1ethernet unmanaged -- lo loopback unmanaged -- * The above output shows that devices are not managed by nmcli After some investigation we found couple of suggestions like 1. Ubuntu(version <17.04): Creating an empty file(/etc/NetworkManager/conf.d/10-globally-managed-devices.conf) and restarting NM, solved the issue. 2. Ubuntu(version 17.10): Copying the said file(10-globally-managed-devices.conf) from /usr/lib to /etc/ and modifying the "unmanaged-devices" to none, resolved the issue. * link for reference: https://bugs.launchpad.net/ubuntu/+source /network-manager/+bug/1638842 For the latest version(18.04), none of the above solutions worked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1772859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1642965] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2018-01-12 05:35 EDT--- IBM bugzilla status -> closed, current out-of-sope for s390x. If this will change, a new bugzilla be created. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1642965 Title: Firefox crashes - Error loading theme icon Status in firefox package in Ubuntu: Won't Fix Bug description: Linux lnx 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:14:35 UTC 2016 s390x s390x s390x GNU/Linux Firefox: firefox 47.0+build3-0ubuntu0.16.04.1 Description: Firefox crashes when trying to start it on the server and display on the local client. Other X application can be displayed. Reproduction: Login to the server: ssh -X lnxserver Start firefox: firefox --no-remote Error Message: (firefox:39655): Gtk-WARNING **: Error loading theme icon 'list-add' for stock: Icon 'list-add' not present in theme System Segmentation fault (core dumped) == Comment: #6 - Thorsten Diehl - 2016-11-16 11:50:35 == I can confirm this. I installed Ubuntu 16.04.1 on s390x (z13 machine) and installed updates, then x11-apps, which were working fine (xclock, xeyes). I installed firefox and started it: firefox --no-remote it created tons of messages, all complaing about an unknown image format. Any subsequent start does not create that many messages. But even with --safe-mode I can't get it started: root@s8330009:~# firefox --no-remote --safe-mode (firefox:1487): Gtk-WARNING **: Locale not supported by C library. Using the fallback 'C' locale. Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknown image format 1 (t=0.627128) [GFX1]: Unknown image format 1 Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknown image format 1 (t=0.627128) |[1][GFX1]: Unknown image format 0 (t=0.631695) [GFX1]: Unknown image format 0 [1487] ###!!! ABORT: X_ShmAttach: BadAccess (attempt to access private resource denied); 3 requests ago: file /build/firefox-xMihVX/firefox-47.0+build3/toolkit/xre/nsX11ErrorHandler.cpp, line 157 [1487] ###!!! ABORT: X_ShmAttach: BadAccess (attempt to access private resource denied); 3 requests ago: file /build/firefox-xMihVX/firefox-47.0+build3/toolkit/xre/nsX11ErrorHandler.cpp, line 157 Perhaps a graphics library (gtklib?) has a problem? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1642965/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1706948] Re: [Ubuntu 18.04] [Feature] Inconsistent report of pm CanSuspend state by systemd and pm-utils
--- Comment From nasas...@in.ibm.com 2017-09-19 01:35 EDT---
Tested this on latest libvirtd 3.6.0 and I am not seeing the issue.
# gdbus call --system --dest org.freedesktop.login1 --object-path
/org/freedesktop/login1 --method
org.freedesktop.login1.Manager.CanSuspend('yes',)
# pm-is-supported --suspend
# echo $?
0
# cat /sys/power/state
freeze mem
--- Comment From nasas...@in.ibm.com 2017-09-19 01:42 EDT---
pm-utils 1.4.1-17
Version of pm-utils
--- Comment From balamuruh...@in.ibm.com 2017-09-19 05:27 EDT---
(In reply to comment #7)
> Bala,
>
> Is this still an issue with the latest libvirt updates in Ubuntu 17.10?
Hi Leonardo,
This bug originated from
https://bugzilla.linux.ibm.com/show_bug.cgi?id=150043 for the purpose of
tracking in Ubuntu. The issue have been fixed in Kernel and can be
closed.
Thank you Nageswara for validating it.
-- Bala
--- Comment From lagar...@br.ibm.com 2017-10-09 08:16 EDT---
Closing based on last comment.
** Bug watch added: bugzilla.linux.ibm.com/ #150043
https://bugzilla.linux.ibm.com/show_bug.cgi?id=150043
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1706948
Title:
[Ubuntu 18.04] [Feature] Inconsistent report of pm CanSuspend state by
systemd and pm-utils
Status in The Ubuntu-power-systems project:
Incomplete
Status in pm-utils package in Ubuntu:
Incomplete
Bug description:
== Comment: #0 - Balamuruhan S <> - 2017-06-28 03:39:15 ==
systemd and pm-utils interprets CanSuspend states differently and reports it
as supported or not in a conflicting way.
# gdbus call --system --dest org.freedesktop.login1 --object-path
/org/freedesktop/login1 --method org.freedesktop.login1.Manager.CanSuspend
('yes',)
# pm-is-supported --suspend
# echo $?
1
Both systemd and pm-is-supported looks into /sys/power/state file to
check if suspend is supported.
pm-is-supported --suspend returns true if either "standby" or "mem" is
present in the file.
( /usr/lib/pm-utils/pm-functions )
systemd(Manager.CanSuspend) returns true if "standby", "freeze" or "mem" is
present in the file.
(
https://github.com/systemd/systemd/blob/dd8352659c9428b196706d04399eec106a8917ed/src/shared/sleep-config.c
)
# cat /sys/power/state
freeze
So here, pm-is-supported --suspend returns false and gdbus returns
true.
Both these utilities interpret /sys/power/state differently.
Secondly, systemd should split CanSuspend to Cansuspend+CanFreeze Or
don't report freeze as CanSuspend.
Impact of this inconsistency can be felt from Libvirt supported pm
states:
To reduce ABI dependency, libvirt queries the available states via
dbus, if not falls to pm-utils. Libvirt won't check for strings in
sys/power/state and interpret directly.
so due to this, libvirt will list that suspend_to_mem is supported
from virsh capabilities but ideally it might not.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1706948/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1734032] Comment bridged from LTC Bugzilla
--- Comment From vaish...@in.ibm.com 2017-11-23 03:36 EDT--- (In reply to comment #9) > nabi is a package that belongs to Ubuntu Desktop. > And the underlying platform is listed as x86_64. > > But why is this ticket marked as affecting the ubuntu-power-systems project? > Ubuntu for Power is Ubuntu Server only. This was tested in a Desktop environment and not Power server. Thank you. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nabi in Ubuntu. https://bugs.launchpad.net/bugs/1734032 Title: X11 application cannot get nabi XIM server's state Status in nabi package in Ubuntu: New Bug description: ---Problem Description--- X11 application cannot get nabi XIM server's state. ---uname output--- 4.10.0-30-generic #34~16.04.1-Ubuntu SMP Wed Aug 2 02:13:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Machine Type = x64 machine ---Steps to Reproduce--- This testing requires X11 desktop environment , nabi XIM server (nabi package) and Korean locale. 1. Login to X11 environmnet 2. Download attached xim_root.zip file 3. Compile it with "-lX11" option, like $ cc -o xim_root xim_root.c -lX11 4. Change current local ko_KR.utf8, like $ export LANG=ko_KR.utf8 5. Start nabi, like $ nabi & (XIM's state may display somewhere...) 6. Start xim_root with XMODIFIERS environment variable, like $ XMODIFIERS=@im=nabi ./xim_root 7. Press "A" key, then xim_root prints "XmbLookupString:a" 8. Press Ctrl+Muddle Mouse button on xim_root, then print "State: IM On", even if IM is not turned ON <== ISSUE 9. Press Shift+Space key to turn on, then type "gks", Korean character is displayed on xim_root, then press Return key, this Korean character is committed 10. Press Ctrl+Left Mouse button to turn off XIM server, then type "gks", but still XIM is turned on <== ISSUE 11. Press Ctrl+Middle Mouse button, print "State: IM Off". So X11 application cannot get XIM state properly. $ ps -ef | grep nabi jdktest 4377 3409 0 21:21 pts/10 00:00:00 nabi jdktest 7427 1760 0 21:40 pts/100:00:00 grep --color=auto nabi $ apport-cli 4377 --save=bug.apport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nabi/+bug/1734032/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1734032] bug.apport
Default Comment by Bridge ** Attachment added: "bug.apport" https://bugs.launchpad.net/bugs/1734032/+attachment/5013198/+files/bug.apport ** Changed in: ubuntu Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** Package changed: ubuntu => nabi (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nabi in Ubuntu. https://bugs.launchpad.net/bugs/1734032 Title: X11 application cannot get nabi XIM server's state Status in nabi package in Ubuntu: New Bug description: ---Problem Description--- X11 application cannot get nabi XIM server's state. ---uname output--- 4.10.0-30-generic #34~16.04.1-Ubuntu SMP Wed Aug 2 02:13:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Machine Type = x64 machine ---Steps to Reproduce--- This testing requires X11 desktop environment , nabi XIM server (nabi package) and Korean locale. 1. Login to X11 environmnet 2. Download attached xim_root.zip file 3. Compile it with "-lX11" option, like $ cc -o xim_root xim_root.c -lX11 4. Change current local ko_KR.utf8, like $ export LANG=ko_KR.utf8 5. Start nabi, like $ nabi & (XIM's state may display somewhere...) 6. Start xim_root with XMODIFIERS environment variable, like $ XMODIFIERS=@im=nabi ./xim_root 7. Press "A" key, then xim_root prints "XmbLookupString:a" 8. Press Ctrl+Muddle Mouse button on xim_root, then print "State: IM On", even if IM is not turned ON <== ISSUE 9. Press Shift+Space key to turn on, then type "gks", Korean character is displayed on xim_root, then press Return key, this Korean character is committed 10. Press Ctrl+Left Mouse button to turn off XIM server, then type "gks", but still XIM is turned on <== ISSUE 11. Press Ctrl+Middle Mouse button, print "State: IM Off". So X11 application cannot get XIM state properly. $ ps -ef | grep nabi jdktest 4377 3409 0 21:21 pts/10 00:00:00 nabi jdktest 7427 1760 0 21:40 pts/100:00:00 grep --color=auto nabi $ apport-cli 4377 --save=bug.apport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nabi/+bug/1734032/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1706948] Comment bridged from LTC Bugzilla
--- Comment From bren...@br.ibm.com 2017-10-19 09:20 EDT---
*** Bug 150856 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1706948
Title:
[Ubuntu 1710] [Feature] Inconsistent report of pm CanSuspend state by
systemd and pm-utils
Status in The Ubuntu-power-systems project:
Incomplete
Status in pm-utils package in Ubuntu:
Incomplete
Bug description:
== Comment: #0 - Balamuruhan S <> - 2017-06-28 03:39:15 ==
systemd and pm-utils interprets CanSuspend states differently and reports it
as supported or not in a conflicting way.
# gdbus call --system --dest org.freedesktop.login1 --object-path
/org/freedesktop/login1 --method org.freedesktop.login1.Manager.CanSuspend
('yes',)
# pm-is-supported --suspend
# echo $?
1
Both systemd and pm-is-supported looks into /sys/power/state file to
check if suspend is supported.
pm-is-supported --suspend returns true if either "standby" or "mem" is
present in the file.
( /usr/lib/pm-utils/pm-functions )
systemd(Manager.CanSuspend) returns true if "standby", "freeze" or "mem" is
present in the file.
(
https://github.com/systemd/systemd/blob/dd8352659c9428b196706d04399eec106a8917ed/src/shared/sleep-config.c
)
# cat /sys/power/state
freeze
So here, pm-is-supported --suspend returns false and gdbus returns
true.
Both these utilities interpret /sys/power/state differently.
Secondly, systemd should split CanSuspend to Cansuspend+CanFreeze Or
don't report freeze as CanSuspend.
Impact of this inconsistency can be felt from Libvirt supported pm
states:
To reduce ABI dependency, libvirt queries the available states via
dbus, if not falls to pm-utils. Libvirt won't check for strings in
sys/power/state and interpret directly.
so due to this, libvirt will list that suspend_to_mem is supported
from virsh capabilities but ideally it might not.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1706948/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1642965] Re: Firefox crashes - Error loading theme icon
** Tags removed: severity-critical ** Tags added: severity-medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1642965 Title: Firefox crashes - Error loading theme icon Status in firefox package in Ubuntu: Incomplete Bug description: Linux lnx 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:14:35 UTC 2016 s390x s390x s390x GNU/Linux Firefox: firefox 47.0+build3-0ubuntu0.16.04.1 Description: Firefox crashes when trying to start it on the server and display on the local client. Other X application can be displayed. Reproduction: Login to the server: ssh -X lnxserver Start firefox: firefox --no-remote Error Message: (firefox:39655): Gtk-WARNING **: Error loading theme icon 'list-add' for stock: Icon 'list-add' not present in theme System Segmentation fault (core dumped) == Comment: #6 - Thorsten Diehl - 2016-11-16 11:50:35 == I can confirm this. I installed Ubuntu 16.04.1 on s390x (z13 machine) and installed updates, then x11-apps, which were working fine (xclock, xeyes). I installed firefox and started it: firefox --no-remote it created tons of messages, all complaing about an unknown image format. Any subsequent start does not create that many messages. But even with --safe-mode I can't get it started: root@s8330009:~# firefox --no-remote --safe-mode (firefox:1487): Gtk-WARNING **: Locale not supported by C library. Using the fallback 'C' locale. Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknown image format 1 (t=0.627128) [GFX1]: Unknown image format 1 Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknown image format 1 (t=0.627128) |[1][GFX1]: Unknown image format 0 (t=0.631695) [GFX1]: Unknown image format 0 [1487] ###!!! ABORT: X_ShmAttach: BadAccess (attempt to access private resource denied); 3 requests ago: file /build/firefox-xMihVX/firefox-47.0+build3/toolkit/xre/nsX11ErrorHandler.cpp, line 157 [1487] ###!!! ABORT: X_ShmAttach: BadAccess (attempt to access private resource denied); 3 requests ago: file /build/firefox-xMihVX/firefox-47.0+build3/toolkit/xre/nsX11ErrorHandler.cpp, line 157 Perhaps a graphics library (gtklib?) has a problem? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1642965/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1706948] [NEW] [Ubuntu 1710] [Feature] Inconsistent report of pm CanSuspend state by systemd and pm-utils
Public bug reported:
== Comment: #0 - Balamuruhan S <> - 2017-06-28 03:39:15 ==
systemd and pm-utils interprets CanSuspend states differently and reports it as
supported or not in a conflicting way.
# gdbus call --system --dest org.freedesktop.login1 --object-path
/org/freedesktop/login1 --method org.freedesktop.login1.Manager.CanSuspend
('yes',)
# pm-is-supported --suspend
# echo $?
1
Both systemd and pm-is-supported looks into /sys/power/state file to
check if suspend is supported.
pm-is-supported --suspend returns true if either "standby" or "mem" is present
in the file.
( /usr/lib/pm-utils/pm-functions )
systemd(Manager.CanSuspend) returns true if "standby", "freeze" or "mem" is
present in the file.
(
https://github.com/systemd/systemd/blob/dd8352659c9428b196706d04399eec106a8917ed/src/shared/sleep-config.c
)
# cat /sys/power/state
freeze
So here, pm-is-supported --suspend returns false and gdbus returns true.
Both these utilities interpret /sys/power/state differently.
Secondly, systemd should split CanSuspend to Cansuspend+CanFreeze Or
don't report freeze as CanSuspend.
Impact of this inconsistency can be felt from Libvirt supported pm
states:
To reduce ABI dependency, libvirt queries the available states via dbus,
if not falls to pm-utils. Libvirt won't check for strings in
sys/power/state and interpret directly.
so due to this, libvirt will list that suspend_to_mem is supported from
virsh capabilities but ideally it might not.
** Affects: pm-utils (Ubuntu)
Importance: Undecided
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
Status: New
** Tags: architecture-ppc64le bugnameltc-156093 severity-high
targetmilestone-inin1710
** Tags added: architecture-ppc64le bugnameltc-156093 severity-high
targetmilestone-inin1710
** Changed in: ubuntu
Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage
(ubuntu-power-triage)
** Package changed: ubuntu => pm-utils (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1706948
Title:
[Ubuntu 1710] [Feature] Inconsistent report of pm CanSuspend state by
systemd and pm-utils
Status in pm-utils package in Ubuntu:
New
Bug description:
== Comment: #0 - Balamuruhan S <> - 2017-06-28 03:39:15 ==
systemd and pm-utils interprets CanSuspend states differently and reports it
as supported or not in a conflicting way.
# gdbus call --system --dest org.freedesktop.login1 --object-path
/org/freedesktop/login1 --method org.freedesktop.login1.Manager.CanSuspend
('yes',)
# pm-is-supported --suspend
# echo $?
1
Both systemd and pm-is-supported looks into /sys/power/state file to
check if suspend is supported.
pm-is-supported --suspend returns true if either "standby" or "mem" is
present in the file.
( /usr/lib/pm-utils/pm-functions )
systemd(Manager.CanSuspend) returns true if "standby", "freeze" or "mem" is
present in the file.
(
https://github.com/systemd/systemd/blob/dd8352659c9428b196706d04399eec106a8917ed/src/shared/sleep-config.c
)
# cat /sys/power/state
freeze
So here, pm-is-supported --suspend returns false and gdbus returns
true.
Both these utilities interpret /sys/power/state differently.
Secondly, systemd should split CanSuspend to Cansuspend+CanFreeze Or
don't report freeze as CanSuspend.
Impact of this inconsistency can be felt from Libvirt supported pm
states:
To reduce ABI dependency, libvirt queries the available states via
dbus, if not falls to pm-utils. Libvirt won't check for strings in
sys/power/state and interpret directly.
so due to this, libvirt will list that suspend_to_mem is supported
from virsh capabilities but ideally it might not.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1706948/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1679184] syslog, partman log, hardware-summary
Default Comment by Bridge ** Attachment added: "syslog, partman log, hardware-summary" https://bugs.launchpad.net/bugs/1679184/+attachment/4853576/+files/logs.tar ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => llvm-toolchain-3.5 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to llvm-toolchain-3.5 in Ubuntu. https://bugs.launchpad.net/bugs/1679184 Title: LVM configuration cannot be removed when volume groups with the same name are found during installation Status in llvm-toolchain-3.5 package in Ubuntu: New Bug description: Installer version: 20101020ubuntu500 Kernel: 4.10.0-14 Description/Reproduction: During installation, the installer finds LVM volume groups from a previous installation. Current LVM configuration: Unallocated physical volumes: * /dev/mapper/mpatha2 (21218MB) Volume groups: * rootVG (21218MB) - Uses physical volume: /dev/dasda2 (21315MB) - Uses physical volume: /dev/mapper/mpathc1 (21470MB) - Uses physical volume: [unknown](21470MB) - Uses physical volume: [unknown](21470MB) * rootVG (21470MB) - Uses physical volume: /dev/dasda2 (21315MB) - Uses physical volume: /dev/mapper/mpathc1 (21470MB) - Uses physical volume: [unknown](21470MB) - Uses physical volume: [unknown](21470MB) * rootvg (42685MB) - Uses physical volume: /dev/mapper/mpathb1 (21470MB) - Uses physical volume: [unknown](214 When trying to remove that LVM using "Configure the Logical Volume Manager", it is not possible to remove logical volumes. The error "The logical volume swapLV on rootVG could not be deleted." is displayed. In syslog, you see the following messages: Apr 3 12:55:56 partman-lvm: Multiple VGs found with the same name: skipping rootVG Apr 3 12:55:56 partman-lvm: Use --select vg_uuid= in place of the VG name. As you cannot use the suggested parameter in the installer, the system cannot be installed without manually removing the LVM setup with another shell. Debug logs are attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.5/+bug/1679184/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1646956] Comment bridged from LTC Bugzilla
--- Comment From ru...@us.ibm.com 2017-03-14 11:57 EDT--- iputils (3:20161105-1ubuntu2) validated and closing out on our end. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1646956 Title: ping -I support broken in yakkety version 3:20150815-2ubuntu3 (multicast test failure) Status in iputils package in Ubuntu: Fix Released Bug description: == Comment: #0 - HARSHA THYAGARAJA - 2016-11-15 03:42:59 == ---Problem Description--- Multicast failing for Shiner interface on Ubuntu 16.10 (bnx2x) Machine Type = S822l1 ---Steps to Reproduce--- On Host: Enable multicast for the test interface 1. echo 0 > /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts 2. ip link set enP5p1s0f1 allmulticast on root@ltciofvtr-s822l1:~# ifconfig enP5p1s0f1 enP5p1s0f1: flags=4675 mtu 1500 inet 170.1.1.20 netmask 255.255.255.0 broadcast 170.1.1.255 inet6 fe80::9abe:94ff:fe5c:f1c1 prefixlen 64 scopeid 0x20 ether 98:be:94:5c:f1:c1 txqueuelen 1000 (Ethernet) RX packets 488 bytes 50254 (50.2 KB) RX errors 0 dropped 442 overruns 0 frame 0 TX packets 25 bytes 2226 (2.2 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 226 memory 0x3d400100-3d40017f On Peer: --> catch the Test interface from the multicast group ping 224.0.0.1 -I enP4p1s0f2 | grep 170.1.1.20 ---uname output--- Linux ltciofvtr-s822l1 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20 21:01:16 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux == Comment: #9 - Kevin W. Rudd - 2016-11-28 15:40:24 == I'm able to replicate this behavior in a KVM environment with Yakkety, so it does not appear to be related to the specific type of interface. From my testing, it looks like the SO_BINDTODEVICE option is not being honored, so both broadcasts and multicasts are going out the default route device instead of the device specified by -I option to ping. I am unable to replicate this on a xenial host with the same 4.8.0-27 kernel version. so I suspect some other setting is interfering with the ability to bind the output to a specific device. From my own testing: Xenial: # ip addr show 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s6: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:15:b7:ba brd ff:ff:ff:ff:ff:ff inet 10.168.122.139/24 brd 10.168.122.255 scope global enp0s6 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe15:b7ba/64 scope link valid_lft forever preferred_lft forever 3: enp0s1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:e1:35:be brd ff:ff:ff:ff:ff:ff inet 192.168.122.139/24 brd 192.168.122.255 scope global enp0s1 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fee1:35be/64 scope link valid_lft forever preferred_lft forever # ping -I enp0s6 -i 30 224.0.0.1 PING 224.0.0.1 (224.0.0.1) from 10.168.122.139 enp0s6: 56(84) bytes of data. 64 bytes from 10.168.122.139: icmp_seq=1 ttl=64 time=0.063 ms 64 bytes from 10.168.122.100: icmp_seq=1 ttl=64 time=0.435 ms (DUP!) ^C ... Yakkety: # ip addr show 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s5: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:be:97:ab brd ff:ff:ff:ff:ff:ff inet 10.168.122.100/24 brd 10.168.122.255 scope global enp0s5 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:febe:97ab/64 scope link valid_lft forever preferred_lft forever 3: enp0s1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:30:d0:14 brd ff:ff:ff:ff:ff:ff inet 192.168.122.100/24 brd 192.168.122.255 scope global enp0s1 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe30:d014/64 scope link valid_lft forever preferred_lft forever # ping -I enp0s5 -i 30 224.0.0.1 PING 224.0.0.1 (224.0.0.1) from 10.168.122.100 enp0s5: 56(84) bytes of data. 64 bytes from 192.168.122.100: icmp_seq=1 ttl=64 time=0.115 ms 64 bytes from 192.168.122.139: icmp_seq=1 ttl=64 time=1.65 ms (DUP!) ^C ... Note that the Yakkety system received answers from the hosts on the 192.168.122 network
[Desktop-packages] [Bug 1642965] Re: Firefox crashes - Error loading theme icon
** Tags removed: severity-medium ** Tags added: severity-critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1642965 Title: Firefox crashes - Error loading theme icon Status in firefox package in Ubuntu: Incomplete Bug description: Linux lnx 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:14:35 UTC 2016 s390x s390x s390x GNU/Linux Firefox: firefox 47.0+build3-0ubuntu0.16.04.1 Description: Firefox crashes when trying to start it on the server and display on the local client. Other X application can be displayed. Reproduction: Login to the server: ssh -X lnxserver Start firefox: firefox --no-remote Error Message: (firefox:39655): Gtk-WARNING **: Error loading theme icon 'list-add' for stock: Icon 'list-add' not present in theme System Segmentation fault (core dumped) == Comment: #6 - Thorsten Diehl - 2016-11-16 11:50:35 == I can confirm this. I installed Ubuntu 16.04.1 on s390x (z13 machine) and installed updates, then x11-apps, which were working fine (xclock, xeyes). I installed firefox and started it: firefox --no-remote it created tons of messages, all complaing about an unknown image format. Any subsequent start does not create that many messages. But even with --safe-mode I can't get it started: root@s8330009:~# firefox --no-remote --safe-mode (firefox:1487): Gtk-WARNING **: Locale not supported by C library. Using the fallback 'C' locale. Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknown image format 1 (t=0.627128) [GFX1]: Unknown image format 1 Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknown image format 1 (t=0.627128) |[1][GFX1]: Unknown image format 0 (t=0.631695) [GFX1]: Unknown image format 0 [1487] ###!!! ABORT: X_ShmAttach: BadAccess (attempt to access private resource denied); 3 requests ago: file /build/firefox-xMihVX/firefox-47.0+build3/toolkit/xre/nsX11ErrorHandler.cpp, line 157 [1487] ###!!! ABORT: X_ShmAttach: BadAccess (attempt to access private resource denied); 3 requests ago: file /build/firefox-xMihVX/firefox-47.0+build3/toolkit/xre/nsX11ErrorHandler.cpp, line 157 Perhaps a graphics library (gtklib?) has a problem? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1642965/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1646956] Comment bridged from LTC Bugzilla
--- Comment From ru...@us.ibm.com 2017-02-21 10:05 EDT--- Thanks Steve. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1646956 Title: ping -I support broken in yakkety version 3:20150815-2ubuntu3 (multicast test failure) Status in iputils package in Ubuntu: Fix Committed Bug description: == Comment: #0 - HARSHA THYAGARAJA - 2016-11-15 03:42:59 == ---Problem Description--- Multicast failing for Shiner interface on Ubuntu 16.10 (bnx2x) Machine Type = S822l1 ---Steps to Reproduce--- On Host: Enable multicast for the test interface 1. echo 0 > /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts 2. ip link set enP5p1s0f1 allmulticast on root@ltciofvtr-s822l1:~# ifconfig enP5p1s0f1 enP5p1s0f1: flags=4675 mtu 1500 inet 170.1.1.20 netmask 255.255.255.0 broadcast 170.1.1.255 inet6 fe80::9abe:94ff:fe5c:f1c1 prefixlen 64 scopeid 0x20 ether 98:be:94:5c:f1:c1 txqueuelen 1000 (Ethernet) RX packets 488 bytes 50254 (50.2 KB) RX errors 0 dropped 442 overruns 0 frame 0 TX packets 25 bytes 2226 (2.2 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 226 memory 0x3d400100-3d40017f On Peer: --> catch the Test interface from the multicast group ping 224.0.0.1 -I enP4p1s0f2 | grep 170.1.1.20 ---uname output--- Linux ltciofvtr-s822l1 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20 21:01:16 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux == Comment: #9 - Kevin W. Rudd - 2016-11-28 15:40:24 == I'm able to replicate this behavior in a KVM environment with Yakkety, so it does not appear to be related to the specific type of interface. From my testing, it looks like the SO_BINDTODEVICE option is not being honored, so both broadcasts and multicasts are going out the default route device instead of the device specified by -I option to ping. I am unable to replicate this on a xenial host with the same 4.8.0-27 kernel version. so I suspect some other setting is interfering with the ability to bind the output to a specific device. From my own testing: Xenial: # ip addr show 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s6: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:15:b7:ba brd ff:ff:ff:ff:ff:ff inet 10.168.122.139/24 brd 10.168.122.255 scope global enp0s6 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe15:b7ba/64 scope link valid_lft forever preferred_lft forever 3: enp0s1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:e1:35:be brd ff:ff:ff:ff:ff:ff inet 192.168.122.139/24 brd 192.168.122.255 scope global enp0s1 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fee1:35be/64 scope link valid_lft forever preferred_lft forever # ping -I enp0s6 -i 30 224.0.0.1 PING 224.0.0.1 (224.0.0.1) from 10.168.122.139 enp0s6: 56(84) bytes of data. 64 bytes from 10.168.122.139: icmp_seq=1 ttl=64 time=0.063 ms 64 bytes from 10.168.122.100: icmp_seq=1 ttl=64 time=0.435 ms (DUP!) ^C ... Yakkety: # ip addr show 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s5: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:be:97:ab brd ff:ff:ff:ff:ff:ff inet 10.168.122.100/24 brd 10.168.122.255 scope global enp0s5 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:febe:97ab/64 scope link valid_lft forever preferred_lft forever 3: enp0s1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:30:d0:14 brd ff:ff:ff:ff:ff:ff inet 192.168.122.100/24 brd 192.168.122.255 scope global enp0s1 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe30:d014/64 scope link valid_lft forever preferred_lft forever # ping -I enp0s5 -i 30 224.0.0.1 PING 224.0.0.1 (224.0.0.1) from 10.168.122.100 enp0s5: 56(84) bytes of data. 64 bytes from 192.168.122.100: icmp_seq=1 ttl=64 time=0.115 ms 64 bytes from 192.168.122.139: icmp_seq=1 ttl=64 time=1.65 ms (DUP!) ^C ... Note that the Yakkety system received answers from the hosts on the 192.168.122 network (the network associated with the route for 224.0.0.1). =
[Desktop-packages] [Bug 1646956] Comment bridged from LTC Bugzilla
--- Comment From ru...@us.ibm.com 2017-02-17 12:34 EDT--- Hello Canonical. May we please have a status update for this bug? Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1646956 Title: ping -I support broken in yakkety version 3:20150815-2ubuntu3 (multicast test failure) Status in iputils package in Ubuntu: New Bug description: == Comment: #0 - HARSHA THYAGARAJA - 2016-11-15 03:42:59 == ---Problem Description--- Multicast failing for Shiner interface on Ubuntu 16.10 (bnx2x) Machine Type = S822l1 ---Steps to Reproduce--- On Host: Enable multicast for the test interface 1. echo 0 > /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts 2. ip link set enP5p1s0f1 allmulticast on root@ltciofvtr-s822l1:~# ifconfig enP5p1s0f1 enP5p1s0f1: flags=4675 mtu 1500 inet 170.1.1.20 netmask 255.255.255.0 broadcast 170.1.1.255 inet6 fe80::9abe:94ff:fe5c:f1c1 prefixlen 64 scopeid 0x20 ether 98:be:94:5c:f1:c1 txqueuelen 1000 (Ethernet) RX packets 488 bytes 50254 (50.2 KB) RX errors 0 dropped 442 overruns 0 frame 0 TX packets 25 bytes 2226 (2.2 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 226 memory 0x3d400100-3d40017f On Peer: --> catch the Test interface from the multicast group ping 224.0.0.1 -I enP4p1s0f2 | grep 170.1.1.20 ---uname output--- Linux ltciofvtr-s822l1 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20 21:01:16 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux == Comment: #9 - Kevin W. Rudd - 2016-11-28 15:40:24 == I'm able to replicate this behavior in a KVM environment with Yakkety, so it does not appear to be related to the specific type of interface. From my testing, it looks like the SO_BINDTODEVICE option is not being honored, so both broadcasts and multicasts are going out the default route device instead of the device specified by -I option to ping. I am unable to replicate this on a xenial host with the same 4.8.0-27 kernel version. so I suspect some other setting is interfering with the ability to bind the output to a specific device. From my own testing: Xenial: # ip addr show 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s6: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:15:b7:ba brd ff:ff:ff:ff:ff:ff inet 10.168.122.139/24 brd 10.168.122.255 scope global enp0s6 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe15:b7ba/64 scope link valid_lft forever preferred_lft forever 3: enp0s1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:e1:35:be brd ff:ff:ff:ff:ff:ff inet 192.168.122.139/24 brd 192.168.122.255 scope global enp0s1 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fee1:35be/64 scope link valid_lft forever preferred_lft forever # ping -I enp0s6 -i 30 224.0.0.1 PING 224.0.0.1 (224.0.0.1) from 10.168.122.139 enp0s6: 56(84) bytes of data. 64 bytes from 10.168.122.139: icmp_seq=1 ttl=64 time=0.063 ms 64 bytes from 10.168.122.100: icmp_seq=1 ttl=64 time=0.435 ms (DUP!) ^C ... Yakkety: # ip addr show 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s5: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:be:97:ab brd ff:ff:ff:ff:ff:ff inet 10.168.122.100/24 brd 10.168.122.255 scope global enp0s5 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:febe:97ab/64 scope link valid_lft forever preferred_lft forever 3: enp0s1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:30:d0:14 brd ff:ff:ff:ff:ff:ff inet 192.168.122.100/24 brd 192.168.122.255 scope global enp0s1 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe30:d014/64 scope link valid_lft forever preferred_lft forever # ping -I enp0s5 -i 30 224.0.0.1 PING 224.0.0.1 (224.0.0.1) from 10.168.122.100 enp0s5: 56(84) bytes of data. 64 bytes from 192.168.122.100: icmp_seq=1 ttl=64 time=0.115 ms 64 bytes from 192.168.122.139: icmp_seq=1 ttl=64 time=1.65 ms (DUP!) ^C ... Note that the Yakkety system received answers from the hosts on the 192.168.122 network (the netw
[Desktop-packages] [Bug 1646956] Re: ping -I support broken in yakkety version 3:20150815-2ubuntu3 (multicast test failure)
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin1704 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1646956 Title: ping -I support broken in yakkety version 3:20150815-2ubuntu3 (multicast test failure) Status in iputils package in Ubuntu: New Bug description: == Comment: #0 - HARSHA THYAGARAJA - 2016-11-15 03:42:59 == ---Problem Description--- Multicast failing for Shiner interface on Ubuntu 16.10 (bnx2x) Machine Type = S822l1 ---Steps to Reproduce--- On Host: Enable multicast for the test interface 1. echo 0 > /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts 2. ip link set enP5p1s0f1 allmulticast on root@ltciofvtr-s822l1:~# ifconfig enP5p1s0f1 enP5p1s0f1: flags=4675 mtu 1500 inet 170.1.1.20 netmask 255.255.255.0 broadcast 170.1.1.255 inet6 fe80::9abe:94ff:fe5c:f1c1 prefixlen 64 scopeid 0x20 ether 98:be:94:5c:f1:c1 txqueuelen 1000 (Ethernet) RX packets 488 bytes 50254 (50.2 KB) RX errors 0 dropped 442 overruns 0 frame 0 TX packets 25 bytes 2226 (2.2 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 226 memory 0x3d400100-3d40017f On Peer: --> catch the Test interface from the multicast group ping 224.0.0.1 -I enP4p1s0f2 | grep 170.1.1.20 ---uname output--- Linux ltciofvtr-s822l1 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20 21:01:16 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux == Comment: #9 - Kevin W. Rudd - 2016-11-28 15:40:24 == I'm able to replicate this behavior in a KVM environment with Yakkety, so it does not appear to be related to the specific type of interface. From my testing, it looks like the SO_BINDTODEVICE option is not being honored, so both broadcasts and multicasts are going out the default route device instead of the device specified by -I option to ping. I am unable to replicate this on a xenial host with the same 4.8.0-27 kernel version. so I suspect some other setting is interfering with the ability to bind the output to a specific device. From my own testing: Xenial: # ip addr show 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s6: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:15:b7:ba brd ff:ff:ff:ff:ff:ff inet 10.168.122.139/24 brd 10.168.122.255 scope global enp0s6 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe15:b7ba/64 scope link valid_lft forever preferred_lft forever 3: enp0s1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:e1:35:be brd ff:ff:ff:ff:ff:ff inet 192.168.122.139/24 brd 192.168.122.255 scope global enp0s1 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fee1:35be/64 scope link valid_lft forever preferred_lft forever # ping -I enp0s6 -i 30 224.0.0.1 PING 224.0.0.1 (224.0.0.1) from 10.168.122.139 enp0s6: 56(84) bytes of data. 64 bytes from 10.168.122.139: icmp_seq=1 ttl=64 time=0.063 ms 64 bytes from 10.168.122.100: icmp_seq=1 ttl=64 time=0.435 ms (DUP!) ^C ... Yakkety: # ip addr show 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s5: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:be:97:ab brd ff:ff:ff:ff:ff:ff inet 10.168.122.100/24 brd 10.168.122.255 scope global enp0s5 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:febe:97ab/64 scope link valid_lft forever preferred_lft forever 3: enp0s1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:30:d0:14 brd ff:ff:ff:ff:ff:ff inet 192.168.122.100/24 brd 192.168.122.255 scope global enp0s1 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe30:d014/64 scope link valid_lft forever preferred_lft forever # ping -I enp0s5 -i 30 224.0.0.1 PING 224.0.0.1 (224.0.0.1) from 10.168.122.100 enp0s5: 56(84) bytes of data. 64 bytes from 192.168.122.100: icmp_seq=1 ttl=64 time=0.115 ms 64 bytes from 192.168.122.139: icmp_seq=1 ttl=64 time=1.65 ms (DUP!) ^C ... Note that the Yakkety system received answers from the hosts on the 192.168.122 network (the network associated with the route for 224.0.0.1). == Comment
[Desktop-packages] [Bug 1646956] Comment bridged from LTC Bugzilla
--- Comment From ru...@us.ibm.com 2017-01-12 17:44 EDT--- iputils commit f455fee41c077d4b700a473b2f5b3487b8febc1d has been confirmed to resolve the issue when applied to the iputils_20150815-2ubuntu3 codebase. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1646956 Title: ping -I support broken in yakkety version 3:20150815-2ubuntu3 (multicast test failure) Status in iputils package in Ubuntu: New Bug description: == Comment: #0 - HARSHA THYAGARAJA - 2016-11-15 03:42:59 == ---Problem Description--- Multicast failing for Shiner interface on Ubuntu 16.10 (bnx2x) Machine Type = S822l1 ---Steps to Reproduce--- On Host: Enable multicast for the test interface 1. echo 0 > /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts 2. ip link set enP5p1s0f1 allmulticast on root@ltciofvtr-s822l1:~# ifconfig enP5p1s0f1 enP5p1s0f1: flags=4675 mtu 1500 inet 170.1.1.20 netmask 255.255.255.0 broadcast 170.1.1.255 inet6 fe80::9abe:94ff:fe5c:f1c1 prefixlen 64 scopeid 0x20 ether 98:be:94:5c:f1:c1 txqueuelen 1000 (Ethernet) RX packets 488 bytes 50254 (50.2 KB) RX errors 0 dropped 442 overruns 0 frame 0 TX packets 25 bytes 2226 (2.2 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 226 memory 0x3d400100-3d40017f On Peer: --> catch the Test interface from the multicast group ping 224.0.0.1 -I enP4p1s0f2 | grep 170.1.1.20 ---uname output--- Linux ltciofvtr-s822l1 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20 21:01:16 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux == Comment: #9 - Kevin W. Rudd - 2016-11-28 15:40:24 == I'm able to replicate this behavior in a KVM environment with Yakkety, so it does not appear to be related to the specific type of interface. From my testing, it looks like the SO_BINDTODEVICE option is not being honored, so both broadcasts and multicasts are going out the default route device instead of the device specified by -I option to ping. I am unable to replicate this on a xenial host with the same 4.8.0-27 kernel version. so I suspect some other setting is interfering with the ability to bind the output to a specific device. From my own testing: Xenial: # ip addr show 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s6: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:15:b7:ba brd ff:ff:ff:ff:ff:ff inet 10.168.122.139/24 brd 10.168.122.255 scope global enp0s6 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe15:b7ba/64 scope link valid_lft forever preferred_lft forever 3: enp0s1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:e1:35:be brd ff:ff:ff:ff:ff:ff inet 192.168.122.139/24 brd 192.168.122.255 scope global enp0s1 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fee1:35be/64 scope link valid_lft forever preferred_lft forever # ping -I enp0s6 -i 30 224.0.0.1 PING 224.0.0.1 (224.0.0.1) from 10.168.122.139 enp0s6: 56(84) bytes of data. 64 bytes from 10.168.122.139: icmp_seq=1 ttl=64 time=0.063 ms 64 bytes from 10.168.122.100: icmp_seq=1 ttl=64 time=0.435 ms (DUP!) ^C ... Yakkety: # ip addr show 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s5: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:be:97:ab brd ff:ff:ff:ff:ff:ff inet 10.168.122.100/24 brd 10.168.122.255 scope global enp0s5 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:febe:97ab/64 scope link valid_lft forever preferred_lft forever 3: enp0s1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:30:d0:14 brd ff:ff:ff:ff:ff:ff inet 192.168.122.100/24 brd 192.168.122.255 scope global enp0s1 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe30:d014/64 scope link valid_lft forever preferred_lft forever # ping -I enp0s5 -i 30 224.0.0.1 PING 224.0.0.1 (224.0.0.1) from 10.168.122.100 enp0s5: 56(84) bytes of data. 64 bytes from 192.168.122.100: icmp_seq=1 ttl=64 time=0.115 ms 64 bytes from 192.168.122.139: icmp_seq=1 ttl=64 time=1.65 ms (DUP!) ^C ... Note that the Yakkety
[Desktop-packages] [Bug 1646956] Comment bridged from LTC Bugzilla
--- Comment From ru...@us.ibm.com 2017-01-12 12:52 EDT--- *** Bug 150504 has been marked as a duplicate of this bug. *** --- Comment From ru...@us.ibm.com 2017-01-12 12:57 EDT--- FYI Canonical. This was also confirmed to be an issue with the iputils-ping version in Zesty: 3:20150815-2ubuntu3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1646956 Title: ping -I support broken in yakkety version 3:20150815-2ubuntu3 (multicast test failure) Status in iputils package in Ubuntu: New Bug description: == Comment: #0 - HARSHA THYAGARAJA - 2016-11-15 03:42:59 == ---Problem Description--- Multicast failing for Shiner interface on Ubuntu 16.10 (bnx2x) Machine Type = S822l1 ---Steps to Reproduce--- On Host: Enable multicast for the test interface 1. echo 0 > /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts 2. ip link set enP5p1s0f1 allmulticast on root@ltciofvtr-s822l1:~# ifconfig enP5p1s0f1 enP5p1s0f1: flags=4675 mtu 1500 inet 170.1.1.20 netmask 255.255.255.0 broadcast 170.1.1.255 inet6 fe80::9abe:94ff:fe5c:f1c1 prefixlen 64 scopeid 0x20 ether 98:be:94:5c:f1:c1 txqueuelen 1000 (Ethernet) RX packets 488 bytes 50254 (50.2 KB) RX errors 0 dropped 442 overruns 0 frame 0 TX packets 25 bytes 2226 (2.2 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 226 memory 0x3d400100-3d40017f On Peer: --> catch the Test interface from the multicast group ping 224.0.0.1 -I enP4p1s0f2 | grep 170.1.1.20 ---uname output--- Linux ltciofvtr-s822l1 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20 21:01:16 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux == Comment: #9 - Kevin W. Rudd - 2016-11-28 15:40:24 == I'm able to replicate this behavior in a KVM environment with Yakkety, so it does not appear to be related to the specific type of interface. From my testing, it looks like the SO_BINDTODEVICE option is not being honored, so both broadcasts and multicasts are going out the default route device instead of the device specified by -I option to ping. I am unable to replicate this on a xenial host with the same 4.8.0-27 kernel version. so I suspect some other setting is interfering with the ability to bind the output to a specific device. From my own testing: Xenial: # ip addr show 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s6: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:15:b7:ba brd ff:ff:ff:ff:ff:ff inet 10.168.122.139/24 brd 10.168.122.255 scope global enp0s6 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe15:b7ba/64 scope link valid_lft forever preferred_lft forever 3: enp0s1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:e1:35:be brd ff:ff:ff:ff:ff:ff inet 192.168.122.139/24 brd 192.168.122.255 scope global enp0s1 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fee1:35be/64 scope link valid_lft forever preferred_lft forever # ping -I enp0s6 -i 30 224.0.0.1 PING 224.0.0.1 (224.0.0.1) from 10.168.122.139 enp0s6: 56(84) bytes of data. 64 bytes from 10.168.122.139: icmp_seq=1 ttl=64 time=0.063 ms 64 bytes from 10.168.122.100: icmp_seq=1 ttl=64 time=0.435 ms (DUP!) ^C ... Yakkety: # ip addr show 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s5: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:be:97:ab brd ff:ff:ff:ff:ff:ff inet 10.168.122.100/24 brd 10.168.122.255 scope global enp0s5 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:febe:97ab/64 scope link valid_lft forever preferred_lft forever 3: enp0s1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:30:d0:14 brd ff:ff:ff:ff:ff:ff inet 192.168.122.100/24 brd 192.168.122.255 scope global enp0s1 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe30:d014/64 scope link valid_lft forever preferred_lft forever # ping -I enp0s5 -i 30 224.0.0.1 PING 224.0.0.1 (224.0.0.1) from 10.168.122.100 enp0s5: 56(84) bytes of data. 64 bytes from 192.168.122.100: icmp_seq=1 ttl=64 time=0.115 ms 64 bytes fro
[Desktop-packages] [Bug 1489483] Comment bridged from LTC Bugzilla
--- Comment From bren...@br.ibm.com 2016-12-08 14:42 EDT--- THis problem is now fixed with Ubuntu 17.04 llvm-3.8-dev (>= 1:3.8) [amd64 i386 kfreebsd-amd64 kfreebsd-i386 arm64 armhf ppc64el], -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1489483 Title: Enable llvmpipe on libgl-mesa-dri Status in mesa package in Ubuntu: Triaged Bug description: == Comment: #0 - Gabriel Krisman Bertazi - 2015-08-12 09:53:27 == The llvmpipe software renderer is disabled in the mesa (libgl1-mesa-dri) package for ppc64le, even though llvmpipe is fully supported on this architecture. We need this feature enabled in order to run Unity with video cards lacking 3D Hardware Acceleration. Please enable it and, if possible, backport this change to 14.04.3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1489483/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1646956] Comment bridged from LTC Bugzilla
--- Comment From ru...@us.ibm.com 2016-12-02 17:10 EDT--- Testing with an updated version of uputils indicates that this has already been fixed upstream. Most likely with the following commit: commit f455fee41c077d4b700a473b2f5b3487b8febc1d ping: also bind the ICMP socket to the specific device -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1646956 Title: ping -I support broken in yakkety version 3:20150815-2ubuntu3 (multicast test failure) Status in iputils package in Ubuntu: New Bug description: == Comment: #0 - HARSHA THYAGARAJA - 2016-11-15 03:42:59 == ---Problem Description--- Multicast failing for Shiner interface on Ubuntu 16.10 (bnx2x) Machine Type = S822l1 ---Steps to Reproduce--- On Host: Enable multicast for the test interface 1. echo 0 > /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts 2. ip link set enP5p1s0f1 allmulticast on root@ltciofvtr-s822l1:~# ifconfig enP5p1s0f1 enP5p1s0f1: flags=4675 mtu 1500 inet 170.1.1.20 netmask 255.255.255.0 broadcast 170.1.1.255 inet6 fe80::9abe:94ff:fe5c:f1c1 prefixlen 64 scopeid 0x20 ether 98:be:94:5c:f1:c1 txqueuelen 1000 (Ethernet) RX packets 488 bytes 50254 (50.2 KB) RX errors 0 dropped 442 overruns 0 frame 0 TX packets 25 bytes 2226 (2.2 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 226 memory 0x3d400100-3d40017f On Peer: --> catch the Test interface from the multicast group ping 224.0.0.1 -I enP4p1s0f2 | grep 170.1.1.20 ---uname output--- Linux ltciofvtr-s822l1 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20 21:01:16 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux == Comment: #9 - Kevin W. Rudd - 2016-11-28 15:40:24 == I'm able to replicate this behavior in a KVM environment with Yakkety, so it does not appear to be related to the specific type of interface. From my testing, it looks like the SO_BINDTODEVICE option is not being honored, so both broadcasts and multicasts are going out the default route device instead of the device specified by -I option to ping. I am unable to replicate this on a xenial host with the same 4.8.0-27 kernel version. so I suspect some other setting is interfering with the ability to bind the output to a specific device. From my own testing: Xenial: # ip addr show 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s6: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:15:b7:ba brd ff:ff:ff:ff:ff:ff inet 10.168.122.139/24 brd 10.168.122.255 scope global enp0s6 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe15:b7ba/64 scope link valid_lft forever preferred_lft forever 3: enp0s1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:e1:35:be brd ff:ff:ff:ff:ff:ff inet 192.168.122.139/24 brd 192.168.122.255 scope global enp0s1 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fee1:35be/64 scope link valid_lft forever preferred_lft forever # ping -I enp0s6 -i 30 224.0.0.1 PING 224.0.0.1 (224.0.0.1) from 10.168.122.139 enp0s6: 56(84) bytes of data. 64 bytes from 10.168.122.139: icmp_seq=1 ttl=64 time=0.063 ms 64 bytes from 10.168.122.100: icmp_seq=1 ttl=64 time=0.435 ms (DUP!) ^C ... Yakkety: # ip addr show 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s5: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:be:97:ab brd ff:ff:ff:ff:ff:ff inet 10.168.122.100/24 brd 10.168.122.255 scope global enp0s5 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:febe:97ab/64 scope link valid_lft forever preferred_lft forever 3: enp0s1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:30:d0:14 brd ff:ff:ff:ff:ff:ff inet 192.168.122.100/24 brd 192.168.122.255 scope global enp0s1 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe30:d014/64 scope link valid_lft forever preferred_lft forever # ping -I enp0s5 -i 30 224.0.0.1 PING 224.0.0.1 (224.0.0.1) from 10.168.122.100 enp0s5: 56(84) bytes of data. 64 bytes from 192.168.122.100: icmp_seq=1 ttl=64 time=0.115 ms 64 bytes from 19
[Desktop-packages] [Bug 1646956] sosreport for multicast failure
Default Comment by Bridge ** Attachment added: "sosreport for multicast failure" https://bugs.launchpad.net/bugs/1646956/+attachment/4786712/+files/sosreport-Harsha.148714-20161116014533.tar.xz ** Changed in: ubuntu Assignee: (unassigned) => Taco Screen team (taco-screen-team) ** Package changed: ubuntu => iputils (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1646956 Title: ping -I support broken in yakkety version 3:20150815-2ubuntu3 (multicast test failure) Status in iputils package in Ubuntu: New Bug description: == Comment: #0 - HARSHA THYAGARAJA - 2016-11-15 03:42:59 == ---Problem Description--- Multicast failing for Shiner interface on Ubuntu 16.10 (bnx2x) Machine Type = S822l1 ---Steps to Reproduce--- On Host: Enable multicast for the test interface 1. echo 0 > /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts 2. ip link set enP5p1s0f1 allmulticast on root@ltciofvtr-s822l1:~# ifconfig enP5p1s0f1 enP5p1s0f1: flags=4675 mtu 1500 inet 170.1.1.20 netmask 255.255.255.0 broadcast 170.1.1.255 inet6 fe80::9abe:94ff:fe5c:f1c1 prefixlen 64 scopeid 0x20 ether 98:be:94:5c:f1:c1 txqueuelen 1000 (Ethernet) RX packets 488 bytes 50254 (50.2 KB) RX errors 0 dropped 442 overruns 0 frame 0 TX packets 25 bytes 2226 (2.2 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 226 memory 0x3d400100-3d40017f On Peer: --> catch the Test interface from the multicast group ping 224.0.0.1 -I enP4p1s0f2 | grep 170.1.1.20 ---uname output--- Linux ltciofvtr-s822l1 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20 21:01:16 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux == Comment: #9 - Kevin W. Rudd - 2016-11-28 15:40:24 == I'm able to replicate this behavior in a KVM environment with Yakkety, so it does not appear to be related to the specific type of interface. From my testing, it looks like the SO_BINDTODEVICE option is not being honored, so both broadcasts and multicasts are going out the default route device instead of the device specified by -I option to ping. I am unable to replicate this on a xenial host with the same 4.8.0-27 kernel version. so I suspect some other setting is interfering with the ability to bind the output to a specific device. From my own testing: Xenial: # ip addr show 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s6: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:15:b7:ba brd ff:ff:ff:ff:ff:ff inet 10.168.122.139/24 brd 10.168.122.255 scope global enp0s6 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe15:b7ba/64 scope link valid_lft forever preferred_lft forever 3: enp0s1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:e1:35:be brd ff:ff:ff:ff:ff:ff inet 192.168.122.139/24 brd 192.168.122.255 scope global enp0s1 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fee1:35be/64 scope link valid_lft forever preferred_lft forever # ping -I enp0s6 -i 30 224.0.0.1 PING 224.0.0.1 (224.0.0.1) from 10.168.122.139 enp0s6: 56(84) bytes of data. 64 bytes from 10.168.122.139: icmp_seq=1 ttl=64 time=0.063 ms 64 bytes from 10.168.122.100: icmp_seq=1 ttl=64 time=0.435 ms (DUP!) ^C ... Yakkety: # ip addr show 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s5: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:be:97:ab brd ff:ff:ff:ff:ff:ff inet 10.168.122.100/24 brd 10.168.122.255 scope global enp0s5 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:febe:97ab/64 scope link valid_lft forever preferred_lft forever 3: enp0s1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:30:d0:14 brd ff:ff:ff:ff:ff:ff inet 192.168.122.100/24 brd 192.168.122.255 scope global enp0s1 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe30:d014/64 scope link valid_lft forever preferred_lft forever # ping -I enp0s5 -i 30 224.0.0.1 PING 224.0.0.1 (224.0.0.1) from 10.168.122.100 enp0s5: 56(84) bytes of data. 64 bytes from 192.168.122.100: icmp_seq=1 ttl=64 tim
[Desktop-packages] [Bug 1642965] crash dump
Default Comment by Bridge ** Attachment added: "crash dump" https://bugs.launchpad.net/bugs/1642965/+attachment/4779345/+files/_usr_lib_firefox_firefox.4549.crash ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => firefox (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1642965 Title: Firefox crashes - Error loading theme icon Status in firefox package in Ubuntu: New Bug description: Linux lnx 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:14:35 UTC 2016 s390x s390x s390x GNU/Linux Firefox: firefox 47.0+build3-0ubuntu0.16.04.1 Description: Firefox crashes when trying to start it on the server and display on the local client. Other X application can be displayed. Reproduction: Login to the server: ssh -X lnxserver Start firefox: firefox --no-remote Error Message: (firefox:39655): Gtk-WARNING **: Error loading theme icon 'list-add' for stock: Icon 'list-add' not present in theme System Segmentation fault (core dumped) == Comment: #6 - Thorsten Diehl - 2016-11-16 11:50:35 == I can confirm this. I installed Ubuntu 16.04.1 on s390x (z13 machine) and installed updates, then x11-apps, which were working fine (xclock, xeyes). I installed firefox and started it: firefox --no-remote it created tons of messages, all complaing about an unknown image format. Any subsequent start does not create that many messages. But even with --safe-mode I can't get it started: root@s8330009:~# firefox --no-remote --safe-mode (firefox:1487): Gtk-WARNING **: Locale not supported by C library. Using the fallback 'C' locale. Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknown image format 1 (t=0.627128) [GFX1]: Unknown image format 1 Crash Annotation GraphicsCriticalError: |[0][GFX1]: Unknown image format 1 (t=0.627128) |[1][GFX1]: Unknown image format 0 (t=0.631695) [GFX1]: Unknown image format 0 [1487] ###!!! ABORT: X_ShmAttach: BadAccess (attempt to access private resource denied); 3 requests ago: file /build/firefox-xMihVX/firefox-47.0+build3/toolkit/xre/nsX11ErrorHandler.cpp, line 157 [1487] ###!!! ABORT: X_ShmAttach: BadAccess (attempt to access private resource denied); 3 requests ago: file /build/firefox-xMihVX/firefox-47.0+build3/toolkit/xre/nsX11ErrorHandler.cpp, line 157 Perhaps a graphics library (gtklib?) has a problem? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1642965/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1608954] libica RNG performance fix
Default Comment by Bridge ** Attachment added: "libica RNG performance fix" https://bugs.launchpad.net/bugs/1608954/+attachment/4712375/+files/ica_random_number_generate_performance.patch ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => libical (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libical in Ubuntu. https://bugs.launchpad.net/bugs/1608954 Title: Performance degradation caused by libica2 library Status in libica package in Ubuntu: New Bug description: == Comment: #0 - Bastian Pfeifer - 2016-07-29 09:07:47 == ---Problem Description--- 'Libica' library versions >= 2.6.0 implement a new DRBG (Deterministic Random Number Generator) with a unnecessary stiff reseed limit leading to performance degradation (factor >20) for RSA encryption via opencryptoki. A patch is already upstream and can be found under this commit: https://sourceforge.net/p/opencryptoki/libica/ci/3bcd3efb0aff364515ab9b3c39dd68fbbb1534d0/ It will fix the issue + we will get a great performance improvement for the RSA encryption via opencryptoki's ICA-TOKEN. Contact Information = bastian.pfei...@de.ibm.com ---uname output--- Linux s42lp26 4.4.0-28-generic #47-Ubuntu SMP Fri Jun 24 10:14:29 UTC 2016 s390x s390x s390x GNU/Linux Machine Type = 2964, 701 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- na Userspace tool common name: libica version 2.6.1 The userspace tool has the following bit modes: 64-bit Userspace rpm: libica2:s390x Userspace tool obtained from project website: na *Additional Instructions for bastian.pfei...@de.ibm.com: -Attach ltrace and strace of userspace application. == Comment: #2 - Ingo Tuchscherer - 2016-08-01 06:53:45 == == Comment: #3 - Heinz-Werner Seeck - 2016-08-02 08:19:23 == 'Libica' library versions >= 2.6.0 implement a new DRBG (Deterministic Random Number Generator) with a unnecessary stiff reseed limit leading to performance degradation (factor >20) for RSA encryption via opencryptoki. A patch is already upstream and can be found under this commit: https://sourceforge.net/p/opencryptoki/libica/ci/3bcd3efb0aff364515ab9b3c39dd68fbbb1534d0/ Also attached to this bugzilla ! It will fix the issue + we will get a great performance improvement for the RSA encryption via opencryptoki's ICA-TOKEN. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libica/+bug/1608954/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1580951] Comment bridged from LTC Bugzilla
dgddfdr -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1580951 Title: Upgrade libseccomp from 2.2.3 ->2.3.1 Status in unity-webapps-linkedin package in Ubuntu: Invalid Bug description: == Comment: #1 - Heinz-Werner Seeck - 2016-05-11 05:09:09 == Please upgrade package libseccomp. The new version 2.3.1 is available on github https://github.com/seccomp/libseccomp/releases == Comment: #2 - Heinz-Werner Seeck - 2016-05-11 05:10:59 == ?Version 2.3.0 - February 29, 2016 ?Added support for the s390 and s390x architectures ?Added support for the ppc, ppc64, and ppc64le architectures ?Update the internal syscall tables to match the Linux 4.5-rcX releases ?Filter generation for both multiplexed and direct socket syscalls on x86 ?Support for the musl libc implementation ?Additions to the API to enable runtime version checking of the library ?Enable the use of seccomp() instead of prctl() on supported systems ?Added additional tests to the regression test suite ?Version 2.3.1 - April 20, 2016 ?Fixed a problem with 32-bit x86 socket syscalls on some systems ?Fixed problems with ipc syscalls on 32-bit x86 ?Fixed problems with socket and ipc syscalls on s390 and s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-webapps-linkedin/+bug/1580951/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1580951] Comment bridged from LTC Bugzilla
go go --- Comment From cdead...@us.ibm.com 2016-07-22 02:38 EDT--- gogogo -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1580951 Title: Upgrade libseccomp from 2.2.3 ->2.3.1 Status in account-plugins package in Ubuntu: Invalid Bug description: == Comment: #1 - Heinz-Werner Seeck - 2016-05-11 05:09:09 == Please upgrade package libseccomp. The new version 2.3.1 is available on github https://github.com/seccomp/libseccomp/releases == Comment: #2 - Heinz-Werner Seeck - 2016-05-11 05:10:59 == ?Version 2.3.0 - February 29, 2016 ?Added support for the s390 and s390x architectures ?Added support for the ppc, ppc64, and ppc64le architectures ?Update the internal syscall tables to match the Linux 4.5-rcX releases ?Filter generation for both multiplexed and direct socket syscalls on x86 ?Support for the musl libc implementation ?Additions to the API to enable runtime version checking of the library ?Enable the use of seccomp() instead of prctl() on supported systems ?Added additional tests to the regression test suite ?Version 2.3.1 - April 20, 2016 ?Fixed a problem with 32-bit x86 socket syscalls on some systems ?Fixed problems with ipc syscalls on 32-bit x86 ?Fixed problems with socket and ipc syscalls on s390 and s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1580951/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1549300] Re: dialog wrongly requires double backslashes (\\n, \\Z) for control codes in option file
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin1610 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to dialog in Ubuntu. https://bugs.launchpad.net/bugs/1549300 Title: dialog wrongly requires double backslashes (\\n, \\Z) for control codes in option file Status in dialog package in Ubuntu: Triaged Bug description: == Comment: #0 - Liang Chang Guo - 2015-09-11 18:44:18 == From Ubuntu 15.10 daily builds, the window-like tool "dialog" in Linux now turns to look for double backslashes (like \\n, \\Z...) as control codes in command option file, which causes incorrect display in format for programs (like PMLinux) that get used to only feeding with single backslash (\n, \Z...). This bug affects menu, form, and form etc. dialog boxes. There is no such problem for other disros, even ubuntu 15.05 ... *** Info of ubuntu/dialog that fail, and command/file to reproduce *** root@ubt1510F:~# uname -a Linux ubt1510F 4.2.0-7-generic #7-Ubuntu SMP Tue Sep 1 16:42:17 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux root@ubt1510F:~# dialog --version Version: 1.2-20150528 root@ubt1510F:~# dialog --file PMLinux.menus (see display effect in attachment) root@ubt1510F:~# cat PMLinux.menus --begin 2 2 --default-item "2) Disable" --ok-label " Select " --item-help --help-button --no-cancel --colors --timeout 585 --title " Setup Performance Management " --backtitle "IBM PMLinux Main Menus" --menu " \Z4I\Znnternational \Z4B\Znusiness \Z4M\Znachines (\Zu\Z4IBM\Zn), Copyright 2012-2015 \Z1(C)\Zn\n\n \Z0Move by \Zb\Z4\Zn or \Zb\Z4Mouse\Zn to desired function/button\n Presss \Z1\Zn to select, or \Z1\Zn to exit.\n\n \Zu\Z5ubt1510F\ZU\Zn STATUS: Collection \Z2ON\Zn, Transmission \Z2ON\Zn, CustomerInfo \Z1NO\Zn\n \Z4Linux OS Version\Z0: Ubuntu Wily Werewolf (development branch)" 25 81 11 "1)*Enable" "\Z2Data Transmission" "To correct & reset parameters to enable PMLinux Data Collection & Transmission" "2) Disable" "Data Transmission" "To disable PMLinux Data Collection & Transmission. Proceed with Caution !!!" "3) Retransmit" "Recorded Data" "To package historical data files of one or all day(s) into PMstats.send for manual transmission" "4)*Change/Show" "\Z1Customer Information" "To fill out contact info, so that IBM PMLinux team can create a login user for your web reports" "5) Change/Show" "Data Retention Period" "To setup the period length (days) for PMLinux to keep the data files" "6) Change/Show" "Trending Days and Shift Times" "To setup your weekly working days & shift times for PMLinux reports" "7) Change/Show" "System Parameters (Advanced)" "To setup some system configurations" "8) Change/Show" "KVM Guest Collection Settings" "To setup KVM Guest info and querying utilization data intervals" "9) ReadMe" "Guide/References/License" "To browse PMLinux manual/license text documents" "0) Exit""Quit" "To end this window-style PMLinux configuration tool" *** Info of ubuntu/dialog that pass *** [root@kvmhost ~]# uname -a Linux kvmhost 3.18.17-349.el7_1.pkvm3_1_0.3103.1.daily.donotship.ppc64le #1 SMP Thu Sep 10 07:17:08 CDT 2015 ppc64le ppc64le ppc64le GNU/Linux [root@kvmhost ~]# dialog --version Version: 1.2-20130523 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialog/+bug/1549300/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1549300] Re: dialog wrongly requires double backslashes (\\n, \\Z) for control codes in option file
--- Comment From lc...@us.ibm.com 2016-06-17 12:59 EDT--- A new defect was opened against dialog under the platform Fedora 23: https://bugzilla.linux.ibm.com/show_bug.cgi?id=142786 - dialog wrongly requires double backslashes (\\n, \\Z) for control codes in option file Now is the time to conclude this defect for Ubuntu. ** Bug watch added: bugzilla.linux.ibm.com/ #142786 https://bugzilla.linux.ibm.com/show_bug.cgi?id=142786 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to dialog in Ubuntu. https://bugs.launchpad.net/bugs/1549300 Title: dialog wrongly requires double backslashes (\\n, \\Z) for control codes in option file Status in dialog package in Ubuntu: Triaged Bug description: == Comment: #0 - Liang Chang Guo - 2015-09-11 18:44:18 == From Ubuntu 15.10 daily builds, the window-like tool "dialog" in Linux now turns to look for double backslashes (like \\n, \\Z...) as control codes in command option file, which causes incorrect display in format for programs (like PMLinux) that get used to only feeding with single backslash (\n, \Z...). This bug affects menu, form, and form etc. dialog boxes. There is no such problem for other disros, even ubuntu 15.05 ... *** Info of ubuntu/dialog that fail, and command/file to reproduce *** root@ubt1510F:~# uname -a Linux ubt1510F 4.2.0-7-generic #7-Ubuntu SMP Tue Sep 1 16:42:17 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux root@ubt1510F:~# dialog --version Version: 1.2-20150528 root@ubt1510F:~# dialog --file PMLinux.menus (see display effect in attachment) root@ubt1510F:~# cat PMLinux.menus --begin 2 2 --default-item "2) Disable" --ok-label " Select " --item-help --help-button --no-cancel --colors --timeout 585 --title " Setup Performance Management " --backtitle "IBM PMLinux Main Menus" --menu " \Z4I\Znnternational \Z4B\Znusiness \Z4M\Znachines (\Zu\Z4IBM\Zn), Copyright 2012-2015 \Z1(C)\Zn\n\n \Z0Move by \Zb\Z4\Zn or \Zb\Z4Mouse\Zn to desired function/button\n Presss \Z1\Zn to select, or \Z1\Zn to exit.\n\n \Zu\Z5ubt1510F\ZU\Zn STATUS: Collection \Z2ON\Zn, Transmission \Z2ON\Zn, CustomerInfo \Z1NO\Zn\n \Z4Linux OS Version\Z0: Ubuntu Wily Werewolf (development branch)" 25 81 11 "1)*Enable" "\Z2Data Transmission" "To correct & reset parameters to enable PMLinux Data Collection & Transmission" "2) Disable" "Data Transmission" "To disable PMLinux Data Collection & Transmission. Proceed with Caution !!!" "3) Retransmit" "Recorded Data" "To package historical data files of one or all day(s) into PMstats.send for manual transmission" "4)*Change/Show" "\Z1Customer Information" "To fill out contact info, so that IBM PMLinux team can create a login user for your web reports" "5) Change/Show" "Data Retention Period" "To setup the period length (days) for PMLinux to keep the data files" "6) Change/Show" "Trending Days and Shift Times" "To setup your weekly working days & shift times for PMLinux reports" "7) Change/Show" "System Parameters (Advanced)" "To setup some system configurations" "8) Change/Show" "KVM Guest Collection Settings" "To setup KVM Guest info and querying utilization data intervals" "9) ReadMe" "Guide/References/License" "To browse PMLinux manual/license text documents" "0) Exit""Quit" "To end this window-style PMLinux configuration tool" *** Info of ubuntu/dialog that pass *** [root@kvmhost ~]# uname -a Linux kvmhost 3.18.17-349.el7_1.pkvm3_1_0.3103.1.daily.donotship.ppc64le #1 SMP Thu Sep 10 07:17:08 CDT 2015 ppc64le ppc64le ppc64le GNU/Linux [root@kvmhost ~]# dialog --version Version: 1.2-20130523 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialog/+bug/1549300/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1549300] Re: dialog wrongly requires double backslashes (\\n, \\Z) for control codes in option file
--- Comment From lc...@us.ibm.com 2016-06-16 20:48 EDT--- The bad package dialog-1.2-16.20150528.fc23.ppc64 had arrived in Fedora 23, and soon will go into Red Hat, CentOS ... everywhere. It is ruining the configuration UI of our PMLinux application, and must be fixed as soon as possible. ** Tags removed: architecture-ppc64le ** Tags added: architecture-ppc64 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to dialog in Ubuntu. https://bugs.launchpad.net/bugs/1549300 Title: dialog wrongly requires double backslashes (\\n, \\Z) for control codes in option file Status in dialog package in Ubuntu: Triaged Bug description: == Comment: #0 - Liang Chang Guo - 2015-09-11 18:44:18 == From Ubuntu 15.10 daily builds, the window-like tool "dialog" in Linux now turns to look for double backslashes (like \\n, \\Z...) as control codes in command option file, which causes incorrect display in format for programs (like PMLinux) that get used to only feeding with single backslash (\n, \Z...). This bug affects menu, form, and form etc. dialog boxes. There is no such problem for other disros, even ubuntu 15.05 ... *** Info of ubuntu/dialog that fail, and command/file to reproduce *** root@ubt1510F:~# uname -a Linux ubt1510F 4.2.0-7-generic #7-Ubuntu SMP Tue Sep 1 16:42:17 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux root@ubt1510F:~# dialog --version Version: 1.2-20150528 root@ubt1510F:~# dialog --file PMLinux.menus (see display effect in attachment) root@ubt1510F:~# cat PMLinux.menus --begin 2 2 --default-item "2) Disable" --ok-label " Select " --item-help --help-button --no-cancel --colors --timeout 585 --title " Setup Performance Management " --backtitle "IBM PMLinux Main Menus" --menu " \Z4I\Znnternational \Z4B\Znusiness \Z4M\Znachines (\Zu\Z4IBM\Zn), Copyright 2012-2015 \Z1(C)\Zn\n\n \Z0Move by \Zb\Z4\Zn or \Zb\Z4Mouse\Zn to desired function/button\n Presss \Z1\Zn to select, or \Z1\Zn to exit.\n\n \Zu\Z5ubt1510F\ZU\Zn STATUS: Collection \Z2ON\Zn, Transmission \Z2ON\Zn, CustomerInfo \Z1NO\Zn\n \Z4Linux OS Version\Z0: Ubuntu Wily Werewolf (development branch)" 25 81 11 "1)*Enable" "\Z2Data Transmission" "To correct & reset parameters to enable PMLinux Data Collection & Transmission" "2) Disable" "Data Transmission" "To disable PMLinux Data Collection & Transmission. Proceed with Caution !!!" "3) Retransmit" "Recorded Data" "To package historical data files of one or all day(s) into PMstats.send for manual transmission" "4)*Change/Show" "\Z1Customer Information" "To fill out contact info, so that IBM PMLinux team can create a login user for your web reports" "5) Change/Show" "Data Retention Period" "To setup the period length (days) for PMLinux to keep the data files" "6) Change/Show" "Trending Days and Shift Times" "To setup your weekly working days & shift times for PMLinux reports" "7) Change/Show" "System Parameters (Advanced)" "To setup some system configurations" "8) Change/Show" "KVM Guest Collection Settings" "To setup KVM Guest info and querying utilization data intervals" "9) ReadMe" "Guide/References/License" "To browse PMLinux manual/license text documents" "0) Exit""Quit" "To end this window-style PMLinux configuration tool" *** Info of ubuntu/dialog that pass *** [root@kvmhost ~]# uname -a Linux kvmhost 3.18.17-349.el7_1.pkvm3_1_0.3103.1.daily.donotship.ppc64le #1 SMP Thu Sep 10 07:17:08 CDT 2015 ppc64le ppc64le ppc64le GNU/Linux [root@kvmhost ~]# dialog --version Version: 1.2-20130523 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialog/+bug/1549300/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1549300] Comment bridged from LTC Bugzilla
--- Comment From bren...@br.ibm.com 2016-03-24 14:04 EDT--- > dialog is a desktop package and not supported on ppc64el Ok. Rejecting it internally. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to dialog in Ubuntu. https://bugs.launchpad.net/bugs/1549300 Title: dialog wrongly requires double backslashes (\\n, \\Z) for control codes in option file Status in dialog package in Ubuntu: New Bug description: == Comment: #0 - Liang Chang Guo - 2015-09-11 18:44:18 == From Ubuntu 15.10 daily builds, the window-like tool "dialog" in Linux now turns to look for double backslashes (like \\n, \\Z...) as control codes in command option file, which causes incorrect display in format for programs (like PMLinux) that get used to only feeding with single backslash (\n, \Z...). This bug affects menu, form, and form etc. dialog boxes. There is no such problem for other disros, even ubuntu 15.05 ... *** Info of ubuntu/dialog that fail, and command/file to reproduce *** root@ubt1510F:~# uname -a Linux ubt1510F 4.2.0-7-generic #7-Ubuntu SMP Tue Sep 1 16:42:17 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux root@ubt1510F:~# dialog --version Version: 1.2-20150528 root@ubt1510F:~# dialog --file PMLinux.menus (see display effect in attachment) root@ubt1510F:~# cat PMLinux.menus --begin 2 2 --default-item "2) Disable" --ok-label " Select " --item-help --help-button --no-cancel --colors --timeout 585 --title " Setup Performance Management " --backtitle "IBM PMLinux Main Menus" --menu " \Z4I\Znnternational \Z4B\Znusiness \Z4M\Znachines (\Zu\Z4IBM\Zn), Copyright 2012-2015 \Z1(C)\Zn\n\n \Z0Move by \Zb\Z4\Zn or \Zb\Z4Mouse\Zn to desired function/button\n Presss \Z1\Zn to select, or \Z1\Zn to exit.\n\n \Zu\Z5ubt1510F\ZU\Zn STATUS: Collection \Z2ON\Zn, Transmission \Z2ON\Zn, CustomerInfo \Z1NO\Zn\n \Z4Linux OS Version\Z0: Ubuntu Wily Werewolf (development branch)" 25 81 11 "1)*Enable" "\Z2Data Transmission" "To correct & reset parameters to enable PMLinux Data Collection & Transmission" "2) Disable" "Data Transmission" "To disable PMLinux Data Collection & Transmission. Proceed with Caution !!!" "3) Retransmit" "Recorded Data" "To package historical data files of one or all day(s) into PMstats.send for manual transmission" "4)*Change/Show" "\Z1Customer Information" "To fill out contact info, so that IBM PMLinux team can create a login user for your web reports" "5) Change/Show" "Data Retention Period" "To setup the period length (days) for PMLinux to keep the data files" "6) Change/Show" "Trending Days and Shift Times" "To setup your weekly working days & shift times for PMLinux reports" "7) Change/Show" "System Parameters (Advanced)" "To setup some system configurations" "8) Change/Show" "KVM Guest Collection Settings" "To setup KVM Guest info and querying utilization data intervals" "9) ReadMe" "Guide/References/License" "To browse PMLinux manual/license text documents" "0) Exit""Quit" "To end this window-style PMLinux configuration tool" *** Info of ubuntu/dialog that pass *** [root@kvmhost ~]# uname -a Linux kvmhost 3.18.17-349.el7_1.pkvm3_1_0.3103.1.daily.donotship.ppc64le #1 SMP Thu Sep 10 07:17:08 CDT 2015 ppc64le ppc64le ppc64le GNU/Linux [root@kvmhost ~]# dialog --version Version: 1.2-20130523 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialog/+bug/1549300/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1549300] Comment bridged from LTC Bugzilla
--- Comment From hepat...@in.ibm.com 2016-03-24 07:04 EDT--- Hi Canonical, Do you need any other information in order to debug/solve this bug? Can you please assign this bug to an appropriate developer to fix it as soon as possible? This has been hanging around a long time without an update. Thanks for your support.!! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to dialog in Ubuntu. https://bugs.launchpad.net/bugs/1549300 Title: dialog wrongly requires double backslashes (\\n, \\Z) for control codes in option file Status in dialog package in Ubuntu: New Bug description: == Comment: #0 - Liang Chang Guo - 2015-09-11 18:44:18 == From Ubuntu 15.10 daily builds, the window-like tool "dialog" in Linux now turns to look for double backslashes (like \\n, \\Z...) as control codes in command option file, which causes incorrect display in format for programs (like PMLinux) that get used to only feeding with single backslash (\n, \Z...). This bug affects menu, form, and form etc. dialog boxes. There is no such problem for other disros, even ubuntu 15.05 ... *** Info of ubuntu/dialog that fail, and command/file to reproduce *** root@ubt1510F:~# uname -a Linux ubt1510F 4.2.0-7-generic #7-Ubuntu SMP Tue Sep 1 16:42:17 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux root@ubt1510F:~# dialog --version Version: 1.2-20150528 root@ubt1510F:~# dialog --file PMLinux.menus (see display effect in attachment) root@ubt1510F:~# cat PMLinux.menus --begin 2 2 --default-item "2) Disable" --ok-label " Select " --item-help --help-button --no-cancel --colors --timeout 585 --title " Setup Performance Management " --backtitle "IBM PMLinux Main Menus" --menu " \Z4I\Znnternational \Z4B\Znusiness \Z4M\Znachines (\Zu\Z4IBM\Zn), Copyright 2012-2015 \Z1(C)\Zn\n\n \Z0Move by \Zb\Z4\Zn or \Zb\Z4Mouse\Zn to desired function/button\n Presss \Z1\Zn to select, or \Z1\Zn to exit.\n\n \Zu\Z5ubt1510F\ZU\Zn STATUS: Collection \Z2ON\Zn, Transmission \Z2ON\Zn, CustomerInfo \Z1NO\Zn\n \Z4Linux OS Version\Z0: Ubuntu Wily Werewolf (development branch)" 25 81 11 "1)*Enable" "\Z2Data Transmission" "To correct & reset parameters to enable PMLinux Data Collection & Transmission" "2) Disable" "Data Transmission" "To disable PMLinux Data Collection & Transmission. Proceed with Caution !!!" "3) Retransmit" "Recorded Data" "To package historical data files of one or all day(s) into PMstats.send for manual transmission" "4)*Change/Show" "\Z1Customer Information" "To fill out contact info, so that IBM PMLinux team can create a login user for your web reports" "5) Change/Show" "Data Retention Period" "To setup the period length (days) for PMLinux to keep the data files" "6) Change/Show" "Trending Days and Shift Times" "To setup your weekly working days & shift times for PMLinux reports" "7) Change/Show" "System Parameters (Advanced)" "To setup some system configurations" "8) Change/Show" "KVM Guest Collection Settings" "To setup KVM Guest info and querying utilization data intervals" "9) ReadMe" "Guide/References/License" "To browse PMLinux manual/license text documents" "0) Exit""Quit" "To end this window-style PMLinux configuration tool" *** Info of ubuntu/dialog that pass *** [root@kvmhost ~]# uname -a Linux kvmhost 3.18.17-349.el7_1.pkvm3_1_0.3103.1.daily.donotship.ppc64le #1 SMP Thu Sep 10 07:17:08 CDT 2015 ppc64le ppc64le ppc64le GNU/Linux [root@kvmhost ~]# dialog --version Version: 1.2-20130523 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialog/+bug/1549300/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1436448] Re: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24)
*** This bug is a duplicate of bug 1447654 *** https://bugs.launchpad.net/bugs/1447654 --- Comment From ss...@in.ibm.com 2016-02-28 23:57 EDT--- I can recreate this problem with latest 16.04 build. Created symlink from /run/systemd/system/polkitd.service to /dev/null. Unpacking policykit-1 (0.105-14.1) ... Selecting previously unselected package python3-systemd. Preparing to unpack .../python3-systemd_231-2build1_ppc64el.deb ... Unpacking python3-systemd (231-2build1) ... Processing triggers for systemd (229-1ubuntu4) ... Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit polkitd.service is masked. (g-io-error-quark, 36) Processing triggers for ureadahead (0.100.0-19) ... ureadahead will be reprofiled on next reboot Processing triggers for shared-mime-info (1.5-2) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for libc-bin (2.21-0ubuntu6) ... Processing triggers for dbus (1.10.6-1ubuntu2) ... Setting up python3-problem-report (2.20-0ubuntu3) ... Setting up python3-apport (2.20-0ubuntu3) ... Setting up apport (2.20-0ubuntu3) ... Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit polkitd.service is masked. (g-io-error-quark, 36) Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit polkitd.service is masked. (g-io-error-quark, 36) Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit polkitd.service is masked. (g-io-error-quark, 36) Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit polkitd.service is masked. (g-io-error-quark, 36) Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit polkitd.service is masked. (g-io-error-quark, 36) Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit polkitd.service is masked. (g-io-error-quark, 36) Setting up apport-symptoms (0.20) ... Setting up libpam-systemd:ppc64el (229-1ubuntu4) ... locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory Setting up libpolkit-agent-1-0:ppc64el (0.105-14.1) ... Setting up libpolkit-backend-1-0:ppc64el (0.105-14.1) ... Setting up policykit-1 (0.105-14.1) ... Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit polkitd.service is masked. (g-io-error-quark, 36) Removed symlink /run/systemd/system/polkitd.service. PolicyKit daemon disconnected from the bus. We are no longer a registered authentication agent. PolicyKit daemon reconnected to bus. Attempting to re-register as an authentication agent. We are now a registered authentication agent. Setting up python3-systemd (231-2build1) ... Processing triggers for systemd (229-1ubuntu4) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for libc-bin (2.21-0ubuntu6) ... Processing triggers for dbus (1.10.6-1ubuntu2) ... ** Tags removed: targetmilestone-inin1504 ** Tags added: targetmilestone-inin1604 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1436448 Title: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24) Status in policykit-1 package in Ubuntu: Confirmed Bug description: ---Problem Description--- Error messages while installing apport package ---uname output--- 3.19.0-9-generic Machine Type = POWER8 ---Steps to Reproduce--- 1) Install Ubuntu 15.04 as a PowerKVM guest. 2) Install apport package using following command apt-get install apport Error messages are displayed during the installation. The installation eventually succeeds. root@ub1504:~# apt-get install apport Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-3.18.0-13 linux-headers-3.18.0-13-generic linux-image-3.18.0-13-generic linux-image-extra-3.18.0-13-generic python-support Use 'apt-get autoremove' to remove them. The f
[Desktop-packages] [Bug 1489483] Re: Enable llvmpipe on libgl-mesa-dri
** Tags removed: severity-medium ** Tags added: severity-high -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1489483 Title: Enable llvmpipe on libgl-mesa-dri Status in mesa package in Ubuntu: Triaged Bug description: == Comment: #0 - Gabriel Krisman Bertazi - 2015-08-12 09:53:27 == The llvmpipe software renderer is disabled in the mesa (libgl1-mesa-dri) package for ppc64le, even though llvmpipe is fully supported on this architecture. We need this feature enabled in order to run Unity with video cards lacking 3D Hardware Acceleration. Please enable it and, if possible, backport this change to 14.04.3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1489483/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1489483] Re: Enable llvmpipe on libgl-mesa-dri
** Tags removed: targetmilestone-inin1604 ** Tags added: targetmilestone-inin1610 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1489483 Title: Enable llvmpipe on libgl-mesa-dri Status in mesa package in Ubuntu: Triaged Bug description: == Comment: #0 - Gabriel Krisman Bertazi - 2015-08-12 09:53:27 == The llvmpipe software renderer is disabled in the mesa (libgl1-mesa-dri) package for ppc64le, even though llvmpipe is fully supported on this architecture. We need this feature enabled in order to run Unity with video cards lacking 3D Hardware Acceleration. Please enable it and, if possible, backport this change to 14.04.3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1489483/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1436448] Comment bridged from LTC Bugzilla
*** This bug is a duplicate of bug 1447654 *** https://bugs.launchpad.net/bugs/1447654 --- Comment From pawak...@in.ibm.com 2016-02-15 03:09 EDT--- *** Bug 137078 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1436448 Title: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24) Status in policykit-1 package in Ubuntu: Confirmed Bug description: ---Problem Description--- Error messages while installing apport package ---uname output--- 3.19.0-9-generic Machine Type = POWER8 ---Steps to Reproduce--- 1) Install Ubuntu 15.04 as a PowerKVM guest. 2) Install apport package using following command apt-get install apport Error messages are displayed during the installation. The installation eventually succeeds. root@ub1504:~# apt-get install apport Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-3.18.0-13 linux-headers-3.18.0-13-generic linux-image-3.18.0-13-generic linux-image-extra-3.18.0-13-generic python-support Use 'apt-get autoremove' to remove them. The following extra packages will be installed: apport-symptoms libpolkit-agent-1-0 libpolkit-backend-1-0 policykit-1 python3-apport python3-problem-report Suggested packages: apport-gtk apport-kde python3-launchpadlib The following NEW packages will be installed: apport apport-symptoms libpolkit-agent-1-0 libpolkit-backend-1-0 policykit-1 python3-apport python3-problem-report 0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded. Need to get 312 kB of archives. After this operation, 2,296 kB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://ports.ubuntu.com/ubuntu-ports/ vivid/main libpolkit-agent-1-0 ppc64el 0.105-8ubuntu2 [14.6 kB] Get:2 http://ports.ubuntu.com/ubuntu-ports/ vivid/main libpolkit-backend-1-0 ppc64el 0.105-8ubuntu2 [33.5 kB] Get:3 http://ports.ubuntu.com/ubuntu-ports/ vivid/main python3-problem-report all 2.16.2-0ubuntu4 [10.1 kB] Get:4 http://ports.ubuntu.com/ubuntu-ports/ vivid/main python3-apport all 2.16.2-0ubuntu4 [75.9 kB] Get:5 http://ports.ubuntu.com/ubuntu-ports/ vivid/main apport all 2.16.2-0ubuntu4 [113 kB] Get:6 http://ports.ubuntu.com/ubuntu-ports/ vivid/main apport-symptoms all 0.20 [14.2 kB] Get:7 http://ports.ubuntu.com/ubuntu-ports/ vivid/main policykit-1 ppc64el 0.105-8ubuntu2 [50.7 kB] Fetched 312 kB in 1s (217 kB/s) Selecting previously unselected package libpolkit-agent-1-0:ppc64el. (Reading database ... 114319 files and directories currently installed.) Preparing to unpack .../libpolkit-agent-1-0_0.105-8ubuntu2_ppc64el.deb ... Unpacking libpolkit-agent-1-0:ppc64el (0.105-8ubuntu2) ... Selecting previously unselected package libpolkit-backend-1-0:ppc64el. Preparing to unpack .../libpolkit-backend-1-0_0.105-8ubuntu2_ppc64el.deb ... Unpacking libpolkit-backend-1-0:ppc64el (0.105-8ubuntu2) ... Selecting previously unselected package python3-problem-report. Preparing to unpack .../python3-problem-report_2.16.2-0ubuntu4_all.deb ... Unpacking python3-problem-report (2.16.2-0ubuntu4) ... Selecting previously unselected package python3-apport. Preparing to unpack .../python3-apport_2.16.2-0ubuntu4_all.deb ... Unpacking python3-apport (2.16.2-0ubuntu4) ... Selecting previously unselected package apport. Preparing to unpack .../apport_2.16.2-0ubuntu4_all.deb ... Unpacking apport (2.16.2-0ubuntu4) ... Selecting previously unselected package apport-symptoms. Preparing to unpack .../apport-symptoms_0.20_all.deb ... Unpacking apport-symptoms (0.20) ... Selecting previously unselected package policykit-1. Preparing to unpack .../policykit-1_0.105-8ubuntu2_ppc64el.deb ... Unpacking policykit-1 (0.105-8ubuntu2) ... Processing triggers for man-db (2.7.0.2-5) ... Processing triggers for shared-mime-info (1.3-1) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for dbus (1.8.12-1ubuntu3) ... Setting up libpolkit-agent-1-0:ppc64el (0.105-8ubuntu2) ... Setting up libpolkit-backend-1-0:ppc64el (0.105-8ubuntu2) ... Setting up python3-problem-report (2.16.2-0ubuntu4) ... Setting up python3-apport (2.16.2-0ubuntu4) ... Setting up apport (2.16.2-0ubuntu4) ... Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24) Failed to execute operation: Connection timed out invoke-rc.d: apport.service doesn't exist but the upstart job does. Nothing to start or stop until a systemd or init job is present. Setting u
[Desktop-packages] [Bug 1478087] Comment bridged from LTC Bugzilla
--- Comment From gcwil...@us.ibm.com 2016-02-02 17:56 EDT--- Thanks to Tyler and the Canonical crew! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1478087 Title: Add libaudit support Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.16 series: Fix Released Status in Light Display Manager 1.2 series: Won't Fix Status in lightdm package in Ubuntu: Fix Released Status in openssh package in Ubuntu: Fix Released Status in shadow package in Ubuntu: Fix Released Status in lightdm source package in Trusty: Triaged Status in openssh source package in Trusty: Fix Committed Status in shadow source package in Trusty: Fix Committed Status in lightdm source package in Vivid: Triaged Status in openssh source package in Vivid: Triaged Status in shadow source package in Vivid: Triaged Status in lightdm source package in Wily: Fix Released Status in openssh source package in Wily: Fix Released Status in shadow source package in Wily: Fix Released Status in openssh package in Debian: Fix Released Bug description: [Impact] Auditing support is a commonly used feature in large enterprises, and allows better tracking of actions happening on secured systems, especially when it comes to accounting for login events. Such systems fail to correctly list login events in aureport due to some software not integrating libaudit. [Test Case] 1) Install auditd 2) Login to the system multiple times (or allow for others to connect to the system) 3) Run aureport -l System should list login information. [Regression Potential] There is minimal risk for issues since libaudit support only allows for generating extra logging saved on the local system. A possible side-effect of this may be that systems on which auditing is enabled and where there are many users of the affected software (see bug tasks), such as many logins over SSH, there may be an increased demand on disk space necessary for the auditing data. --- -- Problem Description -- We installed ubuntu 14.04.3 on lakelp1 and installed package auditd. We tried to ssh to lakelp1 several times and found that "aureport -l" couldn't print out the login info. root@lakelp1:~# /etc/init.d/auditd status * auditd is running. root@lakelp1:~# auditctl -e 1 AUDIT_STATUS: enabled=1 flag=1 pid=38784 rate_limit=0 backlog_limit=320 lost=12 backlog=1 root@lakelp1:~# grep -i login /var/log/audit/audit.log type=LOGIN msg=audit(1437641256.987:67): pid=11752 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=4 res=1 type=LOGIN msg=audit(1437642646.478:85): pid=44269 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=5 res=1 type=LOGIN msg=audit(1437642700.295:90): pid=21504 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=6 res=1 type=LOGIN msg=audit(1437642765.339:104): pid=16628 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=7 res=1 type=LOGIN msg=audit(1437644638.593:130): pid=3 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=8 res=1 root@lakelp1:~# aureport -l Login Report # date time auid host term exe success event This looks like a bug in aureport or libaudit. In addition to giving admins falsely empty record selections, this would prevent successful completion of a Common Criteria certification. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1478087/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1478087] Comment bridged from LTC Bugzilla
--- Comment From fen...@cn.ibm.com 2016-01-31 23:04 EDT--- Verified on Ubuntu14.04.4, this bug is not fixed. root@monklp1:~# /etc/init.d/auditd status * auditd is running. root@monklp1:~# auditctl -e 1 AUDIT_STATUS: enabled=1 flag=1 pid=9417 rate_limit=0 backlog_limit=320 lost=2 backlog=0 root@monklp1:~# grep -i login /var/log/audit/audit.log type=LOGIN msg=audit(1454295455.634:27): pid=9439 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=1 res=1 type=LOGIN msg=audit(1454295480.786:35): pid=9471 uid=0 old-auid=4294967295 auid=1000 old-ses=4294967295 ses=2 res=1 type=LOGIN msg=audit(1454295524.534:43): pid=9508 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=3 res=1 root@monklp1:~# aureport -l Login Report # date time auid host term exe success event root@monklp1:~# uname -a Linux monklp1 4.2.0-25-generic #30~14.04.1-Ubuntu SMP Mon Jan 18 16:25:16 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux root@monklp1:~# dpkg -s auditd Package: auditd Status: install ok installed Priority: extra Section: admin Installed-Size: 713 Maintainer: Ubuntu Developers Architecture: ppc64el Source: audit Version: 1:2.3.2-2ubuntu1 Depends: lsb-base (>= 3.0-6), init-system-helpers (>= 1.13~), libaudit1 (>= 1:2.2.1), libauparse0 (>= 1:2.3.1), libc6 (>= 2.17) Suggests: audispd-plugins -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1478087 Title: Add libaudit support Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.16 series: Fix Released Status in Light Display Manager 1.2 series: Won't Fix Status in audit package in Ubuntu: Invalid Status in lightdm package in Ubuntu: Fix Released Status in openssh package in Ubuntu: Fix Released Status in shadow package in Ubuntu: Fix Released Status in lightdm source package in Trusty: Triaged Status in openssh source package in Trusty: Fix Committed Status in shadow source package in Trusty: Fix Committed Status in lightdm source package in Vivid: Triaged Status in openssh source package in Vivid: Triaged Status in shadow source package in Vivid: Triaged Status in lightdm source package in Wily: Fix Released Status in openssh source package in Wily: Fix Released Status in shadow source package in Wily: Fix Released Bug description: [Impact] Auditing support is a commonly used feature in large enterprises, and allows better tracking of actions happening on secured systems, especially when it comes to accounting for login events. Such systems fail to correctly list login events in aureport due to some software not integrating libaudit. [Test Case] 1) Install auditd 2) Login to the system multiple times (or allow for others to connect to the system) 3) Run aureport -l System should list login information. [Regression Potential] There is minimal risk for issues since libaudit support only allows for generating extra logging saved on the local system. A possible side-effect of this may be that systems on which auditing is enabled and where there are many users of the affected software (see bug tasks), such as many logins over SSH, there may be an increased demand on disk space necessary for the auditing data. --- -- Problem Description -- We installed ubuntu 14.04.3 on lakelp1 and installed package auditd. We tried to ssh to lakelp1 several times and found that "aureport -l" couldn't print out the login info. root@lakelp1:~# /etc/init.d/auditd status * auditd is running. root@lakelp1:~# auditctl -e 1 AUDIT_STATUS: enabled=1 flag=1 pid=38784 rate_limit=0 backlog_limit=320 lost=12 backlog=1 root@lakelp1:~# grep -i login /var/log/audit/audit.log type=LOGIN msg=audit(1437641256.987:67): pid=11752 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=4 res=1 type=LOGIN msg=audit(1437642646.478:85): pid=44269 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=5 res=1 type=LOGIN msg=audit(1437642700.295:90): pid=21504 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=6 res=1 type=LOGIN msg=audit(1437642765.339:104): pid=16628 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=7 res=1 type=LOGIN msg=audit(1437644638.593:130): pid=3 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=8 res=1 root@lakelp1:~# aureport -l Login Report # date time auid host term exe success event This looks like a bug in aureport or libaudit. In addition to giving admins falsely empty record selections, this would prevent successful completion of a Common Criteria certification. To manage notificati
[Desktop-packages] [Bug 1478087] Comment bridged from LTC Bugzilla
--- Comment From amda...@us.ibm.com 2015-11-16 18:17 EDT--- Because this is a security, we request this fix be included in 14.04 SRU please. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1478087 Title: Add libaudit support Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.16 series: Fix Released Status in Light Display Manager 1.2 series: Won't Fix Status in audit package in Ubuntu: Invalid Status in lightdm package in Ubuntu: Fix Released Status in openssh package in Ubuntu: Fix Released Status in shadow package in Ubuntu: Fix Released Status in lightdm source package in Trusty: Triaged Status in openssh source package in Trusty: Triaged Status in shadow source package in Trusty: Triaged Status in lightdm source package in Vivid: Triaged Status in openssh source package in Vivid: Triaged Status in shadow source package in Vivid: Triaged Status in lightdm source package in Wily: Fix Released Status in openssh source package in Wily: Fix Released Status in shadow source package in Wily: Fix Released Bug description: -- Problem Description -- We installed ubuntu 14.04.3 on lakelp1 and installed package auditd. We tried to ssh to lakelp1 several times and found that "aureport -l" couldn't print out the login info. root@lakelp1:~# /etc/init.d/auditd status * auditd is running. root@lakelp1:~# auditctl -e 1 AUDIT_STATUS: enabled=1 flag=1 pid=38784 rate_limit=0 backlog_limit=320 lost=12 backlog=1 root@lakelp1:~# grep -i login /var/log/audit/audit.log type=LOGIN msg=audit(1437641256.987:67): pid=11752 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=4 res=1 type=LOGIN msg=audit(1437642646.478:85): pid=44269 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=5 res=1 type=LOGIN msg=audit(1437642700.295:90): pid=21504 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=6 res=1 type=LOGIN msg=audit(1437642765.339:104): pid=16628 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=7 res=1 type=LOGIN msg=audit(1437644638.593:130): pid=3 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=8 res=1 root@lakelp1:~# aureport -l Login Report # date time auid host term exe success event This looks like a bug in aureport or libaudit. In addition to giving admins falsely empty record selections, this would prevent successful completion of a Common Criteria certification. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1478087/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1478087] Re: Add libaudit support
** Tags removed: severity-high ** Tags added: severity-medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1478087 Title: Add libaudit support Status in Light Display Manager: Fix Committed Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Committed Status in Light Display Manager 1.16 series: Fix Released Status in Light Display Manager 1.2 series: Won't Fix Status in audit package in Ubuntu: Invalid Status in lightdm package in Ubuntu: Fix Released Status in openssh package in Ubuntu: Fix Released Status in shadow package in Ubuntu: Fix Released Status in lightdm source package in Trusty: Triaged Status in openssh source package in Trusty: Triaged Status in shadow source package in Trusty: Triaged Status in lightdm source package in Vivid: Triaged Status in openssh source package in Vivid: Triaged Status in shadow source package in Vivid: Triaged Status in lightdm source package in Wily: Fix Released Status in openssh source package in Wily: Fix Released Status in shadow source package in Wily: Fix Released Bug description: -- Problem Description -- We installed ubuntu 14.04.3 on lakelp1 and installed package auditd. We tried to ssh to lakelp1 several times and found that "aureport -l" couldn't print out the login info. root@lakelp1:~# /etc/init.d/auditd status * auditd is running. root@lakelp1:~# auditctl -e 1 AUDIT_STATUS: enabled=1 flag=1 pid=38784 rate_limit=0 backlog_limit=320 lost=12 backlog=1 root@lakelp1:~# grep -i login /var/log/audit/audit.log type=LOGIN msg=audit(1437641256.987:67): pid=11752 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=4 res=1 type=LOGIN msg=audit(1437642646.478:85): pid=44269 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=5 res=1 type=LOGIN msg=audit(1437642700.295:90): pid=21504 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=6 res=1 type=LOGIN msg=audit(1437642765.339:104): pid=16628 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=7 res=1 type=LOGIN msg=audit(1437644638.593:130): pid=3 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=8 res=1 root@lakelp1:~# aureport -l Login Report # date time auid host term exe success event This looks like a bug in aureport or libaudit. In addition to giving admins falsely empty record selections, this would prevent successful completion of a Common Criteria certification. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1478087/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1489483] Re: Enable llvmpipe on libgl-mesa-dri
** Tags removed: targetmilestone-inin1510 ** Tags added: targetmilestone-inin1604 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1489483 Title: Enable llvmpipe on libgl-mesa-dri Status in mesa package in Ubuntu: Triaged Bug description: == Comment: #0 - Gabriel Krisman Bertazi - 2015-08-12 09:53:27 == The llvmpipe software renderer is disabled in the mesa (libgl1-mesa-dri) package for ppc64le, even though llvmpipe is fully supported on this architecture. We need this feature enabled in order to run Unity with video cards lacking 3D Hardware Acceleration. Please enable it and, if possible, backport this change to 14.04.3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1489483/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1489483] Re: Enable llvmpipe on libgl-mesa-dri
** Tags removed: severity-high ** Tags added: severity-medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1489483 Title: Enable llvmpipe on libgl-mesa-dri Status in mesa package in Ubuntu: New Bug description: == Comment: #0 - Gabriel Krisman Bertazi - 2015-08-12 09:53:27 == The llvmpipe software renderer is disabled in the mesa (libgl1-mesa-dri) package for ppc64le, even though llvmpipe is fully supported on this architecture. We need this feature enabled in order to run Unity with video cards lacking 3D Hardware Acceleration. Please enable it and, if possible, backport this change to 14.04.3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1489483/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1436448] Comment bridged from LTC Bugzilla
--- Comment From brsri...@in.ibm.com 2015-09-15 08:18 EDT--- Hello Canonical, Can you please let us know if you need more inputs from us? thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1436448 Title: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24) Status in policykit-1 package in Ubuntu: Confirmed Bug description: ---Problem Description--- Error messages while installing apport package ---uname output--- 3.19.0-9-generic Machine Type = POWER8 ---Steps to Reproduce--- 1) Install Ubuntu 15.04 as a PowerKVM guest. 2) Install apport package using following command apt-get install apport Error messages are displayed during the installation. The installation eventually succeeds. root@ub1504:~# apt-get install apport Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-3.18.0-13 linux-headers-3.18.0-13-generic linux-image-3.18.0-13-generic linux-image-extra-3.18.0-13-generic python-support Use 'apt-get autoremove' to remove them. The following extra packages will be installed: apport-symptoms libpolkit-agent-1-0 libpolkit-backend-1-0 policykit-1 python3-apport python3-problem-report Suggested packages: apport-gtk apport-kde python3-launchpadlib The following NEW packages will be installed: apport apport-symptoms libpolkit-agent-1-0 libpolkit-backend-1-0 policykit-1 python3-apport python3-problem-report 0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded. Need to get 312 kB of archives. After this operation, 2,296 kB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://ports.ubuntu.com/ubuntu-ports/ vivid/main libpolkit-agent-1-0 ppc64el 0.105-8ubuntu2 [14.6 kB] Get:2 http://ports.ubuntu.com/ubuntu-ports/ vivid/main libpolkit-backend-1-0 ppc64el 0.105-8ubuntu2 [33.5 kB] Get:3 http://ports.ubuntu.com/ubuntu-ports/ vivid/main python3-problem-report all 2.16.2-0ubuntu4 [10.1 kB] Get:4 http://ports.ubuntu.com/ubuntu-ports/ vivid/main python3-apport all 2.16.2-0ubuntu4 [75.9 kB] Get:5 http://ports.ubuntu.com/ubuntu-ports/ vivid/main apport all 2.16.2-0ubuntu4 [113 kB] Get:6 http://ports.ubuntu.com/ubuntu-ports/ vivid/main apport-symptoms all 0.20 [14.2 kB] Get:7 http://ports.ubuntu.com/ubuntu-ports/ vivid/main policykit-1 ppc64el 0.105-8ubuntu2 [50.7 kB] Fetched 312 kB in 1s (217 kB/s) Selecting previously unselected package libpolkit-agent-1-0:ppc64el. (Reading database ... 114319 files and directories currently installed.) Preparing to unpack .../libpolkit-agent-1-0_0.105-8ubuntu2_ppc64el.deb ... Unpacking libpolkit-agent-1-0:ppc64el (0.105-8ubuntu2) ... Selecting previously unselected package libpolkit-backend-1-0:ppc64el. Preparing to unpack .../libpolkit-backend-1-0_0.105-8ubuntu2_ppc64el.deb ... Unpacking libpolkit-backend-1-0:ppc64el (0.105-8ubuntu2) ... Selecting previously unselected package python3-problem-report. Preparing to unpack .../python3-problem-report_2.16.2-0ubuntu4_all.deb ... Unpacking python3-problem-report (2.16.2-0ubuntu4) ... Selecting previously unselected package python3-apport. Preparing to unpack .../python3-apport_2.16.2-0ubuntu4_all.deb ... Unpacking python3-apport (2.16.2-0ubuntu4) ... Selecting previously unselected package apport. Preparing to unpack .../apport_2.16.2-0ubuntu4_all.deb ... Unpacking apport (2.16.2-0ubuntu4) ... Selecting previously unselected package apport-symptoms. Preparing to unpack .../apport-symptoms_0.20_all.deb ... Unpacking apport-symptoms (0.20) ... Selecting previously unselected package policykit-1. Preparing to unpack .../policykit-1_0.105-8ubuntu2_ppc64el.deb ... Unpacking policykit-1 (0.105-8ubuntu2) ... Processing triggers for man-db (2.7.0.2-5) ... Processing triggers for shared-mime-info (1.3-1) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for dbus (1.8.12-1ubuntu3) ... Setting up libpolkit-agent-1-0:ppc64el (0.105-8ubuntu2) ... Setting up libpolkit-backend-1-0:ppc64el (0.105-8ubuntu2) ... Setting up python3-problem-report (2.16.2-0ubuntu4) ... Setting up python3-apport (2.16.2-0ubuntu4) ... Setting up apport (2.16.2-0ubuntu4) ... Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24) Failed to execute operation: Connection timed out invoke-rc.d: apport.service doesn't exist but the upstart job does. Nothing to start or stop until a systemd or init job is present. Setting up apport-symptoms (0.20) ... Setting up policykit-1 (0.105-8ubuntu
[Desktop-packages] [Bug 1489483] Enable llvmpipe renderer
--- Comment on attachment From gbert...@br.ibm.com 2015-08-28 15:13 EDT--- Proposed changes to enable llvmpipe Software Renderer in the mesa package for ppc64el. ** Attachment added: "Enable llvmpipe renderer" https://bugs.launchpad.net/bugs/1489483/+attachment/4453864/+files/llvmpipe.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1489483 Title: Enable llvmpipe on libgl-mesa-dri Status in mesa package in Ubuntu: New Bug description: == Comment: #0 - Gabriel Krisman Bertazi - 2015-08-12 09:53:27 == The llvmpipe software renderer is disabled in the mesa (libgl1-mesa-dri) package for ppc64le, even though llvmpipe is fully supported on this architecture. We need this feature enabled in order to run Unity with video cards lacking 3D Hardware Acceleration. Please enable it and, if possible, backport this change to 14.04.3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1489483/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1436448] Comment bridged from LTC Bugzilla
--- Comment From brsri...@in.ibm.com 2015-07-22 08:50 EDT--- *** Bug 127858 has been marked as a duplicate of this bug. *** --- Comment From brsri...@in.ibm.com 2015-07-22 09:00 EDT--- Hello Canonical, We are seeing this issue on the latest daily builds (http://cdimage.ubuntu.com/ubuntu-server/daily/current/ ) also. Can you please let us know if you need more details from us to proceed on this ? Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1436448 Title: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24) Status in policykit-1 package in Ubuntu: Confirmed Bug description: ---Problem Description--- Error messages while installing apport package ---uname output--- 3.19.0-9-generic Machine Type = POWER8 ---Steps to Reproduce--- 1) Install Ubuntu 15.04 as a PowerKVM guest. 2) Install apport package using following command apt-get install apport Error messages are displayed during the installation. The installation eventually succeeds. root@ub1504:~# apt-get install apport Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-3.18.0-13 linux-headers-3.18.0-13-generic linux-image-3.18.0-13-generic linux-image-extra-3.18.0-13-generic python-support Use 'apt-get autoremove' to remove them. The following extra packages will be installed: apport-symptoms libpolkit-agent-1-0 libpolkit-backend-1-0 policykit-1 python3-apport python3-problem-report Suggested packages: apport-gtk apport-kde python3-launchpadlib The following NEW packages will be installed: apport apport-symptoms libpolkit-agent-1-0 libpolkit-backend-1-0 policykit-1 python3-apport python3-problem-report 0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded. Need to get 312 kB of archives. After this operation, 2,296 kB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://ports.ubuntu.com/ubuntu-ports/ vivid/main libpolkit-agent-1-0 ppc64el 0.105-8ubuntu2 [14.6 kB] Get:2 http://ports.ubuntu.com/ubuntu-ports/ vivid/main libpolkit-backend-1-0 ppc64el 0.105-8ubuntu2 [33.5 kB] Get:3 http://ports.ubuntu.com/ubuntu-ports/ vivid/main python3-problem-report all 2.16.2-0ubuntu4 [10.1 kB] Get:4 http://ports.ubuntu.com/ubuntu-ports/ vivid/main python3-apport all 2.16.2-0ubuntu4 [75.9 kB] Get:5 http://ports.ubuntu.com/ubuntu-ports/ vivid/main apport all 2.16.2-0ubuntu4 [113 kB] Get:6 http://ports.ubuntu.com/ubuntu-ports/ vivid/main apport-symptoms all 0.20 [14.2 kB] Get:7 http://ports.ubuntu.com/ubuntu-ports/ vivid/main policykit-1 ppc64el 0.105-8ubuntu2 [50.7 kB] Fetched 312 kB in 1s (217 kB/s) Selecting previously unselected package libpolkit-agent-1-0:ppc64el. (Reading database ... 114319 files and directories currently installed.) Preparing to unpack .../libpolkit-agent-1-0_0.105-8ubuntu2_ppc64el.deb ... Unpacking libpolkit-agent-1-0:ppc64el (0.105-8ubuntu2) ... Selecting previously unselected package libpolkit-backend-1-0:ppc64el. Preparing to unpack .../libpolkit-backend-1-0_0.105-8ubuntu2_ppc64el.deb ... Unpacking libpolkit-backend-1-0:ppc64el (0.105-8ubuntu2) ... Selecting previously unselected package python3-problem-report. Preparing to unpack .../python3-problem-report_2.16.2-0ubuntu4_all.deb ... Unpacking python3-problem-report (2.16.2-0ubuntu4) ... Selecting previously unselected package python3-apport. Preparing to unpack .../python3-apport_2.16.2-0ubuntu4_all.deb ... Unpacking python3-apport (2.16.2-0ubuntu4) ... Selecting previously unselected package apport. Preparing to unpack .../apport_2.16.2-0ubuntu4_all.deb ... Unpacking apport (2.16.2-0ubuntu4) ... Selecting previously unselected package apport-symptoms. Preparing to unpack .../apport-symptoms_0.20_all.deb ... Unpacking apport-symptoms (0.20) ... Selecting previously unselected package policykit-1. Preparing to unpack .../policykit-1_0.105-8ubuntu2_ppc64el.deb ... Unpacking policykit-1 (0.105-8ubuntu2) ... Processing triggers for man-db (2.7.0.2-5) ... Processing triggers for shared-mime-info (1.3-1) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for dbus (1.8.12-1ubuntu3) ... Setting up libpolkit-agent-1-0:ppc64el (0.105-8ubuntu2) ... Setting up libpolkit-backend-1-0:ppc64el (0.105-8ubuntu2) ... Setting up python3-problem-report (2.16.2-0ubuntu4) ... Setting up python3-apport (2.16.2-0ubuntu4) ... Setting up apport (2.16.2-0ubuntu4) ... Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark,
[Desktop-packages] [Bug 1436448] Comment bridged from LTC Bugzilla
--- Comment From erwan.pri...@fr.ibm.com 2015-07-02 12:45 EDT--- *** Bug 122925 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1436448 Title: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24) Status in policykit-1 package in Ubuntu: Confirmed Bug description: ---Problem Description--- Error messages while installing apport package ---uname output--- 3.19.0-9-generic Machine Type = POWER8 ---Steps to Reproduce--- 1) Install Ubuntu 15.04 as a PowerKVM guest. 2) Install apport package using following command apt-get install apport Error messages are displayed during the installation. The installation eventually succeeds. root@ub1504:~# apt-get install apport Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-3.18.0-13 linux-headers-3.18.0-13-generic linux-image-3.18.0-13-generic linux-image-extra-3.18.0-13-generic python-support Use 'apt-get autoremove' to remove them. The following extra packages will be installed: apport-symptoms libpolkit-agent-1-0 libpolkit-backend-1-0 policykit-1 python3-apport python3-problem-report Suggested packages: apport-gtk apport-kde python3-launchpadlib The following NEW packages will be installed: apport apport-symptoms libpolkit-agent-1-0 libpolkit-backend-1-0 policykit-1 python3-apport python3-problem-report 0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded. Need to get 312 kB of archives. After this operation, 2,296 kB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://ports.ubuntu.com/ubuntu-ports/ vivid/main libpolkit-agent-1-0 ppc64el 0.105-8ubuntu2 [14.6 kB] Get:2 http://ports.ubuntu.com/ubuntu-ports/ vivid/main libpolkit-backend-1-0 ppc64el 0.105-8ubuntu2 [33.5 kB] Get:3 http://ports.ubuntu.com/ubuntu-ports/ vivid/main python3-problem-report all 2.16.2-0ubuntu4 [10.1 kB] Get:4 http://ports.ubuntu.com/ubuntu-ports/ vivid/main python3-apport all 2.16.2-0ubuntu4 [75.9 kB] Get:5 http://ports.ubuntu.com/ubuntu-ports/ vivid/main apport all 2.16.2-0ubuntu4 [113 kB] Get:6 http://ports.ubuntu.com/ubuntu-ports/ vivid/main apport-symptoms all 0.20 [14.2 kB] Get:7 http://ports.ubuntu.com/ubuntu-ports/ vivid/main policykit-1 ppc64el 0.105-8ubuntu2 [50.7 kB] Fetched 312 kB in 1s (217 kB/s) Selecting previously unselected package libpolkit-agent-1-0:ppc64el. (Reading database ... 114319 files and directories currently installed.) Preparing to unpack .../libpolkit-agent-1-0_0.105-8ubuntu2_ppc64el.deb ... Unpacking libpolkit-agent-1-0:ppc64el (0.105-8ubuntu2) ... Selecting previously unselected package libpolkit-backend-1-0:ppc64el. Preparing to unpack .../libpolkit-backend-1-0_0.105-8ubuntu2_ppc64el.deb ... Unpacking libpolkit-backend-1-0:ppc64el (0.105-8ubuntu2) ... Selecting previously unselected package python3-problem-report. Preparing to unpack .../python3-problem-report_2.16.2-0ubuntu4_all.deb ... Unpacking python3-problem-report (2.16.2-0ubuntu4) ... Selecting previously unselected package python3-apport. Preparing to unpack .../python3-apport_2.16.2-0ubuntu4_all.deb ... Unpacking python3-apport (2.16.2-0ubuntu4) ... Selecting previously unselected package apport. Preparing to unpack .../apport_2.16.2-0ubuntu4_all.deb ... Unpacking apport (2.16.2-0ubuntu4) ... Selecting previously unselected package apport-symptoms. Preparing to unpack .../apport-symptoms_0.20_all.deb ... Unpacking apport-symptoms (0.20) ... Selecting previously unselected package policykit-1. Preparing to unpack .../policykit-1_0.105-8ubuntu2_ppc64el.deb ... Unpacking policykit-1 (0.105-8ubuntu2) ... Processing triggers for man-db (2.7.0.2-5) ... Processing triggers for shared-mime-info (1.3-1) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for dbus (1.8.12-1ubuntu3) ... Setting up libpolkit-agent-1-0:ppc64el (0.105-8ubuntu2) ... Setting up libpolkit-backend-1-0:ppc64el (0.105-8ubuntu2) ... Setting up python3-problem-report (2.16.2-0ubuntu4) ... Setting up python3-apport (2.16.2-0ubuntu4) ... Setting up apport (2.16.2-0ubuntu4) ... Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24) Failed to execute operation: Connection timed out invoke-rc.d: apport.service doesn't exist but the upstart job does. Nothing to start or stop until a systemd or init job is present. Setting up apport-symptoms (0.20) ... Setting up policykit-1 (0.105-8ubuntu2) ... Processing
[Desktop-packages] [Bug 1400420] Comment bridged from LTC Bugzilla
--- Comment From bren...@br.ibm.com 2015-01-07 15:09 EDT--- Thanks. Closing per previous comments. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1400420 Title: [Ubuntu 15.04] Mesa/gallium: Fix Altivec pack intrinsics for little endian Status in mesa package in Ubuntu: In Progress Bug description: Please ensure the following patch is incorporated into the mesa package for correct behavior on ppc64el: http://lists.freedesktop.org/archives/mesa-dev/2014-August/064711.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1400420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1400420] Comment bridged from LTC Bugzilla
--- Comment From wschm...@us.ibm.com 2015-01-06 18:09 EDT--- To my knowledge there should not be. The request was simply to ensure that this patch is included, to avoid potential problems. Thanks! Bill -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1400420 Title: [Ubuntu 15.04] Mesa/gallium: Fix Altivec pack intrinsics for little endian Status in mesa package in Ubuntu: In Progress Bug description: Please ensure the following patch is incorporated into the mesa package for correct behavior on ppc64el: http://lists.freedesktop.org/archives/mesa-dev/2014-August/064711.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1400420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1400420] Re: [Ubuntu 15.04] Mesa/gallium: Fix Altivec pack intrinsics for little endian
** Tags removed: targetmilestone-inin1410 ** Tags added: targetmilestone-inin1504 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1400420 Title: [Ubuntu 15.04] Mesa/gallium: Fix Altivec pack intrinsics for little endian Status in mesa package in Ubuntu: New Bug description: Please ensure the following patch is incorporated into the mesa package for correct behavior on ppc64el: http://lists.freedesktop.org/archives/mesa-dev/2014-August/064711.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1400420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
