[Desktop-packages] [Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
Christian submitted https://github.com/systemd/systemd/pull/18559 which got turned into https://github.com/systemd/systemd/pull/18684 and has now been merged in upstream systemd. We've both tested the resulting systemd and can confirm that /run/udev is now properly populated. Please cherry-pick those udevd fixes into Ubuntu's systemd. ** Changed in: systemd (Ubuntu) Assignee: Christian Brauner (cbrauner) => (unassigned) ** Changed in: systemd (Ubuntu) Status: Fix Released => Triaged ** Changed in: systemd (Ubuntu) Importance: Wishlist => High -- 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/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in lxd package in Ubuntu: Won't Fix Status in network-manager package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Triaged Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1914062/+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 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
** Changed in: systemd (Ubuntu) Assignee: Ubuntu containers team (ubuntu-lxc) => Christian Brauner (cbrauner) -- 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/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in lxd package in Ubuntu: Won't Fix Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Triaged Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1914062/+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 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
** Changed in: network-manager (Ubuntu) Status: New => Invalid ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Ubuntu containers team (ubuntu-lxc) -- 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/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in lxd package in Ubuntu: Won't Fix Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Triaged Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1914062/+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 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
This is a systemd/udev bug. We're aware of the CONTAINER_INTERFACE and it being wrong doesn't mean we need to change LXD to make it similarly wrong. LXD containers need to have udevd running to function properly, so you'll need to undo that change. If there is a bug in how udevd now behaves, that's what needs to be fixed and we can assist you with that. ** Changed in: lxd (Ubuntu) Status: New => Won't Fix -- 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/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in lxd package in Ubuntu: Won't Fix Status in network-manager package in Ubuntu: New Status in systemd package in Ubuntu: Triaged Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1914062/+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 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
Making /sys read-only will break very very many things that we have no intention of breaking. LXD is also completely init system agnostic and we have no idea what the init system in a particular container may be. ** Changed in: lxd (Ubuntu) Status: New => Invalid -- 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/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in lxd package in Ubuntu: Invalid Status in network-manager package in Ubuntu: New Status in systemd package in Ubuntu: Triaged Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1914062/+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 1915091] Re: Nautilus shows LXD storage pool in sidebar
Ok, so the mount table output confirms that your LXD default storage pool isn't visible in the host's mount table, so that's not what's triggering nautilus. Also, if that was the case, I'd have seen it on my own machine a long time ago ;) My best guess is that it's the loop device (also called default.img) which nautilus is incorrectly showing as some kind of external block device (like a USB stick or SD card). You'll most likely see it in `losetup -a` and it may show up in some `/dev/disk/` sub-directories which I supposed nautilus or something in the gnome desktop is monitoring. Unfortunately unlike actual mount entries that we can hide in a different mount namespace or pass custom mount flags to have the desktop ignore, the same can't be done with block devices, so re-assigning this to nautilus for further investigation. ** Package changed: lxc (Ubuntu) => nautilus (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1915091 Title: Nautilus shows LXD storage pool in sidebar Status in nautilus package in Ubuntu: Incomplete Bug description: I recently set up LXD 4.11 on Ubuntu 20.04 with a file-backed btrfs storage pool called "default". Now Nautilus shows a "default" device in the sidebar despite the loop device not being intended for users to directly interact with. System: Ubuntu 20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1915091/+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 1870354] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_text_align() from _st_set_text_from_style() from st_label_style_changed()
https://github.com/gTile/gTile/issues/124 ** Bug watch added: github.com/gTile/gTile/issues #124 https://github.com/gTile/gTile/issues/124 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1870354 Title: gnome-shell crashed with SIGSEGV in st_theme_node_get_text_align() from _st_set_text_from_style() from st_label_style_changed() Status in gnome-shell package in Ubuntu: Invalid Bug description: https://errors.ubuntu.com/problem/6289ea5c593afc5b43d7c38e671ae741c8f66fcf --- Seems to be happening when docking/undocking or when locking the screen. Ignore the LD_LIBRARY_PATH bit, it's just dqlite/raft dev libraries for LXD, doesn't affect desktop. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 09:37:12 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell LocalLibraries: /home/stgraber/data/code/go/deps/sqlite/.libs/libsqlite3.so.0.8.6 ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SegvAnalysis: Segfault happened at: 0x7f4da0ee6de9 : repz cmpsb %es:(%rdi),%ds:(%rsi) PC (0x7f4da0ee6de9) ok source "%es:(%rdi)" (0x7f4da0f17934) ok destination "%ds:(%rsi)" (0xe9f78948fa1e0ff3) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: st_theme_node_get_text_align () at /usr/lib/gnome-shell/libst-1.0.so _st_set_text_from_style () at /usr/lib/gnome-shell/libst-1.0.so () at /usr/lib/gnome-shell/libst-1.0.so () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in st_theme_node_get_text_align() UpgradeStatus: Upgraded to focal on 2018-12-17 (472 days ago) UserGroups: adm dialout kvm libvirt lp lpadmin lxd plugdev sbuild scanner sudo video separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870354/+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 1870354] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_text_align() from _st_set_text_from_style() from st_label_style_changed()
Tracked it down to gTile being the issue actually, disabling that one with the rest of them on seems to fix it. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1870354 Title: gnome-shell crashed with SIGSEGV in st_theme_node_get_text_align() from _st_set_text_from_style() from st_label_style_changed() Status in gnome-shell package in Ubuntu: Invalid Bug description: https://errors.ubuntu.com/problem/6289ea5c593afc5b43d7c38e671ae741c8f66fcf --- Seems to be happening when docking/undocking or when locking the screen. Ignore the LD_LIBRARY_PATH bit, it's just dqlite/raft dev libraries for LXD, doesn't affect desktop. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 09:37:12 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell LocalLibraries: /home/stgraber/data/code/go/deps/sqlite/.libs/libsqlite3.so.0.8.6 ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SegvAnalysis: Segfault happened at: 0x7f4da0ee6de9 : repz cmpsb %es:(%rdi),%ds:(%rsi) PC (0x7f4da0ee6de9) ok source "%es:(%rdi)" (0x7f4da0f17934) ok destination "%ds:(%rsi)" (0xe9f78948fa1e0ff3) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: st_theme_node_get_text_align () at /usr/lib/gnome-shell/libst-1.0.so _st_set_text_from_style () at /usr/lib/gnome-shell/libst-1.0.so () at /usr/lib/gnome-shell/libst-1.0.so () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in st_theme_node_get_text_align() UpgradeStatus: Upgraded to focal on 2018-12-17 (472 days ago) UserGroups: adm dialout kvm libvirt lp lpadmin lxd plugdev sbuild scanner sudo video separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870354/+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 1519228] Re: Drop obsolete dh_installinit --upstart-only option
** Changed in: lxc (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1519228 Title: Drop obsolete dh_installinit --upstart-only option Status in avahi package in Ubuntu: Fix Released Status in console-setup package in Ubuntu: Fix Released Status in cups package in Ubuntu: Fix Released Status in dcbd package in Ubuntu: Fix Released Status in debhelper package in Ubuntu: Fix Released Status in hostname package in Ubuntu: Fix Released Status in lxc package in Ubuntu: Fix Released Status in nfs-utils package in Ubuntu: Fix Released Status in nis package in Ubuntu: Fix Released Status in rfkill package in Ubuntu: Fix Released Status in xdiagnose package in Ubuntu: Fix Released Bug description: dh_installinit's --upstart-only option has been a deprecated no-op for a long time. Drop the remaining usage of it in packages so that we can get rid of this delta. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1519228/+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 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default
Hello Markus, or anyone else affected, Accepted console-setup into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/console- setup/1.178ubuntu2.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags removed: verification-failed verification-failed-bionic ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1762952 Title: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default Status in console-setup package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Invalid Status in console-setup source package in Bionic: Fix Committed Status in gnome-control-center source package in Bionic: Invalid Bug description: [Impact] The keyboard-configuration package provides a tool for configuring the keyboard via /etc/default/keyboard. However, there are desktop GUIs which provide such tools as well, and in the case of gnome-control- center it has another idea of what /etc/default/keyboard should contain. In short: The different tools don't play well together. The proposed upload does not claim to fix all issues with this incompatibility. But one of the annoyances is that a pure upgrade of the keyboard-configuration package may result in a changed keyboard configuration without the user asking for it. The proposed upload does address that particular issue on desktop systems. [Test Case] 1. On an Ubuntu 18.04 system, make sure that the contents of /etc/default/keyboard is 'the g-c-c style', for instance: XKBLAYOUT=se,us BACKSPACE=guess XKBVARIANT=, 2. Reboot. 3. Upgrade to the version of the keyboard-configuration package in bionic-proposed. => Find that /etc/default/keyboard was not changed through the upgrade. 4. Run the command sudo dpkg-reconfigure keyboard-configuration => Find that you are now offered to change your keyboard configuration. [Regression Potential] As a result of this upload, and unlike before, no keyboard configuration will happen behind the scenes on a desktop system due to an upgrade of the keyboard-configuration package. This is the desired change, and I can't think of a case when a user would want the configuration to be changed without having asked for it. [Original description] Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in 18.04 Steps to reproduce: 1. Define two keyboard input methods in Settings -> Region & Language -> Input Sources 2. Open several applications 3. Observe that application windows can be iterated with Alt + Tab 4. Once application window iteration was begun with Alt + Tab, try to iterate backwards with Alt + Shift + Tab. 5. Try to change keyboard input method switching hotkeys in Settings -> Region & Language -> Input Sources -> Options. 6. Observe that Keyboard shortcut for "Alternative switch to next source" is set to "Alt + Shift" and that keyboard shortcuts can only be changed in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. 7. Observe that the shortcut for "Alternative switch to next source" is not available for configuration in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Actual state: * Performing step 4 does not select the previous app in application switcher but instead changes keyboard input method. Expected state: * The shortcut for "Alternative switch to next source" can be changed and / or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Notes: * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to next source" did not exist in that version of Gnome Shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default
** Changed in: console-setup (Ubuntu Bionic) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1762952 Title: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default Status in console-setup package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Invalid Status in console-setup source package in Bionic: Fix Committed Status in gnome-control-center source package in Bionic: Invalid Bug description: [Impact] The keyboard-configuration package provides a tool for configuring the keyboard via /etc/default/keyboard. However, there are desktop GUIs which provide such tools as well, and in the case of gnome-control- center it has another idea of what /etc/default/keyboard should contain. In short: The different tools don't play well together. The proposed upload does not claim to fix all issues with this incompatibility. But one of the annoyances is that a pure upgrade of the keyboard-configuration package may result in a changed keyboard configuration without the user asking for it. The proposed upload does address that particular issue on desktop systems. [Test Case] 1. On an Ubuntu 18.04 system, make sure that the contents of /etc/default/keyboard is 'the g-c-c style', for instance: XKBLAYOUT=se,us BACKSPACE=guess XKBVARIANT=, 2. Reboot. 3. Upgrade to the version of the keyboard-configuration package in bionic-proposed. => Find that /etc/default/keyboard was not changed through the upgrade. 4. Run the command sudo dpkg-reconfigure keyboard-configuration => Find that you are now offered to change your keyboard configuration. [Regression Potential] As a result of this upload, and unlike before, no keyboard configuration will happen behind the scenes on a desktop system due to an upgrade of the keyboard-configuration package. This is the desired change, and I can't think of a case when a user would want the configuration to be changed without having asked for it. [Original description] Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in 18.04 Steps to reproduce: 1. Define two keyboard input methods in Settings -> Region & Language -> Input Sources 2. Open several applications 3. Observe that application windows can be iterated with Alt + Tab 4. Once application window iteration was begun with Alt + Tab, try to iterate backwards with Alt + Shift + Tab. 5. Try to change keyboard input method switching hotkeys in Settings -> Region & Language -> Input Sources -> Options. 6. Observe that Keyboard shortcut for "Alternative switch to next source" is set to "Alt + Shift" and that keyboard shortcuts can only be changed in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. 7. Observe that the shortcut for "Alternative switch to next source" is not available for configuration in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Actual state: * Performing step 4 does not select the previous app in application switcher but instead changes keyboard input method. Expected state: * The shortcut for "Alternative switch to next source" can be changed and / or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Notes: * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to next source" did not exist in that version of Gnome Shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+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 1666264] Re: FFe: Update gnome-terminal to 3.24 and vte to 0.48
I'm not seeing a compelling reason to switch to 3.24 and the newer vte other than the version bump. If your argument is that after this revert, both gnome-terminal and vte are effectively identical feature-wise as what we have in the archive right now, then you're not introducing or removing features, in which case you don't need a Feature Freeze Exception in the first place. If this change does introduce/remove features to gnome-terminal and vte, please list them in a readable format (not an upstream git log/diff). I think the pcre2 MIR could do with an API diff between pcre3 and pcre2. Your massive patch suggests that the two APIs are very much different and that it's not something we can do as a typical transition, making the need for both of them to live in main together much clearer. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1666264 Title: FFe: Update gnome-terminal to 3.24 and vte to 0.48 Status in gnome-terminal package in Ubuntu: New Status in vte2.91 package in Ubuntu: New Bug description: gnome-terminal and vte are still at their 3.20 (and 0.44) versions because they now hard-depend on pcre2, but the pcre2 MIR (LP: #163) has stalled because there is already one version of pcre in main and it would be a major task to convert all of main to use pcre2. So I reverted 3 commits for gnome-terminal and 5 for vte to make that MIR less urgent. I am concerned about the long-term maintainability of this approach - the vte patch is over 1600 lines. gnome-terminal 3.22 and vte 0.46 have been tested in the GNOME3 Staging PPA for yakkety and zesty for months. I am not aware of any issues from that. This is slightly different since I haven't tested those versions without pcre2 until this weekend. The development cycle for gnome-terminal and vte has been fairly quiet so I believe it's safe to go ahead and update gnome-terminal to 3.23.90 and vte to 0.47.90. https://git.gnome.org/browse/gnome-terminal/log https://git.gnome.org/browse/vte/log The packages are currently available for testing at https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1666264/+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 1647066] [NEW] Systems with systemd-resolved disabled and dns=default in NetworkManager.conf no longer get DNS
Public bug reported: Since the last Network Manager upload my systems get a completely empty /etc/resolv.conf when they'd before have a directly managed file by NetworkManager. I have dns=default set in NetworkManager.conf which tells NetworkManager to directly manage that file. But that's now apparently ignored. I managed to workaround the issue by turning /etc/resolv.conf into a static file (as opposed to a symlink to the resolvconf path) but that shouldn't be necessary at all. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1647066 Title: Systems with systemd-resolved disabled and dns=default in NetworkManager.conf no longer get DNS Status in network-manager package in Ubuntu: New Bug description: Since the last Network Manager upload my systems get a completely empty /etc/resolv.conf when they'd before have a directly managed file by NetworkManager. I have dns=default set in NetworkManager.conf which tells NetworkManager to directly manage that file. But that's now apparently ignored. I managed to workaround the issue by turning /etc/resolv.conf into a static file (as opposed to a symlink to the resolvconf path) but that shouldn't be necessary at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1647066/+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 1620313] Re: stop using hardening-wrapper, obsoleted by recent dpkg-dev
Re-opening LXC task as it wasn't fixed, the fix was reverted as it was causing an FTBFS. ** Changed in: lxc (Ubuntu) Status: Fix Released => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/1620313 Title: stop using hardening-wrapper, obsoleted by recent dpkg-dev Status in firefox package in Ubuntu: In Progress Status in gtk2-engines-murrine package in Ubuntu: Fix Released Status in lxc package in Ubuntu: Triaged Status in pidgin package in Ubuntu: New Status in proftpd-dfsg package in Ubuntu: New Status in thunderbird package in Ubuntu: New Status in ubuntu-push-qml package in Ubuntu: New Status in unity-control-center package in Ubuntu: Fix Released Status in hardening-wrapper package in Debian: Fix Released Bug description: stop using hardening-wrapper, obsoleted by recent dpkg-dev. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1620313/+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 1620313] Re: stop using hardening-wrapper, obsoleted by recent dpkg-dev
How far back is this supported? LXC is automatically backported all the way back to trusty without any change to the packaging being required right now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk2-engines-murrine in Ubuntu. https://bugs.launchpad.net/bugs/1620313 Title: stop using hardening-wrapper, obsoleted by recent dpkg-dev Status in firefox package in Ubuntu: New Status in gtk2-engines-murrine package in Ubuntu: Fix Released Status in lxc package in Ubuntu: New Status in unity-control-center package in Ubuntu: New Status in hardening-wrapper package in Debian: New Bug description: stop using hardening-wrapper, obsoleted by recent dpkg-dev. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1620313/+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 1603898] Re: DNS resolution fails when using VPN and routing all traffic over it
So I just ran into the exact same problem with my personal VPN when I do have both IPv4 and IPv6 configured to route all traffic over the VPN. -- 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/1603898 Title: DNS resolution fails when using VPN and routing all traffic over it Status in network-manager package in Ubuntu: New Status in network-manager source package in Xenial: New Bug description: When using our company VPN, the Network Manager configured dnsmasq ends up in a weird state where its unable to answer queries because it's (incorrectly) sending them to 127.0.0.1:53 where nothing is listening. | root@ornery:~# nmcli con show 'Canonical UK - All Traffic' | grep -i dns | ipv4.dns: | ipv4.dns-search: | ipv4.dns-options: (default) | ipv4.ignore-auto-dns: no | ipv6.dns: | ipv6.dns-search: | ipv6.dns-options: (default) | ipv6.ignore-auto-dns: no | IP4.DNS[1]: 10.172.192.1 | root@ornery:~# ps auxfw | grep [4]035 | nobody4035 0.0 0.0 52872 1620 ?SJun29 6:39 \_ /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 --cache-size=0 --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq --conf-dir=/etc/NetworkManager/dnsmasq.d | root@ornery:~# Querying the DNS server provided by the VPN connection works; querying dnsmasq doesn't: | root@ornery:~# dig +short @10.172.192.1 www.openbsd.org | 129.128.5.194 | root@ornery:~# dig @127.0.1.1 www.openbsd.org | | ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @127.0.1.1 www.openbsd.org | ; (1 server found) | ;; global options: +cmd | ;; Got answer: | ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 6996 | ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 | | ;; QUESTION SECTION: | ;www.openbsd.org. IN A | | ;; Query time: 0 msec | ;; SERVER: 127.0.1.1#53(127.0.1.1) | ;; WHEN: Mon Jul 18 10:25:48 CEST 2016 | ;; MSG SIZE rcvd: 33 | | root@ornery:~# While running 'dig @127.0.1.1 www.openbsd.org': | root@ornery:~# tcpdump -i lo port 53 -v -n | tcpdump: listening on lo, link-type EN10MB (Ethernet), capture size 262144 bytes | 10:26:04.728905 IP (tos 0x0, ttl 64, id 56577, offset 0, flags [none], proto UDP (17), length 72) | 127.0.0.1.54917 > 127.0.1.1.53: 32273+ [1au] A? www.openbsd.org. (44) | 10:26:04.729001 IP (tos 0x0, ttl 64, id 49204, offset 0, flags [DF], proto UDP (17), length 61) | 127.0.1.1.53 > 127.0.0.1.54917: 32273 Refused$ 0/0/0 (33) | root@ornery:~# netstat -anp | grep 127.0.[01].1:53 | tcp0 0 127.0.1.1:530.0.0.0:* LISTEN 4035/dnsmasq | udp0 0 127.0.1.1:530.0.0.0:* 4035/dnsmasq | root@ornery:~# You can see below a) that dnsmasq thinks it is configured to use a DNS server provided by the VPN, and/but that b) it tries to answer a non local query like www.openbsd.org locally. | root@ornery:~# kill -USR1 4035; tail /var/log/syslog | grep dnsmasq | Jul 18 09:29:22 ornery dnsmasq[4035]: time 1468830562 | Jul 18 09:29:22 ornery dnsmasq[4035]: cache size 0, 0/0 cache insertions re-used unexpired cache entries. | Jul 18 09:29:22 ornery dnsmasq[4035]: queries forwarded 1880976, queries answered locally 375041 | Jul 18 09:29:22 ornery dnsmasq[4035]: queries for authoritative zones 0 | Jul 18 09:29:22 ornery dnsmasq[4035]: server 10.172.192.1#53: queries sent 792, retried or failed 0 | root@ornery:~# dig +short @127.0.1.1 www.openbsd.org | root@ornery:~# kill -USR1 4035; tail /var/log/syslog | grep dnsmasq | Jul 18 09:29:22 ornery dnsmasq[4035]: queries for authoritative zones 0 | Jul 18 09:29:22 ornery dnsmasq[4035]: server 10.172.192.1#53: queries sent 792, retried or failed 0 | Jul 18 09:29:37 ornery dnsmasq[4035]: time 1468830577 | Jul 18 09:29:37 ornery dnsmasq[4035]: cache size 0, 0/0 cache insertions re-used unexpired cache entries. | Jul 18 09:29:37 ornery dnsmasq[4035]: queries forwarded 1880976, queries answered locally 375042 | Jul 18 09:29:37 ornery dnsmasq[4035]: queries for authoritative zones 0 | Jul 18 09:29:37 ornery dnsmasq[4035]: server 10.172.192.1#53: queries sent 792, retried or failed 0 | root@ornery:~# This is on Ubuntu 16.04, with the following packages: | james@ornery:~$ COLUMNS=200 dpkg -l dnsmasq-base network-manager network-manager-openvpn | grep ^ii | ii dnsmasq-base 2.75-1ubuntu0.16.04.1 amd64 Small caching DNS proxy and DHCP/TFTP server | ii network-manager
[Desktop-packages] [Bug 1603898] Re: DNS resolution fails when using VPN and routing all traffic over it
Could you include what gets written to your syslog while the VPN connection is established? SIGUSR1 to dnsmasq tells you what server it's talking to, but unfortunately not for what domain... Based on your described symptoms, I'm suspecting that the openvpn plugin told NM to configure dnsmasq only for the domains pushed by the VPN server rather than for all domains (as it should when you route everything over the VPN). If that's what happened, you should see log lines like: Jul 18 22:14:06 castiana dnsmasq[9394]: using nameserver 172.16.20.30#53 for domain stgraber.net Jul 18 22:14:06 castiana dnsmasq[9394]: using nameserver 172.16.20.30#53 for domain 16.172.in-addr.arpa Jul 18 22:14:06 castiana dnsmasq[9394]: using nameserver 172.16.20.30#53 for domain 17.172.in-addr.arpa Jul 18 22:14:06 castiana dnsmasq[9394]: using nameserver 172.16.20.30#53 for domain 18.172.in-addr.arpa Jul 18 22:14:06 castiana dnsmasq[9394]: using nameserver 172.16.20.30#53 for domain 19.172.in-addr.arpa Jul 18 22:14:06 castiana dnsmasq[9394]: using nameserver 172.16.20.30#53 for domain 22.172.in-addr.arpa Jul 18 22:14:06 castiana dnsmasq[9394]: using nameserver 172.16.20.30#53 for domain 56.149.in-addr.arpa Jul 18 22:14:06 castiana dnsmasq[9394]: using nameserver 172.16.20.31#53 for domain stgraber.net Jul 18 22:14:06 castiana dnsmasq[9394]: using nameserver 172.16.20.31#53 for domain 16.172.in-addr.arpa Jul 18 22:14:06 castiana dnsmasq[9394]: using nameserver 172.16.20.31#53 for domain 17.172.in-addr.arpa Jul 18 22:14:06 castiana dnsmasq[9394]: using nameserver 172.16.20.31#53 for domain 18.172.in-addr.arpa Jul 18 22:14:06 castiana dnsmasq[9394]: using nameserver 172.16.20.31#53 for domain 19.172.in-addr.arpa Jul 18 22:14:06 castiana dnsmasq[9394]: using nameserver 172.16.20.31#53 for domain 22.172.in-addr.arpa Jul 18 22:14:06 castiana dnsmasq[9394]: using nameserver 172.16.20.31#53 for domain 56.149.in-addr.arpa And resolution of any of record that's part of one of those domains would succeed. -- 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/1603898 Title: DNS resolution fails when using VPN and routing all traffic over it Status in network-manager package in Ubuntu: New Bug description: When using our company VPN, the Network Manager configured dnsmasq ends up in a weird state where its unable to answer queries because it's (incorrectly) sending them to 127.0.0.1:53 where nothing is listening. | root@ornery:~# nmcli con show 'Canonical UK - All Traffic' | grep -i dns | ipv4.dns: | ipv4.dns-search: | ipv4.dns-options: (default) | ipv4.ignore-auto-dns: no | ipv6.dns: | ipv6.dns-search: | ipv6.dns-options: (default) | ipv6.ignore-auto-dns: no | IP4.DNS[1]: 10.172.192.1 | root@ornery:~# ps auxfw | grep [4]035 | nobody4035 0.0 0.0 52872 1620 ?SJun29 6:39 \_ /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 --cache-size=0 --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq --conf-dir=/etc/NetworkManager/dnsmasq.d | root@ornery:~# Querying the DNS server provided by the VPN connection works; querying dnsmasq doesn't: | root@ornery:~# dig +short @10.172.192.1 www.openbsd.org | 129.128.5.194 | root@ornery:~# dig @127.0.1.1 www.openbsd.org | | ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @127.0.1.1 www.openbsd.org | ; (1 server found) | ;; global options: +cmd | ;; Got answer: | ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 6996 | ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 | | ;; QUESTION SECTION: | ;www.openbsd.org. IN A | | ;; Query time: 0 msec | ;; SERVER: 127.0.1.1#53(127.0.1.1) | ;; WHEN: Mon Jul 18 10:25:48 CEST 2016 | ;; MSG SIZE rcvd: 33 | | root@ornery:~# While running 'dig @127.0.1.1 www.openbsd.org': | root@ornery:~# tcpdump -i lo port 53 -v -n | tcpdump: listening on lo, link-type EN10MB (Ethernet), capture size 262144 bytes | 10:26:04.728905 IP (tos 0x0, ttl 64, id 56577, offset 0, flags [none], proto UDP (17), length 72) | 127.0.0.1.54917 > 127.0.1.1.53: 32273+ [1au] A? www.openbsd.org. (44) | 10:26:04.729001 IP (tos 0x0, ttl 64, id 49204, offset 0, flags [DF], proto UDP (17), length 61) | 127.0.1.1.53 > 127.0.0.1.54917: 32273 Refused$ 0/0/0 (33) | root@ornery:~# netstat -anp | grep 127.0.[01].1:53 | tcp0 0 127.0.1.1:530.0.0.0:* LISTEN 4035/dnsmasq | udp0 0 127.0.1.1:530.0.0.0:* 4035/dnsmasq | root@ornery:~# You can see below a) that dnsmasq thinks it is
[Desktop-packages] [Bug 1552424] Re: [FFE] NetworkManager 1.2-beta
Okay, lets do this then. FFe granted. Given how critical NM is, I expect you to be taking a very very close look at any bug reports and IRC chatter following this change and very quickly upload fixes as needed until release time so the final delta between what we ship at release time and final 1.2 is minimal. ** Changed in: network-manager (Ubuntu) Status: Confirmed => Triaged ** Changed in: network-manager-applet (Ubuntu) Status: Confirmed => Triaged ** Changed in: network-manager-iodine (Ubuntu) Status: Confirmed => Triaged ** Changed in: network-manager-openconnect (Ubuntu) Status: Confirmed => Triaged ** Changed in: network-manager-openvpn (Ubuntu) Status: Confirmed => Triaged ** Changed in: network-manager-pptp (Ubuntu) Status: Confirmed => Triaged ** Changed in: network-manager-vpnc (Ubuntu) Status: Confirmed => Triaged -- 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/1552424 Title: [FFE] NetworkManager 1.2-beta Status in network-manager package in Ubuntu: Triaged Status in network-manager-applet package in Ubuntu: Triaged Status in network-manager-iodine package in Ubuntu: Triaged Status in network-manager-openconnect package in Ubuntu: Triaged Status in network-manager-openvpn package in Ubuntu: Triaged Status in network-manager-pptp package in Ubuntu: Triaged Status in network-manager-vpnc package in Ubuntu: Triaged Bug description: We really should update NetworkManager to 1.2 (or some other updated stable release) for the LTS, this will allow us to better deal with any bugs that might come up post-release. This new release will also much improve interop with LXC, which has recently been an issue. Other FFEs will be opened for NM VPN plugins and for NetworkManager- applet. NetworkManager-1.2 Overview of changes since NetworkManager-1.0 This is a new stable release of NetworkManager. Notable changes include: * Added an option to enable use of random MAC addresses for Wi-Fi access point scanning (defaults to disabled). Controlled with 'wifi.mac-address-randomization' property (MAC_ADDRESS_RANDOMIZATION key in ifcfg files). * Wi-Fi scanning now utilizes wpa_supplicant's AP list. * Added support for Wi-Fi powersave, configured with POWERSAVE key in ifcfg files. * Added support for creation of more types of software devices: tun & tap, macvlan, vxlan and ip tunnels (ipip, gre, sit, ip6ip6 and ipip6). * The software devices (bond, bridge, vlan, team, ...) can now be stacked arbitrarily. The nmcli interface for creating master-slave relationships has been significantly improved by the use of 'master' argument to all link types. * RFC7217 stable privacy addressing is now used by default to protect from address-based host tracking. The IPv6 addressing mode is configured with IPV6_ADDR_GEN_MODE key in ifcfg files. * Improved route management code to avoid clashes between conflicting routes in multiple connections. * Refactored platform code resulting in more robust interface to platform, less overhead and reduced memory footprint. * Improved interoperability with other network management tools. The externally created software devices are not managed until they're activated. * The Device instances now exist for all software connections and the platform devices are now only created when the device is activated. This makes it possible for connections with device of same name not to clash unless they're activated concurrently. The links are now not unnecessarily present unless the connection is active, avoiding pollution of the link namespace. * NetworkManager now correctly manages connectivity in namespace-based containers such as LXC and Docker. * Support for configuring ethernet Wake-On-Lan has been added. * Added LLDP listener functionality and related CLI client commands. Enabled via LLDP option in ifcfg files. * CLI secret agent has been extended with support for VPN secrets. * The command line client now utilizes colors for its output. * The command line client now sorts the devices and properties for better clarity. * Numerous improvements to Bash command completion for nmcli. * NetworkManager relies on less external libraries. The use of dbus-glib has been replaced with gio's native D-Bus support and libnl-route is no longer used. * Dependency on avahi-autoipd has been dropped. Native IPv4 link-local addressing configuration based on systemd network library is now used instead. * Hostname is now managed via systemd-hostnamed on systemd-based systems. * Management of resolv.conf
[Desktop-packages] [Bug 1552424] Re: [FFE] NetworkManager 1.2-beta
Is Network Manager 1.2 out yet? I don't seem to remember seeing an announcement. If not, when is it expected to be out? Also, can you comment on our existing delta (phone & others) and give some more details on how those will be updated and tested? Overall, I absolutely support us moving to 1.2, it does fix a lot of pain points that I've encountered in the past and I'm sure it would greatly benefit our users. But we need to make sure landing this won't cause regressions and that we'll ship with a properly supported NM by release time. -- 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/1552424 Title: [FFE] NetworkManager 1.2-beta Status in network-manager package in Ubuntu: New Bug description: We really should update NetworkManager to 1.2 (or some other updated stable release) for the LTS, this will allow us to better deal with any bugs that might come up post-release. This new release will also much improve interop with LXC, which has recently been an issue. Other FFEs will be opened for NM VPN plugins and for NetworkManager- applet. NetworkManager-1.2 Overview of changes since NetworkManager-1.0 This is a new stable release of NetworkManager. Notable changes include: * Added an option to enable use of random MAC addresses for Wi-Fi access point scanning (defaults to disabled). Controlled with 'wifi.mac-address-randomization' property (MAC_ADDRESS_RANDOMIZATION key in ifcfg files). * Wi-Fi scanning now utilizes wpa_supplicant's AP list. * Added support for Wi-Fi powersave, configured with POWERSAVE key in ifcfg files. * Added support for creation of more types of software devices: tun & tap, macvlan, vxlan and ip tunnels (ipip, gre, sit, ip6ip6 and ipip6). * The software devices (bond, bridge, vlan, team, ...) can now be stacked arbitrarily. The nmcli interface for creating master-slave relationships has been significantly improved by the use of 'master' argument to all link types. * RFC7217 stable privacy addressing is now used by default to protect from address-based host tracking. The IPv6 addressing mode is configured with IPV6_ADDR_GEN_MODE key in ifcfg files. * Improved route management code to avoid clashes between conflicting routes in multiple connections. * Refactored platform code resulting in more robust interface to platform, less overhead and reduced memory footprint. * Improved interoperability with other network management tools. The externally created software devices are not managed until they're activated. * The Device instances now exist for all software connections and the platform devices are now only created when the device is activated. This makes it possible for connections with device of same name not to clash unless they're activated concurrently. The links are now not unnecessarily present unless the connection is active, avoiding pollution of the link namespace. * NetworkManager now correctly manages connectivity in namespace-based containers such as LXC and Docker. * Support for configuring ethernet Wake-On-Lan has been added. * Added LLDP listener functionality and related CLI client commands. Enabled via LLDP option in ifcfg files. * CLI secret agent has been extended with support for VPN secrets. * The command line client now utilizes colors for its output. * The command line client now sorts the devices and properties for better clarity. * Numerous improvements to Bash command completion for nmcli. * NetworkManager relies on less external libraries. The use of dbus-glib has been replaced with gio's native D-Bus support and libnl-route is no longer used. * Dependency on avahi-autoipd has been dropped. Native IPv4 link-local addressing configuration based on systemd network library is now used instead. * Hostname is now managed via systemd-hostnamed on systemd-based systems. * Management of resolv.conf management can be changed at runtime, private resolv.conf is always written in /run. * NetworkManager can now write DNS options to resolv.conf. * Updated version of systemd network library used for internal DHCP and IPv4 link-local support. * Support for event logging via audit subsystem has been added. * Support for native logging via systemd-journald has been added taking advantage of its structured logging. * Live reconfiguration of IP configuration after changing the settings without reactivation of the device with "nmcli device reapply" command and via D-Bus API. * The API for VPN plugins now supports multiple simultaneous connections. Most popular VPN plugins have
[Desktop-packages] [Bug 1546232] Re: Applet doesn't update after adding a VPN
That's on current Xenial. -- 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/1546232 Title: Applet doesn't update after adding a VPN Status in network-manager package in Ubuntu: New Bug description: I just added a VPN and it doesn't show up in the list, had to restart network-manager for it to show up... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1546232/+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 1546232] [NEW] Applet doesn't update after adding a VPN
Public bug reported: I just added a VPN and it doesn't show up in the list, had to restart network-manager for it to show up... ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1546232 Title: Applet doesn't update after adding a VPN Status in network-manager package in Ubuntu: New Bug description: I just added a VPN and it doesn't show up in the list, had to restart network-manager for it to show up... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1546232/+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 1539634] Re: network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1
Hello Ryan, or anyone else affected, Accepted network-manager into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/network- manager/0.9.8.8-0ubuntu7.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: network-manager (Ubuntu Trusty) Status: Triaged => Fix Committed ** Tags added: verification-needed -- 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/1539634 Title: network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1 Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Trusty: Fix Committed Bug description: [Triage Notes] This regression is caused by a libnl proposed update tracked in bug 1511735. It has not been released as an update, only proposed as an update for early testing. If you volunteered to test proposed updates, then thank you. Your care and attention will stop this regression from hitting ordinary users, and we appreciate your contribution to Ubuntu. If you are not aware that you volunteered to test proposed updates, then please be aware that your system is configured to do so. In this case, you probably should turn this off. I'd appreciate if someone could explain how to do this in the comments. [Impact] * NetworkManager depends on libnl (libnl-3-200 libnl-genl-3-200 libnl-route-3-200) and when libnl is updated to proposed 3.2.21-1ubuntu1 NM segfaults due to libnl exposing a bug in NM validation packets. This affects the 0.98 release of NetworkManager and has already been fixed in newer releases. * Backporting fixes from upstream release is required to prevent NetworkManager from faulting which breaks networking on most Desktop releases. * All patches applied are already accepted upstream and newer Ubuntu releases are not affected. * Upgrading NetworkManager to 0.9.8.8-0ubuntu7.3 prior to updating libnl-3.2.21-1ubuntu1 is required to prevent NetworkManager crashing. [Test Case] * Reproduce crash test: 1. Download 14.04.03 Desktop iso, amd64 2. Launched in a VM, run from iso 3. In terminal, enable proposed 4. sudo apt-get install libnl-3-200 libnl-genl-3-200 libnl-route-3-200 5. sudo restart network-manager # note the nm-applet disappears as NM has now crashed, no network conn. 6. dmesg to confirm network-manager crash 7. sudo dpkg --install gir1.2-networkmanager-1.0_0.9.8.8-0ubuntu7.3_amd64.deb libnm-glib4_0.9.8.8-0ubuntu7.3_amd64.deb libnm-glib-vpn1_0.9.8.8-0ubuntu7.3_amd64.deb libnm-util2_0.9.8.8-0ubuntu7.3_amd64.deb network-manager_0.9.8.8-0ubuntu7.3_amd64.deb 8. sudo start network-manager # nm-applet reappears, network connectivity restored * Successful upgrade test: 1. Download 14.04.03 Desktop iso, amd64 2. Launched in a VM, run from iso 3. In a terminal, sudo dpkg --install gir1.2-networkmanager-1.0_0.9.8.8-0ubuntu7.3_amd64.deb libnm-glib4_0.9.8.8-0ubuntu7.3_amd64.deb libnm-glib-vpn1_0.9.8.8-0ubuntu7.3_amd64.deb libnm-util2_0.9.8.8-0ubuntu7.3_amd64.deb network-manager_0.9.8.8-0ubuntu7.3_amd64.deb 4. sudo restart network-manager # NM still runs, no crash, net up 5. enable trusty-proposed in /etc/apt/sources.list 6. sudo apt-get update 7. sudo apt-get install libnl-3-200 libnl-genl-3-200 libnl-route-3-200 8. sudo restart network-manager # NM still runs, no crash, net up. [Regression Potential] * NetworkManager is a highly visible package, so testing NetworkManager functionality is critical. The patch does address the crash specificly introduced by the updated libnl SRU. * We need to ensure that users have installed this NetworkManager update before installing libnl3 update (special phasing needed). [Original Description] Testing out proposed libnl-3 package[1] exposed a bug in NM 0.98. After installing updated libnl3 and restarting networkmanager, NM crashes with: /var/log/syslog shows: init: network-manager main process
[Desktop-packages] [Bug 1519228] Re: Drop obsolete dh_installinit --upstart-only option
Fix pushed to the lxc packaging branch. ** Changed in: lxc (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rfkill in Ubuntu. https://bugs.launchpad.net/bugs/1519228 Title: Drop obsolete dh_installinit --upstart-only option Status in avahi package in Ubuntu: Fix Released Status in console-setup package in Ubuntu: Fix Committed Status in cups package in Ubuntu: Fix Released Status in debhelper package in Ubuntu: In Progress Status in hostname package in Ubuntu: Fix Released Status in lxc package in Ubuntu: Fix Committed Status in nfs-utils package in Ubuntu: Fix Released Status in nis package in Ubuntu: Fix Committed Status in rfkill package in Ubuntu: Fix Released Status in xdiagnose package in Ubuntu: Fix Released Bug description: dh_installinit's --upstart-only option has been a deprecated no-op for a long time. Drop the remaining usage of it in packages so that we can get rid of this delta. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1519228/+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 1313550] Re: ping does not work as a normal user on trusty tarball cloud images.
** Changed in: lxc (Ubuntu Precise) Status: Confirmed => Won't Fix ** No longer affects: lxc (Ubuntu Precise) ** No longer affects: lxc (Ubuntu Saucy) ** Changed in: lxc (Ubuntu Trusty) Status: Confirmed => Triaged ** Changed in: lxc (Ubuntu) Status: Confirmed => Triaged ** Also affects: iputils (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: tar (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: lxc (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: maas (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: curtin (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: iputils (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: tar (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: lxc (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: maas (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: curtin (Ubuntu Vivid) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu Vivid) Importance: Undecided => High ** Changed in: lxc (Ubuntu Vivid) Status: New => Triaged ** Changed in: lxc (Ubuntu Wily) Importance: Undecided => High ** Changed in: lxc (Ubuntu Wily) Status: New => Triaged ** No longer affects: iputils (Ubuntu Vivid) ** No longer affects: iputils (Ubuntu Wily) ** No longer affects: curtin (Ubuntu Vivid) ** No longer affects: curtin (Ubuntu Wily) ** No longer affects: tar (Ubuntu Vivid) ** No longer affects: tar (Ubuntu Wily) -- 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/1313550 Title: ping does not work as a normal user on trusty tarball cloud images. Status in curtin: Fix Committed Status in MAAS: Fix Committed Status in curtin package in Ubuntu: Fix Released Status in iputils package in Ubuntu: Fix Released Status in lxc package in Ubuntu: Triaged Status in maas package in Ubuntu: Confirmed Status in tar package in Ubuntu: Fix Released Status in tar source package in Precise: Confirmed Status in maas source package in Saucy: Won't Fix Status in tar source package in Saucy: Won't Fix Status in curtin source package in Trusty: Fix Released Status in lxc source package in Trusty: Triaged Status in maas source package in Trusty: Confirmed Status in tar source package in Trusty: Fix Released Status in lxc source package in Vivid: Triaged Status in maas source package in Vivid: New Status in lxc source package in Wily: Triaged Status in maas source package in Wily: New Bug description: With trusty, /bin/ping relies on having extended attributes and kernel capabilities to gain the cap_net_raw+p capability. This allows removing the suid bit. However, the tarball cloud images do not preserve the extended attributes, and thus /bin/ping does not work on a system derived from them. Summary of problem per package: * lxc: ubuntu cloud template needs to extract * download template needs to extract with xattr flags * server side download creation tools need xattr flags * [unconfirmed] tarball caches need creation and extraction with xattr flags * tar: need the '--xattr' and '--acl' flags backported * maas: uec2roottgz needs to use xattr/acl flags * curtin: extraction needs to use xattr/acl flags. * cloud-image-build: needs to create -root.tar.gz with xattr/acl flags Related Bugs: * bug 1382632: horizon insecure key file permissions * bug 1386237: tar strange behavior with --acl and xattr * bug 1313550: ping broken (xattrs lost in tar extraction) To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1313550/+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 1068614] Re: weblive WebLiveEverythingServer.packages add ~100mb of memory
weblive is no more. ** Changed in: software-center (Ubuntu) Assignee: Stéphane Graber (stgraber) => (unassigned) ** Changed in: software-center (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/1068614 Title: weblive WebLiveEverythingServer.packages add ~100mb of memory Status in software-center package in Ubuntu: Won't Fix Bug description: With weblive I get 4x ~40k package from the server which results in ~100mb of additional memory being used. It seems like it would be good if the weblive server would actually only submit the available apps instead of all installed packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1068614/+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 777275] Re: Syncing from Debian should work with the next upload
** Changed in: rdesktop (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rdesktop in Ubuntu. https://bugs.launchpad.net/bugs/777275 Title: Syncing from Debian should work with the next upload Status in rdesktop package in Ubuntu: Fix Released Bug description: Binary package hint: rdesktop After I did the merge of rdesktop in Oneiric, I noticed that the only delta that Ubuntu still caries is an extra build-dep on "libsamplerate" to fix bug #231997. Debian apparently also has alsa support enabled and working but without that extra build-dep (only build=depending on libasound2-dev). So it'd be worth the try to sync from Debian next time and make sure rdesktop actually works as expected. Would be one less package to merge every cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rdesktop/+bug/777275/+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 1073669] Re: Bluetooth won't stay disabled after reboot due to early upstart job
** Changed in: rfkill (Ubuntu) Assignee: Stéphane Graber (stgraber) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rfkill in Ubuntu. https://bugs.launchpad.net/bugs/1073669 Title: Bluetooth won't stay disabled after reboot due to early upstart job Status in rfkill package in Ubuntu: Confirmed Bug description: Using a Dell XPS 13 with Ubuntu 12.04. In order to restore RF interfaces to their previous state between boots, rfkill is run via two Upstart jobs in /etc/init/: rfkill- store.conf (run while shutting down) and rfkill-restore.conf (run when starting up). However, while rfkill-restore.conf starts on the Upstart local-filesystems signal, there is a high probability that the RF kill switches in /sys/class/rfkill/ still won't yet be populated (i.e. every time on the Dell XPS 13). This results in behavior like the following: 1. Disable bluetooth via applet. 2. Reboot. 3. Login. 4. Observe bluetooth is re-enabled! Bluetooth should have stayed disabled, but since the kill switches weren't present when rfkill-restore was run, the kill switch states were not restored. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rfkill/+bug/1073669/+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 1512749] Re: lxcbr0 dissappears on Ubuntu 15.10
I have confirmed on both wily and xenial that the new network-manager does behave properly. After updating network-manager and restarting it (or rebooting as the updater recommends), installing lxd which then pulls lxc as a dependency does work reliably. I've also confirmed that wired connectivity as well as wireless connectivity appears unaffected by this fix, my laptop has been running the xenial version ever since Mathieu uploaded it and it's been working perfectly. I'm marking this verification-done and given the importance of the fix, will immediately release it to wily-updates. ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1512749 Title: lxcbr0 dissappears on Ubuntu 15.10 Status in lxc package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Fix Released Status in lxc source package in Wily: Invalid Status in network-manager source package in Wily: Fix Released Status in lxc source package in Xenial: Invalid Status in network-manager source package in Xenial: Fix Released Bug description: === SRU === Rationale: Network Manager in wily triggers on newly created interfaces and resets their network configuration even though it's not supposed to manage them at all. This breaks LXC and quite possibly libvirt as those provide bridges which are then completely unconfigured by Network Manager. Test case: 1) Update (or not) network-manager 2) Restart it 3) Install lxc 4) Check that lxcbr0 exists and has an IP configured Regression potential: The change to Network Manager is related to udev handling of new devices, even though normal operation on a regular desktop machine was tested, it's not impossible that this may regress handling of some devices. The fix was cherry-picked directly from upstream, so did go through code review and has been publicly available for a while. This fixes a significant regression compared to Ubuntu 15.04 and looks less risky than the alternative workaround which was uploaded earlier. === Original report === After initial upgrade from Ubuntu 15.04 to Ubuntu 15.10 LXC worked for a couple days then failed. I found that the lxcbr0 interface no longer existed. I reported this on the lxc-user alias and about the same time several others had this happen to them also. Serge Hallyn requested I open a launchpad bug and post some info but before I could gather that info the system returned to normal (re lxcbr0 was back) the next day after the server was booted up again. note: at least one other person had this happen to them also (lxcbr0 came back by itself). Today, I booted this server again and ... again lxcbr0 was missing where it had been working last night. Below is all of the Info Serge Hallyn asked me to post. $ ifconfig lxcbr0 lxcbr0: error fetching interface information: Device not found $ journalctl -u lxc-net -- Logs begin at Tue 2015-11-03 07:25:22 EST, end at Tue 2015-11-03 10:02:08 EST Nov 03 07:25:48 server3 systemd[1]: Starting LXC network bridge setup... Nov 03 07:25:50 server3 lxc-net[913]: dnsmasq: failed to create listening socket Nov 03 07:25:50 server3 lxc-net[913]: Failed to setup lxc-net. Nov 03 07:25:50 server3 systemd[1]: Started LXC network bridge setup. root@server3:/home/bmullan# /usr/lib/x86_64-linux-gnu/lxc/lxc-net stop # note - execution just returns to command line root@server3:/home/bmullan# >> and lxcbr0 is still missing # ifconfig lxcbr0 lxcbr0: error fetching interface information: Device not found root@server3:/home/bmullan# /usr/lib/x86_64-linux-gnu/lxc/lxc-net start dnsmasq: failed to create listening socket for 10.0.3.1: Cannot assign requested address Failed to setup lxc-net. root@server3:/home/bmullan# $ uname -a Linux server3 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID:Ubuntu Description:Ubuntu 15.10 Release:15.10 Codename:wily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1512749/+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 1512749] Update Released
The verification of the Stable Release Update for network-manager has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1512749 Title: lxcbr0 dissappears on Ubuntu 15.10 Status in lxc package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Fix Released Status in lxc source package in Wily: Invalid Status in network-manager source package in Wily: Fix Released Status in lxc source package in Xenial: Invalid Status in network-manager source package in Xenial: Fix Released Bug description: === SRU === Rationale: Network Manager in wily triggers on newly created interfaces and resets their network configuration even though it's not supposed to manage them at all. This breaks LXC and quite possibly libvirt as those provide bridges which are then completely unconfigured by Network Manager. Test case: 1) Update (or not) network-manager 2) Restart it 3) Install lxc 4) Check that lxcbr0 exists and has an IP configured Regression potential: The change to Network Manager is related to udev handling of new devices, even though normal operation on a regular desktop machine was tested, it's not impossible that this may regress handling of some devices. The fix was cherry-picked directly from upstream, so did go through code review and has been publicly available for a while. This fixes a significant regression compared to Ubuntu 15.04 and looks less risky than the alternative workaround which was uploaded earlier. === Original report === After initial upgrade from Ubuntu 15.04 to Ubuntu 15.10 LXC worked for a couple days then failed. I found that the lxcbr0 interface no longer existed. I reported this on the lxc-user alias and about the same time several others had this happen to them also. Serge Hallyn requested I open a launchpad bug and post some info but before I could gather that info the system returned to normal (re lxcbr0 was back) the next day after the server was booted up again. note: at least one other person had this happen to them also (lxcbr0 came back by itself). Today, I booted this server again and ... again lxcbr0 was missing where it had been working last night. Below is all of the Info Serge Hallyn asked me to post. $ ifconfig lxcbr0 lxcbr0: error fetching interface information: Device not found $ journalctl -u lxc-net -- Logs begin at Tue 2015-11-03 07:25:22 EST, end at Tue 2015-11-03 10:02:08 EST Nov 03 07:25:48 server3 systemd[1]: Starting LXC network bridge setup... Nov 03 07:25:50 server3 lxc-net[913]: dnsmasq: failed to create listening socket Nov 03 07:25:50 server3 lxc-net[913]: Failed to setup lxc-net. Nov 03 07:25:50 server3 systemd[1]: Started LXC network bridge setup. root@server3:/home/bmullan# /usr/lib/x86_64-linux-gnu/lxc/lxc-net stop # note - execution just returns to command line root@server3:/home/bmullan# >> and lxcbr0 is still missing # ifconfig lxcbr0 lxcbr0: error fetching interface information: Device not found root@server3:/home/bmullan# /usr/lib/x86_64-linux-gnu/lxc/lxc-net start dnsmasq: failed to create listening socket for 10.0.3.1: Cannot assign requested address Failed to setup lxc-net. root@server3:/home/bmullan# $ uname -a Linux server3 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID:Ubuntu Description:Ubuntu 15.10 Release:15.10 Codename:wily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1512749/+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 1512749] Re: lxcbr0 dissappears on Ubuntu 15.10
Tracking for lxc too as we'll be landing a workaround there for now. ** Also affects: lxc (Ubuntu) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu Wily) Status: New => Triaged ** Changed in: lxc (Ubuntu Xenial) Status: New => Triaged ** Changed in: lxc (Ubuntu Wily) Importance: Undecided => Critical ** Changed in: lxc (Ubuntu Xenial) Importance: Undecided => Critical -- 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/1512749 Title: lxcbr0 dissappears on Ubuntu 15.10 Status in lxc package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Triaged Status in lxc source package in Wily: Triaged Status in network-manager source package in Wily: Triaged Status in lxc source package in Xenial: Triaged Status in network-manager source package in Xenial: Triaged Bug description: After initial upgrade from Ubuntu 15.04 to Ubuntu 15.10 LXC worked for a couple days then failed. I found that the lxcbr0 interface no longer existed. I reported this on the lxc-user alias and about the same time several others had this happen to them also. Serge Hallyn requested I open a launchpad bug and post some info but before I could gather that info the system returned to normal (re lxcbr0 was back) the next day after the server was booted up again. note: at least one other person had this happen to them also (lxcbr0 came back by itself). Today, I booted this server again and ... again lxcbr0 was missing where it had been working last night. Below is all of the Info Serge Hallyn asked me to post. $ ifconfig lxcbr0 lxcbr0: error fetching interface information: Device not found $ journalctl -u lxc-net -- Logs begin at Tue 2015-11-03 07:25:22 EST, end at Tue 2015-11-03 10:02:08 EST Nov 03 07:25:48 server3 systemd[1]: Starting LXC network bridge setup... Nov 03 07:25:50 server3 lxc-net[913]: dnsmasq: failed to create listening socket Nov 03 07:25:50 server3 lxc-net[913]: Failed to setup lxc-net. Nov 03 07:25:50 server3 systemd[1]: Started LXC network bridge setup. root@server3:/home/bmullan# /usr/lib/x86_64-linux-gnu/lxc/lxc-net stop # note - execution just returns to command line root@server3:/home/bmullan# >> and lxcbr0 is still missing # ifconfig lxcbr0 lxcbr0: error fetching interface information: Device not found root@server3:/home/bmullan# /usr/lib/x86_64-linux-gnu/lxc/lxc-net start dnsmasq: failed to create listening socket for 10.0.3.1: Cannot assign requested address Failed to setup lxc-net. root@server3:/home/bmullan# $ uname -a Linux server3 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID:Ubuntu Description:Ubuntu 15.10 Release:15.10 Codename:wily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1512749/+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 1512749] Re: lxcbr0 dissappears on Ubuntu 15.10
simplest reproduce for NM: ip link add dev test type bridge && ip link set dev test up && ip addr add 1.2.3.4/24 dev test && sleep 2 && ifconfig test && ip link delete 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/1512749 Title: lxcbr0 dissappears on Ubuntu 15.10 Status in lxc package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Triaged Status in lxc source package in Wily: Triaged Status in network-manager source package in Wily: Triaged Status in lxc source package in Xenial: Triaged Status in network-manager source package in Xenial: Triaged Bug description: After initial upgrade from Ubuntu 15.04 to Ubuntu 15.10 LXC worked for a couple days then failed. I found that the lxcbr0 interface no longer existed. I reported this on the lxc-user alias and about the same time several others had this happen to them also. Serge Hallyn requested I open a launchpad bug and post some info but before I could gather that info the system returned to normal (re lxcbr0 was back) the next day after the server was booted up again. note: at least one other person had this happen to them also (lxcbr0 came back by itself). Today, I booted this server again and ... again lxcbr0 was missing where it had been working last night. Below is all of the Info Serge Hallyn asked me to post. $ ifconfig lxcbr0 lxcbr0: error fetching interface information: Device not found $ journalctl -u lxc-net -- Logs begin at Tue 2015-11-03 07:25:22 EST, end at Tue 2015-11-03 10:02:08 EST Nov 03 07:25:48 server3 systemd[1]: Starting LXC network bridge setup... Nov 03 07:25:50 server3 lxc-net[913]: dnsmasq: failed to create listening socket Nov 03 07:25:50 server3 lxc-net[913]: Failed to setup lxc-net. Nov 03 07:25:50 server3 systemd[1]: Started LXC network bridge setup. root@server3:/home/bmullan# /usr/lib/x86_64-linux-gnu/lxc/lxc-net stop # note - execution just returns to command line root@server3:/home/bmullan# >> and lxcbr0 is still missing # ifconfig lxcbr0 lxcbr0: error fetching interface information: Device not found root@server3:/home/bmullan# /usr/lib/x86_64-linux-gnu/lxc/lxc-net start dnsmasq: failed to create listening socket for 10.0.3.1: Cannot assign requested address Failed to setup lxc-net. root@server3:/home/bmullan# $ uname -a Linux server3 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID:Ubuntu Description:Ubuntu 15.10 Release:15.10 Codename:wily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1512749/+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 1512749] Re: lxcbr0 dissappears on Ubuntu 15.10
As this is currently breaking all lxc installs, therefore breaking JuJu, LXD and anything else that depends or installs LXC, I am going to fast track this SRU. Test plan before releasing is: - Test on a wired machine without LXC - Test on a wireless machine without LXC - Test on a wired machine with LXC - Test on a wireless machine with LXC ** Changed in: network-manager (Ubuntu Xenial) Status: Triaged => Fix Committed -- 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/1512749 Title: lxcbr0 dissappears on Ubuntu 15.10 Status in lxc package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Fix Committed Status in lxc source package in Wily: Invalid Status in network-manager source package in Wily: Fix Committed Status in lxc source package in Xenial: Invalid Status in network-manager source package in Xenial: Fix Committed Bug description: === SRU === Rationale: Network Manager in wily triggers on newly created interfaces and resets their network configuration even though it's not supposed to manage them at all. This breaks LXC and quite possibly libvirt as those provide bridges which are then completely unconfigured by Network Manager. Test case: 1) Update (or not) network-manager 2) Restart it 3) Install lxc 4) Check that lxcbr0 exists and has an IP configured Regression potential: The change to Network Manager is related to udev handling of new devices, even though normal operation on a regular desktop machine was tested, it's not impossible that this may regress handling of some devices. The fix was cherry-picked directly from upstream, so did go through code review and has been publicly available for a while. This fixes a significant regression compared to Ubuntu 15.04 and looks less risky than the alternative workaround which was uploaded earlier. === Original report === After initial upgrade from Ubuntu 15.04 to Ubuntu 15.10 LXC worked for a couple days then failed. I found that the lxcbr0 interface no longer existed. I reported this on the lxc-user alias and about the same time several others had this happen to them also. Serge Hallyn requested I open a launchpad bug and post some info but before I could gather that info the system returned to normal (re lxcbr0 was back) the next day after the server was booted up again. note: at least one other person had this happen to them also (lxcbr0 came back by itself). Today, I booted this server again and ... again lxcbr0 was missing where it had been working last night. Below is all of the Info Serge Hallyn asked me to post. $ ifconfig lxcbr0 lxcbr0: error fetching interface information: Device not found $ journalctl -u lxc-net -- Logs begin at Tue 2015-11-03 07:25:22 EST, end at Tue 2015-11-03 10:02:08 EST Nov 03 07:25:48 server3 systemd[1]: Starting LXC network bridge setup... Nov 03 07:25:50 server3 lxc-net[913]: dnsmasq: failed to create listening socket Nov 03 07:25:50 server3 lxc-net[913]: Failed to setup lxc-net. Nov 03 07:25:50 server3 systemd[1]: Started LXC network bridge setup. root@server3:/home/bmullan# /usr/lib/x86_64-linux-gnu/lxc/lxc-net stop # note - execution just returns to command line root@server3:/home/bmullan# >> and lxcbr0 is still missing # ifconfig lxcbr0 lxcbr0: error fetching interface information: Device not found root@server3:/home/bmullan# /usr/lib/x86_64-linux-gnu/lxc/lxc-net start dnsmasq: failed to create listening socket for 10.0.3.1: Cannot assign requested address Failed to setup lxc-net. root@server3:/home/bmullan# $ uname -a Linux server3 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID:Ubuntu Description:Ubuntu 15.10 Release:15.10 Codename:wily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1512749/+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 1512749] Re: lxcbr0 dissappears on Ubuntu 15.10
Confirmed that the new network-manager does fix the issue here. I've now uploaded a reverted lxc. ** Changed in: lxc (Ubuntu Wily) Status: Triaged => Invalid ** Changed in: lxc (Ubuntu Xenial) Status: Triaged => Invalid ** Description changed: - After initial upgrade from Ubuntu 15.04 to Ubuntu 15.10 LXC worked for a - couple days then failed. I found that the lxcbr0 interface no longer - existed. + === SRU === + Rationale: + Network Manager in wily triggers on newly created interfaces and resets their network configuration even though it's not supposed to manage them at all. + This breaks LXC and quite possibly libvirt as those provide bridges which are then completely unconfigured by Network Manager. + + Test case: + 1) Update (or not) network-manager + 2) Restart it + 3) Install lxc + 4) Check that lxcbr0 exists and has an IP configured + + Regression potential: + The change to Network Manager is related to udev handling of new devices, even though normal operation on a regular desktop machine was tested, it's not impossible that this may regress handling of some devices. + The fix was cherry-picked directly from upstream, so did go through code review and has been publicly available for a while. + + This fixes a significant regression compared to Ubuntu 15.04 and looks + less risky than the alternative workaround which was uploaded earlier. + + + === Original report === + After initial upgrade from Ubuntu 15.04 to Ubuntu 15.10 LXC worked for a couple days then failed. I found that the lxcbr0 interface no longer existed. I reported this on the lxc-user alias and about the same time several others had this happen to them also. Serge Hallyn requested I open a launchpad bug and post some info but before I could gather that info the system returned to normal (re lxcbr0 was back) the next day after the server was booted up again. note: at least one other person had this happen to them also (lxcbr0 came back by itself). Today, I booted this server again and ... again lxcbr0 was missing where it had been working last night. Below is all of the Info Serge Hallyn asked me to post. $ ifconfig lxcbr0 lxcbr0: error fetching interface information: Device not found - $ journalctl -u lxc-net -- Logs begin at Tue 2015-11-03 07:25:22 EST, end at Tue 2015-11-03 10:02:08 EST Nov 03 07:25:48 server3 systemd[1]: Starting LXC network bridge setup... Nov 03 07:25:50 server3 lxc-net[913]: dnsmasq: failed to create listening socket Nov 03 07:25:50 server3 lxc-net[913]: Failed to setup lxc-net. Nov 03 07:25:50 server3 systemd[1]: Started LXC network bridge setup. root@server3:/home/bmullan# /usr/lib/x86_64-linux-gnu/lxc/lxc-net stop # note - execution just returns to command line root@server3:/home/bmullan# >> and lxcbr0 is still missing # ifconfig lxcbr0 lxcbr0: error fetching interface information: Device not found root@server3:/home/bmullan# /usr/lib/x86_64-linux-gnu/lxc/lxc-net start dnsmasq: failed to create listening socket for 10.0.3.1: Cannot assign requested address Failed to setup lxc-net. root@server3:/home/bmullan# $ uname -a Linux server3 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID:Ubuntu Description:Ubuntu 15.10 Release:15.10 Codename:wily ** Changed in: network-manager (Ubuntu Wily) Status: Triaged => Fix Committed ** Tags added: verification-needed -- 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/1512749 Title: lxcbr0 dissappears on Ubuntu 15.10 Status in lxc package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Fix Committed Status in lxc source package in Wily: Invalid Status in network-manager source package in Wily: Fix Committed Status in lxc source package in Xenial: Invalid Status in network-manager source package in Xenial: Fix Committed Bug description: === SRU === Rationale: Network Manager in wily triggers on newly created interfaces and resets their network configuration even though it's not supposed to manage them at all. This breaks LXC and quite possibly libvirt as those provide bridges which are then completely unconfigured by Network Manager. Test case: 1) Update (or not) network-manager 2) Restart it 3) Install lxc 4) Check that lxcbr0 exists and has an IP configured Regression potential: The change to Network Manager is related to udev handling of new devices, even though normal operation on a regular desktop machine was tested, it's not impossible that this may regress handling of some devices. The fix was cherry-picked directly from upstream, so did go through code review and has been publicly available
[Desktop-packages] [Bug 1512749] Please test proposed package
Hello brian, or anyone else affected, Accepted network-manager into wily-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/network- manager/1.0.4-0ubuntu5.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- 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/1512749 Title: lxcbr0 dissappears on Ubuntu 15.10 Status in lxc package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Fix Committed Status in lxc source package in Wily: Invalid Status in network-manager source package in Wily: Fix Committed Status in lxc source package in Xenial: Invalid Status in network-manager source package in Xenial: Fix Committed Bug description: === SRU === Rationale: Network Manager in wily triggers on newly created interfaces and resets their network configuration even though it's not supposed to manage them at all. This breaks LXC and quite possibly libvirt as those provide bridges which are then completely unconfigured by Network Manager. Test case: 1) Update (or not) network-manager 2) Restart it 3) Install lxc 4) Check that lxcbr0 exists and has an IP configured Regression potential: The change to Network Manager is related to udev handling of new devices, even though normal operation on a regular desktop machine was tested, it's not impossible that this may regress handling of some devices. The fix was cherry-picked directly from upstream, so did go through code review and has been publicly available for a while. This fixes a significant regression compared to Ubuntu 15.04 and looks less risky than the alternative workaround which was uploaded earlier. === Original report === After initial upgrade from Ubuntu 15.04 to Ubuntu 15.10 LXC worked for a couple days then failed. I found that the lxcbr0 interface no longer existed. I reported this on the lxc-user alias and about the same time several others had this happen to them also. Serge Hallyn requested I open a launchpad bug and post some info but before I could gather that info the system returned to normal (re lxcbr0 was back) the next day after the server was booted up again. note: at least one other person had this happen to them also (lxcbr0 came back by itself). Today, I booted this server again and ... again lxcbr0 was missing where it had been working last night. Below is all of the Info Serge Hallyn asked me to post. $ ifconfig lxcbr0 lxcbr0: error fetching interface information: Device not found $ journalctl -u lxc-net -- Logs begin at Tue 2015-11-03 07:25:22 EST, end at Tue 2015-11-03 10:02:08 EST Nov 03 07:25:48 server3 systemd[1]: Starting LXC network bridge setup... Nov 03 07:25:50 server3 lxc-net[913]: dnsmasq: failed to create listening socket Nov 03 07:25:50 server3 lxc-net[913]: Failed to setup lxc-net. Nov 03 07:25:50 server3 systemd[1]: Started LXC network bridge setup. root@server3:/home/bmullan# /usr/lib/x86_64-linux-gnu/lxc/lxc-net stop # note - execution just returns to command line root@server3:/home/bmullan# >> and lxcbr0 is still missing # ifconfig lxcbr0 lxcbr0: error fetching interface information: Device not found root@server3:/home/bmullan# /usr/lib/x86_64-linux-gnu/lxc/lxc-net start dnsmasq: failed to create listening socket for 10.0.3.1: Cannot assign requested address Failed to setup lxc-net. root@server3:/home/bmullan# $ uname -a Linux server3 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID:Ubuntu Description:Ubuntu 15.10 Release:15.10 Codename:wily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1512749/+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 1512749] Re: lxcbr0 dissappears on Ubuntu 15.10
A proper network-manager fix is being uploaded now, I'll confirm it and then revert the LXC workaround. -- 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/1512749 Title: lxcbr0 dissappears on Ubuntu 15.10 Status in lxc package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Triaged Status in lxc source package in Wily: Triaged Status in network-manager source package in Wily: Triaged Status in lxc source package in Xenial: Triaged Status in network-manager source package in Xenial: Triaged Bug description: After initial upgrade from Ubuntu 15.04 to Ubuntu 15.10 LXC worked for a couple days then failed. I found that the lxcbr0 interface no longer existed. I reported this on the lxc-user alias and about the same time several others had this happen to them also. Serge Hallyn requested I open a launchpad bug and post some info but before I could gather that info the system returned to normal (re lxcbr0 was back) the next day after the server was booted up again. note: at least one other person had this happen to them also (lxcbr0 came back by itself). Today, I booted this server again and ... again lxcbr0 was missing where it had been working last night. Below is all of the Info Serge Hallyn asked me to post. $ ifconfig lxcbr0 lxcbr0: error fetching interface information: Device not found $ journalctl -u lxc-net -- Logs begin at Tue 2015-11-03 07:25:22 EST, end at Tue 2015-11-03 10:02:08 EST Nov 03 07:25:48 server3 systemd[1]: Starting LXC network bridge setup... Nov 03 07:25:50 server3 lxc-net[913]: dnsmasq: failed to create listening socket Nov 03 07:25:50 server3 lxc-net[913]: Failed to setup lxc-net. Nov 03 07:25:50 server3 systemd[1]: Started LXC network bridge setup. root@server3:/home/bmullan# /usr/lib/x86_64-linux-gnu/lxc/lxc-net stop # note - execution just returns to command line root@server3:/home/bmullan# >> and lxcbr0 is still missing # ifconfig lxcbr0 lxcbr0: error fetching interface information: Device not found root@server3:/home/bmullan# /usr/lib/x86_64-linux-gnu/lxc/lxc-net start dnsmasq: failed to create listening socket for 10.0.3.1: Cannot assign requested address Failed to setup lxc-net. root@server3:/home/bmullan# $ uname -a Linux server3 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID:Ubuntu Description:Ubuntu 15.10 Release:15.10 Codename:wily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1512749/+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 1512749] Re: lxcbr0 dissappears on Ubuntu 15.10
Just managed to reproduce it here, it's caused by Network Manager deciding to mess with our bridge instead of leaving it alone as it should. Current workarounds include: - reboot - systemctl stop network-manager && systemctl restart lxc-net && systemct start network-manager This only kicks in when the interface is brought up after network- manager, so it doesn't affect boot since lxc-net starts before network- manager and it doesn't affect upgrades where a container is already running (as we don't destroy the bridge in that case). But it does absolutely affect all new installs and upgrades done when no container is running. This is a critical regression in Network Manager behavior, NM should NEVER touch non-physical interfaces and it should even less start flushing existing network configuration. Changes are this affects libvirt too, unless libvirt bring up takes long enough to win the race against NM. ** Package changed: lxc (Ubuntu) => network-manager (Ubuntu) ** Changed in: network-manager (Ubuntu) Importance: Undecided => Critical ** Changed in: network-manager (Ubuntu) Status: New => Triaged ** Also affects: network-manager (Ubuntu Xenial) Importance: Critical Status: Triaged ** Also affects: network-manager (Ubuntu Wily) Importance: Undecided Status: New ** Changed in: network-manager (Ubuntu Wily) Status: New => Triaged ** Changed in: network-manager (Ubuntu Wily) Importance: Undecided => Critical ** Tags added: regression-release -- 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/1512749 Title: lxcbr0 dissappears on Ubuntu 15.10 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Wily: Triaged Status in network-manager source package in Xenial: Triaged Bug description: After initial upgrade from Ubuntu 15.04 to Ubuntu 15.10 LXC worked for a couple days then failed. I found that the lxcbr0 interface no longer existed. I reported this on the lxc-user alias and about the same time several others had this happen to them also. Serge Hallyn requested I open a launchpad bug and post some info but before I could gather that info the system returned to normal (re lxcbr0 was back) the next day after the server was booted up again. note: at least one other person had this happen to them also (lxcbr0 came back by itself). Today, I booted this server again and ... again lxcbr0 was missing where it had been working last night. Below is all of the Info Serge Hallyn asked me to post. $ ifconfig lxcbr0 lxcbr0: error fetching interface information: Device not found $ journalctl -u lxc-net -- Logs begin at Tue 2015-11-03 07:25:22 EST, end at Tue 2015-11-03 10:02:08 EST Nov 03 07:25:48 server3 systemd[1]: Starting LXC network bridge setup... Nov 03 07:25:50 server3 lxc-net[913]: dnsmasq: failed to create listening socket Nov 03 07:25:50 server3 lxc-net[913]: Failed to setup lxc-net. Nov 03 07:25:50 server3 systemd[1]: Started LXC network bridge setup. root@server3:/home/bmullan# /usr/lib/x86_64-linux-gnu/lxc/lxc-net stop # note - execution just returns to command line root@server3:/home/bmullan# >> and lxcbr0 is still missing # ifconfig lxcbr0 lxcbr0: error fetching interface information: Device not found root@server3:/home/bmullan# /usr/lib/x86_64-linux-gnu/lxc/lxc-net start dnsmasq: failed to create listening socket for 10.0.3.1: Cannot assign requested address Failed to setup lxc-net. root@server3:/home/bmullan# $ uname -a Linux server3 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID:Ubuntu Description:Ubuntu 15.10 Release:15.10 Codename:wily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1512749/+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 1501588] [NEW] Wily's wpasupplicant frequently fails on WPA enterprise networks
Public bug reported: Ever since I upgraded from vivid to wily on my laptop, I'm running into problems when connecting to my home WPA2 enterprise network. Typically the first connection immediately after the driver is loaded works as expected, however any further reconnection and the occasional roaming between APs cause wpasupplicant to freeze entirely requiring me to kill it and most often also reload my wireless driver to get things working again. ## A failed (hanging) association looks like: Sep 30 23:31:06 castiana NetworkManager[25815]: (wlan0): Activation: (wifi) connection 'stgraber.net-secure' has security, and secrets exist. No new secrets needed. Sep 30 23:31:06 castiana NetworkManager[25815]: Config: added 'ssid' value 'stgraber.net-secure' Sep 30 23:31:06 castiana NetworkManager[25815]: Config: added 'scan_ssid' value '1' Sep 30 23:31:06 castiana NetworkManager[25815]: Config: added 'key_mgmt' value 'WPA-EAP' Sep 30 23:31:06 castiana NetworkManager[25815]: Config: added 'eap' value 'TLS' Sep 30 23:31:06 castiana NetworkManager[25815]: Config: added 'fragment_size' value '1300' Sep 30 23:31:06 castiana NetworkManager[25815]: Config: added 'ca_cert' value '/home/stgraber/data/certs/stgraber-radius/ca.crt' Sep 30 23:31:06 castiana NetworkManager[25815]: Config: added 'private_key' value '/home/stgraber/data/certs/stgraber-radius/castiana.p12' Sep 30 23:31:06 castiana NetworkManager[25815]: Config: added 'private_key_passwd' value '' Sep 30 23:31:06 castiana NetworkManager[25815]: Config: added 'identity' value 'castiana' Sep 30 23:31:06 castiana NetworkManager[25815]: Config: added 'bgscan' value 'simple:30:-65:300' Sep 30 23:31:06 castiana NetworkManager[25815]: Config: added 'proactive_key_caching' value '1' Sep 30 23:31:06 castiana NetworkManager[25815]: Connection disconnected (reason -3) Sep 30 23:31:06 castiana NetworkManager[25815]: (wlan0): supplicant interface state: associated -> disconnected Sep 30 23:31:06 castiana NetworkManager[25815]: Failed to GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not connected: disconnect. Sep 30 23:31:06 castiana NetworkManager[25815]: Failed to GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not connected: disconnect. Sep 30 23:31:06 castiana NetworkManager[25815]: Config: set interface ap_scan to 1 Sep 30 23:31:06 castiana NetworkManager[25815]: (wlan0): supplicant interface state: disconnected -> scanning Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: SME: Trying to authenticate with 24:a4:3c:c8:69:03 (SSID='stgraber.net-secure' freq=2412 MHz) Sep 30 23:31:07 castiana kernel: [102903.079940] wlan0: authenticate with 24:a4:3c:c8:69:03 Sep 30 23:31:07 castiana kernel: [102903.085128] wlan0: send auth to 24:a4:3c:c8:69:03 (try 1/3) Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: Trying to associate with 24:a4:3c:c8:69:03 (SSID='stgraber.net-secure' freq=2412 MHz) Sep 30 23:31:07 castiana NetworkManager[25815]: (wlan0): supplicant interface state: scanning -> authenticating Sep 30 23:31:07 castiana kernel: [102903.086942] wlan0: authenticated Sep 30 23:31:07 castiana kernel: [102903.090103] wlan0: associate with 24:a4:3c:c8:69:03 (try 1/3) Sep 30 23:31:07 castiana NetworkManager[25815]: (wlan0): supplicant interface state: authenticating -> associating Sep 30 23:31:07 castiana kernel: [102903.101962] wlan0: RX AssocResp from 24:a4:3c:c8:69:03 (capab=0x411 status=0 aid=1) Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: Associated with 24:a4:3c:c8:69:03 Sep 30 23:31:07 castiana kernel: [102903.103701] wlan0: associated Sep 30 23:31:07 castiana NetworkManager[25815]: (wlan0): supplicant interface state: associating -> associated Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=13 Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 13 (TLS) selected Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: CTRL-EVENT-EAP-PEER-CERT depth=2 subject='/C=CA/ST=Quebec/L=Montreal/O=stgraber.net/OU=Internal Infrastructure/CN=stgraber.net Root CA/name=stgraber.net Infrastructure Root CA/emailAddress=stgra...@stgraber.org' hash=87b9750baadddac7f05164d7fde3a0eb3d3efe0c948b430a3ecd093c629956e9 Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: CTRL-EVENT-EAP-PEER-CERT depth=1 subject='/C=CA/ST=Quebec/L=Montreal/O=stgraber.net/OU=Internal Infrastructure/CN=radius/name=stgraber.net Infrastructure Root CA/emailAddress=stgra...@stgraber.org' hash=1fc5a4237c625f445a8eaf3794d4ee475d47dd7be31301a0215ee9701dee46e0 Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='/C=CA/ST=Quebec/L=Montreal/O=stgraber.net/OU=Internal Infrastructure/CN=freeradius01/name=stgraber.net Internal
[Desktop-packages] [Bug 1448179] Re: veth devices still appear in the applet
Still a problem with wily... -- 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/1448179 Title: veth devices still appear in the applet Status in network-manager package in Ubuntu: Confirmed Bug description: vethXYZ devices as created by LXC shouldn't be managed or even displayed by Network Manager. They currently don't appear to be managed (good), but running a few hundred containers, having each of them take two lines in the network menu makes NM almost unusable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1448179/+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 1501588] Re: Wily's wpasupplicant frequently fails on WPA enterprise networks
Same issue happened again after I downgraded to vivid's version... Now rebooting my laptop on a vivid kernel to confirm it's a kernel bug and not a wpasupplicant bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1501588 Title: Wily's wpasupplicant frequently fails on WPA enterprise networks Status in wpa package in Ubuntu: New Bug description: Ever since I upgraded from vivid to wily on my laptop, I'm running into problems when connecting to my home WPA2 enterprise network. Typically the first connection immediately after the driver is loaded works as expected, however any further reconnection and the occasional roaming between APs cause wpasupplicant to freeze entirely requiring me to kill it and most often also reload my wireless driver to get things working again. ## A failed (hanging) association looks like: Sep 30 23:31:06 castiana NetworkManager[25815]: (wlan0): Activation: (wifi) connection 'stgraber.net-secure' has security, and secrets exist. No new secrets needed. Sep 30 23:31:06 castiana NetworkManager[25815]: Config: added 'ssid' value 'stgraber.net-secure' Sep 30 23:31:06 castiana NetworkManager[25815]: Config: added 'scan_ssid' value '1' Sep 30 23:31:06 castiana NetworkManager[25815]: Config: added 'key_mgmt' value 'WPA-EAP' Sep 30 23:31:06 castiana NetworkManager[25815]: Config: added 'eap' value 'TLS' Sep 30 23:31:06 castiana NetworkManager[25815]: Config: added 'fragment_size' value '1300' Sep 30 23:31:06 castiana NetworkManager[25815]: Config: added 'ca_cert' value '/home/stgraber/data/certs/stgraber-radius/ca.crt' Sep 30 23:31:06 castiana NetworkManager[25815]: Config: added 'private_key' value '/home/stgraber/data/certs/stgraber-radius/castiana.p12' Sep 30 23:31:06 castiana NetworkManager[25815]: Config: added 'private_key_passwd' value '' Sep 30 23:31:06 castiana NetworkManager[25815]: Config: added 'identity' value 'castiana' Sep 30 23:31:06 castiana NetworkManager[25815]: Config: added 'bgscan' value 'simple:30:-65:300' Sep 30 23:31:06 castiana NetworkManager[25815]: Config: added 'proactive_key_caching' value '1' Sep 30 23:31:06 castiana NetworkManager[25815]: Connection disconnected (reason -3) Sep 30 23:31:06 castiana NetworkManager[25815]: (wlan0): supplicant interface state: associated -> disconnected Sep 30 23:31:06 castiana NetworkManager[25815]: Failed to GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not connected: disconnect. Sep 30 23:31:06 castiana NetworkManager[25815]: Failed to GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not connected: disconnect. Sep 30 23:31:06 castiana NetworkManager[25815]: Config: set interface ap_scan to 1 Sep 30 23:31:06 castiana NetworkManager[25815]: (wlan0): supplicant interface state: disconnected -> scanning Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: SME: Trying to authenticate with 24:a4:3c:c8:69:03 (SSID='stgraber.net-secure' freq=2412 MHz) Sep 30 23:31:07 castiana kernel: [102903.079940] wlan0: authenticate with 24:a4:3c:c8:69:03 Sep 30 23:31:07 castiana kernel: [102903.085128] wlan0: send auth to 24:a4:3c:c8:69:03 (try 1/3) Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: Trying to associate with 24:a4:3c:c8:69:03 (SSID='stgraber.net-secure' freq=2412 MHz) Sep 30 23:31:07 castiana NetworkManager[25815]: (wlan0): supplicant interface state: scanning -> authenticating Sep 30 23:31:07 castiana kernel: [102903.086942] wlan0: authenticated Sep 30 23:31:07 castiana kernel: [102903.090103] wlan0: associate with 24:a4:3c:c8:69:03 (try 1/3) Sep 30 23:31:07 castiana NetworkManager[25815]: (wlan0): supplicant interface state: authenticating -> associating Sep 30 23:31:07 castiana kernel: [102903.101962] wlan0: RX AssocResp from 24:a4:3c:c8:69:03 (capab=0x411 status=0 aid=1) Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: Associated with 24:a4:3c:c8:69:03 Sep 30 23:31:07 castiana kernel: [102903.103701] wlan0: associated Sep 30 23:31:07 castiana NetworkManager[25815]: (wlan0): supplicant interface state: associating -> associated Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=13 Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 13 (TLS) selected Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: CTRL-EVENT-EAP-PEER-CERT depth=2 subject='/C=CA/ST=Quebec/L=Montreal/O=stgraber.net/OU=Internal Infrastructure/CN=stgraber.net Root CA/name=stgraber.net Infrastructure Root CA/emailAddress=stgra...@stgraber.org' hash=87b9750baadddac7f05164d7fde3a0eb3d3efe0c948b430a3ecd093c629956e9 Sep 30 23:31:07
[Desktop-packages] [Bug 1448179] [NEW] veth devices still appear in the applet
Public bug reported: vethXYZ devices as created by LXC shouldn't be managed or even displayed by Network Manager. They currently don't appear to be managed (good), but running a few hundred containers, having each of them take two lines in the network menu makes NM almost unusable. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1448179 Title: veth devices still appear in the applet Status in network-manager package in Ubuntu: New Bug description: vethXYZ devices as created by LXC shouldn't be managed or even displayed by Network Manager. They currently don't appear to be managed (good), but running a few hundred containers, having each of them take two lines in the network menu makes NM almost unusable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1448179/+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 1445064] [NEW] Re-implement container crash forwarding
Public bug reported: The container crash forwarding feature must be re-implemented to use a safe design. The current thought is: - Introduce a systemd unit and upstart job to have a socket activated apport crash handler - When a crash comes from a container, have apport connect to the socket in the crashed process' root, write the arguments it received to the socket. - The crash handler in the container will then run and close the socket when it doesn't need the crashed process anymore. - The host crash handler then exits. This means that we only rely on an accessible root directory for the crashed process and the crash handler will be spawned by init inside that container. This makes it safe for privileged and unprivileged containers. As an extra security measure, rate limiting should be added so that we can only have 10 in-flight crashes and that any crash taking more than 30s to be handled get cancelled (preventing host DoS). ** Affects: apport (Ubuntu) Importance: Wishlist Assignee: Stéphane Graber (stgraber) Status: Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1445064 Title: Re-implement container crash forwarding Status in apport package in Ubuntu: Triaged Bug description: The container crash forwarding feature must be re-implemented to use a safe design. The current thought is: - Introduce a systemd unit and upstart job to have a socket activated apport crash handler - When a crash comes from a container, have apport connect to the socket in the crashed process' root, write the arguments it received to the socket. - The crash handler in the container will then run and close the socket when it doesn't need the crashed process anymore. - The host crash handler then exits. This means that we only rely on an accessible root directory for the crashed process and the crash handler will be spawned by init inside that container. This makes it safe for privileged and unprivileged containers. As an extra security measure, rate limiting should be added so that we can only have 10 in-flight crashes and that any crash taking more than 30s to be handled get cancelled (preventing host DoS). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1445064/+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 1382291] Re: Account creation during first boot of an OEM image needs to scale based on resolution
So for the ubiquity task, ubiquity calls unity-settings-daemon when running under ubiquity-dm (as is the case for the standalone installer and for OEM config), so once the unity-settings-daemon issue is resolved, I'd expect the UI to just scale as expected. As such, marking the ubiquity tasks invalid. ** Changed in: ubiquity (Ubuntu Trusty) Status: New = Invalid ** Changed in: ubiquity (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1382291 Title: Account creation during first boot of an OEM image needs to scale based on resolution Status in OEM Priority Project: Confirmed Status in OEM Priority Project trusty series: New Status in “ubiquity” package in Ubuntu: Invalid Status in “unity-settings-daemon” package in Ubuntu: New Status in “ubiquity” source package in Trusty: Invalid Status in “unity-settings-daemon” source package in Trusty: New Bug description: In HiDPI screens, the OOBE for OEM images is not ideal. The new gSettings to scale GTK applications (and their corresponding settings in System Settings) work great, but this does not help for the account creation (first boot) for users buying a pre-install system. We would need changes in Ubiquity to: * Probe the monitor to get resolution information * Re-scale the ubiquity window using the corresponding gsetting (com.ubuntu.user-interface scale-factor) based on resolution We would need the changes to be backported to Trusty as well. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1382291/+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 1296275] Update Released
The verification of the Stable Release Update for libgphoto2 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1296275 Title: PTP Cameras not working on 14.04, works flawlessly on 12.04 Status in GVFS: Confirmed Status in libgphoto: New Status in Rapid Photo Downloader: Invalid Status in “gvfs” package in Ubuntu: Triaged Status in “libgphoto2” package in Ubuntu: Fix Released Status in “gvfs” source package in Trusty: Won't Fix Status in “libgphoto2” source package in Trusty: Fix Released Status in “gvfs” source package in Utopic: Triaged Status in “libgphoto2” source package in Utopic: Fix Released Bug description: I have a Canon Powershot A3200 camera. It works perfectly on 12.04, pops right up when I plug it in. However on 14.04 nothing happens. lsusb outputs shows that the camera is detected, with the right model. SRU INFORMATION: IMPACT: All PtP cameras which don't have an explicit vendor/model match in /lib/udev/hwdb.d/20-libgphoto2-6.hwdb stop working in gvfs/shotwell/etc. This is a regression since Saucy. FIX: Bring back the udev rule to tag generic PtP devices that we had had for many releases. This will tag the udev_device with the ID_GPHOTO2 property which is where gvfs and friends are looking (not on the usb_interface child). Patch: http://launchpadlibrarian.net/177343655/libgphoto2_2.5.4-1ubuntu1_2.5.4-1ubuntu2.diff.gz REGRESSION POTENTIAL: Very low. Adding tags to the wrong device might confuse gvfs/shotwell and friends, but this rule had been in production for many years. Broken udev rules are harmless except for error spew in syslog, and this doesn't interfere with the hwdb database as it only matches on usb_devices, not on usb_interfaces. To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1296275/+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 1237191] Update Released
The verification of the Stable Release Update for telepathy-gabble has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-gabble in Ubuntu. https://bugs.launchpad.net/bugs/1237191 Title: telepathy-gabble crashed with SIGSEGV in stun_server_resolved_cb() Status in Jabber/XMPP connection manager: Fix Released Status in “telepathy-gabble” package in Ubuntu: Fix Released Status in “telepathy-gabble” source package in Trusty: Fix Released Bug description: * Impact telepathy-gabble segfaults sometimes * Test case no specific testcase, watch reports on https://errors.ubuntu.com/problem/93026bff3a7b3efe53da33fcbdc6c6cb5c8282f3 * Regression potential check that jabber keeps working fine with telepathy (change should be safe, it's just handling of a null case) To manage notifications about this bug go to: https://bugs.launchpad.net/telepathy-gabble/+bug/1237191/+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 1326295] Re: Unable to print to Konica Minolta bizhub C253 printer (and other Konica Minolta, Minolta, Brother, and old HP LaserJet)
Hello Adam, or anyone else affected, Accepted cups-filters into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/cups- filters/1.0.52-0ubuntu1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cups-filters (Ubuntu Trusty) Status: In Progress = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1326295 Title: Unable to print to Konica Minolta bizhub C253 printer (and other Konica Minolta, Minolta, Brother, and old HP LaserJet) Status in “cups-filters” package in Ubuntu: Fix Committed Status in “cups-filters” source package in Trusty: Fix Committed Bug description: This bug was already fixed in Ubuntu 13.10 but it is broken again in 14.04. The printer freezes right after I try to print something. The original report is bug #1053443. [Impact] Several PostScript printers do not work with the PostScript generated by Ghostscript but do not have problems with the PostScript from Poppler. In 14.04 the auto-switching to Poppler for these cases is missing, making printers from Brother, Minolta, Konica Minolta, and old HP LaserJets misbehave. Some Konica Minolta even crash and need to get turned off and turned on again. [Test Case] Print on any Brother, Minolta, Konica Minolta, or old HP LaserJet with Ubuntu 14.04. This will not work as always Ghostscript is used to generate PostScript. The proposed package re-activates the switching mechanism to use Poppler for these printers, so you will be able to print. [Regression Potential] None, as we had the switching mechanism already in 13.10. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups-filters 1.0.52-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Wed Jun 4 10:54:55 2014 InstallationDate: Installed on 2013-07-22 (316 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) Lpstat: device for KONICA-MINOLTA-C353-Series: dnssd://KONICA%20MINOLTA%20bizhub%20C253(5D%3A9C%3A78)._pdl-datastream._tcp.local/ device for Samsung-ML-1640-Series: usb://Samsung/ML-1640%20Series?serial=144QBACQC10705R. device for windows_printer: winp://NIEDLING-5A803D/print MachineType: Acer V5-171 Papersize: a4 PpdFiles: Samsung-ML-1640-Series: Samsung ML-1640, 2.0.0 KONICA-MINOLTA-C353-Series: KONICA MINOLTA C353 Series PS(P) windows_printer: Acrobat Distiller 3011.104 adist5: Acrobat Distiller 3011.104 ProcEnviron: LANGUAGE=hu TERM=xterm PATH=(custom, no user) LANG=hu_HU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-27-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: cups-filters UpgradeStatus: Upgraded to trusty on 2014-05-07 (27 days ago) dmi.bios.date: 03/22/2013 dmi.bios.vendor: Acer dmi.bios.version: V2.17 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Mimic dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.17 dmi.modalias: dmi:bvnAcer:bvrV2.17:bd03/22/2013:svnAcer:pnV5-171:pvrV2.17:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.17: dmi.product.name: V5-171 dmi.product.version: V2.17 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1326295/+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 1318581] Re: Tooltips for Next and Previous pages are mixed up
Hello TenLeftFingers, or anyone else affected, Accepted evince into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/evince/3.10.3-0ubuntu10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1318581 Title: Tooltips for Next and Previous pages are mixed up Status in “evince” package in Ubuntu: Fix Released Bug description: * Impact The button for the next page shows the tooltip Previous Page and vice versa. It's a little confusing :) * Test Case - run evince, open a document - move the mouse over the previous/next buttons, read the tooltip displayed * Regression potential the change just inverts wrong labels in the code, it shouldn't create any issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1318581/+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 1312179] Re: fit and width hotkeys broken
Hello Krister, or anyone else affected, Accepted evince into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/evince/3.10.3-0ubuntu10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1312179 Title: fit and width hotkeys broken Status in “evince” package in Ubuntu: Fix Released Bug description: * Impact The keys f and w no longer change the document size to fit the window or the width to match the window width * Test case: - open a document in evince, press the f and w keys, see if the zoom changes * Regression potential: check that keybindings work as they should -- The keys f and w no longer change the document size to fit the window or the width to match the window width, respectively. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evince 3.10.3-0ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 24 15:29:49 2014 InstallationDate: Installed on 2013-10-03 (202 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: evince UpgradeStatus: Upgraded to trusty on 2014-04-23 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1312179/+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 1310782] Re: Zoom in shortcut should be =/+, not shift +
Hello Aibara, or anyone else affected, Accepted evince into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/evince/3.10.3-0ubuntu10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1310782 Title: Zoom in shortcut should be =/+, not shift + Status in “evince” package in Ubuntu: Fix Released Bug description: * Impact the zoom in keyboard shortcut is no longer just the =/+ key but now requires the shift key to be held down * Test case: - open a document in evince, press =/+, see if the view zooms * Regression potential: check that keybindings work as they should -- In Ubuntu 14.04, the Evince/Document viewer (version 3.10.3) the zoom in keyboard shortcut is no longer just the =/+ key but now requires the shift key to be held down. I assume this is a regression, since every previous version of Evince simply mapped zoom in to =/+, no shift required. The Zoom out shortcut is unchanged (the -/_ key). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1310782/+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 1313250] Re: Shortcut key Ctrl+L no longer sets cursor to page selector in 3.10.3
Hello macho, or anyone else affected, Accepted evince into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/evince/3.10.3-0ubuntu10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1313250 Title: Shortcut key Ctrl+L no longer sets cursor to page selector in 3.10.3 Status in “evince” package in Ubuntu: Fix Released Bug description: * Impact Ctrl+L stopped working (should focus the page number box) * Test case: - open a document in evince, press ctrl+L, see if the page number box is selected * Regression potential: check that keybindings work as they should --- In previous versions of evince, when I pressed Ctrl+L the cursor focus would be set to the page number box. It made it extremely convenient to navigate documents. Since I upgraded to Ubuntu 14.04 / evince 3.10.3, this seems no longer to work. Would be great to get the functionality back. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1313250/+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 1272716] Re: Undo doesn't work: gnome-sudoku crashed with TypeError in set_value(): unorderable types: int() NoneType()
Hello Vassili, or anyone else affected, Accepted gnome-sudoku into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/gnome- sudoku/1:3.10.2-0ubuntu3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-sudoku in Ubuntu. https://bugs.launchpad.net/bugs/1272716 Title: Undo doesn't work: gnome-sudoku crashed with TypeError in set_value(): unorderable types: int() NoneType() Status in “gnome-sudoku” package in Ubuntu: Fix Released Bug description: Impact: using undo sometime hits an error Test Case: - run gnome-sudoku - start an easy game - enter a number somewhere - click on undo - it should undo and not trigger an error dialog Regression potential: check that undo keeps working correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-sudoku/+bug/1272716/+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 1320485] Re: about:startpage is http://start.ubuntu.com/13.10/Google/ on Ubuntu 14.04
Hello Michał, or anyone else affected, Accepted ubufox into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/ubufox/2.9-0ubuntu0.14.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: ubufox (Ubuntu Trusty) Status: Triaged = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubufox in Ubuntu. https://bugs.launchpad.net/bugs/1320485 Title: about:startpage is http://start.ubuntu.com/13.10/Google/ on Ubuntu 14.04 Status in Ubuntu Firefox Extension: Fix Released Status in Ubuntu Start Page: In Progress Status in “ubufox” package in Ubuntu: Fix Released Status in “ubufox” source package in Trusty: Fix Committed Bug description: Firefox (29.0), about:startpage. It's totally not a problem for me, but it's a sign that someone forgot to update the version in the start page URL. On the other hand... If it wasn't noticed by anyone, then maybe it's not important. If it's not important, then maybe it would be best to remove the version from the URL? To manage notifications about this bug go to: https://bugs.launchpad.net/ubufox/+bug/1320485/+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 1104230] Re: DisplayPort 1.2 MST support is missing in the Intel driver
Yep, I've been following David's recent work on this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1104230 Title: DisplayPort 1.2 MST support is missing in the Intel driver Status in “xserver-xorg-video-intel” package in Ubuntu: Confirmed Bug description: I have two recent DisplayPort monitors, both supporting the 1.2 version of the standard and one containing an MST hub (DELL 2913WM). I have an Intel Haswell based NUC connected over mini-displayport to the display containing the hub, then the second display is plugged in that one over DisplayPort. DisplayPort 1.2 is enabled on the display containing the hub and the second display lights up fine but just works as a clone of the first display, without ever showing up in xrandr, dmesg or any other useful logs I could find. My understanding of MST is that the second display should show up as DP2 on my laptop so I can configure it as I would any other display. UPDATE: Updated the bug report after it was pointed out that the original test hardware, a Lenovo x230 isn't DP 1.2 capable. The same test on hardware also fails, due to missing support for MST in the driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1104230/+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 1313550] Re: ping does not work as a normal user on trusty tarball cloud images.
gnome-keyring-daemon isn't really a problem because all official images shipping it have installer hooks to restore the flag. Setting the binary setuid would also be completely wrong as we never want this to run as root, we just want it to have extra ipc locking capabilities. My understanding is that those aren't even entirely required and that it has a fallback mode for systems where the capability isn't set. -- 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/1313550 Title: ping does not work as a normal user on trusty tarball cloud images. Status in The curt installer: Confirmed Status in MAAS: Confirmed Status in “curtin” package in Ubuntu: Confirmed Status in “iputils” package in Ubuntu: Fix Released Status in “lxc” package in Ubuntu: Confirmed Status in “maas” package in Ubuntu: Confirmed Status in “tar” package in Ubuntu: Fix Released Status in “lxc” source package in Precise: Confirmed Status in “tar” source package in Precise: Confirmed Status in “curtin” source package in Saucy: Confirmed Status in “lxc” source package in Saucy: Confirmed Status in “maas” source package in Saucy: Confirmed Status in “tar” source package in Saucy: Confirmed Status in “curtin” source package in Trusty: Confirmed Status in “lxc” source package in Trusty: Confirmed Status in “maas” source package in Trusty: Confirmed Status in “tar” source package in Trusty: Fix Released Bug description: With trusty, /bin/ping relies on having extended attributes and kernel capabilities to gain the cap_net_raw+p capability. This allows removing the suid bit. However, the tarball cloud images do not preserve the extended attributes, and thus /bin/ping does not work on a system derived from them. Summary of problem per package: * lxc: ubuntu cloud template needs to extract * download template needs to extract with xattr flags * server side download creation tools need xattr flags * [unconfirmed] tarball caches need creation and extraction with xattr flags * tar: need the '--xattr' and '--acl' flags backported * maas: uec2roottgz needs to use xattr/acl flags * curtin: extraction needs to use xattr/acl flags. * cloud-image-build: needs to create -root.tar.gz with xattr/acl flags To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1313550/+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 1313550] Re: ping does not work as a normal user on trusty tarball cloud images.
So yeah, my understanding is that --xattr is broken at the moment, we should fix that as an SRU but we also have the problem that: 1) It's not set by default in either create or extract mode 2) Not all tar implementations we use support it 3) Not all version of gnu-tar we support have it So as long as we don't get this fixed, we shouldn't rely on xattrs working in tarballs and should investigate alternative methods of shipping and setting those attributes. -- 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/1313550 Title: ping does not work as a normal user on trusty tarball cloud images. Status in The curt installer: Confirmed Status in MAAS: Confirmed Status in “curtin” package in Ubuntu: Confirmed Status in “iputils” package in Ubuntu: Fix Released Status in “lxc” package in Ubuntu: Confirmed Status in “maas” package in Ubuntu: Confirmed Status in “tar” package in Ubuntu: Fix Released Status in “lxc” source package in Precise: Confirmed Status in “tar” source package in Precise: Confirmed Status in “curtin” source package in Saucy: Confirmed Status in “lxc” source package in Saucy: Confirmed Status in “maas” source package in Saucy: Confirmed Status in “tar” source package in Saucy: Confirmed Status in “curtin” source package in Trusty: Confirmed Status in “lxc” source package in Trusty: Confirmed Status in “maas” source package in Trusty: Confirmed Status in “tar” source package in Trusty: Fix Released Bug description: With trusty, /bin/ping relies on having extended attributes and kernel capabilities to gain the cap_net_raw+p capability. This allows removing the suid bit. However, the tarball cloud images do not preserve the extended attributes, and thus /bin/ping does not work on a system derived from them. Summary of problem per package: * lxc: ubuntu cloud template needs to extract * download template needs to extract with xattr flags * server side download creation tools need xattr flags * [unconfirmed] tarball caches need creation and extraction with xattr flags * tar: need the '--xattr' and '--acl' flags backported * maas: uec2roottgz needs to use xattr/acl flags * curtin: extraction needs to use xattr/acl flags. * cloud-image-build: needs to create -root.tar.gz with xattr/acl flags To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1313550/+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 1302192] Re: capabilities not preserved on installation
** Also affects: iputils (Ubuntu) Importance: Undecided Status: New -- 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/1302192 Title: capabilities not preserved on installation Status in “attr” package in Ubuntu: Fix Released Status in “iputils” package in Ubuntu: New Status in “live-installer” package in Ubuntu: Fix Released Status in “ubiquity” package in Ubuntu: Fix Released Status in “attr” source package in Trusty: Fix Released Status in “iputils” source package in Trusty: New Status in “live-installer” source package in Trusty: Fix Released Status in “ubiquity” source package in Trusty: Fix Released Bug description: Ping is not longer setuid root and I have to ping as root: [~]$ ping kubuntu.org ping: icmp open socket: Operation not permitted [~]$ sudo ping kubuntu.org PING kubuntu.org (91.189.94.156) 56(84) bytes of data. 64 bytes from vostok.canonical.com (91.189.94.156): icmp_seq=1 ttl=51 time=52.2 ms --- kubuntu.org ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 52.231/52.231/52.231/0.000 ms [~]$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/attr/+bug/1302192/+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 1313550] Re: ping does not work as a normal user on trusty tarball cloud images.
After some more discussion we decided to simply make it setuid again for now and then spend some time thinking about a proper solution for all this, possibly involving small dpkg/debhelper changes so there's a cleaner nicer way of declaring filesystem capabilities. -- 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/1313550 Title: ping does not work as a normal user on trusty tarball cloud images. Status in The curt installer: Confirmed Status in MAAS: Confirmed Status in “curtin” package in Ubuntu: Confirmed Status in “iputils” package in Ubuntu: Confirmed Status in “lxc” package in Ubuntu: Confirmed Status in “maas” package in Ubuntu: Confirmed Status in “tar” package in Ubuntu: Fix Released Status in “lxc” source package in Precise: Confirmed Status in “tar” source package in Precise: Confirmed Status in “curtin” source package in Saucy: Confirmed Status in “lxc” source package in Saucy: Confirmed Status in “maas” source package in Saucy: Confirmed Status in “tar” source package in Saucy: Confirmed Status in “curtin” source package in Trusty: Confirmed Status in “lxc” source package in Trusty: Confirmed Status in “maas” source package in Trusty: Confirmed Status in “tar” source package in Trusty: Fix Released Bug description: With trusty, /bin/ping relies on having extended attributes and kernel capabilities to gain the cap_net_raw+p capability. This allows removing the suid bit. However, the tarball cloud images do not preserve the extended attributes, and thus /bin/ping does not work on a system derived from them. Summary of problem per package: * lxc: ubuntu cloud template needs to extract * download template needs to extract with xattr flags * server side download creation tools need xattr flags * [unconfirmed] tarball caches need creation and extraction with xattr flags * tar: need the '--xattr' and '--acl' flags backported * maas: uec2roottgz needs to use xattr/acl flags * curtin: extraction needs to use xattr/acl flags. * cloud-image-build: needs to create -root.tar.gz with xattr/acl flags To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1313550/+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 1313550] Re: ping does not work as a normal user on trusty tarball cloud images.
** Tags removed: verification-needed ** Tags added: verification-done -- 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/1313550 Title: ping does not work as a normal user on trusty tarball cloud images. Status in The curt installer: Confirmed Status in MAAS: Confirmed Status in “curtin” package in Ubuntu: Confirmed Status in “iputils” package in Ubuntu: Fix Released Status in “lxc” package in Ubuntu: Confirmed Status in “maas” package in Ubuntu: Confirmed Status in “tar” package in Ubuntu: Fix Released Status in “lxc” source package in Precise: Confirmed Status in “tar” source package in Precise: Confirmed Status in “curtin” source package in Saucy: Confirmed Status in “lxc” source package in Saucy: Confirmed Status in “maas” source package in Saucy: Confirmed Status in “tar” source package in Saucy: Confirmed Status in “curtin” source package in Trusty: Confirmed Status in “lxc” source package in Trusty: Confirmed Status in “maas” source package in Trusty: Confirmed Status in “tar” source package in Trusty: Fix Released Bug description: With trusty, /bin/ping relies on having extended attributes and kernel capabilities to gain the cap_net_raw+p capability. This allows removing the suid bit. However, the tarball cloud images do not preserve the extended attributes, and thus /bin/ping does not work on a system derived from them. Summary of problem per package: * lxc: ubuntu cloud template needs to extract * download template needs to extract with xattr flags * server side download creation tools need xattr flags * [unconfirmed] tarball caches need creation and extraction with xattr flags * tar: need the '--xattr' and '--acl' flags backported * maas: uec2roottgz needs to use xattr/acl flags * curtin: extraction needs to use xattr/acl flags. * cloud-image-build: needs to create -root.tar.gz with xattr/acl flags To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1313550/+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 1313550] Re: ping does not work as a normal user on trusty tarball cloud images.
There's a third I mentioned on IRC, just make ping setuid again for 14.04 and only switch to capabilities in 14.10, assuming we don't intend to support 14.10 on 12.04, we'll be good as 14.04 will have a suitable version of tar. -- 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/1313550 Title: ping does not work as a normal user on trusty tarball cloud images. Status in The curt installer: Confirmed Status in MAAS: Confirmed Status in “curtin” package in Ubuntu: Confirmed Status in “iputils” package in Ubuntu: Confirmed Status in “lxc” package in Ubuntu: Confirmed Status in “maas” package in Ubuntu: Confirmed Status in “tar” package in Ubuntu: Fix Released Status in “lxc” source package in Precise: Confirmed Status in “tar” source package in Precise: Confirmed Status in “curtin” source package in Saucy: Confirmed Status in “lxc” source package in Saucy: Confirmed Status in “maas” source package in Saucy: Confirmed Status in “tar” source package in Saucy: Confirmed Status in “curtin” source package in Trusty: Confirmed Status in “lxc” source package in Trusty: Confirmed Status in “maas” source package in Trusty: Confirmed Status in “tar” source package in Trusty: Fix Released Bug description: With trusty, /bin/ping relies on having extended attributes and kernel capabilities to gain the cap_net_raw+p capability. This allows removing the suid bit. However, the tarball cloud images do not preserve the extended attributes, and thus /bin/ping does not work on a system derived from them. Summary of problem per package: * lxc: ubuntu cloud template needs to extract * download template needs to extract with xattr flags * server side download creation tools need xattr flags * [unconfirmed] tarball caches need creation and extraction with xattr flags * tar: need the '--xattr' and '--acl' flags backported * maas: uec2roottgz needs to use xattr/acl flags * curtin: extraction needs to use xattr/acl flags. * cloud-image-build: needs to create -root.tar.gz with xattr/acl flags To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1313550/+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 1302037] Re: [FFE] Add support for creating host route to MMS proxy
Changes are contained to the ofono plugin so only the phone is affected, fine by me. FFe granted. ** Changed in: network-manager (Ubuntu) Status: New = Triaged -- 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/1302037 Title: [FFE] Add support for creating host route to MMS proxy Status in “network-manager” package in Ubuntu: Triaged Bug description: We need to add an extra feature to NetworkManager for MMS support on touch onto the ofono support we already have; that is to create a host route for the MessageProxy should it exist for the context that is being activated. This only affects users of NetworkManager with ofono installed; so is currently limited, on a standard install, to Touch images. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1302037/+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 1298611] Re: [FFe] apparmor signal and ptrace mediation
The LXC change looks good, it's in line with what I was planning to push upstream. Feel free to upload that directly to the archive and I'll do a similar upstream change right around the same time so our PPA users don't break, then shortly after that will tag 1.0.3 and get that into trusty so we can drop the patch. -- 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/1298611 Title: [FFe] apparmor signal and ptrace mediation Status in “apparmor” package in Ubuntu: In Progress Status in “libvirt” package in Ubuntu: In Progress Status in “lightdm” package in Ubuntu: In Progress Status in “linux” package in Ubuntu: Fix Released Status in “lxc” package in Ubuntu: In Progress Bug description: Background: kernel and apparmor userspace updates to support signal and ptrace mediation. These packages are listed in one bug because they are related, but the FFes may be granted and the uploads may happen at different times. = linux = Summary: This feature freeze exception is requested for signal and ptrace mediation via apparmor in the kernel. When used with a compatible apparmor userspace, signals and ptrace rules are supported. When used without a compatible apparmor userspace (eg, on a precise system with a trusty backport kernel), signal and ptrace mediation is not enforced (ie, you can use this kernel with an old userspace without any issues). The fine grained mediation of signals and ptraces also incorporates improved versioning support that allows this kernel to better support older and newer userspaces. This allows for this version of the kernel to work as a backport kernel unmodified (currently a patch and config are used to provide backport kernels). The kernel patch is available at git://kernel.ubuntu.com/jj/ubuntu-trusty.git in the trusty-alpha6 branch apparmor-alpha6-sync Testing: * 12.04 system with backported kernel: DONE * test-apparmor.py: PASS (runs extensive tests (upstream and distro)) * exploratory manual testing: PASS (networking, aa-enforce with firefox, firefox works, apparmor blocks access, etc) * aa-status: PASS * lxc: PASS (containers can be created, started, shutdown) * libvirt: PASS (VMs started via openstack, and test-libvirt.py from QRT passes all tests) * 14.04 system (non-Touch) with current apparmor userspace: DONE (relevant parts of https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor) * test-apparmor.py: PASS (runs extensive tests (upstream and distro)) * exploratory manual testing: PASS (networking, aa-enforce with firefox, firefox works, apparmor blocks access, etc) * aa-status: PASS * lxc: PASS (containers can be created, started, shutdown) * libvirt: PASS (QRT/script/test-libvirt.py (though there are 3 failures unrelated to apparmor)) * click-apparmor QRT touch image tests: PASS * apparmor-easyprof-ubuntu QRT touch image tests: PASS * 14.04 system (non-Touch) with updated apparmor userspace capable of supporting signal and ptrace mediation: DONE (relevant parts of https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor. Note: this is marked 'done' from the kernel perspective-- the apparmor userspace upload is being prepared and tests assume userspace is using latest patches on the list) * test-apparmor.py: PASS (runs extensive tests (upstream and distro)) * exploratory manual testing: PASS (networking, aa-enforce with firefox, firefox works, apparmor blocks access, etc) * aa-status: PASS * lxc: PASS (containers can be created, started, shutdown) * libvirt: PASS (QRT/script/test-libvirt.py (though there are 3 failures unrelated to apparmor)) * click-apparmor QRT touch image tests: PASS * apparmor-easyprof-ubuntu QRT touch image tests: PASS Justification: This feature is required to support comprehensive application confinement on Ubuntu Touch. This feature adds a significant security benefit to libvirt's qemu guest isolation which is fundamental to Ubuntu on Server/Cloud. This feature also adds a welcome improvement to administrators wishing to further protect their systems. = apparmor userspace = Summary: This feature freeze exception is requested for signal and ptrace mediation for apparmor userspace. When used with a compatible kernel, signals and ptrace rules are supported. When used without a compatible kernel (eg, on Ubuntu Touch for a few weeks or with upstream kernels), signal and ptrace rules are skipped (ie, you can use this userspace with other kernels without issue). Testing: * 14.04 system with current kernel (Touch, kernel doesn't have signal and ptrace mediation yet): * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: INPROGRESS (includes click-apparmor, apparmor-easyprof-ubuntu, exploratory manual testing, etc) * 14.04 system with previous kernel lacking signal and ptrace mediation
[Desktop-packages] [Bug 1302302] Re: [regression] Unity now only starts in software rendering mode (i965 Mesa driver can't load)
*** This bug is a duplicate of bug 1302264 *** https://bugs.launchpad.net/bugs/1302264 ** This bug is no longer a duplicate of bug 1302270 [regression] Poor performance with recent update with i965: libGL error: failed to open drm device: Permission denied ** This bug has been marked a duplicate of bug 1302264 systemd-logind assert failure: error.c:319: Assertion failed in nih_error_get: context_stack != NULL -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1302302 Title: [regression] Unity now only starts in software rendering mode (i965 Mesa driver can't load) Status in Compiz: New Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: After updating today Unity only starts in software rendering mode. I can tell because: 1. There's no dash blur. 2. Graphics performance is slow. 3. .xsession-errors says: libGL error: failed to open drm device: Permission denied libGL error: failed to load driver: i965 4. compiz is linked to the software driver: $ pmap `pidof compiz` | grep dri 7f9a1e386000 3256K r-x-- swrast_dri.so 7f9a1e6b4000 2048K - swrast_dri.so 7f9a1e8b4000 60K r swrast_dri.so 7f9a1e8c3000 32K rw--- swrast_dri.so ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140403-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Apr 4 10:46:53 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:220c] InstallationDate: Installed on 2014-04-03 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140331) MachineType: LENOVO 20AQCTO1WW ProcEnviron: LANGUAGE=en_AU:en TERM=xterm PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-22-generic.efi.signed root=UUID=a759a4aa-6f67-434e-8f5a-eae13c810c59 ro acpi_backlight=vendor quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10/2013 dmi.bios.vendor: LENOVO dmi.bios.version: GJET67WW (2.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET67WW(2.17):bd12/10/2013:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQCTO1WW dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Apr 4 10:46:12 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1034 vendor LGD xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1302302/+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 1302270] Re: [regression] Poor performance with recent update with i965: libGL error: failed to open drm device: Permission denied
*** This bug is a duplicate of bug 1302264 *** https://bugs.launchpad.net/bugs/1302264 ** This bug has been marked a duplicate of bug 1302264 systemd-logind assert failure: error.c:319: Assertion failed in nih_error_get: context_stack != NULL -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1302270 Title: [regression] Poor performance with recent update with i965: libGL error: failed to open drm device: Permission denied Status in Compiz: Confirmed Status in Unity: Confirmed Status in “systemd” package in Ubuntu: Confirmed Status in “xorg” package in Ubuntu: Confirmed Bug description: I rebooted into up to date trusty and noticed Unity was incredibly slow. I hadn't rebooted in a while, so I'm not sure what package caused the issue, though I'm guessing it is mesa (I saw i965 pci ids were ifdef'd in the Launchpad diff, but I didn't look super closely). ~/.xsession-errors has this to say: libGL error: failed to open drm device: Permission denied libGL error: failed to load driver: i965 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Apr 3 20:08:18 2014 DistUpgraded: 2013-11-04 08:48:34,282 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:215a] InstallationDate: Installed on 2011-06-28 (1010 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110425.2) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 5129CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-22-generic root=UUID=88689ad2-74b5-442c-9290-8ae60b63e16b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2013-11-04 (150 days ago) dmi.bios.date: 02/24/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 6QET64WW (1.34 ) dmi.board.name: 5129CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6QET64WW(1.34):bd02/24/2011:svnLENOVO:pn5129CTO:pvrThinkPadX201s:rvnLENOVO:rn5129CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 5129CTO dmi.product.version: ThinkPad X201s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Apr 3 19:38:17 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16404 vendor LEN xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1302270/+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 1290315] Re: After 'Switch user', entering password doesn't return to the session
Not actually your fault, we had a 20 days window between ubuntu37 and ubuntu38 in quantal where we indeed added that broken line... Not much we can do about it unfortunately as trying to find and fix existing containers config is almost certainly going to cause more problem than it'd resolve... -- 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/1290315 Title: After 'Switch user', entering password doesn't return to the session Status in “lightdm” package in Ubuntu: Invalid Status in “lxc” package in Ubuntu: Invalid Bug description: 1. Lock screen (ctrl-alt-l) 2. Click 'switch user' 3. Enter password to return to session 4. The greeter disappears as if the session is being restored, then it returns At 4, I should be logged in to my session. I switched vt manually (ctrl-alt-f7) to get back in. In my lightdm log, these lines: [+5871.21s] DEBUG: Activating VT 8 [+5871.21s] WARNING: Error using VT_ACTIVATE 8 on /dev/console: Inappropriate ioctl for device [+5871.21s] WARNING: Error using VT_WAITACTIVE 8 on /dev/console: Inappropriate ioctl for device [+5877.23s] DEBUG: Seat: Switching to existing greeter [+5877.23s] DEBUG: Activating VT 8 [+5877.23s] WARNING: Error using VT_ACTIVATE 8 on /dev/console: Inappropriate ioctl for device [+5877.23s] WARNING: Error using VT_WAITACTIVE 8 on /dev/console: Inappropriate ioctl for device were when I was trying from step 1 again to see if this bug was reproducible. It would not switch back to the greeter vt (vt8). I was just left on gnome-screensaver. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 Uname: Linux 3.13.0-16-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 10 11:00:45 2014 InstallationDate: Installed on 2012-10-07 (518 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007) LightdmConfig: [SeatDefaults] user-session=ubuntu greeter-session=unity-greeter SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2013-05-07 (307 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1290315/+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 1104230] Re: DisplayPort 1.2 MST support is missing in the Intel driver
Thanks for those details, it's good to finally see some documentation on what supports MST and what doesn't! I update the description to reflect the fact that you need 4th gen hardware to get DP 1.2 on Intel. ** Summary changed: - DisplayPort 1.2 MST support seems to be broken in the Intel driver + DisplayPort 1.2 MST support is missing in the Intel driver ** Description changed: I have two recent DisplayPort monitors, both supporting the 1.2 version of the standard and one containing an MST hub (DELL 2913WM). - I have my laptop (Lenovo ThinkPad X230, HD4000 Ivy Bridge) connected - over mini-displayport to the display containing the hub, then the second - display is plugged in that one over DisplayPort. + I have an Intel Haswell based NUC connected over mini-displayport to the + display containing the hub, then the second display is plugged in that + one over DisplayPort. DisplayPort 1.2 is enabled on the display containing the hub and the second display lights up fine but just works as a clone of the first display, without ever showing up in xrandr, dmesg or any other useful logs I could find. My understanding of MST is that the second display should show up as DP2 on my laptop so I can configure it as I would any other display. - ProblemType: Bug - DistroRelease: Ubuntu 13.04 - Package: xorg 1:7.7+1ubuntu4 - ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 - Uname: Linux 3.8.0-1-generic x86_64 - .tmp.unity.support.test.0: - - ApportVersion: 2.8-0ubuntu2 - Architecture: amd64 - CheckboxSubmission: 12108b8b8b67d760cdd84f1b9574e7f3 - CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f - CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] - CompositorRunning: compiz - Date: Thu Jan 24 12:13:30 2013 - DistUpgraded: Fresh install - DistroCodename: raring - DistroVariant: ubuntu - ExtraDebuggingInterest: Yes, including running git bisection searches - GraphicsCard: - Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Lenovo Device [17aa:21fa] - InstallationDate: Installed on 2012-09-02 (143 days ago) - InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120902) - MachineType: LENOVO 2306CTO - MarkForUpload: True - ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-1-generic root=UUID=f72ebb89-0931-4549-ab8f-10e9022e243b ro quiet splash acpi_osi=!Windows 2012 vt.handoff=7 - SourcePackage: xorg - UpgradeStatus: No upgrade log present (probably fresh install) - XorgConf: - Section Device -Identifier Card0 -Driver intel -Option AccelMethod sna - EndSection - dmi.bios.date: 09/11/2012 - dmi.bios.vendor: LENOVO - dmi.bios.version: G2ET82WW (2.02 ) - dmi.board.asset.tag: Not Available - dmi.board.name: 2306CTO - dmi.board.vendor: LENOVO - dmi.board.version: Not Defined - dmi.chassis.asset.tag: No Asset Information - dmi.chassis.type: 10 - dmi.chassis.vendor: LENOVO - dmi.chassis.version: Not Available - dmi.modalias: dmi:bvnLENOVO:bvrG2ET82WW(2.02):bd09/11/2012:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: - dmi.product.name: 2306CTO - dmi.product.version: ThinkPad X230 - dmi.sys.vendor: LENOVO - version.compiz: compiz 1:0.9.9~daily13.01.21-0ubuntu1 - version.ia32-libs: ia32-libs N/A - version.libdrm2: libdrm2 2.4.41-0ubuntu1 - version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1 - version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A - version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1 - version.xserver-xorg-core: xserver-xorg-core 2:1.13.1.901-0ubuntu2 - version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 - version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.0-0ubuntu1 - version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.19-0ubuntu2 - version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu1 - xserver.bootTime: Thu Jan 24 12:07:10 2013 - xserver.configfile: /etc/X11/xorg.conf - xserver.errors: - - xserver.logfile: /var/log/Xorg.0.log - xserver.version: 2:1.13.1.901-0ubuntu2 - xserver.video_driver: intel + UPDATE: Updated the bug report after it was pointed out that the + original test hardware, a Lenovo x230 isn't DP 1.2 capable. The same + test on hardware also fails, due to missing support for MST in the + driver. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1104230 Title: DisplayPort 1.2 MST support is missing in the Intel driver Status in “xserver-xorg-video-intel” package in Ubuntu: Confirmed Bug description: I have two recent DisplayPort monitors, both supporting the 1.2 version of the standard and one
[Desktop-packages] [Bug 1276082] Re: [FFE] Update network-manager-applet to 0.9.8.8
You don't need a FFe for a bugfix release, if all that's in there is indeed bugfix, go ahead and upload it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1276082 Title: [FFE] Update network-manager-applet to 0.9.8.8 Status in “network-manager-applet” package in Ubuntu: New Bug description: Update to 0.9.8.8 (bugfix only, minor release) beb16f4 release: bump version to 0.9.8.8 fc2276b release: update NEWS 3f82e3e nm-applet: change logging to use g_debug bc0f2be applet: redo the gnome-shell interaction code 7274f20 [l10n] Updated Catalan (Valencian) translation 0bf8dbe Tajik translation added 680a608 editor: do not gtk_widget_destroy() dialog on close signal fcf1298 man: some tools (like lexgrog) insist on '\-' in NAME section (rh #99090 469bc00 Updated Traditional Chinese translation(Hong Kong and Taiwan) 6c85101 nma-bt-device: fix creation of BT settings when creating connection 3763c08 Updated Portuguese translation c078bfb Updated Basque language d35fdf4 l10n: Update Japanese translation 2bd61f2 Updated Danish translation 6afbc81 Updated Traditional Chinese translation(Hong Kong and Taiwan) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1276082/+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 1099755] Re: [FFE] Upgrade wpa_supplicant from 1.0 to 2.1
Mathieu, can you give us an high level changelog for the new wpa? I'm mostly interested in potentially user visible features and anything that may require config changes (if any). Overall, I do agree that we should get 2.1 for 14.04, it's just unfortunate that this missed the freeze, so the sooner we get this in the better (so long as we're fairly sure it's regression free). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1099755 Title: [FFE] Upgrade wpa_supplicant from 1.0 to 2.1 Status in “wpa” package in Ubuntu: New Status in “wpa” package in Debian: New Bug description: New releases of wpa_supplicant are available: 1.1 (released 2012-11-06) and 2.0 (released 2013-01-12) and 2.1 (released 2014-02-04). 2.1 contains a number of bugfixes relevant to frequent disconnects some might be seeing on networks where there is a lot of roaming, some IBSS (ad-hoc) fixes, etc. http://lists.shmoo.com/pipermail/hostap/2014-February/029440.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1099755/+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 1099755] Re: [FFE] Upgrade wpa_supplicant from 1.0 to 2.1
That's a lot more changes than I like to see after Feature Freeze, however I believe that cherry-picking every single fixes and maintaining that for the next 5 years would lead to more problems than just getting the new upstream, so go ahead... FFe granted. ** Changed in: wpa (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1099755 Title: [FFE] Upgrade wpa_supplicant from 1.0 to 2.1 Status in “wpa” package in Ubuntu: Confirmed Status in “wpa” package in Debian: New Bug description: New releases of wpa_supplicant are available: 1.1 (released 2012-11-06) and 2.0 (released 2013-01-12) and 2.1 (released 2014-02-04). 2.1 contains a number of bugfixes relevant to frequent disconnects some might be seeing on networks where there is a lot of roaming, some IBSS (ad-hoc) fixes, etc. http://lists.shmoo.com/pipermail/hostap/2014-February/029440.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1099755/+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 1051935] Re: Fails with SystemError when too many files are open
Hello Alin, or anyone else affected, Accepted ubiquity into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/ubiquity/2.10.29 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: ubiquity (Ubuntu Precise) Status: In Progress = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to oneconf in Ubuntu. https://bugs.launchpad.net/bugs/1051935 Title: Fails with SystemError when too many files are open Status in “gdebi” package in Ubuntu: Fix Released Status in “oneconf” package in Ubuntu: Fix Released Status in “python-apt” package in Ubuntu: Fix Released Status in “ubiquity” package in Ubuntu: Fix Released Status in “gdebi” source package in Precise: Confirmed Status in “oneconf” source package in Precise: Confirmed Status in “python-apt” source package in Precise: Confirmed Status in “ubiquity” source package in Precise: Fix Committed Status in “gdebi” source package in Saucy: Fix Released Status in “oneconf” source package in Saucy: Fix Released Status in “python-apt” source package in Saucy: Fix Released Status in “ubiquity” source package in Saucy: Won't Fix Bug description: [Impact] * Failure to complete installation. [Test Case] * At times, apt cache can run out of file descriptors as seen in this bug and its duplicates. * There is no clear-cut way to reproduce it in ubiquity, but there is a significant amount of crash reports submit, which dropped off after the proposed fix has been applied. [Regression Potential] * The proposed fix has been well tested in trusty both automated manual testing and does not regress on any configuration. [Other Info] This error occurs each time I try to install a .deb file with Gdebi in Ubuntu 12.10, after the deb installation finishes. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: gdebi 0.8.5build1 ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Mon Sep 17 15:33:34 2012 ExecutablePath: /usr/share/gdebi/gdebi-gtk InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120914) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/gdebi-gtk --non-interactive /home/andrei/Downloads/gnomishdark-theme_201208014-1~webupd8_all.deb ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash TERM=unknown PythonArgs: ['/usr/bin/gdebi-gtk', '--non-interactive', '/home/andrei/Downloads/gnomishdark-theme_201208014-1~webupd8_all.deb'] SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1051935/+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 1259561] Update Released
The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1259561 Title: config timestamps not updated on hotplugging a output with hybrid graphics Status in “xorg-server” package in Ubuntu: Fix Released Status in “xorg-server” source package in Saucy: Fix Released Bug description: [Impact] In Precise and Saucy, we support hybrid graphics, but this issue prevents users from hotplugging external screens (the ones connected to the Intel card if nvidia is driving the display). The timestamps on the main screen are never updated when a output is plugged in to the gpu screen. This is also the bug for getting xorg-server 1.14.5 backported to saucy. [Test Case] Requires fix for #1224254 first. Plug in a screen after gsd started. The screen should turn on and enter mirror mode or extended mode. Wrong behavior: Screen stays off. Alternate testcase: check timestamps on xev, they should stay the same when plugging or unplugging, but update each time. [Regression Potential] Low, but not zero. We will also bump the micro release with the MRE, the ABI was been broken shortly after 1.14.4, but this was quickly discovered and fixed before 1.14.5rc1 was released. There's also a commit xfree86: Find primary entity when bus types are nominally different which I suspect could have broken driver loading in the optimus configuration, but we already have a different fix because I ran into the same bug after a similar fix before. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1259561/+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 1238410] Update Released
The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1238410 Title: Inconsistent cursor visibility with cursor plugin enabled Status in GNOME Desktop Common Files: Fix Released Status in X.Org X server: In Progress Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “xorg-server” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” source package in Saucy: Confirmed Status in “xorg-server” source package in Saucy: Fix Released Bug description: On fresh boots the greeter desktop may have the cursor visible or may not until mouse is moved. On a log out/in the cursor is almost always invisible until mouse is moved. (unless made visible in greeter screen, then visible on Desktop This is all well good, maybe some intentional aesthetics/design (https://bugzilla.gnome.org/show_bug.cgi?id=687791) , however sometimes the cursor never becomes visible. In that case hitting some keys or context menu can cause it to show, though most times a log out is needed. (with the removal of ctrl+alt+delete log out this means most users will need to either blindly find the session indicator or hit power button. When the g-s-d cursor plugin is disabled then the cursor is always visible, it the plugin has no use in an ubuntu session then maybe it should be default disabled There is also the possibility, particularly on ssd drives, of a login with no session indicator. This occasionally combines with no visible cursor. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu7 ProcVersionSignature: Ubuntu 3.11.0-12.18-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Fri Oct 11 00:38:16 2013 InstallationDate: Installed on 2013-10-03 (8 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131002) MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-desktop/+bug/1238410/+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 1197921] Update Released
The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pixman in Ubuntu. https://bugs.launchpad.net/bugs/1197921 Title: LibreOffice spreadsheet causes full Xorg crash with Anti-Aliasing enabled Status in Pixman: Fix Released Status in “libreoffice” package in Ubuntu: Invalid Status in “pixman” package in Ubuntu: Fix Released Status in “xorg-server” package in Ubuntu: Fix Released Status in “pixman” source package in Precise: Fix Released Status in “xorg-server” source package in Precise: New Status in “pixman” source package in Quantal: Fix Released Status in “xorg-server” source package in Quantal: New Status in “pixman” source package in Raring: Fix Released Status in “xorg-server” source package in Raring: New Status in “pixman” source package in Saucy: Fix Released Status in “xorg-server” source package in Saucy: Fix Released Bug description: [Impact] * Opening spreadsheets in libreoffice crashes X . [Test Case] * Open the attached document ( plantage-mai-only-empty.ods ) [Regression Potential] * n/a [Other Info] * Patch is backport from upstream - http://cgit.freedesktop.org/pixman/commit/?id=5e14da97f16e421d084a9e735be21b1025150f0c . * Alternate test case, http://cgit.freedesktop.org/pixman/commit/?id=2f876cf86718d3dd9b3b04ae9552530edafe58a1 To manage notifications about this bug go to: https://bugs.launchpad.net/pixman/+bug/1197921/+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 1068920] Update Released
The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1068920 Title: Pointer screen crossings broken in Xorg server 1.13.0 (regression) Status in X.Org X server: Fix Released Status in “xorg-server” package in Ubuntu: Fix Released Status in “xorg-server-lts-quantal” package in Ubuntu: Fix Released Status in “xorg-server” source package in Quantal: Fix Released Status in “xorg-server-lts-quantal” source package in Quantal: In Progress Bug description: [Impact] The Xorg server in quantal suffers from the following upstream regression for zaphod setups: https://bugs.freedesktop.org/show_bug.cgi?id=54654 [Test case] When you move the mouse into the second screen, it gets trapped there. When it gets to the edge where it should move back onto the first screen, it wraps around to the far edge of the second screen again. I've rebuilt xserver-xorg-core with the attached patch, which comes from the upstream bug above, and confirmed it fixes this issue. [Regression potential] slim, this has been upstream since 1.13.1 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1068920/+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 1212123] Update Released
The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1212123 Title: Erratic cursor movement when using Coordinate Transformation Matrix Status in “xorg-server” package in Ubuntu: Fix Released Status in “xorg-server-lts-quantal” package in Ubuntu: Invalid Status in “xorg-server-lts-quantal” source package in Precise: Fix Released Status in “xorg-server” source package in Quantal: Fix Released Bug description: [Impact] coordinate mapping is off when using a transformation matrix, needs an upstream patch to fix [Test case] 1. Boot into Ubuntu 12.04.2 live system 2. Expand the laptop display to the external one. For example, `xrandr --output eDP1 --auto --output HDMI1 --auto --right-of eDP1` 3. Restrict the movements of the touchscreen to the laptop display. For example, `xinput map-to-crtc 'ELAN Touchscreen' eDP1` P.S. `xinput map-to-crtc` will calculate and set Coordinate Transformation Matrix correspondingly. = Expected Result = I can operate the touchscreen on the laptop display as usual. = Actual Result = It becomes abnormal and shows erratic cursor movement. P.S. Ubuntu 13.04 is OK. [Regression potential] slim, this has been upstream since 1.13.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1212123/+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 805154] Re: gdm-simple-slave crashed with SIGSEGV in _nss_compat_getpwnam_r()
Hello Blümchen, or anyone else affected, Accepted gdm into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/gdm/3.0.4-0ubuntu15.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gdm (Ubuntu Precise) Status: In Progress = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/805154 Title: gdm-simple-slave crashed with SIGSEGV in _nss_compat_getpwnam_r() Status in “gdm” package in Ubuntu: Fix Released Status in “gdm” source package in Oneiric: Won't Fix Status in “gdm” source package in Precise: Fix Committed Bug description: SRU justification: [Impact] * With automatic login enabled in /etc/gdm/custom.conf, gdm crashes instead of logging in, and doesn't respawn, dropping to a text console instead. [Test Case] * install gdm and choose it as the default display manager at the debconf prompt * create /etc/gdm/custom.conf with contents: [daemon] AutomaticLoginEnable=true AutomaticLogin=some-username (where some-username is a user on the system) * Reboot (or stop the previous display manager and start gdm) * In gdm in precise-updates, instead of logging in, gdm crashes, the system drops to a text console, and a gdm-simple-slave segfault is recorded in dmesg. [Regression Potential] * Minimal. The change consists only of adding a missing NULL parameter check. Original description: Chrash happend while trying to change a desktop-icon. Searching the icon in a hidden folder . in the user directory. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: gdm 3.0.4-0ubuntu3 ProcVersionSignature: Ubuntu 3.0-2.3-generic-pae 3.0.0-rc4 Uname: Linux 3.0-2-generic-pae i686 NonfreeKernelModules: fglrx Architecture: i386 Date: Sun Jul 3 01:25:08 2011 ExecutablePath: /usr/lib/gdm/gdm-simple-slave InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha i386 (20110531.1) ProcCmdline: /usr/lib/gdm/gdm-simple-slave --display-id /org/gnome/DisplayManager/Display2 ProcEnviron: LANGUAGE=de_AT:de PATH=(custom, no user) LANG=de_AT.UTF-8 SegvAnalysis: Segfault happened at: 0xb77405b7 _nss_compat_getpwnam_r+55:movzbl (%edx),%eax PC (0xb77405b7) ok source (%edx) (0x) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gdm StacktraceTop: _nss_compat_getpwnam_r () from /lib/i386-linux-gnu/libnss_compat.so.2 getpwnam_r () from /lib/i386-linux-gnu/libc.so.6 getpwnam () from /lib/i386-linux-gnu/libc.so.6 ?? () ?? () Title: gdm-simple-slave crashed with SIGSEGV in _nss_compat_getpwnam_r() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/805154/+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 1000325] Update Released
The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1000325 Title: After unmounting i got error see screenshot Status in “nautilus” package in Ubuntu: Fix Released Status in “nautilus” source package in Saucy: Fix Released Bug description: * Impact: unmounting/ejecting devices leads to annoying error dialogs, it also triggers some issues with gvfs backend * Test case: - eject/unmount devices or mounts in nautilus, check that there is no error display (nor from nautilus nor whoopsie) * Regression potential: - check that mounts/device get correctly unmounted still To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1000325/+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 1241736] Update Released
The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1241736 Title: Wrong menu is being shown if mouse not moved after area selection Status in Nautilus: Fix Released Status in “nautilus” package in Ubuntu: Fix Released Status in “nautilus” source package in Saucy: Fix Released Bug description: * Impact: the wrong menu is open if you context click without moving the cursor * Test Case What I did: (See attached video.) In both tests I've selected two files and right-clicked one of them. In the first case I didn't move the cursor between releasing LMB and pressing RMB; in the second case, I did. What happened: In the first case Nautilus acted like I've right-clicked empty space in the folder, even though I've clicked a file. In the second case it acted normally - like I've right-clicked a file. What was expected: In both cases Nautilus should act like I've right-clicked a file. * Regression potential: right click on files, folders and backgroud, check that you get the menu corresponding to the element you selected -- Additional info: Ubuntu 13.04, GNOME nautilus 3.6.3 (1:3.6.3-0ubuntu16). I was really confused. I've tried few times and it looked like I can't open right-click menu related to few files. I have found solution in about 15s to 1m, but If I didn't knew anything about mouse events (and average user doesn't have that knowledge) it would last longer. Upstream link: https://bugzilla.gnome.org/show_bug.cgi?id=710473 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1241736/+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 1211887] Update Released
The verification of this Stable Release Update has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regresssions.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to webkit in Ubuntu.
https://bugs.launchpad.net/bugs/1211887
Title:
software-center crashed with signal 5 in _XReadEvents()
Status in Webkit Direct Port:
Fix Released
Status in “software-center” package in Ubuntu:
Invalid
Status in “webkit” package in Ubuntu:
Invalid
Status in “webkitgtk” package in Ubuntu:
Fix Released
Status in “software-center” source package in Saucy:
Invalid
Status in “webkit” source package in Saucy:
Fix Released
Status in “webkitgtk” source package in Saucy:
Invalid
Bug description:
* Impact: software-center hits Xerrors quite often
* Test case:
run software-center, it should be stable (or watch the error buckets on
https://errors.ubuntu.com/problem/94f7beb32c9a9172de3f9281691510762d655d47)
* Regression potential:
check that webkit clients are stable (software-center, epiphany-browser,
yelp, empathy...)
--
Everytime I open software centre after about 30 sec. it crashes
Terminal output
kenn@kenn-520-1138cb:~$ software-center
/usr/lib/python2.7/dist-packages/gi/types.py:226: RuntimeWarning: Mixin class
softwarecenter.ui.gtk3.widgets.stars.StarRenderer is an old style class, please
update this to derive from object.
RuntimeWarning)
/usr/lib/python2.7/dist-packages/gi/types.py:226: RuntimeWarning: Mixin class
softwarecenter.ui.gtk3.widgets.stars.ShapeStar is an old style class, please
update this to derive from object.
RuntimeWarning)
2013-08-13 13:18:59,709 - softwarecenter.ui.gtk3.app - INFO - setting up
proxy 'None'
2013-08-13 13:19:00,402 - softwarecenter.backend.reviews - WARNING - Could
not get usefulness from server, no username in config file
2013-08-13 13:19:00,403 - softwarecenter.plugin - INFO - activating plugin
'module 'webapps_activation' from
'/usr/share/software-center/softwarecenter/plugins/webapps_activation.pyc''
2013-08-13 13:19:00,407 - softwarecenter.fixme - WARNING - logs to the root
logger: '('/usr/lib/python2.7/dist-packages/gi/importer.py', 51, 'find_module')'
2013-08-13 13:19:00,407 - root - ERROR - Could not find any typelib for
LaunchpadIntegration
2013-08-13 13:19:00,438 - softwarecenter.db.pkginfo_impl.aptcache - INFO -
aptcache.open()
(software-center:15225): Gdk-ERROR **: The program 'software-center' received
an X Window System error.
This probably reflects a bug in the program.
The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
(Details: serial 3604 error_code 9 request_code 62 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/breakpoint trap (core dumped)
kenn@kenn-520-1138cb:~$
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: software-center 13.08-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-1.4-generic 3.11.0-rc4
Uname: Linux 3.11.0-1-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.12-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Tue Aug 13 12:55:55 2013
ExecutablePath: /usr/share/software-center/software-center
InstallationDate: Installed on 2013-07-10 (33 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130709)
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-center
ProcEnviron:
LANGUAGE=en_CA:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_CA.UTF-8
SHELL=/bin/bash
Signal: 5
SourcePackage: software-center
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
_XReadEvents () from /usr/lib/x86_64-linux-gnu/libX11.so.6
?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
cairo_surface_flush () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
Title: software-center crashed with signal 5 in _XReadEvents()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
To manage notifications about this bug go to:
https://bugs.launchpad.net/webkit/+bug/1211887/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to :
[Desktop-packages] [Bug 1104230] Re: DisplayPort 1.2 MST support seems to be broken in the Intel driver
No, MST still isn't supported properly in current trusty. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1104230 Title: DisplayPort 1.2 MST support seems to be broken in the Intel driver Status in “xserver-xorg-video-intel” package in Ubuntu: Invalid Bug description: I have two recent DisplayPort monitors, both supporting the 1.2 version of the standard and one containing an MST hub (DELL 2913WM). I have my laptop (Lenovo ThinkPad X230, HD4000 Ivy Bridge) connected over mini-displayport to the display containing the hub, then the second display is plugged in that one over DisplayPort. DisplayPort 1.2 is enabled on the display containing the hub and the second display lights up fine but just works as a clone of the first display, without ever showing up in xrandr, dmesg or any other useful logs I could find. My understanding of MST is that the second display should show up as DP2 on my laptop so I can configure it as I would any other display. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.8-0ubuntu2 Architecture: amd64 CheckboxSubmission: 12108b8b8b67d760cdd84f1b9574e7f3 CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Thu Jan 24 12:13:30 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21fa] InstallationDate: Installed on 2012-09-02 (143 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120902) MachineType: LENOVO 2306CTO MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-1-generic root=UUID=f72ebb89-0931-4549-ab8f-10e9022e243b ro quiet splash acpi_osi=!Windows 2012 vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section Device Identifier Card0 Driver intel Option AccelMethod sna EndSection dmi.bios.date: 09/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET82WW (2.02 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET82WW(2.02):bd09/11/2012:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.9~daily13.01.21-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.41-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.1.901-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.19-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu1 xserver.bootTime: Thu Jan 24 12:07:10 2013 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.1.901-0ubuntu2 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1104230/+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 1196523] Re: gedit crashed with SIGSEGV in magazine_chain_pop_head()
Hello Mitsuya, or anyone else affected, Accepted gtk+3.0 into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/gtk+3.0/3.8.6-0ubuntu3.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gtk+3.0 (Ubuntu Saucy) Status: Triaged = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1196523 Title: gedit crashed with SIGSEGV in magazine_chain_pop_head() Status in Light-Weight Text Editor for Gnome: Confirmed Status in “gedit” package in Ubuntu: Invalid Status in “gtk+3.0” package in Ubuntu: Fix Committed Status in “gedit” source package in Saucy: Invalid Status in “gtk+3.0” source package in Saucy: Fix Committed Status in “gedit” package in Fedora: Unknown Bug description: * Impact: the text editor segfaults when using some input methods * Test Case: Enable japanese input methods and input characters between on this document --- # # AUTHOR EMAIL@ADDRESS, YEAR. # msgid msgstr Project-Id-Version: 0\n POT-Creation-Date: 2012-10-31T14:54:16\n PO-Revision-Date: 2012-10-31T14:54:16\n Last-Translator: Automatically generated\n Language-Team: None\n MIME-Version: 1.0\n Content-Type: application/x-publican; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n --- * Regression potential: check that there is no stability issues in gedit To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1196523/+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 1197395] Re: /run/user/$ID/pulse owned by root and not by the user
Hello Davide, or anyone else affected,
Accepted systemd into saucy-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/systemd/204-0ubuntu19.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Your feedback will aid us getting this update
out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed. In either case, details of your testing will help
us make a better decision.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!
** Changed in: systemd (Ubuntu Saucy)
Status: In Progress = Fix Committed
** Tags added: verification-needed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1197395
Title:
/run/user/$ID/pulse owned by root and not by the user
Status in “pulseaudio” package in Ubuntu:
Invalid
Status in “systemd” package in Ubuntu:
Fix Released
Status in “pulseaudio” source package in Saucy:
Invalid
Status in “systemd” source package in Saucy:
Fix Committed
Status in “systemd” package in Fedora:
Unknown
Bug description:
I'm experiencing this problem with Ubuntu Saucy. Some times, when I start a
media player (I use Musique), it freezes, as it finds that it cannot write into
/run/user/$ID/pulse.
If I change the owner of that directory to me, the media player starts as
usual and is able to play music.
I've never had this problem with previous versions of Ubuntu.
Someone says that running PulseAudio with the -D argument changes the owner
of that directory, but I didn't try.
This is before manually changing the owner of that directory:
$ musique
Failed to create secure directory (/run/user/1000/pulse): Permission denied+
... # it doesn't crash, it keeps waiting
If needed:
(dmesg attached)
lspci:
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory
Controller Hub (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset
Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset
Integrated Graphics Controller (rev 07)
00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI
Controller #4 (rev 03)
00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI
Controller #5 (rev 03)
00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI
Controller #6 (rev 03)
00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI
Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio
Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1
(rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2
(rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3
(rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5
(rev 03)
00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6
(rev 03)
00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI
Controller #1 (rev 03)
00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI
Controller #2 (rev 03)
00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI
Controller #3 (rev 03)
00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI
Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4
port SATA Controller [AHCI mode] (rev 03)
02:00.0 Network controller: Qualcomm Atheros AR9285 Wireless Network Adapter
(PCI-Express) (rev 01)
85:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8072 PCI-E
Gigabit Ethernet Controller (rev 10)
From /var/log/syslog:
Jul 3 14:44:12 Davideddu-Laptop pulseaudio[11387]: [pulseaudio] core-util.c:
Failed to create secure directory (/run/user/1000/pulse): Permission denied
Jul 3 14:44:12 Davideddu-Laptop pulseaudio[11387]: [pulseaudio] main.c:
User-configured server at
{781995e0a8db2617790d55ca51c37499}unix:/run/user/1000/pulse/native, refusing to
start/autospawn.
Jul 3 14:46:08 Davideddu-Laptop pulseaudio[11443]: [pulseaudio] core-util.c:
Failed to create secure
[Desktop-packages] [Bug 1235625] Re: fix legacy keygrabber for gnome-ish sessions
Hello Tim, or anyone else affected, Accepted gnome-settings-daemon into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/gnome- settings-daemon/3.8.5-0ubuntu11.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gnome-settings-daemon (Ubuntu Saucy) Status: In Progress = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1235625 Title: fix legacy keygrabber for gnome-ish sessions Status in “gnome-settings-daemon” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” source package in Saucy: Fix Committed Bug description: [ Description ] In Saucy, media keys in gnome-ish (using gnome-settings-daemon) sessions only work when gnome-panel or Unity are in use, as the code path checks for their names on the bus. They ought to work for all sessions. [ Fix ] Change the logic so that the keygrabber is started all the time except under Shell sessions. [ QA ] In a session that runs gnome-settings-daemon but neither panel nor shell (xfce or Openbox? or a custom xmonad), check that media keys now work. [ Regression potential ] Changes activation criteria for the legacy keygrabber. Check it still works in Unity, panel and that the new method works under shell. [ Original report ] The previous patch to fix the legacy keygrabber was Unity specific and breaks on gnome-ish sessions that require it, instead we should load the legacy keygrabber for any session that is not gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1235625/+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 1094319] Re: p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared o
Hello Rodney, or anyone else affected, Accepted gnome-keyring into quantal-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/gnome- keyring/3.6.1-0ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gnome-keyring (Ubuntu Quantal) Status: In Progress = Fix Committed ** Tags removed: verification-failed ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1094319 Title: p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome- keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring- pkcs11.so: cannot open shared object file: No such file or directory Status in “gnome-keyring” package in Ubuntu: Fix Released Status in “gnome-keyring” source package in Precise: In Progress Status in “gnome-keyring” source package in Quantal: Fix Committed Bug description: [Impact] On a 64-bit system, this message can cause severe problems when running some 32-bit applications, such as wine. For example, attempting to run winecfg results in an infinite loop of these messages being printed to the console. The p11-kit module needs to be moved to a separate multi-arch capable package, so that both arch versions may be installed. [Test Case] Install package(s) verify wine can run under amd64 [Regression Potentional] Minimal, several rdepends build testing have been completed successfully and nothing in the keyring code is attempting to dlopen any hardcoded library paths. [Additional] ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-keyring 3.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.7.0-7.15-generic 3.7.0 Uname: Linux 3.7.0-7-generic x86_64 ApportVersion: 2.7-0ubuntu2 Architecture: amd64 Date: Fri Dec 28 12:39:36 2012 InstallationDate: Installed on 2012-10-21 (67 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: gnome-keyring UpgradeStatus: Upgraded to raring on 2012-12-24 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1094319/+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 859600] Re: Please convert gnome-keyring to multiarch
Hello Riku, or anyone else affected, Accepted gnome-keyring into quantal-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/gnome- keyring/3.6.1-0ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gnome-keyring (Ubuntu Quantal) Status: In Progress = Fix Committed ** Tags removed: verification-failed ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/859600 Title: Please convert gnome-keyring to multiarch Status in “gnome-keyring” package in Ubuntu: Fix Released Status in “gnome-keyring” source package in Precise: Confirmed Status in “gnome-keyring” source package in Quantal: Fix Committed Status in “gnome-keyring” source package in Raring: Fix Released Status in “gnome-keyring” package in Debian: New Bug description: [Impact] Several applications are relying on this package as seen in comments 5 and 6. [Test case] Attempt to install both i386/amd64 versions of libp11-kit-gnome-keyring and preferably verify if the reported applications in this bug are able to run successfully. 1. Run the command 'wine notepad'. Notice the warning from p11-kit. 2. sudo apt-get install libp11-kit-gnome-keyring:i386 3. Run the command 'wine notepad' again. Notice that the warning is gone. [Regression Potential] Minimal, several rdepends build testing have been completed successfully and nothing in the keyring code is attempting to dlopen any hardcoded library paths. gnome-keyring is still installing libraries to /usr/lib instead of the multarch compatible /usr/lib/$(DEB_HOST_MULTIARCH) directory. The attached patch does the conversion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/859600/+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 1198315] Re: [network]: gnome-control-center SIGSEGV in append_escaped_text() (invalid utf8 ssid name)
Hello Cedric, or anyone else affected, Accepted gnome-control-center into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/gnome- control-center/1:3.6.3-0ubuntu45.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gnome-control-center (Ubuntu Saucy) Status: In Progress = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1198315 Title: [network]: gnome-control-center SIGSEGV in append_escaped_text() (invalid utf8 ssid name) Status in GNOME Control Center: New Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “gnome-control-center” source package in Saucy: Fix Committed Bug description: [Impact] Any user who tries to open the gnome-control-center, having a wireless network with extended characters (such as ö, ü, etc.) in range, or saved in connections in NetworkManager. [Test Case] 1) With a wireless network in range or saved, named üö or with any such character in the SSID, try to open gnome-control-center network panel. With the patch, the panel opens. Without the patch, the panel doesn't open, gnome-control-center crashes. [Regression Potential] This changes the way the wireless network SSIDs are displayed in the UI. They will retain the method in which they are sorted, but in the event that multiple SSIDs with very similar names but with a different, complex character in the name in the same location (e.g. ABC vs. ABX, if C and X were special characters), they would both show with ? in place of any special character that cannot be represented in UTF-8. In the previous example; ABC and ABX would be in the right order, but both would be displayed as AB?. --- Got this on saucy ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu29 ProcVersionSignature: Ubuntu 3.10.0-2.9-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Fri Jul 5 21:43:59 2013 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-03-14 (113 days ago) InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MarkForUpload: True ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x7f9814028a20 g_markup_escape_text+80: movzbl (%rbx),%eax PC (0x7f9814028a20) ok source (%rbx) (0x7f97df5a8000) in non-readable VMA region: 0x7f97df5a8000-0x7f97df7a7000 ---p /usr/lib/libnm-gtk.so.0.0.0 destination %eax ok SegvReason: reading VMA /usr/lib/libnm-gtk.so.0.0.0 Signal: 11 SourcePackage: gnome-control-center StacktraceTop: g_markup_escape_text () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/control-center-1/panels/libnetwork.so ?? () from /usr/lib/control-center-1/panels/libnetwork.so g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: [network]: gnome-control-center crashed with SIGSEGV in g_markup_escape_text() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo usr_lib_gnome-control-center: activity-log-manager0.9.6-0ubuntu1 deja-dup27.3.1-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130625-0ubuntu1 gnome-control-center-unity 1.3daily13.06.14.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1198315/+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 1225514] Update Released
The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1225514 Title: adding keyboard layouts no longer seems to update xkb correctly Status in “gnome-screensaver” package in Ubuntu: Fix Released Status in “gnome-screensaver” source package in Saucy: Fix Released Bug description: gnome-screensaver - * Impact: layouts are missing from the unlock screen which might makes difficult to unlock * Test case: Through gnome-control-center, add a few different XKB input sources (e.g., US, French, German, Russian), then lock the screen. Expected results: The lock screen dialog keyboard switching indicator should cycle through all of the XKB (non-IBus) input sources. Actual results: It only allows cycling through at most two XKB layouts, the currently active one, and the US layout. * Regression potential: The changes affect the list from which gnome-screensaver allows cycling, and may affect which layouts are available for unlocking the session. = I'm not sure if this is caused by gnome-control-center, or ibus 1.5, but in saucy, adding or modifying the keyboard layouts doesn't seem to properly update xkb any longer. For example, I can have both French (Canada) and English (US) configured, but xkl_config_rec_get_from_server() will only return 'ca' and xkl_engine_get_num_groups() will return 1, instead of 2. I believe this is also causing the keyboard layouts to not appear on the login screen. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu36 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Sat Sep 14 16:35:50 2013 InstallationDate: Installed on 2012-11-13 (304 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: Upgraded to saucy on 2013-08-19 (26 days ago) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20130903-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3daily13.06.19~13.04-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1225514/+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 1241881] Update Released
The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1241881 Title: gnome-keyring depends on transitional package libgcr-3-1 Status in “gnome-keyring” package in Ubuntu: Fix Committed Status in “seahorse” package in Ubuntu: Fix Released Status in “gnome-keyring” source package in Saucy: Fix Released Status in “seahorse” source package in Saucy: Triaged Bug description: According its package description, libgcr-3-1 version 3.8.2-4 in Saucy Salamander is a transitional package that should be safe to remove. However, an attempt to remove the package reveals that gnome-keyring (version 3.8.2-0ubuntu3) depends on it. I cannot tell if removing the dependency from gnome-keyring was forgotten or libgcr-3-1 has been wrongfully marked as transitional, but the latter seems highly unlikely. Either way this is a problem that should be fixed. [Rationale] People should be able to remove transitional packages without removing the packages that depend on their replacements. This is forbidding people from removing libgcr-3-1 without removing gnome-keyring as well. [Test Case] Install the gnome-keyring package, and then try removing the transitional libgcr-3-1 package. It forces the removal of gnome-keyring, even though gnome-keyring should depend on libgcr-base-3-1 instead. [Regression Potential] None. This is just a simple dependency change. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-keyring 3.8.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Sat Oct 19 01:43:15 2013 InstallationDate: Installed on 2010-09-07 (1137 days ago) InstallationMedia: Xubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901) MarkForUpload: True SourcePackage: gnome-keyring UpgradeStatus: Upgraded to saucy on 2013-10-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1241881/+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 926763] Re: Cannot install local packages (.deb files) without network connection (offline)
Hello dronus, or anyone else affected, Accepted software-center into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/software- center/5.2.10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: software-center (Ubuntu Precise) Status: Triaged = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/926763 Title: Cannot install local packages (.deb files) without network connection (offline) Status in “software-center” package in Ubuntu: Fix Released Status in “software-center” source package in Precise: Fix Committed Status in “software-center” source package in Quantal: Won't Fix Bug description: [Impact] * On Ubuntu, when the software-center is invoked to install a package from a local .deb file, the Install-Button is deactivated while not connected to the internet. [Regression Potential] I dont see any regression potential here. This has been merged into upstream. [Test Case] 1. Download .deb file ( apt-get download mpg123) 2. Disconnect from internet 3. Attempt to install .deb by double-clicking a. Actual Results: the 'install' button is greyed out and not clickable. b. Expected Results: should be able to install normally. [Other Info] Known Workaround: Install with dpkg from CLI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/926763/+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 1245874] Update Released
The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/1245874 Title: Java JAR files are opened in file-roller instead of Java Runtime (remove application/x-jar=file-roller.desktop from /etc/gnome/defaults.list) Status in “desktop-file-utils” package in Ubuntu: Fix Committed Status in “desktop-file-utils” source package in Saucy: Fix Released Status in “desktop-file-utils” package in Baltix: Fix Committed Bug description: * Impact: Java JAR files are opened in file-roller instead of Java Runtime Environment * Steps to reproduce: Install JRE, for example Oracle Java7 In File manager (nautilus) click on Jar file, for example download Minecraft.jar file from https://s3.amazonaws.com/Minecraft.Download/launcher/Minecraft.jar Actual result: minecraft.jar file is opened in file-roller instead of Java Runtime Environment (but Java Runtime Environment can be choosed by right-click-Open With-Java7 Runtime) Expected result: .jar file should be opened in Java Runtime * Regression potential: verify that clicking on java types in nautilus works as it should To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1245874/+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 1236601] Re: wrong background color when editing icons on desktop
Hello Marc, or anyone else affected, Accepted nautilus into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/nautilus/1:3.8.2-0ubuntu2.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: nautilus (Ubuntu Saucy) Status: In Progress = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1236601 Title: wrong background color when editing icons on desktop Status in Nautilus: Fix Released Status in “nautilus” package in Ubuntu: Fix Released Status in “nautilus” source package in Saucy: Fix Committed Bug description: * Impact: renaming icons on the desktop has text contrast issues * Test case: rename an icon on the desktop, move the cursor, see if there is a white background color making the text easy to read or not * Regression potential: check that the rename UI looks as it should - When creating or renaming an icon on the desktop, nautilus no longers colors the background ellipse white, resulting in text being unreadable. See attached screenshot for comparison between Raring and Saucy. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Mon Oct 7 17:24:39 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'1004x670+867+75' InstallationDate: Installed on 2012-11-13 (328 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to saucy on 2013-08-19 (49 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1236601/+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 1252484] Re: Possible data loss when restarting in the middle of a deleted file
Hello Michael, or anyone else affected, Accepted duplicity into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/duplicity/0.6.21-0ubuntu4.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: duplicity (Ubuntu Saucy) Status: New = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1252484 Title: Possible data loss when restarting in the middle of a deleted file Status in Duplicity - Bandwidth Efficient Encrypted Backup: Fix Committed Status in “duplicity” package in Ubuntu: Fix Released Status in “duplicity” source package in Lucid: New Status in “duplicity” source package in Precise: New Status in “duplicity” source package in Quantal: New Status in “duplicity” source package in Raring: New Status in “duplicity” source package in Saucy: Fix Committed Bug description: This was recently fixed in duplicity trunk. But I'm filing a bug for paperwork purposes and for Ubuntu SRUs. [Impact] When restarting a backup, duplicity may accidentally skip the first 65k chunk of one of the source files. This means that when it is restored, it will be incomplete/corrupted, resulting in data loss. [Test Case] mkdir /tmp/source dd if=/dev/urandom of=/tmp/source/bigfile bs=1024 count=5000 # This next command will intentionally fail after the second volume! duplicity full /tmp/source file:///tmp/backup --vol 1 --fail 2 --no-encryption mv /tmp/source/bigfile /tmp/source/newfile duplicity full /tmp/source file:///tmp/backup --no-encryption duplicity restore file:///tmp/backup /tmp/restore --no-encryption # This next line will say the files differ if the bug is present diff /tmp/source/newfile /tmp/restore/newfile [Regression Potential] It's a relatively small patch, only affecting the specific case of restarting a backup when the file we were in the middle of is no longer there. I'd say minor regression potential. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1252484/+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 1241007] Update Released
The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgnome-media-profiles in Ubuntu. https://bugs.launchpad.net/bugs/1241007 Title: FTBFS in saucy Status in “libgnome-media-profiles” package in Ubuntu: Fix Released Bug description: Not sure if libgnome-media-profiles will be replaced in Ubuntu Saucy but I fixed ftbfs. See ftbs buildlog (2013-10-16): https://launchpadlibrarian.net/153893423/buildlog_ubuntu-saucy-arm64 .libgnome-media-profiles_3.0.0-1ubuntu1_FAILEDTOBUILD.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgnome-media-profiles/+bug/1241007/+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 1248578] Re: Adding printer from commandline does not work anymore after upgrade to 13.10
Hello Matthias, or anyone else affected, Accepted cups into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/cups/1.7.0~rc1-0ubuntu5.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1248578 Title: Adding printer from commandline does not work anymore after upgrade to 13.10 Status in “cups” package in Ubuntu: Fix Released Status in “cups” source package in Saucy: Fix Committed Bug description: In Ubuntu 13.10 I can't add printers from the commandline. For example when I use the following command as root: lpadmin -p i44hpneu -m drv:///hpcups.drv/hp-laserjet_4250-pcl3.ppd -D xxx -L xxx -E -v socket://my-printer-url Then the printer i44hpneu is created but it does not work. Another symptom is that no /etc/cups/ppd/i44hpneu.ppd file is created. The model/driver is listed in lpinfo -m, so the printer-driver-hpcups package appears to have installed correctly. Adding printers from the GUI or the cups webpage is working. Ubuntu version 13.04 and earlier work too. (I'm mainting around 20 linux PCs so automating printer installation from the commandline is a very convenient tool as I can prepare scripts to do all the setup). [Impact] Very important feature for administrators of print servers, especially head-less servers are not working, causing major problems for the admin: 1. Setting up print queues with lpadmin, specifying the PPD/driver with the -m option does not work, leading to a raw queue. 2. Setting up printers with the web interface of CUPS (http://localhost:631/) does not work. [Test Case] Run the command lpadmin -p test -E -v file:/dev/null -m drv:///sample.drv/laserjet.ppd This should create a print queue with the generic LaserJet PPD (PCL 5e printer). The PPD should be in /etc/cups/ppd/test.ppd. What you get is a raw queue without the PPD. The proposed package fixes this. The same command correctly creates a print queue with PPD. [Regression Potential] Very low, as only a few lines are modified in the code for lpadmin and for the appropriate part of the web interface. The CUPS daemon and the CUPS library are not modified. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: cups 1.7.0~rc1-0ubuntu5 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: openafs nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Nov 6 15:55:40 2013 InstallationDate: Installed on 2013-02-13 (266 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) Lpstat: device for i44canon: socket://i44canon.info.uni-karlsruhe.de device for i44hp201: socket://i44hp201.info.uni-karlsruhe.de device for i44hp4250: socket://i44hp4250.info.uni-karlsruhe.de device for i44hpneu: socket://i44hpneu.info.uni-karlsruhe.de device for PDF: cups-pdf:/ MachineType: FUJITSU ESPRIMO P910 MarkForUpload: True Papersize: a4 ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=0de5b9f6-e317-48be-83f8-90ee01c66888 ro quiet splash SourcePackage: cups UpgradeStatus: Upgraded to saucy on 2013-11-05 (0 days ago) dmi.bios.date: 12/17/2012 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V4.6.5.3 R1.19.0 for D3162-A1x dmi.board.name: D3162-A1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3162-A1 dmi.chassis.type: 6 dmi.chassis.vendor: FUJITSU dmi.chassis.version: C$PXW6 dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV4.6.5.3R1.19.0forD3162-A1x:bd12/17/2012:svnFUJITSU:pnESPRIMOP910:pvr:rvnFUJITSU:rnD3162-A1:rvrS26361-D3162-A1:cvnFUJITSU:ct6:cvrC$PXW6: dmi.product.name: ESPRIMO P910 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1248578/+subscriptions --
[Desktop-packages] [Bug 1231778] Re: wifi not working on Saucy Salamander
Hello Federico, or anyone else affected,
Accepted apparmor into saucy-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/apparmor/2.8.0-0ubuntu31.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Your feedback will aid us getting this update
out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed. In either case, details of your testing will help
us make a better decision.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!
** Changed in: apparmor (Ubuntu Saucy)
Status: In Progress = Fix Committed
** Tags added: verification-needed
--
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/1231778
Title:
wifi not working on Saucy Salamander
Status in Enablement project for the Toshiba AC100 NetBook:
New
Status in AppArmor Linux application security framework:
Fix Committed
Status in “apparmor” package in Ubuntu:
Fix Released
Status in “network-manager” package in Ubuntu:
Invalid
Status in “apparmor” source package in Saucy:
Fix Committed
Status in “network-manager” source package in Saucy:
Invalid
Status in “apparmor” source package in Trusty:
Fix Released
Status in “network-manager” source package in Trusty:
Invalid
Bug description:
[Impact]
On older kernels that are missing certain AppArmor patches related to
AppArmor D-Bus mediation, the presence of dbus rules in the binary
AppArmor policy will result in policy load failures and, as a result,
applications may run unconfined. On newer kernels that are missing the
same patches mentioned above, the policy load will succeed but the
dbus rules will be quietly ignored.
[Automated Test Case]
* test_lp1231778 has been added to QRT's test-apparmor.py script
* Run the test under the latest Saucy, Raring, and Lucid kernels to excercise
all possible test load scenarios
[Manual Test Case]
* Install and reboot into older, unpatched mainline kernel (such as
3.1.10-030110-generic)
* Bad test results on the mainline 3.1.10 kernel:
$ echo /t { dbus, } | sudo apparmor_parser -r
Cache read/write disabled: /sys/kernel/security/apparmor/features interface
file missing. (Kernel needs AppArmor 2.4 compatibility patch.)
Warning from stdin (line 1): apparmor_parser: cannot use or update cache,
disable, or force-complain via stdin
apparmor_parser: Unable to replace /t. Profile doesn't conform to protocol
* Good test results on the mainline 3.1.10 kernel with a patched
apparmor_parser:
$ echo /t { dbus, } | sudo apparmor_parser -r
Cache read/write disabled: /sys/kernel/security/apparmor/features interface
file missing. (Kernel needs AppArmor 2.4 compatibility patch.)
Warning from stdin (line 1): apparmor_parser: cannot use or update cache,
disable, or force-complain via stdin
Warning from stdin (stdin line 2): profile /t dbus rules not enforced
* Install and reboot into newer, unpatched mainline kernel (such as
3.12.0-031200-generic)
* Bad test results on the mainline 3.12.0 kernel:
$ echo /t { dbus, } | sudo apparmor_parser -r
Warning from stdin (line 1): apparmor_parser: cannot use or update cache,
disable, or force-complain via stdin
* Good test results on the mainline 3.12.0 kernel with a patched
apparmor_parser:
$ echo /t { dbus, } | sudo apparmor_parser -r
Warning from stdin (line 1): apparmor_parser: cannot use or update cache,
disable, or force-complain via stdin
Warning from stdin (stdin line 2): profile /t dbus rules not enforced
* Reboot into Ubuntu 3.11.0-12-generic kernel
* Good test results on the Ubuntu 3.11.0-12-generic kernel with or without a
patched apparmor_parser:
$ echo /t { dbus, } | sudo apparmor_parser -r
Warning from stdin (line 1): apparmor_parser: cannot use or update cache,
disable, or force-complain via stdin
* Verify that dbus mediation occurs under the Ubuntu 3.11.0-12-generic kernel:
$ echo profile nodbus { file, } | sudo apparmor_parser -rq
$ dbus-send --print-reply --system --dest=org.freedesktop.DBus
/org/freedesktop/DBus org.freedesktop.DBus.ListNames | head
method return sender=org.freedesktop.DBus - dest=:1.51 reply_serial=2
array [
string org.freedesktop.DBus
...
$ aa-exec -p nodbus -- dbus-send --print-reply --system
--dest=org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.ListNames
Failed to open
[Desktop-packages] [Bug 1246265] Update Released
The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1246265 Title: Empathy won't show contacts for Facebook, AIM. Status in Chat app, and Telepathy user interface: Fix Released Status in “empathy” package in Ubuntu: Fix Released Status in “empathy” source package in Precise: Fix Released Status in “empathy” source package in Saucy: Fix Released Bug description: Impact: empathy can't connect to facebook Test Case: run empathy add a facebook account go online check that your contacts are listed (or that your account is online in empathy-accounts) Regression potential: Check that your other accounts still connect/work correctly --- even though all my accounts are turned on in the Online accounts manager, empathy won't connect me to my aim or facebook chat account. This bug occurs on both of my computers. I don't know what else to do. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: empathy 3.8.4-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Tue Oct 29 23:27:59 2013 ExecutablePath: /usr/bin/empathy InstallationDate: Installed on 2013-10-05 (24 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: empathy UpgradeStatus: Upgraded to saucy on 2013-10-19 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/1246265/+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 1243777] Update Released
The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-bin in Ubuntu. https://bugs.launchpad.net/bugs/1243777 Title: Fonts are spectacularly broken Status in “lilypond” package in Ubuntu: Confirmed Status in “texlive-bin” package in Ubuntu: Fix Released Status in “lilypond” source package in Saucy: Fix Committed Status in “texlive-bin” source package in Saucy: Fix Released Bug description: [ Description ] metafont / metapost in texlive-binaries shipped with 13.10 is broken. It renders characters incorrectly and breaks note flags. [ Proposed fix ] Update metapost to 1.803, the next upstream release after the one we're shipping. It only contains two bug fixes - from the changelog: 2013-05-22 Taco Hoekwater t...@luatex.org * svgout.w: fix a problem with overly large characters in SVG output mode when prologues != 3. * mp.w: quick fix for a fatal crash during free-ing of TFM metric data at the end of the run. pmpost (Debian patch) needs updating too; this was taken from Debian's git repository. lilypond needs a no-change rebuild with the new texlive-binaries after that is accepted. [ QA ] Download https://bugs.launchpad.net/ubuntu/+source/lilypond/+bug/1243777/+attachment/3891750/+files /ubuntu-example.ly Process it with $ lilypond ubuntu-example.ly Compare the output to comments #5 and #6 on this bug to see if it is correct. [ Regression potential ] Bug fixes only. Check that metapost still works. Wait 14 days before releasing the package from -proposed. [ Original report ] The current build is done with a version of Metafont that is known to be broken. Every single file produced by this compilation of LilyPond has a spectacularly broken treble clef at the start of each line, and most note flags are quite broken as well. The current developer version for LilyPond (2.17.29) refuses to compile with the broken Metafont version. Unfortunately, 2.16.2 does not yet contain the respective check. Metafont versions announcing itself as anything between 1.600 and 1.802 (inclusively) are broken. The currently distributed version of Metafont with Ubuntu is 1.802. Since this affects _every_ output file produced by LilyPond, this bug is _critical_. The texlive-binaries package needs to get updated (Debian already did so), and preferably the build dependencies must reflect the inability of building a working version of LilyPond with the current version of texlive-binaries, which is 2013.20130529.30792-1build2. The corresponding bug in texlive-bin is https://bugs.launchpad.net/ubuntu/+source/texlive-bin/+bug/1220653 which has not seen a lot of interest. This build of LilyPond has to be withdrawn as _fast_ _as_ _possible_. It is not possible to typeset music of useful quality with it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lilypond/+bug/1243777/+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 1209092] Update Released
The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1209092 Title: network : gnome-control-center crashed with SIGABRT in g_assertion_message Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “gnome-control-center” source package in Saucy: Fix Released Bug description: [ Description ] gnome-control-center network can crash when unknown rfkill types are encountered [ Fix ] Ignore instead of crashing in this case. [ Test case ] The problem arised after upgrade to 13.10. To reproduce: 1. Click on System Settings 2. Gnome Control Center window appears 3. Click on Network under Hardware section 4. At this point Gnome Control Center window crashes. [ Regression potential ] Stops crashing but does nothing instead. Just check the bt panel still works. [ … ] ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu30 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic x86_64 ApportVersion: 2.12-0ubuntu3 Architecture: amd64 Date: Wed Aug 7 09:30:30 2013 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2010-03-26 (1229 days ago) InstallationMedia: Ubuntu 10.04 Lucid Lynx - Beta amd64 (20100318) MarkForUpload: True ProcCmdline: gnome-control-center Signal: 6 SourcePackage: gnome-control-center StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libnetwork.so ?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libnetwork.so ?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libnetwork.so Title: [network]: gnome-control-center crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to saucy on 2013-08-07 (0 days ago) UserGroups: adm admin cdrom dialout dip lpadmin plugdev sambashare usr_lib_gnome-control-center: activity-log-manager0.9.7-0ubuntu4 deja-dup27.3.1-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity 1.3daily13.06.19~13.04-0ubuntu1 indicator-datetime 12.10.3+13.10.20130731-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1209092/+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 408903] Re: Does not handle microphone mute button (KEY_MICMUTE)
Hello Christopher, or anyone else affected, Accepted gnome-settings-daemon into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/gnome- settings-daemon/3.4.2-0ubuntu0.6.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gnome-settings-daemon (Ubuntu Precise) Status: New = Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed ** Changed in: xkeyboard-config (Ubuntu Precise) Status: New = Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11proto-core in Ubuntu. https://bugs.launchpad.net/bugs/408903 Title: Does not handle microphone mute button (KEY_MICMUTE) Status in OEM Priority Project: Triaged Status in OEM Priority Project precise series: Confirmed Status in OEM Priority Project raring series: Won't Fix Status in central project for keyboard configuration: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “libx11” package in Ubuntu: Confirmed Status in “udev” package in Ubuntu: Fix Released Status in “x11proto-core” package in Ubuntu: New Status in “xkeyboard-config” package in Ubuntu: New Status in “xserver-xorg-input-evdev” package in Ubuntu: Won't Fix Status in “gnome-settings-daemon” source package in Precise: Fix Committed Status in “libx11” source package in Precise: Fix Released Status in “udev” source package in Precise: Fix Released Status in “x11proto-core” source package in Precise: Fix Released Status in “xkeyboard-config” source package in Precise: Fix Committed Status in “xserver-xorg-input-evdev” source package in Precise: Won't Fix Status in “gnome-settings-daemon” source package in Raring: Triaged Status in “libx11” source package in Raring: New Status in “udev” source package in Raring: Triaged Status in “x11proto-core” source package in Raring: New Status in “xkeyboard-config” source package in Raring: New Status in “xserver-xorg-input-evdev” source package in Raring: Won't Fix Bug description: [Impact] * People buying thinkpad hardware are not able to use a mic mute key, that comes with their machine [Test Case] * Press mic mute key * Observe that nothing happens [Regression Potential] * Very low. This is very isolated code. All it does is add functionality. In fact there are very few deletions in the diffs. * There is an existing acpi solution, that's already been mentioned in this bug. I'm not sure how these users would be affected once the upgrade hits, but it was never released as an official fix. [Original Report] Pressing the new microphone mute button does not do anything. It should toggle the mute on the current capture device and toggle an led that is part of the button. acpi_listen output: ibm/hotkey HKEY 0080 101b xev output: MappingNotify event, serial 34, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 248 MappingNotify event, serial 34, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 247 KeyPress event, serial 34, synthetic NO, window 0x341, root 0x118, subw 0x0, time 10334714, (317,-162), root:(322,207), state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 34, synthetic NO, window 0x341, root 0x118, subw 0x0, time 10334714, (317,-162), root:(322,207), state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/408903/+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 408903] Please test proposed package
Hello Christopher, or anyone else affected, Accepted xkeyboard-config into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/xkeyboard- config/2.5-1ubuntu1.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11proto-core in Ubuntu. https://bugs.launchpad.net/bugs/408903 Title: Does not handle microphone mute button (KEY_MICMUTE) Status in OEM Priority Project: Triaged Status in OEM Priority Project precise series: Confirmed Status in OEM Priority Project raring series: Won't Fix Status in central project for keyboard configuration: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “libx11” package in Ubuntu: Confirmed Status in “udev” package in Ubuntu: Fix Released Status in “x11proto-core” package in Ubuntu: New Status in “xkeyboard-config” package in Ubuntu: New Status in “xserver-xorg-input-evdev” package in Ubuntu: Won't Fix Status in “gnome-settings-daemon” source package in Precise: Fix Committed Status in “libx11” source package in Precise: Fix Released Status in “udev” source package in Precise: Fix Released Status in “x11proto-core” source package in Precise: Fix Released Status in “xkeyboard-config” source package in Precise: Fix Committed Status in “xserver-xorg-input-evdev” source package in Precise: Won't Fix Status in “gnome-settings-daemon” source package in Raring: Triaged Status in “libx11” source package in Raring: New Status in “udev” source package in Raring: Triaged Status in “x11proto-core” source package in Raring: New Status in “xkeyboard-config” source package in Raring: New Status in “xserver-xorg-input-evdev” source package in Raring: Won't Fix Bug description: [Impact] * People buying thinkpad hardware are not able to use a mic mute key, that comes with their machine [Test Case] * Press mic mute key * Observe that nothing happens [Regression Potential] * Very low. This is very isolated code. All it does is add functionality. In fact there are very few deletions in the diffs. * There is an existing acpi solution, that's already been mentioned in this bug. I'm not sure how these users would be affected once the upgrade hits, but it was never released as an official fix. [Original Report] Pressing the new microphone mute button does not do anything. It should toggle the mute on the current capture device and toggle an led that is part of the button. acpi_listen output: ibm/hotkey HKEY 0080 101b xev output: MappingNotify event, serial 34, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 248 MappingNotify event, serial 34, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 247 KeyPress event, serial 34, synthetic NO, window 0x341, root 0x118, subw 0x0, time 10334714, (317,-162), root:(322,207), state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 34, synthetic NO, window 0x341, root 0x118, subw 0x0, time 10334714, (317,-162), root:(322,207), state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/408903/+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 1224098] Update Released
The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1224098 Title: xserver wont start after nvidia-prime installation Status in “nvidia-prime” package in Ubuntu: Fix Released Status in “nvidia-prime” source package in Precise: Fix Committed Status in “nvidia-prime” source package in Saucy: Fix Released Bug description: SRU request: [Impact] * As a result of this bug, the lightdm configuration file will always been overwritten. This is not desirabled or expected and causes serious problems on any *buntu system other than Ubuntu. [Test Case] * Enable the precise-proposed or the saucy-proposed repository and install nvidia-prime (0.4.2~hybrid0.0.1 in precise or 0.4.2~hybrid0.1 in saucy). * If the package doesn't overwrite the lightdm greeter in the lightdm.conf file, then the fix is correct. [Regression Potential] * The regression potential here should be zero, as we only replace two conditions ( test -f and test ! -s) that can never be true at the same time, with the test -s condition which does exactly what we need - it checks that the file exists and has a size greater than zero - and reuse the existing file if this condition is satisfied. I have done a fresh install of saucy, before the installation of nvidia-prime lightdm-gtk-greeter was set in lightdm.conf. During the installation of nvidia-prime the greeter ist changed to unity-greeter which causes a crash and no display after a reboot. When changing the greeter back to lightdm-gtk-greeter everything works fine. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nvidia-prime 0.4 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Wed Sep 11 22:11:06 2013 InstallationDate: Installed on 2013-09-11 (0 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Alpha amd64 (20130902.1) MarkForUpload: True PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1224098/+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 1219650] Update Released
The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1219650 Title: Failed to install on 12.04.3 , /var/lib/dpkg/info/nvidia- prime.postinst: 36: printf: 08: not completely converted Status in “nvidia-prime” package in Ubuntu: Fix Released Status in “nvidia-prime” source package in Precise: Fix Committed Status in “nvidia-prime” source package in Saucy: Fix Released Bug description: SRU request: [Impact] * As a result of this bug, systems whose card has a bus id containing numbers such as 08 or 09 numbers will trigger an error in printf where it treats these string values with leading zeros as octal. This causes the postinst script to fail. [Test Case] * Enable the precise-proposed or the saucy-proposed repository and install nvidia-prime (0.4.2~hybrid0.0.1 in precise or 0.4.2~hybrid0.1 in saucy). * If the package can be installed without errors, then the fix is correct. * Alternatively, you can launch the attached script (see comment #8) as follows, you'll be able to reproduce the issue: sh printf_test.sh reproduce You can then test the fix by running the attached script without any arguments: sh printf_test.sh [Regression Potential] * The regression potential here is zero. As the attached script demonstrates. -- Encountered this problem during install nvidia driver by using jockey, then verified using apt-get install nvidia-prime, received following messages: $ sudo apt-get install nvidia-prime Reading package lists... Done Building dependency tree Reading state information... Done nvidia-prime is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 7 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue [Y/n]? y Setting up nvidia-prime (0.3~hybrid0.0.1) ... /var/lib/dpkg/info/nvidia-prime.postinst: 36: printf: 08: not completely converted dpkg: error processing nvidia-prime (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: nvidia-prime E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nvidia-prime 0.3~hybrid0.0.1 ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 Date: Mon Sep 2 14:07:37 2013 InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1219650/+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
