** Also affects: busybox (Ubuntu Noble)
Importance: Undecided
Status: Confirmed
** Also affects: busybox (Ubuntu Mantic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Setting as wishlist per request by the OP in #ubuntu-discuss
** Changed in: apport (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
Public bug reported:
"respectively" is wrongly spelled:
-l Used to specify that nc should listen for an incoming
connection rather than initiate a connection to a remote host. The
destination and port to listen on can be specified either as non-
optional arguments, or with options -s
Hello Christopher, thank you for opening this bug and helping make
Ubuntu (and coreutils!) better.
I am somewhat confused here. Are you suggesting a change in wording?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Thank you for opening this bug and helping make Ubuntu better.
Can you explain what is wrong? "idk how to show you" means we also do
not know what to look for...
** Changed in: xorg (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
Closing INVALID.
** Changed in: apt (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1826585
Title:
I can't update, upgrade or
Assigning package to apt, setting incomplete (but tending to INVALID).
** Package changed: ubuntu => apt (Ubuntu)
** Changed in: apt (Ubuntu)
Status: New => Incomplete
** Changed in: apt (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a
I think the Ubuntu patch has been obsoleted by common usage now, with
pretty much all distros using upstream version (of *not* keeping HOME).
Removing the patch would lower the delta we carry; additionally there is
the benefit of having Ubuntu behave as everybody else, lowering the
easter-egg
re-assigning bug to glibc
** Package changed: coreutils (Ubuntu) => glibc (Ubuntu)
** Description changed:
I have been using 'date +%-Y -d "- 2010 years" in a script for years but
today after using the script after upgrading to disco it has failed.
After some experimentation it
Assaf's test, attached.
** Attachment added: "inv-year.c"
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1824688/+attachment/5256314/+files/inv-year.c
** Changed in: coreutils (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member
Further exchange on https://debbugs.gnu.org/35289 suggests this is a
libc6 problem, not a coreutils/date one.
Assaf Gordon (upstream) provided a test that can be run (attached here
are inv-year.c). If it fails on the mktime() call, then it is not
'date', but libc6.
I also found that setting
I have ran a few tests on 16.04, 18.04, 18.10, and 19.04 (all X86_64):
16.04:
root@u1604:~# date +%-Y -d '- 2010 years'
9
root@u1604:~# date --version
date (GNU coreutils) 8.25
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
Also, you may want to try https://askubuntu.com/ before opening a bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1824565
Title:
I'm just trying to make my compouter
Hello,
I am sorry, but this is NOT a bug. It seems you are unhappy with some
programs/packages you have installed (either by yourself, or
automatically), but it is not at all clear what, where, why, and how.
Right now this sounds much more like usage issues than actual bugs (a
bug is an error in
re-assigning to systemD as requested.
** Package changed: coreutils (Ubuntu) => systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1813052
Title:
who
upstream (and, for Coreutils
and many of the Ubuntu packages, from Debian).
Cheers,
-- email from upstream --
Hello,
On 2018-12-28 11:21 a.m., C de-Avillez wrote:
> We have had some bugs reported recently at our BTS:
>
> https://bugs.launchpad.net/bugs/1807295
> https://bugs.l
upstream (and, for Coreutils
and many of the Ubuntu packages, from Debian).
Cheers,
-- email from upstream --
Hello,
On 2018-12-28 11:21 a.m., C de-Avillez wrote:
> We have had some bugs reported recently at our BTS:
>
> https://bugs.launchpad.net/bugs/1807295
> https://bugs.l
upstream (and, for Coreutils
and many of the Ubuntu packages, from Debian).
Cheers,
-- email from upstream --
Hello,
On 2018-12-28 11:21 a.m., C de-Avillez wrote:
> We have had some bugs reported recently at our BTS:
>
> https://bugs.launchpad.net/bugs/1807295
> https://bugs.l
upstream (and, for Coreutils
and many of the Ubuntu packages, from Debian).
Cheers,
-- email from upstream --
Hello,
On 2018-12-28 11:21 a.m., C de-Avillez wrote:
> We have had some bugs reported recently at our BTS:
>
> https://bugs.launchpad.net/bugs/1807295
> https://bugs.l
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1184152
Title:
du crashed with SIGABRT in leave_dir()
Status in
*** This bug is a duplicate of bug 1184152 ***
https://bugs.launchpad.net/bugs/1184152
bug 1184152 has been set public.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
Thank you for opening this bug and helping make Ubuntu/GNU Coreutils
better. I have sent email to coreut...@gnu.org asking about this, and a
few other bugs relating to the same basic issue, and am waiting on
feedback from upstream:
Hello,
We have had some bugs reported recently at our BTS:
Thank you for opening this bug and helping make Ubuntu/GNU Coreutils
better. I have sent email to coreut...@gnu.org asking about this, and a
few other bugs relating to the same basic issue, and am waiting on
feedback from upstream:
Hello,
We have had some bugs reported recently at our BTS:
Thank you for opening this bug and helping make Ubuntu/GNU Coreutils
better. I have sent email to coreut...@gnu.org asking about this, and a
few other bugs relating to the same basic issue, and am waiting on
feedback from upstream:
Hello,
We have had some bugs reported recently at our BTS:
Thank you for opening this bug and helping make Ubuntu/GNU Coreutils
better. I have sent email to coreut...@gnu.org asking about this, and a
few other bugs relating to the same basic issue, and am waiting on
feedback from upstream:
Hello,
We have had some bugs reported recently at our BTS:
** Package changed: ubuntu => xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1804874
Title:
can't reconnect mouse/mouse stops working after a while
Status in
Closing INVALID, then, given this is a known, documented limitation.
** Changed in: coreutils (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
Hello Kevin, and thank you for opening this bug and helping make Ubuntu
better.
The info page for seq (info seq) has the following note:
" On most systems, seq can produce whole-number output for values up to
at least 2^{53}. Larger integers are approximated. The details differ
depending on
Updated with upstream bug #; this seems to be an on-going concern, and
depends on some not-yet-available interfaces between kernel and systemd.
Marking Triaged/Medium. There are some bypasses discussed in the
upstream bug, but not all possible effects have already been discussed
(for example,
I have moved it over to procps. Thank you for confirming.
** Package changed: coreutils (Ubuntu) => procps (Ubuntu)
** Changed in: procps (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Hello Guido,
Thank you for opening this bug and helping make Ubuntu better.
As far as I can remember, Ubuntu has been using kill from the procps
package, not coreutils. On Cosmic and 16.04 (the only machines I have
access to right now), /bin/kill is being provided by procps:
cerdea@piatam:$
setting to Triaged/Low per request on #ubuntu-bugs. Description updated
as in comment #24.
** Changed in: cups (Ubuntu)
Importance: Undecided => Low
** Changed in: cups (Ubuntu)
Status: New => Triaged
** Description changed:
+ Ubuntu version 16.04
+ 16.04 (cups 2.1.3-4ubuntu0.5).
Thank you for opening this bug and helping make Ubuntu better.
You refer to "crash" and "abort", but this bug does not have an apport-
generated stacktrace, neither *any* details on how 'du' fails. As it is,
there is not much we can do.
On a standard Ubuntu system, if 'du' crashes, it should
** Changed in: coreutils (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1774049
Title:
df incorrectly reports available space
Thank you, although we are still missing the Ubuntu version.
Nevertheless, your issue may be shown here:
https://www.gnu.org/software/coreutils/faq/coreutils-faq.html#df-and-du-
report-different-information and the next FAQ question.
Also, it is possible that you may need to check the filesystem
I am sorry, but this does not match with what you reported.
The above df line shows a filesystem that is pretty much empty; even
more it is just 116 MEGA bytes is size, while you stated, when opening
the bug, that the filesystem would be reporting 19 GIGA bytes available.
Please give us:
1. the
setting as wishlist per chat with the OP.
** Changed in: systemd (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1776742
correcting package. /usr/bin/find belong to the findutils package.
** Package changed: coreutils (Ubuntu) => findutils (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to findutils in Ubuntu.
** Description changed:
xserver-xorg-input-all was installed. As a result, both xserver-xorg-
input synaptics and xserver-xorg-input-libinput got installed.
This breaks usage for both natural scrolling *and* moving the primary
button of the mouse/touchpad to the right (a.k.a. typing
Public bug reported:
xserver-xorg-input-all was installed. As a result, both xserver-xorg-
input synaptics and xserver-xorg-input-libinput got installed.
This breaks usage for both natural scrolling *and* moving the primary
button of the mouse/touchpad to the right (a.k.a. typing while being
Setting the coreutils task to invalid. 'who' reports based on wtmp. If
wtmp is not being updated by the applications, this is not a coreutils
issue.
** Changed in: coreutils (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
this fix will need an SRU for 16.04.
** Changed in: coreutils
Status: New => Fix Released
** Changed in: coreutils (Ubuntu)
Milestone: None => xenial-updates
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Also affects: coreutils
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1620139
Title:
factor buffers output when run
ran some 15 profile reloads with JJ's kernel (a mix of reinstalls and
restarts), could not reproduce.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1579135
Title:
I worked with Ralph figuring out this issue. I can reproduce it. Marking
as triaged.
** Changed in: lsb (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lsb in Ubuntu.
reassigning bug to Alien. Issue was noted on lsb-core:i386 install, but
it is Alien that has the issue.
** Package changed: lsb (Ubuntu) => alien (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lsb in Ubuntu.
reverting to Triaged.
** Changed in: apport (Ubuntu)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/764414
Title:
private master
** Also affects: curl (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to curl in Ubuntu.
https://bugs.launchpad.net/bugs/1556330
Title:
upstream curl bug #1371: p12
** Also affects: ntp (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: ntp (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in
This is most certainly because you are using your shell's built-in
'echo':
[cerdea-aws]cerdea@icatu:~$ echo --version
--version
[cerdea-aws]cerdea@icatu:~$ env echo --version
echo (GNU coreutils) 8.23
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
** Also affects: binutils (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1490352
Title:
please backport
/usr/bin/look is from the bsdmainutils package, not from coreutils. Re-
assigning.
** Package changed: coreutils (Ubuntu) = bsdmainutils (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
Thank you for opening this bug and helping make Ubuntu and GNU software
better. As Pádraig commented above, this has already been discussed
upstream, and there is a consensus among the Coreutils maintainers *not*
to do it.
As such, closing invalid (not a bug). We will not create a delta for
this.
Hello Pádraig,
You can always set the Ubuntu task to Fix Committed. This means a fix
was made available (probably in upstream) but has not yet been packaged
for Ubuntu.
Given this is a low impact bug (it *is*, after all, documented in the
man page, I expect this bug to move to Fix Released when
Actually, no, the current implementation is correct. See [1]. As such,
closing invalid (not-a-bug).
[1]https://blueprints.launchpad.net/ubuntu/+spec/umask-to-0002
** Changed in: coreutils (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a
your umask is 0002, which matches the permissions on the directory you
created. I am unsure where mkdir is doing something wrong.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
Please provide us with a test case:
* the command, and its output;
* the version (run mkdir --version)
* the filesystem type
* the output of umask.
Just for reference, on my 15.04 the output of 'umask' is 0002.
** Changed in: coreutils (Ubuntu)
Importance: Undecided = Low
** Changed in:
@Gabriele Tozzi: please open a new bug with 'ubuntu-bug coreutils'. This
bug is quite old, and coreutils versions have changed a lot since
Feisty.
Marking invalid.
** Changed in: coreutils (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a
Public bug reported:
The printer is a HP-3600N. Was printing nicely, got out-of-tone on
magenta. Loaded a new toner, print output is still held with printer
out of toner messages.
/var/log/syslog shows many messages like:
2015-01-21T11:09:15.511793-06:00 icatu kernel: [336562.378463] audit:
syslog
** Attachment added: syslog
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1413313/+attachment/4303227/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
for the record, adjusting as above makes my printer work.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1413313
Title:
apparmor denied messages in log, may be responsible
** Bug watch added: Debian Bug tracker #760861
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760861
** Also affects: coreutils via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760861
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are
Thank you for opening this bug and helping make Ubuntu, and free
software, better.
The Debian bug I linked to has more information, and is the core bug for
this issue. Right now, for Ubuntu (and Debian) 'info coreutils
command will work, and can be used as a bypass.
I am not sure how to
Thank you for opening this bug and helping make Ubuntu better.
This is not a bug. Coreutils (as most of GNU packages) uses Texinfo as
the primary source for documentation. The man pages are a summary
*only*; for full docs, the user is referred to 'info':
The full documentation for md5sum is
64 matches
Mail list logo
