I don't think this is an openconnect issue? Or are you handling network
manager issues there too? I see the Ubuntu patch was merged upstream
since this was opened?
"External browser" would be nice, but IT says we can't turn it on, needs
some upgrade, and CISCO says not to use it:
The saml
Upon more research it seems there is alot more wrong here than the
misleading message from Duo.
GTK Webkit completely lacks support for webauthn, so it is pointless to
think about anything at the network-manager-openconnect level. This
means this will not support security tokens for VPN login.
That does, work, note that the leading and trailing _ are garbage, file
should be:
root@c5c1367d7a8e:/# cat /tmp/openssl.conf
openssl_conf = openssl_init
[openssl_init]
ssl_conf = ssl_sect
[ssl_sect]
system_default = system_default_sect
[system_default_sect]
Options = UnsafeLegacyRenegotiation
Public bug reported:
Thanks a lot for working on the new SAML support for openconnect, I just
succeeded to make it work with our cisco anyconnect setup - it is going
to make a lot of people happy here. Is there any thing I can do to help
get the upstream parts merged - eg confirm it works etc?
On Mon, Apr 11, 2022 at 6:00 PM Dan Lenski <1968...@bugs.launchpad.net>
wrote:
> > My feeling is that curl should set the SSL option when -k is used.
> openconnect itself sets this option already, it was fixed in commit
> c8dcf10
>
> If you replace the cURL invocation in the CSD/Trojan script
Public bug reported:
The CSD scripts all use curl to communicate to the ASA server and in
Jammy curl has been linked with openssl 3.
openssl 3 switched off SSL_OP_LEGACY_SERVER_CONNECT by default, and
CISCO never implemented RFC5746 in ASA so the curl commands in the CSD
script just fail to
This still happens on a fresh Focal install using linux-
image-5.4.0-26-generic version 5.4.0-26.30
** Also affects: linux-signed (Ubuntu)
Importance: Undecided
Status: New
** Tags removed: bionic
** Tags added: focal
--
You received this bug notification because you are a member of
Public bug reported:
This system is a Dell Precision Tower 3420 with the latest BIOS 2.13.1,
kernel version is 5.3.0-26-generic (HWE, bionic)
Freshly booting the system and doing something CPU intensive, like
compiling a kernel, cause the CPU fan to ramp up as expected and the CPU
temperatures
Were you still wanting to test this new kernel?
On Mon, Jul 25, 2016 at 2:33 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> This does appear to be an Ubuntu specific kernel. I'll build an Ubuntu
> kernel based on 4.0 and post a link to it for testing.
>
> --
> You received this
Wasn't testing with 3.16 and 3.19 ubuntu patched kernels enough to disprove
the grub theory?
Jason
On Mon, Jul 25, 2016 at 1:44 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> Can you see if the bug still happens when booting a Trusty kernel on the
> Xenial system? This can be
As a clarification, the mainline boot behaviour is identical to the Ubuntu
kernel with $vt_handoff removed. I double checked that the option is
present in grub for all the tests. I guess this isn't surprising since that
option isn't part of mainline.
Jason
On Wed, Jul 20, 2016 at 8:30 PM, Jason
4.1.0-040100-generic works
4.4.14-040414-generic works
Didn't test others.
The boot sequence is different with the main line kernels. There is a black
screen period with a couple of messages (1-2s), then the console font load,
then it briefly switches to the splash, black screen flash back to
On Mon, Jul 18, 2016 at 2:48 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> Does booting back into the Trusty kernel on the Xenial installed system
> make the bug go away?
>
Yes. I've done multiple reboot experiments now and have learned the bug
only happens about 80% of the
Public bug reported:
This is a regression, at least trusty (and prior) worked fine on this
hardware.
Booting the Xenial installer image off USB also worked fine.
The system boots fine, however the monitor is in DPMS power-off and does
not ever turn back on. Switching VTs doesn't help, I have
Public bug reported:
If you leave openvpn running for long enough it will eventually begin to
fail with output like:
May 27 19:16:54 wakko nm-openvpn[16480]: RESOLVE: Cannot resolve host
address: : Temporary failure in name resolution
Analysis shows this is because openvpn is sending DNS
This still happens in Xenial.
#7 has it right, if the IPv4 and IPv6 'use this connection only for
resources on its network' are different then the default DNS server is
dropped.
It is very easy to make this mistake and very hard to figure out that is
the problem!
--
You received this bug
Public bug reported:
This small example does not compile in Xenial:
#include
#if !(BACKTRACE_SUPPORTED)
#error "Not supported"
#endif
#include
int main(int argc,const char *argv[])
{
struct backtrace_state *state =
backtrace_create_state(nullptr,false,nullptr,nullptr);
}
$ clang++-3.8
I hit this problem as well, booting on my system hangs for three minutes
waiting for udev to settle. I have a HP keyboard.
Booting without the keyboard plugged in, or removing the hplip package
solves the problem.
hplip version 3.15.2-0ubuntu4.1
$ lsusb
Bus 001 Device 002: ID 03f0:0024
Public bug reported:
This is a regression from Trusty, which worked OK
$ rdesktop ads1.ads.orcorp.ca
Connection established using CredSSP.
$ echo $?
76
No GUI appears.
It does go through kerberos steps:
$ klist
05/25/15 15:39:52 05/26/15 01:39:48 TERMSRV/ads1.ads.orcorp.ca@
renew
Ignoring the raid label is the entire problem - that is what the broken
dmraid script is already doing.
Fundamentally, if /dev/sda has a valid RAID label then it *MUST* be setup
and accessed through the dmraid device and *NEVER* via /dev/sda.
Otherwise the installer will see a disc that is too
On Tue, Oct 28, 2014 at 9:06 PM, Phillip Susi ps...@ubuntu.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 10/28/2014 09:55 PM, Jason Gunthorpe wrote:
Fundamentally, if /dev/sda has a valid RAID label then it *MUST* be setup
and accessed through the dmraid device and *NEVER
The LSI option rom will not present a drive to the EFI BIOS without a raid
label on the disc. If the array is deleted then EFI will not boot off the
drive at all. As far as I can tell there is no fall back option rom that
provides simple AHCI services to EFI.
This is the problem, because the boot
You'd think, but if this BIOS has an option to disable the LSI option ROM
and still boot in EFI mode, then it is very well hidden..
On Tue, Oct 14, 2014 at 12:27 PM, Phillip Susi ps...@ubuntu.com wrote:
The test in that script is wrong, but since you only have a single disk,
you should be able
Public bug reported:
I have a Lenovo server with a LSI controller that insists on having a
RAID set to boot. So the BIOS is configured with a RAID0 stripe set,
with a single disk:
$ dmraid -i -si
*** Group superset .ddf1_disks
-- Subset
name :
Turns out this is not just a cosmetic problem, having -1 in a
supplementary group list completely breaks the NFS sever as well, in a
very hard to find way.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
Turns out this is not just a cosmetic problem, having -1 in a
supplementary group list completely breaks the NFS sever as well, in a
very hard to find way.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
This is a regression, 2.9.1+dfsg1-3ubuntu4 and all prior for the last 5
years work fine.
xmllint 2.9.1+dfsg1-3ubuntu4.1 doesn't load entities, for instance
attempting to validate a docbook document:
$ xmllint --load-trace --path build-hosted/doc/ --path doc/ --xinclude
Public bug reported:
This is a regression. Prior versions of Ubuntu allowed the 32 bit and 64
bit libnss-winbind library to co-exist on the same system.
$ apt-get install libnss-winbind:i386
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some
Public bug reported:
Attempting to login via PAM causes winbind to segfault and log this to
syslog:
May 2 16:25:54 jggl winbindd[2416]: [2014/05/02 16:25:54.540190, 0]
../lib/util/fault.c:72(fault_report)
May 2 16:25:54 jggl winbindd[2416]:
groups the user is a part of
are not UNIX groups, they are just general AD groups:
$ ldapsearch uid=jgg memberOf
dn: CN=Jason Gunthorpe,CN=Users,DC=ads,DC=orcorp,DC=ca
memberOf: CN=XWEB Users,CN=Users,DC=ads,DC=orcorp,DC=ca
memberOf: CN=VPN Users,CN=Users,DC=ads,DC=orcorp,DC=ca
memberOf: CN=accounting
Public bug reported:
For emacs to properly parse the result of git grep it must not be fed
through a pager (like less) and it must not include colourization escape
codes.
If a pager is spawned, it might blow up with this:
git grep -n -e ClkIB -- *
WARNING: terminal is not fully functional
-
Public bug reported:
This is a regression. Prior versions of Ubuntu allowed the 32 bit and 64
bit libnss-winbind library to co-exist on the same system.
$ apt-get install libnss-winbind:i386
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some
Public bug reported:
Attempting to login via PAM causes winbind to segfault and log this to
syslog:
May 2 16:25:54 jggl winbindd[2416]: [2014/05/02 16:25:54.540190, 0]
../lib/util/fault.c:72(fault_report)
May 2 16:25:54 jggl winbindd[2416]:
groups the user is a part of
are not UNIX groups, they are just general AD groups:
$ ldapsearch uid=jgg memberOf
dn: CN=Jason Gunthorpe,CN=Users,DC=ads,DC=orcorp,DC=ca
memberOf: CN=XWEB Users,CN=Users,DC=ads,DC=orcorp,DC=ca
memberOf: CN=VPN Users,CN=Users,DC=ads,DC=orcorp,DC=ca
memberOf: CN=accounting
I'm not familiar with Ubuntu's process. This is clearly a bug in Raring,
fixed in upstream and I would certainly like a backport to the Raring
kernel package as we have no plans here to use Saucy, which isn't even
in beta yet :)
--
You received this bug notification because you are a member of
Well, if I understand https://wiki.ubuntu.com/KernelTeam/KernelUpdates
properly, oops fixes for raring will not be accepted since it is not a
LTS and it is past 4 months after release.
So I guess that is the end of it.
--
You received this bug notification because you are a member of Ubuntu
when we already know
that 3.11 solves the issue.
Jason
On Tue, Aug 27, 2013 at 4:07 AM, Christopher M. Penalver
christopher.m.penal...@gmail.com wrote:
Jason Gunthorpe, testing the live environment would be just fine.
--
You received this bug notification because you are subscribed
So, it has been 11 days and 3.11.0-031100rc5-generic hasn't crashed, I
think that is enough to confirm it is fixed in this version.
Per Joseph's instructions I've added the 'kernel-fixed-upstream' and
marked the bug complete.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
they actually seem to fix
oops's with a similar back trace.
On Mon, Aug 26, 2013 at 6:11 PM, Christopher M. Penalver
christopher.m.penal...@gmail.com wrote:
Jason Gunthorpe, could you please confirm this issue exists with the
latest development release of Ubuntu? ISO images are available from
Public bug reported:
It is hard to get an oops because the entire FS system seems to hang and
/var/log/kern.log won't capture it. I have managed to get a kdump
capture. I think I told apport to submit the crash dump, but I'm not
really sure if it worked, and I don't know where to look to see if
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1212818/+attachment/3774137/+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/1212818
Title:
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1212818/+attachment/3774130/+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/1212818
Title:
Using
apport information
** Tags added: apport-collected
** Description changed:
It is hard to get an oops because the entire FS system seems to hang and
/var/log/kern.log won't capture it. I have managed to get a kdump
capture. I think I told apport to submit the crash dump, but I'm not
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1212818/+attachment/3774133/+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: Lspci.txt
https://bugs.launchpad.net/bugs/1212818/+attachment/3774129/+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/1212818
Title:
Using
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/1212818/+attachment/3774138/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1212818
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1212818/+attachment/3774127/+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/1212818
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1212818/+attachment/3774126/+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/1212818
apport information
** Attachment added: HookError_cloud_archive.txt
https://bugs.launchpad.net/bugs/1212818/+attachment/3774128/+files/HookError_cloud_archive.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1212818/+attachment/3774134/+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/1212818
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1212818/+attachment/3774132/+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/1212818
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1212818/+attachment/3774136/+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/1212818
Title:
apport information
** Attachment added: PulseList.txt
https://bugs.launchpad.net/bugs/1212818/+attachment/3774135/+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/1212818
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1212818/+attachment/3774131/+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/1212818
Joseph:
I have successfully booted:
Linux jggl 3.11.0-031100rc5-generic #201308112135 SMP Mon Aug 12
01:35:49 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Since I don't know how to reproduce the crash, I will update this bug
either when 3.11 crashes or in about a weeks time.
** Changed in: linux
Wow, I'm really surprised you guys have decided to turn pipe-lining off.
That is crazy. Pipelining has been in APT since day one (ie since 1997,
wow!), and I personally worked with a number of web server developers to
make sure their severs worked properly, according to the RFC.
Squid has
You really need to use --output to process inline signatures, trying to
exactly match what gnupg validated externally is not a robust way to run
such important crypto. It would be better to require full gpg until gpgv
can be fixed - (not having --output in gpgv only encourages incorrect
use of the
True enough - EFI should use the EFI console interface which hopefully works
reliably. But grub prints a warning message at boot that it cannot locate
hwmatch.lua, so maybe the grub.conf construction scripts should be updated
to not include that fragment if the lua script is not available.
On
Thanks Colin,
I also noticed that the missing lua file is from this:
grub.cfg: if lua ${prefix}/hwmatch.lua; then
when grub.cfg is built by the default scripts. Looks like the EFI packages
should also include this file, or something..
On Mon, Jan 17, 2011 at 1:49 PM, Colin Watson
Public bug reported:
Binary package hint: grub2
This is a bug in the grub-install included in grub-efi-amd64
Running it gives:
$ grub-install
/usr/sbin/grub-install: 391: : Permission denied
/usr/sbin/grub-install: 391: : Permission denied
BootCurrent: 0004
Timeout: 1 seconds
BootOrder:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/702707
Title:
grub-install fails to run due to missing grub_mkdevicemap
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I see this too. This is not similar to kernel bug 12135, this is a
failing order 5 allocation, not a failing order 0 allocation. The net
stack should not be making high order allocations, something to do with
Xen causes them to happen and of course they fail as memory is
fragmented.
--
You
*** This bug is a duplicate of bug 570944 ***
https://bugs.launchpad.net/bugs/570944
Unless someone has a plan to actually go and fix pam_unix, I'd suggest a
better idea is to update pam_winbind's /usr/share/pam-configs/winbind to get
rid of use_authtok.
The objection that this disables
*** This bug is a duplicate of bug 570944 ***
https://bugs.launchpad.net/bugs/570944
Unless someone has a plan to actually go and fix pam_unix, I'd suggest a
better idea is to update pam_winbind's /usr/share/pam-configs/winbind to get
rid of use_authtok.
The objection that this disables
** Visibility changed to: Public
--
passwd doesn't work with pam_winbind
https://bugs.launchpad.net/bugs/681598
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs mailing list
Another use case: 64 bit base OS install running 32 bit proprietary
applications using winbind for NSS. The apps tend to freak out when they
try to do NSS lookups (ie getpwname). Sigh.
--
should distribute a 32 bit version of nss_winbind.so
https://bugs.launchpad.net/bugs/141569
You received
Just had this happen here too, using pam_winbind - gdm displayed the
password has expired message and then it locked up :( On maverick
--
GDM has no change password option
https://bugs.launchpad.net/bugs/114620
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Visibility changed to: Public
--
passwd doesn't work with pam_winbind
https://bugs.launchpad.net/bugs/681598
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Another use case: 64 bit base OS install running 32 bit proprietary
applications using winbind for NSS. The apps tend to freak out when they
try to do NSS lookups (ie getpwname). Sigh.
--
should distribute a 32 bit version of nss_winbind.so
https://bugs.launchpad.net/bugs/141569
You received
Public bug reported:
When calling getaddrinfo and specifying AF_UNSPEC and AI_PASSIVE it
returns both IPv4 and IPv6 addresses when the sysctl net.ipv6.bindv6only
= 0. Proper app behavior for AI_PASSIVE should be to bind and listen to
all returned addresses, but the kernel does not allow binding
--
getaddrinfo and AI_PASSIVE is broken for net.ipv6.bindv6only=0
https://bugs.launchpad.net/bugs/673708
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Just saw this on 10.10 too. /etc/init.d/network-manager restart got
things going again.
--
After OpenVPN NM installed its not work, but when I restarted it will works fine
https://bugs.launchpad.net/bugs/344843
You received this bug notification because you are a member of Ubuntu
Bugs, which is
There is more going on here than just loading a lot of completion.
Something is weird inside bash, look at the strace of completion loading
and you see it is doing a wack of busy work crap like this. The fiddling
with FDs looks like it is probably some kind of errant debug feature?
This is from
Public bug reported:
Binary package hint: pulseaudio
SPDIF works fine if pulseaudio is disabled via aplay
The problem is that this ALSA environment has this mixer control:
Simple mixer control 'IEC958 Playback AC97-SPSA',0
Capabilities: volume volume-joined penum
Playback channels: Mono
** Attachment added: AlsaDevices.txt
https://bugs.launchpad.net/bugs/642551/+attachment/1606393/+files/AlsaDevices.txt
** Attachment added: AplayDevices.txt
https://bugs.launchpad.net/bugs/642551/+attachment/1606394/+files/AplayDevices.txt
** Attachment added: BootDmesg.txt
Public bug reported:
Binary package hint: ubufox
This is quite annoying, we cannot customize system wide settings via the
prefs in /etc/firefox/pref/firefox.js if they are overridden by
/usr/lib/firefox-3.0.1/extensions/[EMAIL PROTECTED]/defaults/preferences
/ubuntu-mods.js
Since the
Public bug reported:
Binary package hint: python-mode
python mode no longer auto loads on emacs21 with gutsy.
Looks like the /etc/emacs/site-start.d/50python-mode.el isn't quite
right, I suspect it got broke while fixing 155681.
By my eye, the entire file should be executed when emacs21 is
77 matches
Mail list logo
