[Bug 439818] Re: epiphany-gecko can't be installed

2009-11-24 Thread squiggleslash
I think the switch to Webkit is premature. Both browsers have severe
customizability limitations, but at least Epiphany-gecko allowed to you
tweak it with about:config.

This bug is not invalid BTW, right now this is what you get when you try
to install epiphany-gecko:

# apt-get install epiphany-gecko
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  epiphany-gecko: Depends: epiphany-browser (>= 2.28.0) but it is not going to 
be installed
E: Broken packages
# sudo apt-get install epiphany-gecko epiphany-browser
Reading package lists... Done
Building dependency tree   
Reading state information... Done
epiphany-browser is already the newest version.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  epiphany-browser: Conflicts: epiphany-gecko but 2.28.0-4ubuntu1 is to be 
installed
E: Broken packages
#

The error messages don't make any sense whatsoever. It's one thing to
say "We don't actually offer epiphany-gecko any more", but quite another
to simply leave an entry enticingly in the repository (which will also
break third party attempts to provide a usable version) which cannot be
installed because of an error that clearly isn't an error (how is
2.28.0-4ubuntu1  not >= 2.28.0?)

I've changed the status accordingly. Let's either fix the package or
repair the dependency problems, not pretend there's no bug here simply
because it peripherally involves an unsupported product - the repository
itself most certainly is supported, and at the very minimum, that's
broken.


** Changed in: epiphany-browser (Ubuntu)
   Status: Invalid => Confirmed

-- 
epiphany-gecko can't be installed
https://bugs.launchpad.net/bugs/439818
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 414560] Re: ath9k disassociates/reassociates a lot

2009-11-22 Thread squiggleslash
Yeah, I'll add my name to those saying sudo apt-get install 
linux-backports-modules-wireless-karmic-generic fixes the problem, or at least 
tries to. Before I installed that and rebooted, Hulu.com was virtually 
unusable, and tail -f /var/log/syslog Nov 21 20:23:20 darkstar 
wpa_supplicant[1157]: CTRL-EVENT-SCAN-RESULTS 
Nov 21 20:23:41 darkstar wpa_supplicant[1157]: CTRL-EVENT-DISCONNECTED - 
Disconnect event - remove keys
Nov 21 20:23:41 darkstar NetworkManager:   (wlan1): supplicant connection 
state:  completed -> disconnected
Nov 21 20:23:41 darkstar kernel: [ 5871.484062] wlan1: no probe response from 
AP 00:01:02:03:04:05 - disassociating
Nov 21 20:23:41 darkstar NetworkManager:   (wlan1): supplicant connection 
state:  disconnected -> scanning
Nov 21 20:23:42 darkstar wpa_supplicant[1157]: CTRL-EVENT-SCAN-RESULTS 
Nov 21 20:23:42 darkstar wpa_supplicant[1157]: WPS-AP-AVAILABLE 
Nov 21 20:23:48 darkstar wpa_supplicant[1157]: CTRL-EVENT-SCAN-RESULTS 
Nov 21 20:23:48 darkstar wpa_supplicant[1157]: WPS-AP-AVAILABLE 
Nov 21 20:23:48 darkstar kernel: [ 5878.701142] wlan1: authenticate with AP 
00:01:02:03:04:05
Nov 21 20:23:48 darkstar kernel: [ 5878.704549] wlan1: authenticated
Nov 21 20:23:48 darkstar kernel: [ 5878.704556] wlan1: associate with AP 
00:01:02:03:04:05
Nov 21 20:23:48 darkstar wpa_supplicant[1157]: Trying to associate with 
00:01:02:03:04:05 (SSID='myapsid' freq=2412 MHz)
Nov 21 20:23:48 darkstar wpa_supplicant[1157]: Association request to the 
driver failed
Nov 21 20:23:48 darkstar NetworkManager:   (wlan1): supplicant connection 
state:  scanning -> associating
Nov 21 20:23:48 darkstar wpa_supplicant[1157]: Associated with 00:01:02:03:04:05
Nov 21 20:23:48 darkstar wpa_supplicant[1157]: CTRL-EVENT-CONNECTED - 
Connection to 00:01:02:03:04:05 completed (reauth) [id
=0 id_str=]
Nov 21 20:23:48 darkstar NetworkManager:   (wlan1): supplicant connection 
state:  associating -> associated
Nov 21 20:23:48 darkstar kernel: [ 5878.707771] wlan1: RX ReassocResp from 
00:01:02:03:04:05 (capab=0x11 status=0 aid=5)
Nov 21 20:23:48 darkstar kernel: [ 5878.707776] wlan1: associated
Nov 21 20:23:48 darkstar NetworkManager:   (wlan1): supplicant connection 
state:  associated -> completed

Since the reboot, I've watched the whole of Family Guy via Hulu.com
without incident. So whatever's in those backports appears to have fixed
this specific issue.

-- 
ath9k disassociates/reassociates a lot
https://bugs.launchpad.net/bugs/414560
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 359725] Re: Intrepid Network Manager Lacks Dial-up & Work-Around

2009-08-12 Thread squiggleslash
Agreed.

The same issue effectively prevents any easy way to access the Internet
via a Bluetooth mobile phone and GPRS/EDGE. It took quite a bit of
hacking around and scripting to get things working, and in the meantime
I'm having that stupid "forcing Firefox offline" thing happening all the
time.

Why anyone thought removing dial-up support from NM would be a good idea
is beyond me.

-- 
Intrepid Network Manager Lacks Dial-up & Work-Around
https://bugs.launchpad.net/bugs/359725
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 307604] Re: hostname not IPv6 compliant

2008-12-19 Thread squiggleslash
Further to the last comment, "options inet6" breaks ntp, so this isn't a
workable solution given the importance of ntp in the Ubuntu set-up.

-- 
hostname not IPv6 compliant
https://bugs.launchpad.net/bugs/307604
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 309738] [NEW] kadmind uses wrong path for kadmind.acl

2008-12-19 Thread squiggleslash
Public bug reported:

In Ubuntu 8.04, Heimdal's kadmind daemon is compiled to look for
kadmind.acl in /var/lib/heimdal-kdc/kadmind.acl, but documentation and
the sample file locates it in /etc/heimdal-kdc/kadmind.acl

Location was verified using strace:

open("/var/lib/heimdal-kdc/kadmind.acl", O_RDONLY|O_LARGEFILE) = 5

For other users finding this bug, you can easily fix it either by
editing the file in /var/lib/heimdal-kdc/kadmind.acl, or by setting up a
softlink as follows:

sudo  ln -s /etc/heimdal-kdc/kadmind.acl /var/lib/heimdal-
kdc/kadmind.acl

But presumably the long term fix is to either fix the man page, or
change the compiled-in default. Or, if you must, add the above softlink
as part of the install.

** Affects: heimdal (Ubuntu)
 Importance: Undecided
 Status: New

-- 
kadmind uses wrong path for kadmind.acl
https://bugs.launchpad.net/bugs/309738
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 309339] Re: kadmind will not listen on IPv6 ports

2008-12-19 Thread squiggleslash
Do we need upstream to fix it or can I (or someone else) try and create
a patch we can use locally until MIT does its thing?

-- 
kadmind will not listen on IPv6 ports
https://bugs.launchpad.net/bugs/309339
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 309339] [NEW] kadmind will not listen on IPv6 ports

2008-12-18 Thread squiggleslash
Public bug reported:

kadmind, as issued with Ubuntu 8.04 LTS, will not listen on IPv6 ports.
a netstat -l -p -6 will not show it as listening. kdc does not have the
same problem, it works fine.

Looking at the source code, it appears that the version of kadmind being
shipped with Ubuntu 8.04 LTS is not eyepeasixificationalized (!).
krb5-1.6.dfsg.3~beta1/src/kadmin/server/ovsec_kadmd.c defines a
structure, addr, which is the basic sockaddr_in rather than
sockaddr_in6, used to bind to the kerberos-adm port, and the code that
uses it is:

 memset(&addr, 0, sizeof(addr));
 addr.sin_family = AF_INET;
 addr.sin_addr.s_addr = INADDR_ANY;
 addr.sin_port = htons(params.kadmind_port);

 if ((s = socket(AF_INET, SOCK_STREAM, 0)) < 0) {
  const char *e_txt = krb5_get_error_message (context, ret);
  krb5_klog_syslog(LOG_ERR, "Cannot create TCP socket: %s",
   e_txt);
  fprintf(stderr, "Cannot create TCP socket: %s",
  e_txt);
  kadm5_destroy(global_server_handle);
  krb5_klog_close(context);   
  exit(1);
 }

 if ((schpw = socket(AF_INET, SOCK_DGRAM, 0)) < 0) {
 const char *e_txt = krb5_get_error_message (context, ret);
 krb5_klog_syslog(LOG_ERR,
  "cannot create simple chpw socket: %s",
  e_txt);
 fprintf(stderr, "Cannot create simple chpw socket: %s",
 e_txt);
 kadm5_destroy(global_server_handle);
 krb5_klog_close(context);
 exit(1);
 }

There is no IPv6 code in the thing at all. I'm assuming there's no
elaborate include file somewhere that redefines sockaddr_in and AF_INET
to sockaddr_in6 and AF_INET6 respectively (and I don't know if such a
thing would work anyway, I'm reading conflicting documentation on
whether that would result in an IPv6-only app.)

Without this fixed, the remote admin daemon is essentially not useful on
a network that's primarily IPv6.

** Affects: krb5 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
kadmind will not listen on IPv6 ports
https://bugs.launchpad.net/bugs/309339
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 307604] Re: hostname not IPv6 compliant

2008-12-13 Thread squiggleslash
After looking around, it appears the issue is "solved" if you put
"options inet6" in the resolv.conf. Not sure why that would be
necessary. Is this a policy decision?

-- 
hostname not IPv6 compliant
https://bugs.launchpad.net/bugs/307604
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 307604] [NEW] hostname not IPv6 compliant

2008-12-12 Thread squiggleslash
Public bug reported:

The "hostname" command cannot determine the correct FQDN for the host if
the host + domain only resolves as an IPv6 address.

Example (the names have been changed to protect the innocent):

r...@salamander:/etc# hostname -V
hostname 2.94
r...@salamander:/etc# cat resolv.conf 
domain example.com
search example.com
nameserver 10.0.1.5
r...@salamander:/etc# host salamander.example.com
salamander.example.com has IPv6 address 2002:::1:216:3eff:fe0e:f1f7
r...@salamander:/etc# hostname
salamander
r...@salamander:/etc# hostname -f
hostname: No address associated with name

The correct response would have been:
salamander.example.com

This is a problem because a large number of scripts rely upon hostname
to determine the local machine's FQDN. Right now it's only solvable
using tricks for DNS, which in many cases are undesirable. For example,
I do not want salamander.example.com to resolve to a 10.x.x.x address,
because 10.x.x.x is not globally routable, and because example.com is a
real domain that's externally visible and DNS becomes seriously messy if
you have to mix a "real" DNS for external use and a fake DNS for
internal use.

Whatever the case, hostname should be happy with an IPv6 address.

hostname 2.94 is bundled with Ubuntu 8.04 LTS.

** Affects: hostname (Ubuntu)
 Importance: Undecided
 Status: New

-- 
hostname not IPv6 compliant
https://bugs.launchpad.net/bugs/307604
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs