There is a similar fedora bug report. I too see this error (when adding
--verbose), no idea where it's coming from.
I did try to boot using a debian initramfs, it works there...
https://bugzilla.redhat.com/show_bug.cgi?id=604927
** Bug watch added: Red Hat Bugzilla #604927
https://bugzilla.red
yeah well ... nice automated message :) unfortunately it has nothing to
do with the underlying problem problem. The problem is not an error in
the kernel package, the error is that there is no kernel package. So I
urge you to read the inital report ;)
--
hardy->lucid upgrade using "linux-image-xe
I also tried that a few days ago and was on the edge of reporting it
here, but came to the same conclusion. Helped somehow for sometime, but
not really.
Still there is a workaround that is at least a little better than
unload/loading the module (which interrupts all connections and needs a
few sec
i am using lucid alpha 4 (unr) on my netbook, which has this touchpad.
The touchpad works (the basics), but there is no multitouch, any idea on
how to control that in lucid (i have no such options in system->mouse)?
Since hal has been removed, all the howtos out there don't work no more
:-(
--
Ad
I can confirm, that the driver is unusable when using the netbook on
battery power. It works for about a minute, but then just stops. Would
it be helpful to add output from syslog?
--
Realtek RTL8192SE WLAN Card Fails to work on Medion Akoya E1312 Netbook
https://bugs.launchpad.net/bugs/401126
Yo
is there a reason why this is not in the current lucid alpha?
--
Add provider BOB in Austria
https://bugs.launchpad.net/bugs/428747
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
well guys - you rock. i got my new netbook today and decided to try
lucid netbook remix (although it's sadly just 32bit). It worked like a
charm, except the wireless card wasn't recognized, so i googled and
after seeing so many people playing with ndiswrapper (i really thought
this ancient way woul
ok ... i just solved my problem by manually adding the following line to
/boot/grub/device.map
(hd1) /dev/sdb
so now the file has both hdds
(hd0) /dev/sda
(hd1) /dev/sdb
and everything works like expected now
--
grub-probe crashed with SIGSEGV in __libc_start_main()
https://bugs.launchpa
I am still having this problem - exactly as described here. Installed
ubuntu using LVM and added another physical harddrive to the
volumegroup. Everything worked, except for the latest kernel update:
Setting up linux-image-2.6.31-20-generic (2.6.31-20.57) ...
Running depmod.
update-initramfs: Gene
according to https://wiki.ubuntu.com/LTSDebianImportFreeze "packages
will only be imported from Debian testing in this way on a case by case
basis or by explicit request from a developer."
will this be done?
--
Winbind failed to connect to AD: Program lacks support for encryption type
https://bu
Public bug reported:
I don't really get the decision to create a linux-image-virtual without
support to run the OS paravirtualized on a Xen host. This will drive
people away from ubuntu as a server system. Virtualization is growing on
importance and not supporting something like Xen (or XenServer
This bug persists - ubuntu 8.04.3 running on xenserver 5.5u1
interestingly the bug only happens on i386 machines (system completely up2date
with full-upgrade), the amd64 machines don't crash - at least for several days
now they didn't.
--
xen dom0 crashes with "BUG: soft lockup - CPU#0 stuck fo
Thanks for upping the priority ...
I just tried it, and this also happens if lighty is not automatically
started in a runlevel. It just starts (or at least tries to start) at 22
minutes after the full hour (logrotate) - this may even be an upstream
bug, i guess it's the same in debian (don't have
sorry - it tries that once a day (daily logrotate), i just changed my
logrotating to be hourly because of logfile size restrictions.
--
lighttpd reload executes restart (bad on logrotate!)
https://bugs.launchpad.net/bugs/393792
You received this bug notification because you are a member of Ubuntu
I'm sorry, but starting potentially harmful software like a webserver
with a buggy webpage without the administrator knowing it (who would
expect that a service that got shutdown manually just appears again?)
should really not be a "low" priority, especially since it's easy to
fix...
imho this is
I think the right thing to do is changing the init script to actually
perform a "reload" when reload is called. restart or force-reload stay
the same, reload checks if lighttpd is running, and only performs the
restart if it is
reload)
log_daemon_msg "Reloading $DESC configuration" $NAME
This is related ... somehow ;)
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504319
** Bug watch added: Debian Bug tracker #504319
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504319
--
lighttpd reload executes restart (bad on logrotate!)
https://bugs.launchpad.net/bugs/393792
You rec
*** This bug is a security vulnerability ***
Public security bug reported:
The logrotate script of lighttpd does a lighttpd reload, which is what
it should do, but if I stop the lighttpd daemon manually I certainly do
NOT want it to be started again by the log rotation. reload should NOT
start a
fedora has it :)
http://koji.fedoraproject.org/koji/packageinfo?packageID=4050
** Also affects: ubuntu
Importance: Undecided
Status: New
--
[needs-packaging] utrac "Universal Text Recognizer and Converter"
https://bugs.launchpad.net/bugs/365109
You received this bug notification becau
if the make-ssl-cert script does not get changed this needs to be
checked on other packages too (so they use /dev/urandom and not the
homedir)
for the moment i think apache2 has a ssleay.cnf which uses the homedir
--
make-ssl-cert fails if HOME is unset or empty
https://bugs.launchpad.net/bugs/2
this has an effect on all packages (eg. lighttpd) that use a ssleay.cnf
and may create or update certificates upon installation/upgrade
--
make-ssl-cert fails if HOME is unset or empty
https://bugs.launchpad.net/bugs/250400
You received this bug notification because you are a member of Ubuntu
Bug
well you can try ... if used in an environment where there is no homedir
set it does fail - no certificate is created or updated.
** Changed in: ssl-cert (Ubuntu Intrepid)
Status: Won't Fix => New
--
package ssl-cert 1.0.14-0ubuntu2.1 failed to install/upgrade:
https://bugs.launchpad.net
well ... i am sorry - it seems i have made an error here. I don't know
exactly what i did wrong but i retested everything and fixing the path
is not enough.
the real problem is the ssleay.cnf that is being used to generate the standard
pem file
it sets the RANDFILE variable to $ENV::HOME/.rnd
if
It fails in an automatic upgrade/installation environment because the PATH
variables are different than if you're using a shell. /usr/sbin is not included
if a cron runs the upgrade (or installation) - therefor the command
"make-ssl-cert" fails to create the files (because the file is not execut
so the checksums won't be fixed in feisty & gutsy?
what do you mean by "this is fixed in apt in intrepid"? the checksums are wrong
- what can apt do there? just questions of curiosity ;)
--
sha256 checksums in release files for all gzipped files broken
https://bugs.launchpad.net/bugs/269014
You
** Summary changed:
- sha256 signatures in release files (feisty) for all gzipped files broken
+ sha256 checksums in release files for all gzipped files broken
--
sha256 checksums in release files for all gzipped files broken
https://bugs.launchpad.net/bugs/269014
You received this bug notificat
*** This bug is a duplicate of bug 243630 ***
https://bugs.launchpad.net/bugs/243630
** Description changed:
Binary package hint: apt
- This is new to feisty, there has been a similar (the same!?) bug in
- gutsy++ see #243630
+ UPDATE: All SHA256 checksums for all .gz files in all distri
The error is in every distribution (dapper to intrepid). all the .gz
files have the same checksum in SHA256
--
sha256 signatures in release files (feisty) for all gzipped files broken
https://bugs.launchpad.net/bugs/269014
You received this bug notification because you are a member of Ubuntu
Bugs
*** This bug is a security vulnerability ***
Public security bug reported:
Binary package hint: apt
This is new to feisty, there has been a similar (the same!?) bug in
gutsy++ see #243630
it seems only to have an effect on the gzipped files ...
at the moment, the official mirrors hold lines li
*** This bug is a security vulnerability ***
Public security bug reported:
Binary package hint: clamav
see CVE page for more info - this bug practically crashes clamd and
renders eg. a mailserver useless. just by sending a bad email (happened
to me today)
could be a duplicate of
https://bugs.la
*** This bug is a security vulnerability ***
Public security bug reported:
Binary package hint: clamav
see http://secunia.com/secunia_research/2008-11/advisory/
there is no fix available, but should be soon.
"Secunia Research has discovered a vulnerability in ClamAV, which can
be exploited by
see http://nvd.nist.gov/nvd.cfm?cvename=CVE-2008-1531
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2008-1531
--
lighttpd (security) ssl fix
https://bugs.launchpad.net/bugs/209627
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
*** This bug is a security vulnerability ***
Public security bug reported:
Binary package hint: lighttpd
as of yesterday the lighttpd could have gotten rid of a very nasty bug which
causes SSL sessions to terminate and produce errors ...
see http://trac.lighttpd.net/trac/ticket/285 for more inf
Public bug reported:
Binary package hint: amavisd-new
I updated from amavisd-new 2.4.2 to 2.5.3 and encountered a small problem:
the file /etc/amavis/conf.d/25-amavis_helpers has a change:
$unix_socketname = "/var/run/amavis/amavis.sock";
has been changed to
$unix_socketname = "/var/lib/amavis/a
I have this probem w. ubuntu feisty on multiple machines, and although deleting
lists from /var/lib/apt/lists and /var/lib/apt/lists/partial works, I'd love to
have the working version of apt-transport-https in feisty too.
I'm using my own mirror and changing to gutsy is not an option at the mome
you're right Sam Morris, thing is update-inetd does not check the
variable "DEBCONF_FRONTEND", but checks "DEBIAN_FRONTEND" if it is set
to noninteractive ... so this is no bug of samba directly (i encountered
this one when installing postfix via onetime bootscript), but it is a
problem w. debian/u
36 matches
Mail list logo
