[Bug 1804185] Re: glibc has statx support in 18.10, but the manpage claims otherwise
** Changed in: manpages (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804185 Title: glibc has statx support in 18.10, but the manpage claims otherwise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/manpages/+bug/1804185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804185] Re: glibc has statx support in 18.10, but the manpage claims otherwise
I see, thanks! Since http://man7.org/linux/man-pages/man2/statx.2.html has the same note, I though t it might have slipped past unnoticed. Thanks again! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804185 Title: glibc has statx support in 18.10, but the manpage claims otherwise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/manpages/+bug/1804185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804185] [NEW] glibc has statx support in 18.10, but the manpage claims otherwise
Public bug reported: Glibc added statx support in 2.28 [1], the same version used in 18.10. But `man 2 statx` still has: > NOTES > Glibc does not (yet) provide a wrapper for the statx() system > call; call it using > syscall(2). I have tested it, and I can directly use `statx(2)` in 18.10. This note should be removed. [1]: https://www.sourceware.org/ml/libc-alpha/2018-08/msg3.html ** Affects: manpages (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/1804185 Title: glibc has statx support in 18.10, but the manpage claims otherwise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/manpages/+bug/1804185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1709603] Re: apt {upgrade, install, source} require an update call first
Alternate:
- a `-u`/`--update` option that unconditionally performs an apt update
as an option to apt itself, since every subcommand except `update` and
`edit-sources` can potentially benefit from an `update` beforehand. For
`edit-sources`, have it update after instead of before, and for
`update`, the option can be a NOP.
I'd love to be able to do something like:
apt full-upgrade --autoremove --update
I can do `apt full-upgrade --autoremove` now, removing obsolete packages
and upgrading in one shot. It'd be glorious to include the package lists
update in that operation too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1709603
Title:
apt {upgrade,install, source} require an update call first
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1709603/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1683576] [NEW] cd with multiple directory argument fails
Public bug reported: In bash 4.4, a new behaviour was introduced for cd, where it would complain if multiple arguments are provided. From config-top.h [1]: /* Define CD_COMPLAINS if you want the non-standard, but sometimes-desired error messages about multiple directory arguments to `cd'. */ #define CD_COMPLAINS It seems like this is enabled for Ubuntu. However, this behaviour conflicts with the manual (both Ubuntu's and GNU's), which says something similar to: "Any additional arguments following directory are ignored." Please revert to the old behaviour, or correct the manual. This is not a user-configurable setting, and push is also affected. Ubuntu 17.04 bash 4.4-2ubuntu1 [1]: http://git.savannah.gnu.org/cgit/bash.git/tree/config-top.h#n30 ** Affects: bash (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/1683576 Title: cd with multiple directory argument fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1683576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1661041] [NEW] dnscache script breaks if /run/resolvconf/interface is empty
Public bug reported: Following Debian bug 318464, a script was added to resolvconf which helpfully overwrites dnscache's @ file with root servers if the there are no nameservers offered. In my case, the system, which is a DNS server itself, does not use DHCP or other network-provided DNS servers, but runs both tinydns and dnscache on different interfaces. Naturally, the script finds no offered nameservers, overwrites the @ file, and screws over dnscache since we're behind a firewall which blocks outgoing DNS traffic. I'm not sure how to fix the issue (other than disabling the script somehow, or overwriting /etc/dnsroots.global, which is where djbdns keeps the list of root servers). Version: Ubuntu 14.04.5 djbdns 1:1.05-8ubuntu1 resolvconf 1.69ubuntu1.1 [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=318464 ** Affects: resolvconf (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/1661041 Title: dnscache script breaks if /run/resolvconf/interface is empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1661041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1559482] Re: add-apt-repository manpage does not mention new -u option
That makes sense. This is my second merge attempt. The first, iirc, was against https://code.launchpad.net/~ubuntu-branches/software-properties, because Launchpad offered it as the default. I deleted that and picked the wily one manually because that's what I branched from. Should I delete the merge proposal and start again? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1559482 Title: add-apt-repository manpage does not mention new -u option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1559482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1559482] [NEW] add-apt-repository manpage does not mention new -u option
Public bug reported: The add-apt-repository tool has apparently gained a new option to update the package cache. However, the manpage does not reflect this (as seen on http://manpages.ubuntu.com/manpages/wily/en/man1/add-apt- repository.1.html or http://manpages.ubuntu.com/manpages/xenial/en/man1 /add-apt-repository.1.html). While the tool's own help text does mention it, this should be documented in the manpage as well. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: software-properties-common 0.96.13 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 19 21:07:41 2016 InstallationDate: Installed on 2016-02-01 (47 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1559482 Title: add-apt-repository manpage does not mention new -u option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1559482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1248736] Re: gnome-tweak-tool: some options are truncated and unreadable
The original bug was a duplicate of this one, and this one contains the actual status: fixed in 3.18. ** Bug watch added: GNOME Bug Tracker #711137 https://bugzilla.gnome.org/show_bug.cgi?id=711137 ** Changed in: gnome-tweak-tool Importance: Medium => Unknown ** Changed in: gnome-tweak-tool Status: Invalid => Unknown ** Changed in: gnome-tweak-tool Remote watch: GNOME Bug Tracker #722582 => GNOME Bug Tracker #711137 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1248736 Title: gnome-tweak-tool: some options are truncated and unreadable To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-tweak-tool/+bug/1248736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482641] Re: Lightdm (and GDM) source .profile as bash, indirectly sourcing .bashrc
Presumably this isn't important enough to make an SRU, right, Gunnar? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482641 Title: Lightdm (and GDM) source .profile as bash, indirectly sourcing .bashrc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1482641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482641] Re: Lightdm (and GDM) source .profile as bash, indirectly sourcing .bashrc
** Description changed: The fix for https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/678421 leads to `.profile` being sourced by bash instead of dash. This leads - `.bashrc` being sourced indirectly twice: once by bash when the script - started, and once via .profile. IMHO, `.bashrc` should not be sourced - even *once* in this situation. I suggest: + `.bashrc` being sourced indirectly via .profile. IMHO, `.bashrc` should + not be sourced even *once* in this situation. I suggest that sourcing + .profile actually be done with BASH_VERSION unset: - 1. That the shebang be changed to: - - #! /bin/bash --norc - - 2. And that sourcing .profile actually be done with BASH_VERSION unset: - - BASH_VERSION= . $CONFIG + BASH_VERSION= . $CONFIG At the very least, a check should be done whether bash is the user's login shell. In combination with the modified shebang line, it can be done thus: - [ $SHELL == /bin/bash ] .bashrc + [ $SHELL != /bin/bash ] BASH_VERSION= + . $CONFIG utilizing `$SHELL` given it stores the login shell (http://unix.stackexchange.com/questions/45458/why-shell-doesnt-change- when-i-run-new-shell). - - Sourcing `.profile` should still avoid sourcing `.bashrc` to avoid - complications due to it being sourced twice. ** Description changed: The fix for https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/678421 leads to `.profile` being sourced by bash instead of dash. This leads `.bashrc` being sourced indirectly via .profile. IMHO, `.bashrc` should not be sourced even *once* in this situation. I suggest that sourcing .profile actually be done with BASH_VERSION unset: BASH_VERSION= . $CONFIG At the very least, a check should be done whether bash is the user's - login shell. In combination with the modified shebang line, it can be - done thus: + login shell. It can be done thus: [ $SHELL != /bin/bash ] BASH_VERSION= - . $CONFIG + . $CONFIG utilizing `$SHELL` given it stores the login shell (http://unix.stackexchange.com/questions/45458/why-shell-doesnt-change- when-i-run-new-shell). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482641 Title: Lightdm (and GDM) source .profile as bash, indirectly sourcing .bashrc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1482641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482641] [NEW] Lightdm (and GDM) source .profile as bash, indirectly sourcing .bashrc
Public bug reported: The fix for https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/678421 leads to `.profile` being sourced by bash instead of dash. This leads `.bashrc` being sourced indirectly via .profile. IMHO, `.bashrc` should not be sourced even *once* in this situation. I suggest that sourcing .profile actually be done with BASH_VERSION unset: BASH_VERSION= . $CONFIG At the very least, a check should be done whether bash is the user's login shell. It can be done thus: [ $SHELL != /bin/bash ] BASH_VERSION= . $CONFIG utilizing `$SHELL` given it stores the login shell (http://unix.stackexchange.com/questions/45458/why-shell-doesnt-change- when-i-run-new-shell). ** Affects: gdm (Ubuntu) Importance: Undecided Status: New ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Also affects: lightdm (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/1482641 Title: Lightdm (and GDM) source .profile as bash, indirectly sourcing .bashrc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1482641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1383409] Re: Support TLS (not just SSLv3)
*** This bug is a duplicate of bug 1382133 *** https://bugs.launchpad.net/bugs/1382133 ** This bug has been marked a duplicate of bug 1382133 Issue with servers with SSLv3 disabled due to Poodle -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1383409 Title: Support TLS (not just SSLv3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1383409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1365834] [NEW] The list of hashes on the UbuntuHashes page doesn't contain 14.04.1
Public bug reported: The community help page (https://help.ubuntu.com/community/UbuntuHashes) doesn't have any hashes for 14.04.1. The page tells us to file a bug here if we want an update to it. ** Affects: ubuntu-docs (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/1365834 Title: The list of hashes on the UbuntuHashes page doesn't contain 14.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1365834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1335289] Re: Shutdown timer regression
** Package changed: gnome-power-manager (Ubuntu) = unity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1335289 Title: Shutdown timer regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1335289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1335289] Re: Shutdown timer regression
There was a change in the shutdown dialog introduced here: https://launchpad.net/ubuntu/+source/unity/6.12.0daily13.03.11-0ubuntu1, with the bug that brought about the change being https://bugs.launchpad.net/unity/+bug/1152374. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1335289 Title: Shutdown timer regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1335289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1329094] [NEW] Shows pointless confirmation message when lacking authority to shutdown
Public bug reported: I added polkit restrictions preventing anybody from shutting down (using settings from http://askubuntu.com/a/454230/158442). As restrictions are added or removed, entries from the greeter's Shutdown confirmation dialog change. When there are no permissions, just the question is displayed, with no selectable options. I suggest that no message, or better yet, no menu item, be displayed if no permissions are present. (I have restricted shutdown permissions in a lab to prevent well-meaning students from unneccessarily shutting down PCs). Release information: Description:Ubuntu 14.04 LTS Release:14.04 Package information: unity-greeter: Installed: 14.04.10-0ubuntu1 Candidate: 14.04.10-0ubuntu1 Version table: *** 14.04.10-0ubuntu1 0 500 http://mirror.cse.iitk.ac.in/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 14.04.9-0ubuntu1 0 500 http://mirror.cse.iitk.ac.in/ubuntu/ trusty/main amd64 Packages ** Affects: unity-greeter (Ubuntu) Importance: Undecided Status: New ** Tags: trusty ui ** Attachment added: Screenshot of confirmation dialog https://bugs.launchpad.net/bugs/1329094/+attachment/4129955/+files/shot.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1329094 Title: Shows pointless confirmation message when lacking authority to shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1329094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 857228] Re: libmutter0 depends on both libcogl2 and libcogl5
After updating the package lists a few minutes ago, I saw that libmutter0 has been updated to version 3.1.92-0ubuntu2, gnome-shell to 3.1.92-0ubuntu1, gnome-tweak-tool remains at 3.1.90-0ubuntu1. ** Changed in: mutter (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857228 Title: libmutter0 depends on both libcogl2 and libcogl5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/857228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
