Public bug reported:
Binary package hint: kernel-image-2.6.20-9-generic-di
Apt-update signaled a number of available package upgrades for Fiesty
this morning. Included were updates to the generic kernels to 2.6.20-9.
Installed fine, booted okay, noticed the boot was faster then normal.
When desk
Brian Murray mentioned linux-restricted-modules. I noticed on a couple
of recent updates/upgrades that linux-restricted-modules for this kernel
update (2.6.20-9-generic) was selected by Adept for "install" but wasn't
included when the rest of the updates were upgraded.
I manually installed linux-r
*** This bug is a duplicate of bug 88416 ***
Comment is duplicated one left on Bug #88416:
Brian Murray mentioned linux-restricted-modules. I noticed on a couple
of recent updates/upgrades that linux-restricted-modules for this kernel
update (2.6.20-9-generic) was selected by Adept for "install"
Ditto the above.
--
adept manager crash on launch (kubuntu feisty)
https://launchpad.net/bugs/85229
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Public bug reported:
During recent upgrades, the following messages appear during or after
the upgrade is complete:
Setting up console-setup (1.13ubuntu9) ...
dpkg: error processing console-setup (--configure):
subprocess post-installation script returned error exit status 20
dpkg: dependency pr
rian Murray
>Status: Unconfirmed => Needs Info
>
> --
> console-setup and ubuntu-minimal report configuration errors during
> apt-get upgrades
> https://launchpad.net/bugs/93911
>
--
Joe Dougherty
mail: [EMAIL PROTECTED]
Blog:http://attaboy.tommydoc.net
--
console-set
Martin's comment got me thinking about this again. Are either one of
these packages necessary for Kubuntu? I have some gnome apps installed,
which is really the only non-KDE/ubuntu stuff I have on the system.
What's odd about this is that it only began to occur about two weeks
ago. I ignored it for
I can confirm the x11-common issue on my HP Pavilion dv6000t. I pulled a
bunch of updated debs using adept, but the update would break as
described above in the bug report. I deleted the x11-common deb from the
cache (/var/cache/apt), ran the update from a command-line with apt-get,
and the remaini
Re: my comment above...
I thought the problem might have been with multiple packages, as I had the same
issues as sveri. The problem with other debs only seemed to occur when I used
an interface application to do the updates (i.e., adept or adept updater).
Both seemed to want to update xorg-com
