Sounds like it could be a multicast problem. I have had similar with a
Broadcom Wifi chipset whose drivers don't properly do multicast.
I realise this is an old bug, I didn't check for historical ones last time I
tidied up this package, but in case I can still help -
- first thing to check, ha
Not a bug in libupnp, as far as I can see. Seems to be to do with your
package manager (apport?) that's got itself into a knot, but as I don't
run Ubuntu I can't recommend where to go for that.
** Changed in: libupnp (Ubuntu)
Status: New => Invalid
--
You received this bug notification b
** Changed in: linux-igd (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1207099
Title:
linux-igd does not honour paranoid=1 variable
To manage noti
This is fixed in linux-igd/1.0+cvs20070630-5, when that reaches Ubuntu.
Apols for the time taken to find and fix it.
Nick (Debian maintainer)
** Changed in: linux-igd (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Fixed in Debian Jessie linux-igd/1.0+cvs20070630-5, with apols that I
didn't get that uploaded in time for it to trickle down into Ubuntu.
Nick (Debian maintainer)
** Changed in: linux-igd (Ubuntu)
Status: Expired => Confirmed
** Bug watch added: Debian Bug tracker #675244
http://bugs.
Thanks for the report; I suspect this is Debian #605899
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605899 which was
fixed in nullmailer package 1.10-1
I'll leave the bug open for reference, until 1.05 expires from LTS next year.
Hope I'm not teaching my grandmother but perhaps someone can
Forwarded upstream: https://github.com/bruceg/nullmailer/issues/23
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318851
Title:
Nullmailer doesn't believe in the existence of spaces
To manage notif
This was added in nullmailer 1.10. First version in Ubuntu supporting
sending with TLS was 1.11 (Quantal / Ubuntu 12.10)
** Changed in: nullmailer (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: nullmailer (Debian)
Status: Confirmed => New
** Changed in: nullmailer (Debian)
Remote watch: Debian Bug tracker #329192 => None
** Bug watch added: Debian Bug tracker #757221
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757221
** Changed in: nullmailer (Debian)
*** This bug is a duplicate of bug 236715 ***
https://bugs.launchpad.net/bugs/236715
** This bug has been marked a duplicate of bug 236715
nullmailer spams relay host if misconfigured
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Seems from the linked commit that this message is officially benign, but will
be fixed in a forthcoming
release.
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=e0a972461156c12ad1be40f4a4ed84705c4603aa
--
You received this bug notification because you are a member of Ubuntu
I am experiencing this crash from synaptiks every time i close and
reopen the laptop lid. Not even suspend/hibernation is required to
trigger it: it just happens. Apport refuses to report it as it says
this bug is duplicate and there are too many reports already.
It would be really nice to get t
I don't think it is meant to end in just plain &0 because bash parses
that as a command. Has the command been bitten by a missing angle
bracket perhaps ?
[/testing: leveret@george ~]$ killall kded4 && sleep 2 && kded4 &0
[2] 30401
bash: 0: command not found
[/testing: leveret@george ~]$
Experim
Actually I apologise for being snarky yesterday. I've read the full
upstream bug now and whilst it is a complex set of needs to make VPNs
work in all use cases (mine being relatively simple), it looks like NM
with this check box is up to its usual tricks of claiming features that
just don't work i
Still broken in Quantal (12.10).
This is not a wishlist, this is a feature supposedly offered by the
software - the VPN tab has a "Connect automatically" checkbox and it
does not work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
Are you still having this problem ? What versions did you upgrade from
and to if you can remember, please ?
Nick (Debian maintainer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/687642
Title:
IANOMOTU but as Debian maintainer I'm happy to say that nullmailer now
implements -bs and no longer conflicts with the LSB. This fix was
recently imported to Ubuntu in version 1.11.
** Changed in: nullmailer (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification b
Still happening in Precise, see #952999. This occurs every time the
crash reporter tries to invoke gdb for a backtrace. DrKonqui can get
backtraces quite happily so I'm not sure what the difference is.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Upstream issue https://github.com/bruceg/nullmailer/issues/4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/236715
Title:
nullmailer spams relay host if misconfigured
To manage notifications about t
Upstream issue https://github.com/bruceg/nullmailer/issues/4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/254130
Title:
smtp problems, zoneminder? cause of games crashing?
To manage notifications
Hmm. I've just rewritten the template prompting in postinst for Debian
version 1.11-1 so I hope this problem, whatever it was, might be fixed.
Could you keep an eye on your next upgrade when Ubuntu gets 1.11,
please, and see if it recurs or not ?
--
You received this bug notification because you
The remotes file shouldn't be empty because it determines where the mail
is being forwarded to.
I guess that your hostname (in /etc/mailname or in the dhcp response, if
you use dhcp) doesn't include a fully qualified domain name. This
wasn't a supported configuration hence why an empty domain str
Fixed in 1.10-1
** Changed in: nullmailer (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/531796
Title:
Status messages are logged with severity "error"
T
Nullmailer working as designed.
** Changed in: nullmailer (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/619702
Title:
nullmailer-inject ignores defaulthost
T
Nullmailer should have prompted for some smarthost parameters. Was this
being run in some form of unattended installation, and if so then how ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/295253
Ti
This is what adminaddr does if it is set. Have you tried removing it ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/619702
Title:
nullmailer-inject ignores defaulthost
To manage notifications abo
I can confirm that upgrading will involve a library transition from
libupnp3 to libupnp6, due to upstream changing the SONAME. This will
have a knock-on effect of requiring build-dependency changes from
libupnp3-dev to libupnp-dev to the following packages:
amule
djmount
vlc
and rebuilds to the
*** This bug is a duplicate of bug 855339 ***
https://bugs.launchpad.net/bugs/855339
** This bug has been marked a duplicate of bug 855339
Package version is strongly outdated
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Be careful, upstream has poor ABI stability. If you upgrade the library
you'll probably need to rebuild all dependent packages. This is why
1.6.6 is still in Debian, for instance. I intend to do something about
this before Wheezy is released, but if you guys want to do something
earlier please f
Hi,
Just dropping in - I'm the intending new Debian maintainer for
nullmailer and I'd be open to reviewing the decision on dbug:271662 (
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=271662 )
It still seems to be the case, however, that the -bs option for SMTP
mail submission is mandated by LS
I'm the Debian libupnp4 maintainer, so not directly responsible for the
Ubuntu package but maybe I can help you.
Libupnp 1.8 is a major API change in order to hide more of the internal
implementation, which is why it is packaged as a different library
(libupnp4) than version 1.6 (libupnp3). I am
On Tue, Nov 04, 2008 at 01:55:55AM -, krazyd wrote:
> Hey Nick,
> my firmware is loading properly now in Intrepid - is this bug still an issue
> for you?
Hi Krazy
I haven't tried Intrepid yet - this laptop is getting a bit unreliable
(failing to boot or unexpected shutdowns, no apparent cause
On Wed, Oct 29, 2008 at 11:06:01AM -, playya wrote:
> I still have this error.
> i rebuilded the initramfs with the patch and it includes the firmwares, but i
> always get some "Rx invalid crypt" errors if i try to connect to a wpa
> encrypted network. Open aps aren't a problem. WEP not teste
Krazyd, sorry I missed your query until I had the same problem crop up
yet again after an upgrade, due to the fact the Ubuntu devs are still
ignoring this bug :-(
Save the patch into your home directory, then it's just two steps:
# Apply the patch
sudo cat ipw200-initramfs-firmware.diff | patch
Trond: have you made sure the i8k module is loaded ? Try "sudo lsmod |
grep i8k". If this returns nothing, then you don't have i8k loaded, so
try "sudo modprobe i8k".
This ought to let i8kmon work. If so you can add "i8k" to the file
/etc/modules to have it loaded automatically every time.
I h
On Sat, Jun 14, 2008 at 03:34:36PM -, Nick Leverton wrote:
> On the other hand there could well be more than one problem here ...
> I see the initramfs-tools package has just been re-issued but this fix
> is still not applied. But - I now have working ipw2200 even though this
>
Hi GeneW,
I'm sorry to hear it. Do you have /etc/kernel-img.conf that looks like
mine ?
do_symlinks = yes
relative_links = yes
do_bootloader = yes
do_bootfloppy = no
do_initrd = yes
link_in_boot = no
ramdisk = /usr/sbin/update-initramfs
If update-initramfs is being called with the patch a
Umm, this problem is a killer under hardy 2.6.24 for anyone running an
ipw2200 wireless adaptor. initramfs-tools fails to include the needed
firmware in the initrd. Any chance my patch could be included in
initramfs-tools please ? If you need more evidence than I already
posted, please contact m
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- ipw2200 driver fails to load firmware
+ ipw2200 driver fails to load firmware (patch attached)
--
ipw2200 driver fails to load firmware (patch attached)
https://bugs.launchpad.net/bugs/18
Confirmed that the problem with firmware loading is because update-
initramfs does not include the firmware in the initrd.
The attached patch to initramfs-tools lets the ipw2200 module load at
boot time.
I am not very happy about having to special-case this module but on the
other hand it is no w
Final note for the evening: don't know if it's relevant, but my
initramfs.conf has "MODULES=dep". It originally had "MODULES=most" but
in hardy this gave me an unbootable system because the initrd was too
large and overflowed low memory.
--
ipw2200 driver fails to load firmware
https://bugs.laun
Still trying to track this one backwards ...
Just confirmed that if I revert to Gutsy 2.6.22 (keeping Hardy
userland/udev/etc), then the ipfw2200 loads fine. The interface doesn't
come up for reasons not yet known, but driver/firmware loads OK and a
simple ifdown/ifup will fix the interface.
In
I've managed to capture the full firmware error message at boot time
(many device driver error messages, such as this one, are still only
printed to console not logged, which can be awkward at times like this).
ipw2200: Detected Intel PRO/Wireless 2915ABG Network Connection
ipw2200: ipw2200-bss.fw
I have the same symptom at boot time. However once the system is
booted, I can rmmod ipw2200 and then insert it again, and the adaptor
then works.
The ipw2200 adaptor worked right from boot time with dapper, edgy and
feisty. The adaptor always fails at boot and has to be removed/inserted
since I
44 matches
Mail list logo
