I second the emotion.
The deb package for 0.19 worked on my Gusty upgraded to Hardy, but it
interferes with gpsd on my pure Hardy laptop. It does not like compiling
from source on Hardy, complaining:
wxWidgets version >= 2.6.2... no (version 2.4.5 is not new enough)
GPSdrive is available in the
> Since Ubuntu Hardy, amanda-common depends on openbsd-inetd or inet-
superserver. Is that enough to mark this bug fixed?
Works for me.
One caveat, though: Amanda comes with an xinetd configuration file all
ready to go. Folks using other programs may have some editing to do (but
if you can handle
This bug is known upstream. See:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=478122
or
http://groups.google.com/group/linux.debian.bugs.dist/browse_thread/thread/b2b69f7b3eccd28f
for the fix.
--
apt-cacher / Use of uninitialized value in concatenation / line 169
https://bugs.launchpad.ne
Log files attached.
** Attachment added: "taltos.dist-upgrade.tar.bz2"
http://launchpadlibrarian.net/14452937/taltos.dist-upgrade.tar.bz2
--
package update-manager 1:0.87.24 failed to install/upgrade: ErrorMessage:
SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error
I upgraded from Gutsy Gnome to Hardy today, and pulled in all the
updates. After a lot of wrestling, I have this working more or less
correctly: two monitors and no way to configure them. But that's another
issue. Possibly an update fixed this issue.
--
I can't install Kubuntu 8.04 on Asus M2A-VM
Public bug reported:
Binary package hint: milter-greylist
I just upgraded from Gutsy to Hardy via the alternate CD. In the
process, a previously running sendmail installation broke. The problem
is the perissions on /var/run/milter-greylist.
[EMAIL PROTECTED]:~# service sendmail start
* Starting
tar/bzip2 ball attached per comment 3
After entering comment 2, I successfully rebooted & the computer is now
running just fine.
** Attachment added: "upgrade logs, tar bzip2"
http://launchpadlibrarian.net/14063434/taltos.dist-upgrade.tar.bz2
--
package linux-ubuntu-modules-2.6.24-16-generic
More information: when I ran "dpkg --configure -a", the initrd build
stopped due to lack of space in /boot. I have kernel debug packages
(/boot/vmlinux-debug-2.6.24-16-generic) installed. As that file occupied
~60 MB of a 100MB partition
Workaround: I moved the vmlinux* package to /, reran the
See also bug #225045.
Thanks
--
package linux-ubuntu-modules-2.6.24-16-generic 2.6.24-16.23 failed to
install/upgrade: dependency problems - leaving unconfigured
https://bugs.launchpad.net/bugs/222393
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
The other bug is Bug #225045
thank you.
--
package update-manager 1:0.87.24 failed to install/upgrade: ErrorMessage:
SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error
code (2)
https://bugs.launchpad.net/bugs/225042
You received this bug notification because you are a
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/14057120/Dependencies.txt
--
package linux-ubuntu-modules-2.6.24-16-generic 2.6.24-16.23 failed to
install/upgrade:
https://bugs.launchpad.net/bugs/225045
You received this bug notification because you are a member of Ubu
Public bug reported:
This may duplicate #222393. I got this running from update-manager
(#225042), not synaptic.
I got this in the process of upgrading from Gutsy (as updated) to Hardy,
and included updates since release. so I'm afraid I have no idea what
happened nor what I expected (except a sm
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/14057014/Dependencies.txt
--
package update-manager 1:0.87.24 failed to install/upgrade: ErrorMessage:
SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error
code (2)
https://bugs.launchpad.net/bugs/
Public bug reported:
Binary package hint: update-manager
This was generated automatically by update manager in the process of
upgrading from Gutsy to Hardy. So I have no idea what happened or what
should have happened. The same installation produced a bug report for
linux-ubuntu-modules-2.6.24, w
Hi Suraj,
Do you have exactly the described problem ("loading hardware drivers"
[fail] linux kernel generic 2.6.24 - 16, hangs on boot), OR does your
system start up and tell you, that it is running with a low resolution?
This would be completeley different.
In my case, in conjunction with the ha
The problem is solved for me along with an upgrade to linux-ubuntu-modules
2.6.24-16.23.
See also
https://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.24/+bug/212271
--
[Hardy] "Loading hardware drivers" hangs while booting on latest kernel
(Bypassing causes XServer crash)
https:
I had the same problem on upgrading from linux-image-generic 2.6.24-15 to
2.6.24-16 before.
The problem is SOLVED for me since upgrading the brand-new package
linux-ubuntu-modules 2.6.24-16.23.
--
"loading hardware drivers" [fail] linux kernel generic 2.6.24 - 16, hangs on
boot
https://bugs.la
The same problem here on a x64_64 after updating 2.6.24-15-generic to
2.6.24-16-generic in Hardy.
Interesting is, that a parallely installed kernel 2.6.24-16-rt boots normally.
Hardware:
- Board: Asus P5B, Intel HDA
- Processor: Intel Code 2 Duo E6300
- Nvidia GeForce 7600 GS
- TV Card Fly DVB-T
Thank you and sorry for the "spam" :-)
--
Recompiled Ubuntu kernel - nvidia driver does not load (comm: modprobe Not
tainted)
https://bugs.launchpad.net/bugs/214499
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Public bug reported:
Binary package hint: nvidia-new-kernel-source
I recompiled the Ubuntu kernel from source 2.6.24-15.27 together with
alsa-source 1.0.16-0ubuntu4 and nvidia-new-kernel-source
169.12+2.6.24.12-15.33 and created Debian packages from them to install
them. This kernel boots well ex
Public bug reported:
Binary package hint: amule-daemon
I'm not able to upgrade amule-daemon in Ubuntu Hardy from
2.2.0~svn20080218-0ubuntu2_amd64 to 2.2.0~svn20080218-0ubuntu2_amd64,
because I get an error in a pre=removal script see below. The daemon is
configured to automatically start with the
Works for me now with nvidia-glx-new-169.12+2.6.24.11-12.31
** Changed in: linux-restricted-modules-2.6.24 (Ubuntu)
Sourcepackagename: None => linux-restricted-modules-2.6.24
Status: New => Fix Released
--
NVidia does not work in linux-image-generic 2.6.24.12.13 (x86_64)
https://bugs.laun
Public bug reported:
The latest kernel image 2.6.24-12 misses the matching native NVidia drivers
nvidia-glx-new (curent nvidia-glx-new version 169.12+2.6.24.10-12.30)
The X Server starts in low resolution mode for that. Maybe there's a new build
of nvidia-glx-new on the way. Only to not forgetti
Public bug reported:
Binary package hint: twinkle
The softphone Twinkle 1.2 is out now, with quite a lot of new features and
fixes. It would be nice to have it in Hardy, too.
See http://www.twinklephone.com/ :
8 march 2008 - 1.2
==
- SIP over TCP
- Automatic selection of IP addr
I agree with the problem being related to WPA. On a dual boot Windows
XP Pro & Ubuntu Gutsy Dell Latitude D830 machine, using the Intel 3945,
connecting to a Watchguard Firebox e10-w, I have no problems connecting
with WPA on Windows, but get many dropped "ping" packets when in Ubuntu.
For example
I'm going to jump in on this. I'm seeing a different but related
problem. I'm using Gutsy. I am working on bare metal restoration
(http://www.charlescurley.com/Linux-Complete-Backup-and-Recovery-
HOWTO.html). The least intrusive way for me to perform a bare metal
restoration is to provide the UUID
I hit this and reported it independently (159360, marked as a
duplicate). I "cured" it by uninstalling OOo entirely, then re-
installing it. I have not changed themes, and it is still crux.
Of course if new packages become available shortly, this workaround is
moot.
Thanks for the work.
--
[gut
Bingo. I had previously switched the theme to Crux.
Unfortunately, I have since removed and re-installed OOo, and I no
longer see the problem. So switching back to the Human theme might not
tell us anything useful. Also, I'm reluctant to test further as this is
on one of my production machines, an
Public bug reported:
Binary package hint: apt-file
I have a fresh install of Gutsy on my laptop. I have the Gutsy Alternate
install CD called out in my sources.list:
deb cdrom:[Ubuntu 7.10 _Gutsy Gibbon_ - Release i386 (20071016.1)]/
gutsy main restricted
When I run other apt-* utilities, I see
Public bug reported:
Binary package hint: openoffice.org2
Launch OOo, attempt to load a new file from "file-> Open".
I had previously set OOo to use the native OO file selector.
OO also crashes when I go to change it back to the Gnome file selector.
("tools-> options-> Openoffice.org-> general"
Relevant packages installed, on Ubuntu 7.10:
[EMAIL PROTECTED]:~# pre openoffice | sort
openoffice.org-1:2.3.0-1ubuntu5--i386
openoffice.org-base-1:2.3.0-1ubuntu5--i386
openoffice.org-calc-1:2.3.0-1ubuntu5--i386
openoffice.org-common-1:2.3.0-1ubuntu5--all
openoffice.org-core-1:2.3.0-1ubuntu5--i386
It's a bare minimum fix, and has problems. It has the minor one of
requiring inetd for the server. Most server installations will also have
clients, or other programs that will use (x)inetd, so it's no big deal.
However, I just tried to install amanda-client on a machine that had
neither amanda-cl
Odd. I can't see why the server should require inetd, since it usually
runs as a cron job. A machine with the server but no client wouldn't
need inetd for Amanda (but it might for other things).
I wonder if Amanda used to be all one package, and when it was split up,
the dependency went to the wro
Public bug reported:
Binary package hint: amanda-common
On a fresh minimal installation of xubuntu, I installed amanda-common
and amanda-client. The file /etc/xinetd.d/amanda was provided. However,
neither inetd nor xinetd were installed as dependencies. update-inetd
was installed. This may be be
101 - 134 of 134 matches
Mail list logo
