[Bug 1853414] [NEW] Bogus run-time error about wrong endianness for boost-numpy
Public bug reported: This is about an upstream bug in Boost 1.67: https://github.com/boostorg/python/issues/209 The bug has been fixed by this merged PR: https://github.com/boostorg/python/pull/218/commits/0fce0e589353d772ceda4d493b147138406b22fd The PR made it to upstream version 1.68 but Ubuntu is still using 1.67. Can there be a minor version upgrade (libboost-numpy1.67.1?) incorporating a patch containing the one-line change in the PR? ** Affects: boost-defaults (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853414 Title: Bogus run-time error about wrong endianness for boost-numpy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boost-defaults/+bug/1853414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848849] Re: Lightdm fails to undo quoting for Exec key
** Package changed: unity-settings-daemon (Ubuntu) => lightdm (Ubuntu) ** Package changed: lightdm (Ubuntu) => lightdm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848849 Title: Lightdm fails to undo quoting for Exec key To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1848849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848849] [NEW] Lightdm fails to undo quoting for Exec key
Public bug reported: According to spec/documentation, "implementations must undo quoting before expanding field codes and before passing the argument to the executable program." https://developer.gnome.org/desktop-entry-spec/#exec-variables lightdm fails to do so and passes the double-quote characters to the executable program. Consider the following files: myecho: #!/bin/bash echo "$1" > /tmp/cmd /usr/share/xsessions/test.desktop: [Desktop Entry] Name=Test Comment=This is a test session Type=Application Exec=myecho "argument" myecho is to be located somewhere in the PATH. When trying to start a desktop session defined by test.desktop, as a result of running myecho, the first command-line argument from the Exec is written to /tmp/cmd. Here is where lightdm is wrong: Starting the 'test' session under lightdm causes '"argument"' (without the surrounding single quotes) to be written to /tmp/cmd. The correct string should be 'argument' (without the surrounding single quotes). If the double-quotes are removed from the Exec line, lightdm behaves normally and 'argument' is written. A practical consequence of this bug is that users can't use "bash -c" to run multiple commands when special characters (including spaces) are needed in the argument after "-c". It seems that the user must resort to a wrapper script because of this bug. $ lsb_release -rd Description:Ubuntu 19.04 Release:19.04 $ apt-cache policy lightdm lightdm: Installed: 1.28.0-0ubuntu1 Candidate: 1.28.0-0ubuntu1 Version table: *** 1.28.0-0ubuntu1 500 500 http://mirrors.yun-idc.com/ubuntu disco/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: unity-settings-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848849 Title: Lightdm fails to undo quoting for Exec key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1848849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1077782] [NEW] oneconf python scripts need Python version-specific shebang
Public bug reported: At least one Python script (/usr/share/oneconf) uses Python 2 syntax but use a version-less /usr/bin/python in its shebang. As a result, if the user configures Python 3 to be the default Python for /usr/bin/python, the script fails. The script(s) should be either fixed to be friendly with both Python 2 and Python 3 or have a version-specific shebang, e.g. /usr/bin/python2.7. I have observed the script crash with a SyntaxError on 'print _(Installed packages.)' $ lsb_release -rd Description:Ubuntu 12.10 Release:12.10 $ apt-cache policy oneconf oneconf: Installed: 0.2.9.1 Candidate: 0.2.9.1 Version table: *** 0.2.9.1 0 500 http://us.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: oneconf (Ubuntu) Importance: Undecided Status: New ** Attachment added: Screenshot of crash https://bugs.launchpad.net/bugs/1077782/+attachment/3430958/+files/oneconf-python.png ** Description changed: - At least one Python scripts (/usr/share/oneconf) uses Python 2 syntax - but use a version-less /usr/bin/python in its shebang. As a result, if - the user configures Python 3 to be the default Python for - /usr/bin/python, the script fails. + At least one Python script (/usr/share/oneconf) uses Python 2 syntax but + use a version-less /usr/bin/python in its shebang. As a result, if the + user configures Python 3 to be the default Python for /usr/bin/python, + the script fails. The script(s) should be either fixed to be friendly with both Python 2 and Python 3 or have a version-specific shebang, e.g. /usr/bin/python2.7. I have observed the script crash with a SyntaxError on 'print _(Installed packages.)' $ lsb_release -rd Description: Ubuntu 12.10 Release: 12.10 $ apt-cache policy oneconf oneconf: - Installed: 0.2.9.1 - Candidate: 0.2.9.1 - Version table: - *** 0.2.9.1 0 - 500 http://us.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 0.2.9.1 + Candidate: 0.2.9.1 + Version table: + *** 0.2.9.1 0 + 500 http://us.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages + 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1077782 Title: oneconf python scripts need Python version-specific shebang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oneconf/+bug/1077782/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 870767] Re: rhythmbox-metadata crashed with SIGSEGV in gst_structure_copy()
I got this segfault soon after I created a symlink of a folder that has music that Rhythmbox knows about. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/870767 Title: rhythmbox-metadata crashed with SIGSEGV in gst_structure_copy() To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/870767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 771263] Re: unity shortcuts do not use appropriate keyboard layout
I have a similar problem. I have always been using Dvorak. After I upgraded from Ubuntu 10 without Unity, to Ubuntu 11 with Unity, ctrl- shift-T works only if I press it according to the QWERTY layout. On a fresh install with Dvorak, ctrl-shift-t works with the Dvorak layout. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/771263 Title: unity shortcuts do not use appropriate keyboard layout -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 771483] Re: With Natty, I can't see the grub menu, it's all garbage displayed on the screen.
I have the same problem. My grub menu is unreadable. It's a black screen with white streaks that look like what is supposed to be menu items. When I press up and down, the streaks get updated. I have a Samsung Series 9 laptop running Natty on a fresh install. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/771483 Title: With Natty, I can't see the grub menu, it's all garbage displayed on the screen. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 768051] Re: Ubiquity crashes on Installing the 'grub2' package
*** This bug is a duplicate of bug 765270 *** https://bugs.launchpad.net/bugs/765270 I just tried installing using a bootable USB with the live image from the daily build of Apr 22, and the problem is gone. I was able to successfully install Natty on my system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/768051 Title: Ubiquity crashes on Installing the 'grub2' package -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 768051] [NEW] Ubiquity crashes on Installing the 'grub2' package
Public bug reported: Binary package hint: ubiquity I was trying to install 64-bit Natty Beta-2 from a USB flash drive with the ISO image onto a Samsung 900X3A, released 1-2 months ago. This machine has a SSD. I think it may also support EFI, if that makes any difference. ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/768051 Title: Ubiquity crashes on Installing the 'grub2' package -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 768051] Re: Ubiquity crashes on Installing the 'grub2' package
** Attachment added: syslog https://bugs.launchpad.net/bugs/768051/+attachment/2078239/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/768051 Title: Ubiquity crashes on Installing the 'grub2' package -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 768051] Re: Ubiquity crashes on Installing the 'grub2' package
** Attachment added: partman https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/768051/+attachment/2078240/+files/partman -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/768051 Title: Ubiquity crashes on Installing the 'grub2' package -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 181915] Re: page scroll causes loss of context to the reader
I have a request for the following feature that may ameliorate the problem. To help the user find the context, I suggest the following behavior: Right after scrolling finishes, a horizontal line that runs across the page flashes briefly that is located at the part of the document that before scrolling was at the bottom of the viewport. This feature should be optional, off course. Another approach is to instantly darken the part of the document before the context-line upon scrolling and then gradually fade it in over one second or less. I don't think that scrolling exactly by the viewport height is going to very user-friendly, because sometimes the bottom edge of the viewport cuts across a text line, which can't be read because it's only partially visible -- the scrolling should be for slightly less than a page. -- page scroll causes loss of context to the reader https://bugs.launchpad.net/bugs/181915 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
