I agree that it is a partial workaround.. it fixes the Ubuntu/Firefox + apache
combination.
But without changing the same thing for all the IIS servers it would still
render my Ubuntu/Firefox + IIS SSO broken.
Since I only administrate the Linux stuff, and the "other side"
genereally are very
Hi Russ.
I cannot say anything about what other are experiencing.. but in our
setup we haven't put the final hostname in the keytab (and neither did
the guys that only cared about MSIE+IIS). And all Ubuntu releases (from
around Dapper) and up and until Lucid has worked for us.
So seen from an Ubu
Hi Sam.
I agree.. the current behaviors seems to be excactly what is in the code
and in the documentation.
Never the less it is a change from earlier versions of Ubuntu and a
change that makes Ubuntu + Firefox work in a different way than MS
Windows + MSIE (negoiating different tickets), thus bre
Tried.. had that before.. but doesn't work any more. (and isn't
documented in man krb5.conf either).
--
krb5 prefers the reverse pointer no matter what for locating service tickets.
https://bugs.launchpad.net/bugs/571572
You received this bug notification because you are a member of Ubuntu
Bugs
Since the problem is in the clientside kerberos libraries it affects all
kerberos enabled stuff.
--
krb5 prefers the reverse pointer no matter what for locating service tickets.
https://bugs.launchpad.net/bugs/571572
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Public bug reported:
I'm trying to upgrade workstations to lucid an fails to access our
kerberos enabled websites. It reveals that the krb5 implementation in
lucid now tries to resolve the "reverse dns" and aquire a tikket for
/ instead of /.
The latter behavior is what the MS environment does an
Hi Dave
Thank you for finally attending to the bug.
Well since the problem now persists in all "official releases" of Ubuntu
as of now, allthough fixed in the current development branch, dont you
think it is a bit premature to close the bug. Even as "invalid" since
fixed is what you actually are
It is really dissapointing .. but there has been posted an awfull lot of
"automated" crap in this bug, by people who either:
* Didnt read the initial bug or
* Did try out the steps to reproduce
Even though it can be done on any installation, just going ahead using
the five points above.
The prob
Public bug reported:
Ubuntu Hardy amd64 with all patches.
Sometimes when snmpd starts it dies with:
[ 374.996791] snmpd[8897] trap divide error rip:7ffd4be9dc2c
rsp:7fff54832550 error:0
Other times it is:
[5631127.259786] snmpd[27035]: segfault at 7f5160145000 ip 7f51600ded00 sp
7fff68d3d2d8
We're also seing this kernel bug in relation to NFS .. (not using XEN at
all);
Aug 4 14:56:00 ko kernel: [263156.166854] PGD 8063 PUD 9063 PMD 0
Aug 4 14:56:00 ko kernel: [263156.166905] CPU 2
Aug 4 14:56:00 ko kernel: [263156.166926] Modules linked in: nfsd auth_rpcgss
exportfs nfs lockd nf
I can reproduce it on a 7.10 system:
May 19 16:02:51 node15 kernel: [2059317.829560] PGD efe18067 PUD efe19067 PMD 0
May 19 16:02:51 node15 kernel: [2059317.922748] CPU 1
May 19 16:02:51 node15 kernel: [2059317.948928] Modules linked in: nfs lockd
sunrpc autofs4 ipv6 usbhid hid uhci_hcd ehci_hcd
Well.. since the problem only is present on a gutsy kernel.. it is quite
obvious that you can reproduce on the hardy kernel. The patch above is
from the patch-stream between gutsy and hardy.
Jesper
--
NFS server: lockd: server not responding
https://bugs.launchpad.net/bugs/181996
You received th
Public bug reported:
Binary package hint: open-iscsi
The boot order is still wrong in some cases for iscsi.
iscsi probably waits for networking to start (due to upstart and
dependencies) but it does not wait long enough, so "link" are available
before.
Trace from bootup:
[EMAIL PROTECTED]:~# dm
I can confirm, both the bug in hardy, and the fix in proposed-updates.
The Hardy iSCSI installation is useless until this has been fixed.
--
Module iscsi_tcp not included in linux-image
https://bugs.launchpad.net/bugs/218215
You received this bug notification because you are a member of Ubuntu
Bu
I've now tried it from hardy-proposed, and can confirm that it works
excellent.
Jesper
--
ifupdown integration broken
https://bugs.launchpad.net/bugs/223759
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
But ubuntu4 hasn't been uploaded to hardy.. so the bug is still present
in hardy (just hit it)
Jesper
--
open-iscsi fails to install
https://bugs.launchpad.net/bugs/214476
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
But ubuntu4 hasn't been uploaded to hardy.. so the bug is still present
in hardy (just hit it)
Jesper
--
open-iscsi fails to install
https://bugs.launchpad.net/bugs/214476
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
No. I integrated the changes from the diff manually on my system. (They
were very trivial).
Jesper
--
ifupdown integration broken
https://bugs.launchpad.net/bugs/223759
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
I can confirm both bug and fix.
This is vital, it breaks networking on any server running with bonded
network interfaces. .. worked flawless in hardy-1
Another change that seems to be releated.
Symbolik names in /etc/modprobe.d/options doesnt work any more:
May 1 22:02:33 hest kernel: [ 175.64
Changing to Confirmed.. as Described by Leann Ogasawara when the
patches are confirmed to work on a gutsy system.
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: Won't Fix => Confirmed
--
NFS server: lockd: server not responding
https://bugs.launchpad.net/bugs/181996
You received thi
SRU is a StableReleaseUpdate .. thats described in the links above. The
process to get fixes pushed to a "stable release".
--
NFS server: lockd: server not responding
https://bugs.launchpad.net/bugs/181996
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Leann Ogasawara: Should we provide more to get a SRU for this bug in
gutsy?
Jesper
--
NFS server: lockd: server not responding
https://bugs.launchpad.net/bugs/181996
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
I can confirm that the above 2 patches solves the problem.
The problem is really grave.. making the NFS-server in gutsy rarely
usable. The locking problem occoured about every second day here.. I
applied the patch over a week ago and hasn't seen the problem since.
Jesper
--
NFS server: lockd:
Hi Mathias.
May I ask why you marked it as incomplete? I'm willing to provide
whatever more information needed, but nothing is asked for in the bug
and the problem is a real PITA when having a large NFS based network.
Jesper
Mathias Gug wrote:
> ** Changed in: autofs (Ubuntu)
>Status:
Problem reproducible on gutsy .. according to the autofs-list autofs5
should be used (currently released).
** Changed in: autofs (Ubuntu)
Status: Incomplete => New
--
Autofs fails to update /net with new shares from server
https://bugs.launchpad.net/bugs/28380
You received this bug notif
Same for mountall
** Attachment added: "mountall-netdev.sh"
http://launchpadlibrarian.net/11991846/mountall-netdev.sh
--
iscsi checkfs and mount
https://bugs.launchpad.net/bugs/192158
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubun
Added patches to checkfs.sh and mountall.sh for _netdev later in the
bootprocess .. after open-iscsi has been started but before applications
that use the device starts.
** Attachment added: "checkfs-netdev.sh"
http://launchpadlibrarian.net/11991843/checkfs-netdev.sh
--
iscsi checkfs and moun
making moutnall.sh adhere to _netdev option.
** Attachment added: "mountall.sh.patch"
http://launchpadlibrarian.net/11991161/mountall.sh.patch
--
iscsi checkfs and mount
https://bugs.launchpad.net/bugs/192158
You received this bug notification because you are a member of Ubuntu
Bugs, which is
For making checkfs.sh adhere to _netdev option
** Attachment added: "checkfs patch"
http://launchpadlibrarian.net/11991156/checkfs.patch
--
iscsi checkfs and mount
https://bugs.launchpad.net/bugs/192158
You received this bug notification because you are a member of Ubuntu
Bugs, which is the b
Public bug reported:
Binary package hint: open-iscsi
When using the _netdev mount-option, fsck at boottime
/etc/init.d/checkfs.sh and mount /etc/init.d/mountall.sh should avoid
the device since those scripts are run before the network is available.
Attached patches makes both checkfs.sh and moun
Public bug reported:
Binary package hint: open-iscsi
Startup iscsi at boot happens to late..
open-iscsi should start rigtht after networking and before any
applications are being startet.
mv rc2.d/S20open-iscsi rcS.d/S41open-iscsi
This fix doesnt make "checkfs" work.
Jesper
** Affects: open-
Public bug reported:
Binary package hint: open-iscsi
Hi.
A server with iscsi may look like this:
ls /etc/rc0.d/K*
lrwxrwxrwx 1 0 0 17 Nov 23 09:02 K09apache2 -> ../init.d/apache2
lrwxrwxrwx 1 0 0 16 Nov 7 11:12 K19autofs -> ../init.d/autofs
lrwxrwxrwx 1 0 0 24 Nov 7 11:23 K19postgresql-8.1 ->
** Attachment added: "Screenshot of top"
http://launchpadlibrarian.net/11568383/Screenshot-1.png
--
Program not utillizing the CPU fully
https://bugs.launchpad.net/bugs/185987
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Public bug reported:
Binary package hint: linux-image-2.6.20-16-generic
Sometimes (not particular reprodusable) we have jobs like the one on the
screenshot allocated on our compute cluster. This jobs is not utillizing
the CPU's as it should. 2 individual processes on a 2-CPU machine leaves
1 x 10
Søren. No It was not accessible.
Problem easily reproducible on feisty
--
Autofs fails to update /net with new shares from server
https://bugs.launchpad.net/bugs/28380
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs maili
Public bug reported:
Binary package hint: bacula
2.2.0 has been released.
** Affects: bacula (Ubuntu)
Importance: Undecided
Status: New
--
2.2.0 released
https://bugs.launchpad.net/bugs/134205
You received this bug notification because you are a member of Ubuntu
Bugs, which is th
Ok.. bug found .. but no soloution.
The problem only occours when an "dhcp"-adresse is assigned. Then does
# nm-tool
NetworkManager Tool
get_nm_state(): didn't get a reply from NetworkManager.
NetworkManager appears not to be running (could not get its state).
instead of in the above situat
Strange.. Now I removed it from rc.local and it works fine. It must somehow be
related to the other stuff of configuration on the system and/or the packages
updated during the last 24 hours in feisty. It works now.
$ nm-tool
NetworkManager Tool
State: connected
print_devices(): didn't get a
Xorg.0.log attached
** Attachment added: "Xorg.0.log"
http://librarian.launchpad.net/7301575/Xorg.0.log
--
X is strange when shifting from X to console and back.
https://bugs.launchpad.net/bugs/105927
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bu
Public bug reported:
On an Amd64 system upgraded from edgy to feisty, switching from X to
console, makes the display act "strange" when shifting back. The LCD-
monitor seems to be initialized wrong and is "flicking" in the view.
The screen isn''t correctly redrawn either.
Restarting X does not s
There is no log-messages about ypbind in syslog (neither when it tries
to start during bootup or when it is started subsequently)
--
nis client fails to start at bootup
https://bugs.launchpad.net/bugs/105648
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Public bug reported:
Binary package hint: nis
On an edgy/amd64 system upgraded to feisty the nis client fails to start
due to something with dbus.
Setting $YPBINDOPTS=-no-dbus in /etc/default/nis solves this problem
but the default configuration of the nis-client was broken.
** Affects: nis (U
Public bug reported:
Binary package hint: nis
On an amd64 edgy upgraded to Feisty the nis client fails to start at
bootup. Subsequently starting it by doing an /etc/init.d/nis start,
brings it up just fine.
** Affects: nis (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
nis
The problem still persists on edgy
--
Autofs fails to update /net with new shares from server
https://launchpad.net/bugs/28380
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
Just opgraded my Thinkpad X30 from dapper to edgy and the wireless card
failes to work. iwconfig doesnt report any wireless extentions on the
card. Booting back into the old 2.6.15-27-686 makes it work again.
lspci output:
$ 01:02.0 Network controller: Intersil Corporation Pr
The module loads automatically:
$ lsmod | grep bcm
bcm43xx 124436 0
ieee80211softmac 30720 1 bcm43xx
ieee80211 33608 2 bcm43xx,ieee80211softmac
>From dmesg:
[17179589.724000] ieee80211_crypt: registered algorithm 'NULL'
[17179589.756000] ieee80211: 802.11 data
The module loads automatically:
$ lsmod | grep bcm
bcm43xx 124436 0
ieee80211softmac 30720 1 bcm43xx
ieee80211 33608 2 bcm43xx,ieee80211softmac
>From dmesg:
[17179589.724000] ieee80211_crypt: registered algorithm 'NULL'
[17179589.756000] ieee80211: 802.11 data
I have the same behaviour on a fresh Edgy installation on an Dell
Inspiron 6400 (sometimes I get a lockup) but mostly I can only view the
accesspoints, but not assosiate with them.
The firmware has been installed using "bcm43xx-fwcutter" and the script
coming in that package.
--
bcm43xx in edgy
I can confirm that I miss the console on an Dell Inspiron 6400.. the
screens are blank. Disabling "splash" form the kernel-boot-commandline
give them back.
Clean Edgy install.
--
Edgy doesn't let me switch to console
https://launchpad.net/bugs/68683
--
ubuntu-bugs mailing list
ubuntu-bugs@list
Public bug reported:
ubuntu-standard depends on openssh-client.. thus using Ubuntu in a
kerberos setup where "ssh-krb5" is needed, ubuntu-standard will be force
off the system.
** Affects: ubuntu-meta (Ubuntu)
Importance: Untriaged
Status: Unconfirmed
--
Ubuntu standard depends on
Now I've tried the above suggestion, it does not seem to solve anything on
Ubuntu.. I've tried adding it:
1) In the /etc/modprobe.d and reconfiguring initrd
2) Adding it on the commandline to the kernel boot parameters.
3) Even tried the old scsi_max_luns the same way.
The aic7xxx module gives
Public bug reported:
Binary package hint: linux-amd64-server
Using an Adaptec SCSI controller on a external raid disk, that supplies
2 luns on same SCSI-id, Ubuntu does not automatically detect the second
lun.
Running the command:
echo "scsi add-single-device 1 0 0 1" > /proc/scsi/scsi
brings
52 matches
Mail list logo
