That still worked fine in 14.04 (allowing to create a custom preseed
script easily), not working in 16.04 or 18.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647368
Title:
[16.04.1 LTS]
Public bug reported:
/usr/share/doc/geoipupdate/examples/GeoIP.conf.default
The file comes w/ default values that won't work, and render a 401 when
geoipupdate is run.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: geoipupdate 2.2.1-1
ProcVersionSignature: Ubuntu
Public bug reported:
This snippet, taken from /etc/bash.bashrc, errors out on the here document,
even though the
man page states that <<-EOF should allow for the terminating EOF to be indented.
#!/bin/bash
# sudo hint
if [ ! -e "$HOME/.sudo_as_admin_successful" ] && [ ! -e "$HOME/.hushlogin" ]
Stripping whitepsace in front of the EOF on line 9 makes the error go
away.
** Also affects: bash (Ubuntu)
Importance: Undecided
Status: New
** Package changed: open-iscsi (Ubuntu) => ubuntu
** No longer affects: ubuntu
--
You received this bug notification because you are a member
Ping
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1083135
Title:
open-iscsi bound to if-*.d in networking kills iSCSI connections
To manage notifications about this bug go to:
Thanks for the "workaround" Stefan Tauner.
I am (still) in the process of upgrading a whole bunch of machines from
12.04 to 14.04, and out of 8 boxes so far only one has displayed this
behvaviour - your workaround worked a treat.
The interesting bit (for me, anyway) was that 6 of the machines
** Package changed: ubuntu => gawk (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647879
Title:
gawk regex range operator not working
To manage notifications about this bug go to:
Public bug reported:
cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.04
DISTRIB_CODENAME=precise
DISTRIB_DESCRIPTION="Ubuntu 12.04.5 LTS"
awk --version
GNU Awk 3.1.8
Copyright (C) 1989, 1991-2010 Free Software Foundation.
apt-cache policy gawk
gawk:
Installed:
Thanks Seth, I doubt that keychain is (even in part) responsible for
this behaviour; I'll try to confirm Tuesday - after the long weekend -
when I'm back at work.
Thanks for responding Robie.
I apologise - was on a rampage because the other bug that I'm sitting on
(not as the original reporter,
And since I'm in a prodding mood ...
Hello?
This is *still* biting us.
Anyone?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1083135
Title:
open-iscsi bound to if-*.d in networking kills iSCSI
Over a year gone, and the problem still exists?
Am I the only one who occasinally logs into a machine running ssh-agent?
Are others happy to log out of the running X session and log back in every
time the ssh'ed to a machine?
No one really gives a rats arse?
--
You received this bug
Hello?
Still not even classified?
Seriously? :/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1083135
Title:
open-iscsi bound to if-*.d in networking kills iSCSI connections
To manage
Public bug reported:
npm http GET https://registry.npmjs.org/chromix
npm ERR! Error: failed to fetch from registry: chromix
npm ERR! at /usr/share/npm/lib/utils/npm-registry-client/get.js:139:12
npm ERR! at cb
(/usr/share/npm/lib/utils/npm-registry-client/request.js:31:9)
npm ERR!
Open for 2.5 years .. yay.
This keeps biting us; can someone PLEASE look into this?
Or alternatively explain to me at which point in the init hierarchy I need to
dig to make this go away; I have a snippet of code that will determine reliably
which interfaces are a) iscsi and b) active, and only
Ooops ... sorry ... thanks for the update!
On 12 May 2015 at 08:44, Seth Arnold 1446...@bugs.launchpad.net wrote:
Andrej, sorry, normally the person who supplies the additional
information sets the status back to 'new' or 'confirmed' as needed. We
don't say that nearly often enough. sorry.
Ooops ... sorry ... thanks for the update!
On 12 May 2015 at 08:44, Seth Arnold 1446...@bugs.launchpad.net wrote:
Andrej, sorry, normally the person who supplies the additional
information sets the status back to 'new' or 'confirmed' as needed. We
don't say that nearly often enough. sorry.
Can you please let me know in which way this is still incomplete?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1446448
Title:
ssh-agent terminates
To manage notifications about this bug go to:
Can you please let me know in which way this is still incomplete?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1446448
Title:
ssh-agent terminates
To manage notifications about
knock knock
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1446448
Title:
ssh-agent terminates
To manage notifications about this bug go to:
knock knock
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1446448
Title:
ssh-agent terminates
To manage notifications about this bug go to:
Still incomplete?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1446448
Title:
ssh-agent terminates
To manage notifications about this bug go to:
Still incomplete?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1446448
Title:
ssh-agent terminates
To manage notifications about this bug go to:
Hi Robie,
The pid I posted didn't exist on the system anymore when you asked.
I took a snapshot of current pids, ran the scp from remote again, this
time the pid in question was 31397, and that, too, appears to be transient.
After ssh-agent died that pid didn't exist anymore. Any cunning plan on
Hi Robie,
The pid I posted didn't exist on the system anymore when you asked.
I took a snapshot of current pids, ran the scp from remote again, this
time the pid in question was 31397, and that, too, appears to be transient.
After ssh-agent died that pid didn't exist anymore. Any cunning plan on
Aight, thanks Seth for the execsnoop link, excellent stuff to have in
your tool-box. I just re-ran my test-case, and this is the new strace
output, with the correlating execsnoop snippet.
select(5, [3 4], [], NULL, NULL)= 1 (in [4])
read(4, \0\0\0\1\v, 1024) = 5
select(5, [3
Aight, thanks Seth for the execsnoop link, excellent stuff to have in
your tool-box. I just re-ran my test-case, and this is the new strace
output, with the correlating execsnoop snippet.
select(5, [3 4], [], NULL, NULL)= 1 (in [4])
read(4, \0\0\0\1\v, 1024) = 5
select(5, [3
Public bug reported:
I have set-up password less ssh connectivity for my workstation. ssh-
agent gets started via keychain when fluxbox boots.
When I use ssh to connect to a server, and then use scp to shuffle a
file from that server to my workstation the ssh-agent on my workstation
dies after
Public bug reported:
I have set-up password less ssh connectivity for my workstation. ssh-
agent gets started via keychain when fluxbox boots.
When I use ssh to connect to a server, and then use scp to shuffle a
file from that server to my workstation the ssh-agent on my workstation
dies after
Same issue, but with the server process dying.
Thanks Václav for your work-around; that worked a treat (and fixed the
keyboard lag, too ;}).
Ubuntu 14.04.1 LTS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
And another one ... any time someone touches an interface we lose disk-
volumes mounted via open-iscsi. Not good. Specifically when they were
being written to at the time the only way of getting back to the disks
is to reboot the machine because the writing process is blocking and
can't be killed.
30 matches
Mail list logo
