Public bug reported:
Binary package hint: kq
kq (and kq-data) packages are severely out of date.
Official web page:
http://kqlives.sourceforge.net/
Download page:
http://sourceforge.net/project/showfiles.php?group_id=61344package_id=130221
Download page shows that the last stable update is
mattismyname has indicated this is no longer an issue for him because he
installed the beta drivers. I indicated that these are available in the
repository. Looks like this issue was related to the 96 series nVidia
drivers broken by the Intrepid changes to Xorg.
** Changed in:
This is not a problem with the nvidia graphics drivers packages in
Ubuntu. I see that you downloaded the script from nVidia, instead of
installing the package from intrepid-updates.
First, check your software sources. You can do this in Gnome from ...
System -- Administration -- Software
I changed the status to Invalid as this is an issue with compatability
between the script made by nVidia and Ubuntu, rather than an issue with
the Ubuntu-supported packages.
** Changed in: nvidia-graphics-drivers-96 (Ubuntu)
Status: Confirmed = Invalid
--
package nvidia-glx-96 None
Guess I'm finally getting around to joining this discussion. If anyone
has this now working on their system, could you please share what you
have in /etc/fstab in relation to your cd-rom(s)?
I am getting error like this in both Intrepid and Jaunty. (This taken
from the Intrepid dmesg log)
[
Filed.
http://bugzilla.gnome.org/show_bug.cgi?id=567703
--
GDM Language Selection not listed properly
https://bugs.launchpad.net/bugs/316617
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: gdm
Using Intrepid Ibex, but I would guess this bug is common to all flavors
of Ubuntu. gdm (2.20.8-0ubuntu3) does not properly localize its
language selections.
Established world example: Next time you use an ATM or point-of-sale
credit card reader
Eh. Don't go through all that work.
Fire up Synaptic, bring up the repositories (sorry, I'm not at my Linux
PC, so I'm not sure all the right menu names), and make sure that the
Proposed repository is turned on. Reload your repositories, and bring
on the latest nvidia updates. I believe that
As noted, this bug is specific to upgrading from Dapper to Edgy. As
Edgy has reached end of life, I am closing this bug.
** Changed in: courier-authlib (Ubuntu)
Status: New = Fix Released
--
apt-get broken after upgrade to edgy eft (courier-authdaemon package)
Fixed? I don't agree.
The need for abiword-gnome was taken out and replaced with a need for
abiword-plugin-goffice. But since abiword-plugin-goffice is *not*
available in intrepid either, this hasn't fixed anything.
So, the breakage has been changed, but not fixed yet.
--
[Intrepid]
(Note: I have fixed my own installation by pulling several abiword
related packages from Debian. So, the abiword piece *is* fixed in
Debian. Now, we just need that pulled back to Intrepid.)
** Changed in: meta-gnome2 (Ubuntu)
Status: Fix Released = In Progress
--
[Intrepid]
I agree. This one is fixed. Is there anything more I need to do to
close this bug?
--
gnome-desktop-environment (intrepid) not installable
https://bugs.launchpad.net/bugs/273929
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
Binary package hint: gnome-desktop-environment
Latest update of gnome-desktop-environment (2.22.2-4ubuntu1) was posted
without all of its requirements. It depends on gnome-user-guide 2.22.1,
but that version of the guide is not available in the repositories. The
latest
Public bug reported:
Intrepid Ibex issue. Meta-package gnome-office depends on abiword-gnome
which does not exist. Either abiword-gnome needs to be created, or this
dependency needs to change to just abiword.
** Affects: meta-gnome2 (Ubuntu)
Importance: Undecided
Status: New
--
** Changed in: ubuntu
Status: New = Invalid
--
Kubuntu Alternate Install CD - Stop making coasters!
https://bugs.launchpad.net/bugs/220030
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Actually -- What I see here
(http://iso.qa.ubuntu.com/qatracker/build/kubuntu/all) is flawed testing
situations.
Under download info Kubuntu Alternate i386 (20080417.1)
From Install (Auto-Resize):
Summary
Install from the Alternate CD using one of 3 partitioning methods, OEM, expert
or rescue
Couple things here.
1) Come to think of it, I'm not certain that I have successfully burned
any ISO's from Gutsy. I have done it with other versions of Ubuntu
(including Hardy -- yes I had Hardy installed once, but had to abandon
it when certain upgrades crashed the system). which makes me
Public bug reported:
I download the Kubuntu Alternate release candidate CD for i386 --
kubuntu-8.04-rc-alternate-i386.iso.In gutsy, I burn this (through
k3b) to a new CD-R medium, first verifying the MD5 sum (its fine). I
then reboot my computer (Authentic AMD Athlon Processor CPU family 6,
Going back to the original poster's messages, I see that something in
his computer is referencing /dev/hda3. Partially with Gutsy, and more
completely with Hardy, we have migrated over to a different way of
referencing drives. The most reliable way to reference all drives in
Hardy, Gutsy, or
For those who have *some* method of booting into their system...
It should be noted that there were a number of issues related to booting
as a result of what was done in Gutsy. See bug 133666 for one prominent
example. This documents an issue that had a known fix that will not be
put into Gutsy
Reviewed in Hardy. I have pciutils installed, and I was able to remove
libpci2. This is no longer an issue as of the hardy release.
** Changed in: pciutils (Ubuntu)
Status: Confirmed = Fix Released
--
Feisty package pciutils depends on obsolete package
It appears that the *intent* with Gutsy was to switch the drives over to
/dev/sd* completely. That did not happen for SiS 5513 IDE controllers.
According to my personal experience, these changes allowed me to use the
stock Ubuntu kernels:
Feisty: No changes from previous installs. Feisty
I would disagree that this issue is *fixed*. Bolek indicated that an
*upgrade* from Feisty to Gutsy on a certain architecture (including a
SiS 5513 IDE driver) will cause the computer to be unbootable, while a
fresh install on the same computer will have it working like a charm.
There is some
Here's a quick rundown of my Gutsy kernel issue.
Feisty was working fine with my computer. An upgrade to Gutsy worked --
with the exception of needing to either use the Feisty kernel, or
compile my own with the SiS 5513 module compiled (it was removed by the
Ubuntu folks).
Then I finally read
Note: I found that my issue was related to an upgrade as opposed to a
fresh install. Please disregard my comments. For those experiencing
upgrade issues, please see bug 152820 for further details of the
problem.
--
Bad recognition of DD by ata_piix
https://bugs.launchpad.net/bugs/131945
You
*** This bug is a duplicate of bug 133666 ***
https://bugs.launchpad.net/bugs/133666
Please note: this is related to upgrade. Please also see bug 152820.
There are issues with the upgrade that do not exist with a fresh
install. I had to make additional updates to /etc/fstab. These updates
Just a note of clarification. My particular problem was related to an
upgrade from Feisty to Gutsy. See Bug 152820. I had to make some
tweaks to /etc/fstab as indicated in the other bug.
Cheers!
--
pata_sis fails to enable udma100, which causes a long (~1min) delay at boot.
Patch available!
See Bug 152820. Another SiS 5513 user there tried both upgrading and a
fresh install. For him, the upgrade caused boot issues, but the install
worked fine. I have made a few tweaks to my /etc/fstab file and am now
using the stock Gutsy kernels. My changes are noted in the other bug.
the
Clarification: after reviewing bug 152820, I found that my issue was
directly related to upgrading from Feisty to Gutsy, and some missing
related upgrade notes. Feel free to review that bug to see how I fixed
my problem. (Had to change the root partition specification in
/etc/fstab)
That being
Tested recompile of 2.6.24. The SiS 5513 module as originally supplied
by the kernel.org folks is still working. The 2.6.22 and 24 kernels
with this module removed in Gutsy and Hardy are not working.
If there's some reason that we do not want this module -- then we still
have not fixed the
Sorry to have further muddied the waters. Note: DaveW, the contributor
who originally posted this issue, has not responded back with his
computer specifications. But the next three contributors (Johan,
Necromancer, and Fabio Marzocca) all showed that they use this IDE
controller: nVidia
Major regression issue still in Gutsy for all SiS 5513 controllers, and
some Intel 82801 controllers. For Gutsy, we are still requesting that
the old patch be put back into the kernel -- that is: restore the
availability of the sis5513 module.
If there is something we are attempting to fix by
Sorry -- I neglected to change the 'Baltix' default.
** Changed in: linux-source-2.6.24 (Baltix)
Status: New = Invalid
--
stock 2.6.22 kernels don't detect both IDE HDDs anymore
https://bugs.launchpad.net/bugs/150693
You received this bug notification because you are a member of Ubuntu
** Also affects: linux-source-2.6.24 (Baltix)
Importance: Undecided
Status: New
--
stock 2.6.22 kernels don't detect both IDE HDDs anymore
https://bugs.launchpad.net/bugs/150693
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
** Also affects: linux-source-2.6.24 (Ubuntu)
Importance: Undecided
Status: New
--
please patch linux-source-2.6.22 to fix ata_piix bug
https://bugs.launchpad.net/bugs/133666
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
I have an Athlon Classic 1200 with a SiS 5513 IDE driver. The 2.6.22
kernels in Gutsy and Hardy, and the 2.6.24 kernel in Hardy all show this
problem by not recognizing my hard drive partitions on bootup --
causing a complete lock up early in the boot process. I have proven
this is fixable in
I tried. The latest 2.6.22 and 2.6.24 Ubuntu kernels both prevent my SiS 5513
driver from seeing my hard drives. They lock up very quickly after starting
the kernel.
Can you please at least explain what the SIS5513 module is trying to do
and why we're adamant that it must be removed from
I tried. The latest 2.6.22 and 2.6.24 Ubuntu kernels both prevent my SiS 5513
driver from seeing my hard drives. They lock up very quickly after starting
the kernel.
Can you please at least explain what the SIS5513 module is trying to do
and why we're adamant that it must be removed from
A careful look at this forum topic:
http://ubuntuforums.org/showthread.php?t=586894
will show that the original poster (mfajer) has an Intel Corporation 82801EB/ER
(ICH5/ICH5R) IDE Controller, yet his Etch lsmod report includes the SIS5513
module. So, looks like people with the Intel 82801
I tried recompiling the latest stable kernel from the official kernel
archives -- 2.6.23.8 -- by taking the stock Ubuntu .config file and a
make oldconfig. By using Ubuntu's .config file, the SiS 5513 module was
*not* included in the kernel. For that test, I had the same results as
I have with
mfajer, original poster of this thread:
http://ubuntuforums.org/showthread.php?t=586894
has an Intel 82801 EB/ER IDE controller, but his lsmod report from Etch shows
that this also uses the SIS5513 module. So, it appears that the Intel 82801
EB/ER driver is also broken by dropping this module.
FYI -- see forum topic http://ubuntuforums.org/showthread.php?t=586894
The original poster of the topic also had an Intel 82801 EB/ER driver, but his
lsmod from Etch included the sis5513 module.
For whatever reason, the Ubuntu kernel folk has chosen to compile the
kernel with the use of this
Hmm. I've a theory -- based on what others are reporting about the
Intel 82801 IDE controllers.
When you boot into the 2.6.20 kernel and run 'lsmod', do you have the
'sis5513' module listed amongst the list? If so, that could be the
problem. The Ubuntu kernel folk chose to disable the sis5513
I see that some people reporting this issue have an nVidia IDE
controller, while others have an Intel 82801 controller, and there may
even be other controllers represented here.
I do not have personal experience with the Intel 82801 controller, but I
have seen reports from other users that
One line of changes in the .config file -- which would only impact those
that actually utilize the module -- could sure fix a lot of problems.
Here's a partial listing of what appear to be issues directly related to
this missing module:
From the forums:
of the kernel
for usability on a computer with a SiS 5513 controller.
David Wynn
--
stock 2.6.22 kernels don't detect both IDE HDDs anymore
https://bugs.launchpad.net/bugs/150693
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu
BTW -- I can't vouch for effectiveness of this fix. I recompiled the
2.6.23 (which already has this fix coded in) and my computer failed to
boot -- got the 1 millimeter of progress hang. But recompiling the
2.6.23 kernel *with* the SIS5513 module fixed my problem. But then
2.6.22 worked fine
** This bug is no longer a duplicate of bug 150693
stock 2.6.22 kernels don't detect both IDE HDDs anymore
--
pata_sis fails to enable udma100, which causes a long (~1min) delay at boot.
Patch available!
https://bugs.launchpad.net/bugs/155702
You received this bug notification because you
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) = Ubuntu Kernel Storage
Team (ubuntu-kernel-storage)
--
stock 2.6.22 kernels don't detect both IDE HDDs anymore
https://bugs.launchpad.net/bugs/150693
You received this bug notification because
*** This bug is a duplicate of bug 150693 ***
https://bugs.launchpad.net/bugs/150693
Marked as a duplicate of 150693. Both are dealing with the SiS 5513
driver. My own experience with the SiS 5513 driver showed that enabling
the kernel module for SiS 5513 fixed my computer. Module was
If you still have the 2.6.22-15 kernel available, please start with that
kernel and provide the information requested at
https://wiki.ubuntu.com/KernelTeamBugPolicies.
--
Crashes on startup on Dell Inspiron 1501
https://bugs.launchpad.net/bugs/150011
You received this bug notification because
** Changed in: linux-source-2.6.20 (Ubuntu)
Assignee: (unassigned) = Ubuntu Kernel Team (ubuntu-kernel-team)
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: (unassigned) = Ubuntu Kernel Team (ubuntu-kernel-team)
** Changed in: linux-source-2.6.20 (Ubuntu)
Assignee: Ubuntu
FYI -- the absence of the SIS5513 module seems to be breaking those of
us with SiS 5513 IDE controllers. I went a little outside the purely
Ubuntu way of doing things, but not too far.
I downloaded the latest 2.6.22.12 version from the linux kernel
archives. Then I took my Ubuntu config file,
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: New = Confirmed
--
stock 2.6.22 kernels don't detect both IDE HDDs anymore
https://bugs.launchpad.net/bugs/150693
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I will admit, I haven't confirmed this in *exactly* a Ubuntu way -- but
I have confirmed the issue, and the fix is very simple -- at least in my
case, it was much easier than the diff shown. The key is right here in
the diff:
-# CONFIG_BLK_DEV_SIS5513 is not set
+CONFIG_BLK_DEV_SIS5513=m
Worthy of noting. I have no problems with SiS5513 IDE in my Feisty
distribution, but cannot get it loaded without some initramfs-tools
overrides in my Gutsy distribution. I would guess this is the reason:
From /boot/config-2.6.20-16-generic (feisty)
CONFIG_BLK_DEV_SIS5513=m
From
FYI -- I also had no problems in Feisty, but have been having *serious*
issues in Gutsy with booting. I update /etc/intiramfs-tools/modules to
include ide-generic, but that means -- no DMA. I also have a SIS5513
IDE controller. I was thinking of recompiling my own kernel, when I
found this:
The error message you listed indicates that you're using nvidia-glx-new.
That one is not intended for use with a GeForce 3. The nvidia-glx is,
although you may need to do some tweaking under nvidia-xconfig.
For the record, there are now two generations of legacy drivers. That's
why there's now
Found this yesterday:
http://kubuntuforums.net/forums/inde...opic=3087867.0
Try 'man nvidia-xconfig'. There are a lot of options here, and what works for
one, may not work for all. Try to think back as to whether there was anything
you needed to tweak for your card in Feisty.. Personally, in
Sorry, that link should be:
http://kubuntuforums.net/forums/index.php?topic=3087867.0
--
NV20 [GeForce3] nvidia not supported by nvidia-glx in gutsy
https://bugs.launchpad.net/bugs/155231
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Found this yesterday:
http://kubuntuforums.net/forums/index.php?topic=3087867.0
Try 'man nvidia-xconfig'. There are a lot of options here, and what works for
one, may not work for all. Try to think back as to whether there was anything
you needed to tweak for your card in Feisty.. Personally,
My apologies. Thank you for the correction. For reference purposes, I
found these two links that should cover the difference between the
various Linux drivers:
Cards that are supported by nvidia-glx-new are here:
http://www.nvidia.com/object/IO_18897.html
Cards supported by the two legacy
Stefan, thank you for pointing me in the right direction. On my Athlon
Classic, I added the ide-generic and ide-disk modules to the /etc
/initramfs-tools/modules. (I couldn't find an ide-core module) I then
ran the command indicated in your message. That fixed my kernel. I
still wonder if the
Although the nvidia-glx-legacy should *not* have updated to nvidia-glx,
the nvidia-glx is the correct drivier for your card (unless its an FX Go
for laptops).
Here's a link giving the specifics as to which cards should be using
nvidia-glx and which should be using nvidia-glx-legacy:
See this link:
http://nvidia.custhelp.com/cgi-
I use Kubuntu, so can't help on the Gnome front. There may be something
with your computer trying to run Compiz Fusion -- which is supposed to
be installed by default in Gutsy for machines that can handle it.
That being said, according to nvidia, the GeForce 3 should be supported
by the later
This could be related to Bug 133666 which indicates problems with
recognizing ATA / IDE hard drives. There is a patch listed in that bug,
but the patch has not been applied to Ubuntu yet.
--
kernel 2.6.22 fails to mount hard drives, drops to busybox
https://bugs.launchpad.net/bugs/146287
You
Perhaps related to Bug 133666, which documents a known issue with ATA /
IDE drive detection. That bug also lists a patch, but the patch has not
been applied to Ubuntu yet.
--
stock 2.6.22 kernels don't detect both IDE HDDs anymore
https://bugs.launchpad.net/bugs/150693
You received this bug
Perhaps related to Bug 133666, which speaks of issues with ATA / IDE
hard-drive detection. The other bug lists a patch, but that patch has
not been applied to Ubuntu yet.
--
can't boot linux-image-2.6.22 ppc
https://bugs.launchpad.net/bugs/151013
You received this bug notification because you
May be related to Bug 133666 which deals with a known issue with
recognizing ATA / IDE drives. A patch is supplied in the other bug, but
that patch has not been applied to Ubuntu yet.
--
Gutsy installation fails on HP 6510b
https://bugs.launchpad.net/bugs/131937
You received this bug
Possibly linked to issue 133666. That issue indicates a recognized
issue with ATA / IDE detection. As indicated in the other issue, a
patch has been created, but not yet applied in Ubuntu.
--
gutsy tribe 5 hangs after reboot
https://bugs.launchpad.net/bugs/135154
You received this bug
Problem still exists in gutsy.
** Tags added: feisty gutsy
--
Feisty package pciutils depends on obsolete package
https://bugs.launchpad.net/bugs/96207
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
As these are updated, please make sure that the description of xbase-
clients and xutisl no longer includes any reference to them being
transitional packages. They are currently used as meta-packages, not
transitional packages. This issue is still occurring in Feisty and
Gutsy.
** Tags added:
Public bug reported:
Ichthux-desktop currently requires xkeyboard-config which is a
transitional package, and thus no longer needed. Please remove
xkeyboard-config from the requirements for ichthux-desktop.
** Affects: ichthux-meta (Ubuntu)
Importance: Undecided
Status: New
**
Public bug reported:
Binary package hint: xfburn
Feisty xfburn depends on package cdrecord. In Feisty, cdrecord is a
transitional package containing just a symlink to package wodim. xfburn
needs to be updated, changing all cdrecord calls to wodim calls. The
cdrecord dependency needs to be
Public bug reported:
Binary package hint: xfburn
Package xfburn includes a dependency on package mkisofs. Package
mkisofs includes two symlinks for mkhybrid and mkisofs. Both are
symlinks for program genisoimage. Package xfburn needs to be updated,
replacing all calls to these two program to
Public bug reported:
Binary package hint: libxklavier11
Feisty package libxklavier11 requires package xkeyboard-config. Package
xkeyboard-config is a transitional package that depends on xkb-data, but
has no files of its own. The dependency needs to be changed from
xkeyboard-config to xkb-data
Public bug reported:
Binary package hint: pciutils
Package pciutils depends on package libpci2. Package libpci2 describes
itself as an obsolete package. This dependency needs to be reviewed.
If libpci2 is still needed, then the description for that package needs
to be changed, (if pciutils
I no longer use edgy. I see that this has been fixed in feisty for
ubuntu-desktop, kubuntu-desktop, edubuntu-desktop, xubuntu-desktop.
--
Ubuntu-Desktop (et al) still depends on xkeyboard-config
https://launchpad.net/bugs/64616
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I have confirmed that this has been fixed in both Dapper and Edgy.
** Changed in: denemo (Ubuntu)
Status: Needs Info = Fix Released
--
Breezy Denemo does not allow note entry
https://launchpad.net/bugs/29833
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
Binary package hint: ubuntu-desktop
This is a problem in edgy ubuntu-desktop and all edgy variants (kubuntu-
desktop, edubuntu-desktop, etc). These packages still depend on
xkeyboard-config.
But, xkeyboard-config has no real files and only depends on one package
101 - 181 of 181 matches
Mail list logo
