** Changed in: bash-completion (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/492611
Title:
Java -cp ../classpath completion no longer working in
Public bug reported:
patch against dput 0.9.6.4ubuntu1.1
1. /usr/share/doc/bash-completion/README.Debian says to use dh_bash-
completion to install the completion script. Then it's not even a
conffile, so you don't have to test have dput before loading the
completion funtion, since it won't be
/usr/share/bash-completion/completions/ktutil has
complete -F _ktutil ktutil
so this was fixed at some point.
** Changed in: bash-completion (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Not seeing this in Trusty. Assuming fixed somewhere between then and
now.
** Changed in: bash-completion (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
on Trusty, nothing obvious goes wrong with shopt -s failglob.
set -o nounset breaks everything, though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/663111
Title:
bash_completion script errors:
** Changed in: bash-completion (Ubuntu)
Status: Confirmed = Fix Released
** Summary changed:
- ubuntu maverick - bash auto-completion (Tab) works only for first word
+ programmable completion not enabled for non-login shells in default install
[Maverick]
--
You received this bug
Can anyone else confirm that /usr/bin/python /etc/baTAB is a valid
testcase for this? Or is ln -s /usr/bin/python tmp/python needed?
I'm not seeing a problem on trusty with Nicolas's testcase, but I don't
have anything special with python source lying around.
** Changed in: bash-completion
fixed in trusty or earlier.
** Changed in: bash-completion (Ubuntu)
Status: New = Fix Committed
** Changed in: bash-completion (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: bash-completion (Ubuntu)
Status: New = 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/684126
Title:
perforce bash completion fails at call to
reassigning this to mysql. Packages can provide their own completion
rules and install them with dh_bash-completion. Not every tool needs to
have its completions shipped in bash-completions to be installed on
every system regardless of whether the tool is installed or not.
There's already a
bash-completion no longer ships anything in /etc/bash_completion.d, it
uses the new dynamic loading mechanism for /usr/share/bash-
completion/completions/.
So this bug is now irrelevant, even if it never got fixed.
** Changed in: bash-completion (Ubuntu)
Status: New = Fix Released
--
** Summary changed:
- bash_completion script errors: undefined variables, failed GLOB
+ errors with set -o nounset
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/663111
Title:
errors with set -o
not reproducible on trusty. I have mutt installed, but my mailserver is
an old Debian box that I ssh to and run mutt on, so I don't have
anything but the default mutt setup to test with easily on current
Ubuntu.
reopen if this is still actually broken.
** Changed in: bash-completion (Ubuntu)
** Summary changed:
- Autocomplete fails on some filenames
+ Autocomplete fails on embedded newlines
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/692554
Title:
Autocomplete fails on embedded
*** This bug is a duplicate of bug 484628 ***
https://bugs.launchpad.net/bugs/484628
I put a \ at the beginning of the command to get default filename
completion. Or use M-/ instead of tab. But yeah, it would be good for
some commands to be flagged to fall back to things that don't match
** Changed in: bash-completion (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/692562
Title:
completion of inserted option after command throws bash
fixed sometime before trusty. Except that cd $dir/tab doesn't
expand or complete any subdirs in /etc. So probably something was
getting evalled too many times, and it isn't now, or just code changes
makes it work differently now.
** Changed in: bash-completion (Ubuntu)
Status:
** Changed in: bash-completion (Ubuntu)
Status: New = 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/745767
Title:
python tab-completion error: bash: COMP_WORDS: bad array
fixed in trusty or earlier, IDK.
** Changed in: bash-completion (Ubuntu)
Status: New = 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/755646
Title:
attempting to complete dpkg
** Changed in: bash-completion (Ubuntu)
Status: New = 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/776561
Title:
Errors with insmod, modprobe, modinfo
To manage notifications
** Changed in: bash-completion (Ubuntu)
Status: New = 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/778679
Title:
_available_interfaces fails without gawk installed
To manage
** Changed in: bash-completion (Ubuntu)
Status: New = 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/794885
Title:
Complete filename.spkg after tar *j*f for www.sagemath.org
To
touch $'tab\ttab'
echo ta[TAB] = works
echo tabliteral tabta[TAB] = works
so it's fixed in Trusty, or earlier.
** Changed in: bash-completion (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
did your computer have bad RAM when you installed or upgraded? In any
case, /usr/share/bash-completion/completions/postfix looks fine.
(/etc/bash_completion.d is obsolete)
** Changed in: bash-completion (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you
It's working fine for me. Do you have some old cruft in
/etc/bash_completion.d that's causing trouble?
And btw, yes once the completion code for ls option processing figures
out that it's completing a filename, it passes it to the same code
that's used generically for filenames. So if that's
dpkg completion now uses _parse_help to get the list of valid options
from dpkg.
** Changed in: bash-completion (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think rsync over ssh passes the command to be run through ssh
directly, rather than feeding it to an interactive shell on the remote
side.
If you run a shell script, bash doesn't even source your .bashrc, so
no, programmable completion isn't even loaded when you run a non-
interactive shell.
BTW, upstream already had the no-results no-errors behaviour, so my
patch didn't actually change anything behaviour-wise in upstream, just
in trusty.
same change in _quote_readline_by_ref():
-[[ ${!2} == \$* ]] eval $2=${!2}
+[[ ${!2} == \$\'* ]] eval $2=${!2}
I'd suggest going with
** Summary changed:
- tab bash-completion adds an unwanted space so path name expansion fails
+ unwanted space after directory completion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1372286
Title:
This doesn't happen on a normal Trusty system, but yeah, there are
similar reports of this happening to people. Must be some kind of
leftover stuff from upgrades. My system has an upgrade chain going back
to Edgy (6.10), but I keep it tidy with aptitude and other tools.
You may have some cruft
If we can figure out if there's one bad file that is commonly left lying
around, and breaks things, a workaround can be shipped in bash-
completion to blacklist it.
I'm going to close any pre-trusty reports of this, since they're
probably the acroread crap. And point those bugs to here.
I
Trusty blacklists acroread.sh from bash_completion.d, so does upstream.
If you still have this on Trusty, bug 1372286 needs to know what other
files to blacklist to un-break completion.
Good testcase and description of exactly what the bug is, copied it for
1372286.
** Changed in:
** Summary changed:
- Tab key not showing possible files
+ jar uf foo.jar xx/yy/zz.class not completing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070250
Title:
jar uf foo.jar xx/yy/zz.class
** Changed in: bash-completion (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1162637
Title:
command completion
To manage notifications about this bug
If this wasn't /etc/bash_completion.d/acroread.sh (which is now
blacklisted), then add info to bug 1372286. If we can file more
problematic files to blacklist, we can prevent this problem for other
people.
Closing this because it was reported against a version before the
acroread blacklist was
If this wasn't /etc/bash_completion.d/acroread.sh (which is now
blacklisted), then add info to bug 1372286. If we can find more
problematic files to blacklist, we can prevent this problem for other
people.
Closing this because it was reported against a version before the
acroread blacklist was
This is 2 separate bugs:
1: yeah, jar completion seems to be broken for jar uf foo.jar ...
2: yeah, completion of args inside command substitution is broken, if you mean
that
cvs -d `cat filenam[TAB] = nothing
This is related to bug 1312243, but it's sort of different. I filed upstream
*** This bug is a duplicate of bug 890913 ***
https://bugs.launchpad.net/bugs/890913
** This bug has been marked a duplicate of bug 890913
Typing prg $HOME/tab expands to prg \$HOME/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
*** This bug is a duplicate of bug 890913 ***
https://bugs.launchpad.net/bugs/890913
** This bug has been marked a duplicate of bug 890913
Typing prg $HOME/tab expands to prg \$HOME/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
btrfs-tools could ship the contributed completions just as easily, and
install them with dh_bash-completion.
See /share/doc/bash-completion/README.Debian
** Also affects: btrfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
works for me on trusty. I don't have lilypond installed, but lilypond
completion is in the main bash_completion script now, so I can test it.
** Changed in: bash-completion (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Is this still a problem? I don't see anything wrong with completion for
vi / vim. bash_completion ships with
_install_xspec
'*.@(o|so|so.!(conf|*/*)|a|[rs]pm|gif|jp?(e)g|mp3|mp?(e)g|avi|asf|ogg|class)'
vi vim gvim rvim view rview rgvim rgview gview emacs xemacs sxemacs kate
kwrite
The xspec
related: upstream
https://alioth.debian.org/tracker/index.php?func=detailaid=314895group_id=100114atid=413095
Which I opened to report the fact that completion inside either kind of
command substitution is broken, even when not spewing errors.
** Bug watch added: alioth.debian.org/ #314895
IDK how this got added to bash-completion. It's already an arch:all
binary package, since it's just shell code.
Ah, I see. False positive from Steve's text search that found:
completions/strace:done 2/dev/null
/usr/include/asm/unistd.h
./completions/strace:
just saw Steve's earlier comment, apparently the logic to pick the right
unistd_32.h or unistd_64.h was added after that, so this is Fix
Released, not Invalid.
There's now asm/unistd_x32.h as well. AFAICT from poking around in the
kernel source, uname -m should return x86_64 when called from a
Anything that completes on package names is potentially going to be
slow, because esp. on the first run.
some dpkg and apt commands are slow when the binaries and the data they
need all have to get loaded from disk.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: bash-completion (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/675987
Title:
Add auto-complete support for various office file format
This is upstream
https://alioth.debian.org/tracker/index.php?func=detailaid=311399group_id=100114atid=413095
As the comments there show, fixing this is hard, and means you can't
even use compgen. (compgen uses newline as its output record
separator.)
** Changed in: bash-completion (Ubuntu)
You can get default completion behaviour (not the special-case stuff)
for a command by doing e.g. \xine. \cmd also disables alias expansion.
The \ just quotes the first letter of the command, but that's enough to
disable some stuff that bash would otherwise do.
--
You received this bug
This should prob. get closed, since Norbert's confirmation turned out to
be in error
** Changed in: bash-completion (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The problem is a lack of quoting in
/usr/share/bash_completion/bash_completion.
set -x revealed where the problem happens: in a compgen -X -f. $quoted
is used without quotes, so it expands, and you get the first of however
many glob expansions.
There are two unquoted uses of $quoted in
/usr/share/bash-completion/bash_completion has a bunch of stuff about
treating : specially, for completing host:path in scp and similar
commands. Spent a bit of time looking at the source of this behaviour,
but haven't found it yet.
set -x before pressing tab, and paste that into a file to look
The fix for bug 1387057 (correctly quoting $quoted) also fixes this.
$ compgen -f 1\'2
1'2 2
@wojtas: completion inside $(command substitutions) is a separate bug.
Fixing the quoting bug didn't solve that. I see you already commented
in bug 1312243, which is what you're seeing.
--
You
*** This bug is a duplicate of bug 1312243 ***
https://bugs.launchpad.net/bugs/1312243
** This bug has been marked a duplicate of bug 1312243
Bash completion within $( fails in Trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Still broken in 14.04, bash-completion 1:2.1-4, even with the fixes for
bug 1387057 and bug 1390061 applied.
Even the fallback minimal completion function fails for that directory from the
OP.
mkdir -- $'--$`\! *@ \a\b\e\E\f\r\t\v' \n'
echo ./-[TAB]bash: bad substitution: no closing ` in
*** This bug is a duplicate of bug 1387057 ***
https://bugs.launchpad.net/bugs/1387057
** This bug has been marked a duplicate of bug 1387057
wildcard incorrect completion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1387057 ***
https://bugs.launchpad.net/bugs/1387057
another symptom of missing quotes on $quoted, see my fix for bug
1387057. Works for me on trusty with that fix applied.
** This bug has been marked a duplicate of bug 1387057
wildcard incorrect
another workaround: as /usr/share/doc/bash-completion/README.gz
suggests, use M-/ to use bash's builtin filename completion, rather than
calling the programmable completion functions. That will complete on
any filename, since it doesn't have any command-specific filtering.
--
You received this
works for me, at least after applying the fix for bug 1387057 (properly
quoting $quoted). On Trusty. This is probably the same bug.
Or maybe not: I'm seeing
$ echo ././foo[TAB] turns into
$ echo ./././foo
every [TAB] adds another ./
foo does get expanded to the longest common prefix of
Apparently this is a known problem that can't be fixed. /usr/share/doc
/bash-completion/README.gz FAQ says:
Q. Completion goes awry when I try to complete on something that contains
a colon.
A. This is actually a 'feature' of bash. bash recognises a colon as
starting a new completion
further update: comments for __ltrim_colon_completions() in /usr/share
/bash-completion/bash_completion say you can
# Remove colon (:) from list of word completion separators
#COMP_WORDBREAKS=${COMP_WORDBREAKS//:}
in your .bashrc
Looked into this some, and I think I might have a fix. The problem is
the backquote, and what we're seeing here is related to the reports of
completion inside $( failing.
the progcomp code uses a lot of constructs like eval $z=$foo, to assign by
reference to a variable whose name is stored as
** Changed in: bash-completion (Ubuntu)
Status: Triaged = 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/254426
Title:
Bash programmed autocomplete of commands with space within
Yeah, I'm not seeing the OP's bug at all, even when sourcing Trusty's
unmodified bash_completion.
The directories inside quotes problem is a different thing. Marked as
fixed, prob. by upstream ages ago.
** Changed in: bash-completion (Ubuntu)
Status: Confirmed = Fix Released
--
You
Hmm, well what's crossing it up is the embedded newline in the filename.
_filedir does
local IFS=$'\n'
...
x=$( compgen -f -X $xspec -- $quoted )
while read -r tmp; do
toks+=( $tmp )
done $x
...
if [[ ${#toks[@]} -ne 0 ]]; then
# 2/dev/null
submitted upstream as
https://alioth.debian.org/tracker/index.php?func=detailaid=314891group_id=100114atid=413095
bug 1390061 is fixed upstream, as a side-effect of reworking the
relevant code.
** Bug watch added: alioth.debian.org/ #314891
This is upstream
https://alioth.debian.org/tracker/index.php?func=detailaid=314667group_id=100114atid=413095
Patch submitted there that makes it at least not spew errors, even
though it still doesn't complete args inside $(command substitution).
** Bug watch added: alioth.debian.org/ #314667
Actually, this isn't broken even with Trusty's unchanged file. Unless
I'm missing something, the OP's testcase works fine on Trusty, so
marking this fix-released
** Changed in: bash-completion (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you
Yup, will test this sometime this week and post again. Good suggestion,
hadn't even thought of doing that, derp. :P
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1395269
Title:
[e1000e] ethtool
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1395269/+attachment/4265982/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1395269
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1395269/+attachment/4265991/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1395269
Title:
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/1395269/+attachment/4265993/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1395269/+attachment/4265986/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1395269
apport information
** Attachment added: PulseList.txt
https://bugs.launchpad.net/bugs/1395269/+attachment/4265990/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1395269
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1395269/+attachment/4265987/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1395269
apport information
** Summary changed:
- ethtool -t eth0 offline loses routing table
+ [e1000e] ethtool -t eth0 offline loses routing table
** Tags added: apport-collected
** Description changed:
ethtool -t eth0 offline does the tests, but leaves the routing table
with only the entry for
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1395269/+attachment/4265985/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1395269
Title:
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1395269/+attachment/4265984/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1395269
Title:
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1395269/+attachment/4265992/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1395269
Title:
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1395269/+attachment/4265988/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1395269/+attachment/4265983/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1395269
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1395269/+attachment/4265989/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1395269
So the idea is for drivers to not tell the kernel that the interface
went down, while it's doing self-tests? I guess igb had this problem
fixed, according to the redhat bug, but I guess not e1000e.
Yes, I'm pretty sure the interface goes down during the offline portion
of the full set of
Public bug reported:
ethtool -t eth0 offline does the tests, but leaves the routing table
with only the entry for the local network. I had to sudo route add
default gw 10.0.0.1, in my case. The online test didn't do this.
Ubuntu 14.04, ethtool 1:3.13-1
Linux tesla 3.13.0-39-generic #66-Ubuntu
Public bug reported:
ethtool -t eth0 offline does the tests, but leaves the routing table
with only the entry for the local network. I had to sudo route add
default gw 10.0.0.1, in my case. The online test didn't do this.
Ubuntu 14.04, ethtool 1:3.13-1
Linux tesla 3.13.0-39-generic #66-Ubuntu
discussion on bugs.debian.org/755023 indicates that the gnome-session
may have recently started actually depending on gnome-shell, so the
appropriate dependency is Depends, which Debian currently has.
** Summary changed:
- should have a recommends: on gnome-shell
+ should have a recommends: on
IDK if having any part of your system on a filesystem that doesn't
support all the usual stuff (like symlinks) is officially supported.
memtest isn't available anymore, as I guess it's been removed since
memtest86+ has been the better choice for years. So this bug should
probably get closed,
Try df -i. You might have run out of inodes if you're using ext4, where
you have to allocate space for inodes at FS creation time. This
happened to me when upgrading 12.04 to 14.04. I got a no space left on
device error while a postinst script was running for something. I'm
still worried I
This kind of thing happens because each package has scripts to make sure
needed stuff gets done, and there's no mechanism for telling it that
more things are going to change again later.
do-release-upgrade doesn't know the details of what every package does
in its postinst. Things don't happen
No text in the bug description. Tell us what the problem is and change
the bug status back to New if you have a bug to report.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I was going to add https://bugs.launchpad.net/ubuntu/+source/ubuntu-
release-upgrader/+bug/1319688 as a duplicate of this, thinking that the
submitter of that bug was mixed up, and hadn't read the prompt carefully
to see it was about config files. However, do-release-upgrade does
actually prompt
See also
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1309802
about the prompts to deal with changed config files.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1319688
You need to provide more information, like which package had a problem.
Try running ubuntu-bug ubuntu-release-upgrader-core in a shell, to
collect information from your system.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New = Incomplete
--
You received this bug notification
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-
upgrader/+bug/1242066 is also very similar. Most packages don't have a
lot of debconf questions these days, and just use debconf for changed-
config-file prompts, but other debconf questions must surely exist in
some packages. (I'm not
I've been collecting up links to the various bugs about prompts during upgrades:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1309802
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
also:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1297318
is looking for a --force-yes for all questions. Presumably including those
asked by children of do-release-upgrade, i.e. dpkg and debconf.
--
You received this bug notification because you are a member of
see
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1007543
for discussion of why upgrades should be fully GUI, and preferably completely
non-interactive, so non-technical users don't get stuck.
--
You received this bug notification because you are a member of Ubuntu
Yes, the comments compound, if I recall correctly.
IDK why you don't just edit the text files (/etc/apt/sources.list, and
/etc/apt/sources.list.d/*.list) with an editor, esp. if the GUI sucks.
It's pretty common practice for tools that mess with your config files
to leave extra comments showing
Public bug reported:
on my seldom-used laptop, (running 12.04LTS last updates early august 2013) I
ran
sudo do-release-upgrade -p
from bash in a gnome-terminal.
It proceeded fine, until for one of the changed-config-file prompts I
had it start a shell to examine the situation. I ran jed, a
** Description changed:
- on my seldom-used laptop, (running 12.04LTS last updates early august 2013) I
ran
- sudo do-release-upgrade -p
+ on my seldom-used laptop, (running 12.04LTS last updates early august 2013) I
ran
+ sudo do-release-upgrade -p
from bash in a gnome-terminal.
- It
101 - 200 of 547 matches
Mail list logo
