Well, color me baffled. I was all set to try testing before and after
applying the update. But now I cannot make the problem happen. I'll
apply the updates anyway. Feel free to do what makes sense with this
bug report -- mark worksforme, mark as duplicate, whatever.
All I can think of is that
Actually, this ran from a thumb drive, and I was about to update the
whole show to 22.0 LTS. I'm not used to doing updates of just one
package. Can you give some details on how to do that? Or would the
blanket update serve your purpose?
--
You received this bug notification because you are a
Public bug reported:
Working on a new app to do full-disk backup and recovery, I'm having
trouble with clearing existing partitions on a target drive. The man
page for wipefs says that wipefs -a should wipe all partitions
on the drive, but I have a situation where it has a strange result:
lsblk
Public bug reported:
As distribted, the file sshd_config has apparently been modified from an
upstream version -- those lines that are NOT comments. There is no good
way for me to change any of them, even though there is a sshd_config.d
directory for my changes. That is because the files in the
Color me embarassed. I just tried this again on a different system,
still with the same software, and it worked perfectly, using the same
source and destination drives as when I first had a problem.
Mark this "worksforme" I guess.
--
You received this bug notification because you are a member
There is probably more going on than I realized. I edited the file so
that all references were to /dev/sdc without those added "p"
characters. It still complained about parsing sdc. Now I'm completely
puzzled and would ask for a better error message.
--
You received this bug notification
Public bug reported:
I have a dump from an M.5 drive named "/dev/nvme0n1" that I wanted to
apply to a regular SCSI drive /dev/sdc. This got the GPT built but when
it tried to work on partitions, it failed, giving the error message
sfdisk: failed to parse partition number: '/dev/sdc'
This is
Public bug reported:
According to the man page, $(variable:offset[:length]} should treat
negative offsets as counting from the end of the value. Instead, I find
any such substring expansion expands the ENTIRE variable regardless of
the exact negative offset or any length provided.
A short
Public bug reported:
Trying to restore a GPT partition table using a dump sfdisk previously
created from a larger disk to a smaller one (but has enough room for the
partitions) fails. I'm using the --force option to try to make this
work. It doesn't. The first line of the output (with added
** Attachment added: "Test script to investigate the error"
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1901343/+attachment/5426630/+files/test.sh
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux
Public bug reported:
This is a creepy bug that seems to disappear under examination. In this
case it appears that the bug is a timing bug, and introducing delays
makes it go away. I call this sort of thing a "frankenbug" because of
creepyness and difficulty diagnosing.
It appears to be an
I tried, but when I went back to the same system, with the same drives,
and tried again -- you guessed it, it did not fail.
I really hate intermittent errors. You may as well mark this one "works
for me".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Public bug reported:
Call this a feature request.
I found that when I use the output of "sfdisk --dump" from one disk to
format another one that is smaller, sfdisk does not complain. Of
course, using those partitions caused problems because they went off the
end of the new disk. The error can
Public bug reported:
I'm posting this against util-linux because it's lsblk calls that fail,
but the failure depends on a prior call to sfdisk which is part of the
fdisk package. Remove the sfdisk call, and the failure does not happen,
at least in my test setup.
A call to sfdisk in a script
Public bug reported:
This system reports /dev/sda5 will be checked on the next reboot. Maybe
it is (it's EXT4 on as SSD drive, so it could be too fast to notice),
but the message persists even after such a reboot.
I would expect it to go away.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
allationDate: Installed on 2018-10-18 (36 days ago)
> InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
> (20180725)
> SourcePackage: python3-defaults
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about t
Public bug reported:
I'm using python3 and want gmpy. Attempts to install it fail.
I routinely capture the output of maintenance tasks, and am attaching
the results. This output begins with the text of the shell script I
wrote to do this, which includes calls to the bash functions I wrote to
Public bug reported:
It may be this is a problem in gmpy itself, but since it is not
installed, ubuntu-bug won't let me report a problem with it.
In any event, I routinely capture the output of package maintenance
tasks, and I'm attaching the output of the most recent run of a shell
script I
I see that this arises when the script calls pip3 to install a python
package. I'll clean this up to do just that by itself, and re-submit.
Call this one invalid, I guess.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt
> ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
> Uname: Linux 4.15.0-36-generic x86_64
> NonfreeKernelModules: nvidia_modeset nvidia
> ApportVersion: 2.20.9-0ubuntu7.4
> Architecture: amd64
> CurrentDesktop: ubuntu:GNOME
> Date: Wed Oct 24 20:17:15 2018
pgraded to bionic on 2018-08-19 (66 days ago)
> modified.conffile..etc.default.apport: [modified]
> mtime.conffile..etc.default.apport: 2017-05-02T14:12:29.908000
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1799
Public bug reported:
Sorry for using Ubuntu to report an Xubuntu bug, but the problem is
exactly that bug reporting is not working for me in Xubuntu. When I
tried to create what eventually became bug 1799868 here on Xubuntu, as
soon as the web browser (Chrome) came up, it waas reporting a
Public bug reported:
I can use seq(1) to generate sequences of large numbers if I use the
default increment:
$ seq 170141183460469231731687303715884105721
170141183460469231731687303715884105725
170141183460469231731687303715884105721
170141183460469231731687303715884105722
It's worse than I thought. Increments of 2 fail even when aa factor of
100 away from the limit:
kevin@plato-x:~$ seq 170141183460469231731687303715884105721 1
170141183460469231731687303715884105725 | head -10
170141183460469231731687303715884105721
170141183460469231731687303715884105722
n Dec 11 17:53:23 2017
> InstallationDate: Installed on 2016-08-08 (490 days ago)
> InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
> (20160719)
> SourcePackage: ntp
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage not
Public bug reported:
This is a feature request.
When solving a problem or in a rush, I don't necessarily remember
everything from a man page, or even think to read it. This is what
happened with ntpdate(8)
$ ntpdate
11 Dec 20:08:12 ntpdate[13930]: no servers can be used, exiting
$
Of course,
Public bug reported:
The INVOCATION section of the man page has the text
"reads and executes commands from ~/.bashrc and ~/.bashrc, if these
files exist and are readable"
which repeats "~/.bashrc". By experiment, I find it probable that the
first of these .bashrc references should read
Oops. I did locate the directory on a backup. As you supposed, I had
created queue.py initially to do the test. I re-ran it as 'q.py' to see if
that helped, but did not delete the original. So you were right -- name
conflict.
On Fri, Oct 20, 2017 at 8:06 AM, Kevin O'Gorman <kogor...@gmail.
op: XFCE
> Date: Wed Sep 28 20:54:17 2016
> InstallationDate: Installed on 2016-08-08 (51 days ago)
> InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
> (20160719)
> SourcePackage: python3-defaults
> UpgradeStatus: No upgrade log present (probab
6-08-08 (214 days ago)
> InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
> (20160719)
> SourcePackage: python3-defaults
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
&
The machine is a Core i7 with 32 GB RAM. The swap space is also 32 GB.
Nothing else was active during this run other than the usual daemons;
some terminal and browser windows were open, but not in use.
The activity was all on a RAID which had at the time 2 TB free.
--
You received this bug
Public bug reported:
I got a seg fault and core dump about 5 hours into a hand-coded merge of
two databases.
WAL (write-ahead logging) was enabled, and the journal was about 500MB,
so I tried again with periodic commits, and after about 20 hours its
still going strong.
In any event, I regard a
Public bug reported:
On booting my system, I see dialog reporting a "system program error"
with no further information, and is asks me if I want to report this.
I have no basis on which to make the choice, because I have been
completely unable to figure out what problem is being reported. The
Public bug reported:
I've seen this on two systems: Xubuntu on dual Xeons, and Ubuntu on an
I-7.
When I choose "advanced options" -> "recovery mode" in Grub, and then
"root shell prompt" in the resulting booted system, I cannot expect it
to be functional for long.
I can do a few things, but
Public bug reported:
I prefer very light background colors, unlike the default xterm's black.
Some time ago, less(1) changed its way of doing highlights (such as when
displaying man pages) so that they are pure white. This makes them much
harder, rather than the intended easier to read.
This
I modified the code to issue commit() calls, which it had not been
doing. It ran to completion, having made over 3 million changes to the
database. Perhaps a really big journal does not work well? Even if so,
I would consider a segmentation fault a bug.
--
You received this bug notification
Public bug reported:
Running a Python 3 / sqlite3 script that develops a database
representing a game tree, a segmentation fault occurred.
The program had written 4,910,495 lines of output when it crashed, redirected
to a file. It
appears normal, and its size is about right for the job being
usicians.com/viewtopic.php?t=16056
>
> https://www.drupal.org/node/2324991 (clues on root cause)
>
> ProblemType: Bug
> DistroRelease: Ubuntu 16.10
> Package: apt 1.3.3
> ProcVersionSignature: Ubuntu 4.8.0-30.32-lowlatency 4.8.6
> Uname: Linux 4.8.0-30-lowlatency x8
Public bug reported:
Attempting to install either python-pip or python3-pip does a request
for a media change, and not having that medium, it cannot be done.
This occurs for me on Xubuntu amd-64, but NOT on i386.
It occurs to me this may belong to the python and python3 packages, but
since I
Public bug reported:
All matches, whether compiled or not, appear to be anchored to the beginning of
the target string.
Un-anchoring requires a beginning ".*" in the pattern
kevin@plato-x:/raid/917$ python3
Python 3.5.2 (default, Nov 17 2016, 17:05:23)
[GCC 5.4.0 20160609] on linux
Type
Public bug reported:
All matches, whether compiled or not, appear to be anchored to the beginning of
the target string.
Un-anchoring requires a beginning ".*" in the pattern
kevin@plato-x:/raid/917$ python3
Python 3.5.2 (default, Nov 17 2016, 17:05:23)
[GCC 5.4.0 20160609] on linux
Type
Public bug reported:
My monitors become unavailable and hard to configure after blanking, or
switching to a different input, let alone unplugging.
I can boot into 14.04 and do not see this problem. It is present in
16.04. I did not use the releases in between on this system.
It is a core-i7
*** This bug is a duplicate of bug 1637213 ***
https://bugs.launchpad.net/bugs/1637213
** This bug has been marked a duplicate of bug 1637213
ubuntu-bug begins with a warning message
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
ubuntu-bug begins immediately with the following warning message, which
I'm pretty sure just confuses most of us. If this gets posted, then the
message does not indicate a failure.
/usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without
specifying a version
Public bug reported:
starting ubuntu-bug, it outputs this warning message immediately:
/usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without
specifying a version first. Use gi.require_version('Wnck', '3.0') before import
to ensure that the right version gets loaded.
from
Public bug reported:
Trying the examples from
https://docs.python.org/3.5/library/multiprocessing.html#exchanging-objects-between-processes
the example for Pool fails. It's attached. The error implicates something
missing in SimpleQueue
$ python3 Pool.py
Traceback (most recent call last):
Noting still further: When I tried the same program with the default
Python (2.7), it worked just as the documentation promised, so the
problem is in the Python 3.5 build.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Noting further: There's a Note at the bottom of the entry for Queue in 17.2.2.2,
https://docs.python.org/3.5/library/multiprocessing.html#pipes-and-queues
which says that ImportErrors can be caused by failure of the system to support
semaphores, as outlined in Issue3770 (Closed years ago):
Public bug reported:
Reading https://docs.python.org/3.5/library/multiprocessing.html
#exchanging-objects-between-processes, I have copy-pasted the code into
a file. Running it with python3 fails thus:
Traceback (most recent call last):
File "q.py", line 7, in
q = Queue()
File
Public bug reported:
I run the command "ubuntu-bug" (with no package name) and it reports
errors that I did not see in previous releases of Ubuntu:
> kevin@camelot-x:~$ ubuntu-bug
> /usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without
> specifying a version first. Use
Public bug reported:
I have a pipeline of about 2 dozen commands that I expect will run for
2-3 weeks, with top running concurrently in another window. They are
compute-intensive, and there is always at least one one that is running
and sometimes more. In spite of this after several days, top
This is probably obvious, but if like me you don't have or want a modem, you
can remove the package that's generating these messages:
apt-get remove modemmanager
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager
Public bug reported:
The --reverse option is supposed to reverse the sense of comparisons, but does
not affect numeric ('g' or 'n') sorts.
With the input filed 02 q
l 10 f
abc 01 x
abc 01 y
abc 01 z
n 10 u
d 02 m
d 02 b
b 10 c
I get the same results with either of
sort --reverse -k2n
sort -k2n
Public bug reported:
I have a program that I'm debugging. It generates enormous log files
which I need to peruse. I use vim as the tool of choice ordinarily, but
vim stops loading the text when it reaches line 2147483647. That sounds
familiar.
It gives no hint of what's wrong, so I tried
54 matches
Mail list logo
