Kubuntu 7.10 Upgrading to Kubuntu 7.10 and after gives error and says Distribution is Up To Date

I confirm this exact same problem. It's a strange problem and should be fixed as soon as possible.

Keith.

Same happens to me.
I'm using Kubuntu an a T30 Laptop. With Feisty all ran fine. During Upgrade to Gutsy I had extreme problems with acpid (this Site describes the prob: http://ubuntuforums.org/howthread.php?t=288724 ).
Since I solved the problems with acpid, I have the same problems like iboware.

Holger

I have this problem too. On my first workstation I updated from Gutsy RC to Gutsy Final by installing all updates. After the release got out, update manager reported that a new version was available and launched the distribution upgrade tool, which stops at the second step, saying that my system is already up-to-date. Well, that's fine with me, but today I got it again, while there were no "normal" updates.
On my second workstation I installed Kubuntu Gutsy from the release cd from the 18th of oktober, and it has the exact same issue.

Safe to say that the RC was more stable than the final, as both the upgrade tool and kopete are broken in the final, while the weren't in the RC.

confirm the same problem

Hi,

I have the same problem after a fresh install of Gutsy from CD. The update manager says that there is a new version available etc.

I have the same issue using a fresh install from the final release disk.

I have the same issue using a fresh install from the final release disk.

Hi,

here is the same bug:
Installed fresh Kubuntu 7.10, no rc or beta, its final release.
Today it says there is a new release. If I chose upgrade, it says a few steps later, that there is no upgrade available and suggest to me to fill in a bug report, which I have done now.

Same problem confirmed.

Same problem. Installed Ubuntu 7.4, later ADDED Kubuntu 7.4, now says I need to upgrade.

I can confirm this bug here on Kubuntu 7.10
I've installed it from a Gutsy CD as the dist-upgrade from Kubuntu Feisty didn't work.

But I have to say that I downloaded the CD before the 18th of October. I couldn't wait ;) Maybe I'll try it with a newly downloaded CD some time soon. But that depends on how long I'll have to backup my data on the other machine (I don't want to reinstall here) which I can't do at the moment.

I can confirm this.

I installed gutsy rc (3 days prior to gutsy release) and this problem appears after every software-upgrade with adept_updater. ie, when a newer version of a program is available, the adept-notifier tells me it's an update. After I've updatet with adept (not apt or aptitude though), the version-upgrade wiz appears (and fails).

I can confirme the previous posts, too. German installation

Upgraded successfully to 7.10, but the upgrade is offered over and over again.

Same here - after a normal package-upgrade, it also displays after finishing "A new version of the OS is available. Click next to start the update progress" (in german) but there is even no "next" button... Only "close".

confirm the same problem!

Same problem Here too

The same her, installed RC3 on one computer and audated to release. Every time after adept_updater the message of "a new version" appears, but of course there is no new one - so this "update" fails (what else should it do ;-) ).

But the same thing happens on another installation of Kubuntu, this time I did not install RC3 but the release itself. The problem here is excatly the same.

Regards,

Ralf

Same thing for me.
Upgraded from Kubuntu 7.04 to 7.10 and it still says I can upgrade to 7.10 , but after the same steps , it comes to the conclusion that my system is up to date ...
Kubuntu 7.10 French on desktop with P4/3Gh

Same for me.
I installed Gutsy from the alternate install CD (last beta) and then the package manager downloaded the last version of all the installed packages (about 350 MB). After that I received a message saying there was a new system upgrade available. After running the first and the second step of the system updater It says that the system is up to date and cancels the process

Same here. I upgraded from kubuntu 7.04 and since then any time I upgrade the system with adept, it then tells me there is an update but fails later on saying there is no upgrade available.

JC

I have the same problem, at the end of all update installs it goes into dist upgrade mode, mine is a clean install of 7.10 from CD in UK English.

same

Same with kubuntu 7.10 on acer aspire 5630

I did a completely fresh install of Kubuntu 7.10, and I can positively confirm the above problems. It wants to upgrade 7.10 to 7.10, and then stops saying that it's already up to date.

confirm problem

Wow...uh...yeah. I guess this one has been confirmed, eh? ;) I suppose for good measure and to beat an already dead, mutilated, and decomposed horse, I shall also confirm that this is happening to my shiny new Kubuntu 7.10 64-bit install too. Cheers, all!

confirm problem

Ditto. Upgraded from 7.04 to 7.10. The installer crashed on the first pass, but the second time it ran to completion. Now adept tells me there is a new distribution available each time it sees normal software updates, but after lots of chugging it tells me there is nothing to upgrade and an error has occurred. Odd. I wonder where the 'current distribution' is stored in Ubuntu/Kubuntu.

Same here on my Compal ITF01 laptop with a fresh Kubuntu 7.10 install.

Same problem Here too

I am joining the club. Its getting crowded in here :p

Same problem here...

Same Problem here with a fresh installed Kubuntu 7.10.
System is a Acer TravelMate C300 (TabletPC).
The updater reports a problem that libportaudio0 is no longer supported by canonical and should be removed after the update.

Alain St-Denis ha scritto:
> Same problem here...
>
>

udating adept the problem seems resolved

i too can confirm false upgrade notice. During upgrade from 7.04 kubuntu to 7.10 kubuntu, sysetem failed horribly. After a reformat, and install from new Installtion of 7.10 kubuntu, the adept manager tells me an upgrade is available, and when I click on it, it says none available. this is on a older intel coppermine PIII desktop 800mhz, 440 RAM. Good luck.

Confirmed the bug :S

Not very useful, but I confirm the same problem... ;-)

me too :)
and it keeps coming again every day as if it still hasn't figured out that it is already up-to-date.

One more piece of data:
After gutsy came out, for some unclear reason I didn't get the suggestion to upgrade from feisty by adept-manager. I waited several days and finally decided to download the ISO. I did a full upgrade from DVD, and only after it was all finished and I rebooted gutsy, I got the offer to upgrade from adept.

Now when I no longer need it. I get the offer to upgrade repeatedly and then it fails.

me too.

 Andrea Ianni wrote;
> udating adept the problem seems resolved
>

How do I update adept? Which version is needed to fix this problem?
This doesn't appear to be updated with the usual update system. My system has adept 2.1.3ubuntu17 and this has the bug.

Problem seems to be gone with the latest adept update

Same problem here

Peter ha scritto:
> Andrea Ianni wrote;
>
>> udating adept the problem seems resolved
>>
>>
>
> How do I update adept? Which version is needed to fix this problem?
> This doesn't appear to be updated with the usual update system. My system has adept 2.1.3ubuntu17 and this has the bug.
>
>
i just made an apt-get update and the system says me there is an updated
version of adept (and some others...). I've installed the new softwares
and problems disappears.

What version of adept fixes the problem?

An update to adept hasn't shown up here. I guess I need to wait until it propagates through the mirrors.

Peter ha scritto:
> What version of adept fixes the problem?
>
> An update to adept hasn't shown up here. I guess I need to wait until
> it propagates through the mirrors.
>
>
on a terminal I 've made this:

sudo apt-get update

and the systems says that there was these updates:

adept adept-batch adept-common adept-installer adept-manager
adept-notifier adept-updater apt apt-utils
  firefox ghostscript ghostscript-x gs-common gs-esp gs-esp-x
kdelibs-data kdelibs4c2a kdesudo libgs8
  libpango1.0-0 libpango1.0-common libpango1.0-dev libssl0.9.8
libwnck-common libwnck22 openssl

i then made:

sudo apt-get upgrade

that's all.
good luck

same for me

confirm the same problem

snap, same again

bug: confirmed, on a Thinkpad R52, after a fresh install (but also happend after a upgrade)
solution from above doesn't work, no updates found.

What ciould I say ? .... SAME THING here, in La Rochelle !

Let's still have Fun, on Kubuntu !

Confirmed the bug. Has happened twice to me usually after an update of some sort.

Same for me.

I get the same problem - i386, Kubuntu 7.10. Exactly as described.

Same problem here, using AMD64, Kubuntu 7.10

Same problem here in Gutsy Gibbon i386 with Adept

Same problem with Intel 64. Description is perfect !

Please stop confirming the bug, which creates an e-mail for all subscribers of the bug(s). It is "Confirmed" already.
Thank you.

Same problem here.

Yo, reinstalling adept fixed it for me (in case you are already on the latest).

After updating adept from gutsy-proposed this bug no longer appears.

I confirm the same issue.

Same for me with adept version 2.1.3ubuntu17. I have no updates avaiables for adept package :-(

Some extra repository?

I can confirm the same happening to me. It is trying to update to 7.10 (from 7.10)
Kubuntu 7.10 RC installed on ASUS A6VA

For me it is fixed with adept version 2.1.3ubuntu17.1, which is now in proposed updates repository.

O.K., thank you for your fast reply. Didn't expect one.

Sincerely,

Sascha

2007/10/24, vrabcak <email address hidden>:
>
> For me it is fixed with adept version 2.1.3ubuntu17.1, which is now in
> proposed updates repository.
>
> --
> Kubuntu 7.10 Upgrading to Kubuntu 7.10 and after gives error and says
> Distribution is Up To Date
> https://bugs.launchpad.net/bugs/154771
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

confirm the same problem

I had the same problem. I started with 7.04, upgraded in early October, then kept getting bugged about upgrading every day.

In what seemed to be an unrelated error, I also noticed that I was getting the following error message when I did a "sudo apt-get update":

Fetched 81.7kB in 0s (259kB/s)
Reading package lists... Done
W: GPG error: http://security.ubuntu.com gutsy-security Release: The following signatures were invalid: BADSIG 40976EAF437D05B5 Ubuntu Archive Automatic Signing Key <email address hidden>
W: GPG error: http://us.archive.ubuntu.com gutsy-updates Release: The following signatures were invalid: BADSIG 40976EAF437D05B5 Ubuntu Archive Automatic Signing Key <email address hidden>
W: You may want to run apt-get update to correct these problems

So I googled around a bit to find a solution to this problem and found this solution:

# Retrieve the ubuntu key with wwwkeys.eu.pgp.net, store it in my keyring
gpg --keyserver wwwkeys.eu.pgp.net --recv-keys 437D05B5
# Add the retrieved key along with other existing keys
sudo apt-key add ~/.gnupg/pubring.gpg
# apt-get update without cache to force the use of the newly added key
sudo apt-get update -o Acquire::http::No-Cache=True

In my case, I had to change the ownership of ~/.gnupg/trustdb.gpg from root to myself. But the key import worked fine and this fixed the bad apt-get key problem. When I did another "sudo apt-get update" and "sudo apt-get dist-upgrade", suddenly it found more updates:

alan@chutney:~$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  adept adept-batch adept-common adept-installer adept-manager adept-notifier adept-updater firefox
  ghostscript ghostscript-x gs-esp-x kdelibs-data kdelibs4c2a libgs8 libssl0.9.8 mozilla-thunderbird openssl
  thunderbird
18 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 46.6MB of archives.
After unpacking 28.7kB of additional disk space will be used.
Do you want to continue [Y/n]?

Notice that several "adept" changes are included above.

I am still installing these changes right now, so I can not verify that this fixes the update-daily problem, but it is consistent with what others are seeing: you keep getting pestered until adept is updated -- and something is holding adept back. In my case, it looked like it was the keys.

Alan

I have the same issue

I confirm the bug... My fresh install was with a 7.10 beta (about 3 weeks ago)

@Alan Porter: I have just executed `apt-get update` as root, but I don't have any messages about invalid signatures, nor did I have those before. I have a fresh 7.10 install though. There were some updates for Adept some time ago, but I still have the problem. On another computer I have activated the "pre-released updates" after which some new updates became available, which fixed the problem. I'm still waiting for official updates though.

.I've got the same bug whit a fresh install of kubuntu 7.10

On 24/10/2007, RexLeo <email address hidden> wrote:
>
> .I've got the same bug whit a fresh install of kubuntu 7.10
>
> --
> Kubuntu 7.10 Upgrading to Kubuntu 7.10 and after gives error and says
> Distribution is Up To Date
> https://bugs.launchpad.net/bugs/154771
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

Yeah it's a weird one, I didn't do a fresh install though, I used the
"version upgrade" option in Adept, but this bug has only happened to me
today.

I too have this problem. I upgraded in Gnome, then KDE's Adept keeps hounding me to upgrade, which I can't because I'm already there.

Strange bug, though not critical. It simply doesn't properly identify which version of the distro I'm using before preaching to word of the Upgrade.

Hello Guys,

I think this bug is _CRITICAL_!

Thank you!

I think this bug can be closed now. After running update-manager, it reported updates for adept, adept_manager, adept_updater and other. The new version was 2.1.3ubuntu17.1 and this one is an official released update, not a prerelease. After updating, I got the new distribution stuff once more, but that was probably because the instance of adept_manager I was running, was still the old version. After restarting, I ran adept_updater again and it reported "no updates". Thanks Kubuntu team, for fixing this annoying bug in just six days after the release, including a weekend.

Hello I have the same problem

Bye

This is a duplicate of #153889, fixed in gutsy-proposed

the bug is fixed for me, with the last upgrade

The bug is not fixed for me

The bug is fixed for me with adept 2.1.3ubuntu17.1. I just had to restart adept-manager. Thank you for making the Kubuntu experience even better :-)

same. stupid computer

I downloaded Kubuntu 7.01 today, installed in English and had the same bug.

Error
Your system is up-to-date
There are no upgrades available for your system. The upgrade will now be cancelled.

[Report Bug] [Close]

kubuntu 7.10 even

Bug 153889 has gone through the SRU verification process and the fix now exists in feisty-updates and gutsy-updates subsequently I am changing this bug's status to Fix Released.

download linuxmint they already did fix it

www.linuxmint.com i'm sure you like the software 7.10

cheers

----- Original Message -----
From: "Brian Murray" <email address hidden>
To: <email address hidden>
Sent: Tuesday, November 13, 2007 6:35 PM
Subject: [Bug 154771] Re: Kubuntu 7.10 Upgrading to Kubuntu 7.10 and
aftergives error and says Distribution is Up To Date

Bug 153889 has gone through the SRU verification process and the fix now
exists in feisty-updates and gutsy-updates subsequently I am changing
this bug's status to Fix Released.

** Changed in: adept (Ubuntu)
       Status: Fix Committed => Fix Released

--
Kubuntu 7.10 Upgrading to Kubuntu 7.10 and after gives error and says
Distribution is Up To Date
https://bugs.launchpad.net/bugs/154771
You received this bug notification because you are a direct subscriber
of a duplicate bug.

On 13/11/2007, Ernst <email address hidden> wrote:
> download linuxmint they already did fix it
>
> www.linuxmint.com i'm sure you like the software 7.10
>
> cheers
>

Right...... why would we do this when this is an Ubuntu/Kubuntu bug
list? The fact that Linuxmint is built on Ubuntu notwithstanding.
--
==============================================

Kevan Farmer
Linux user #373362
Staffordshire

Hi,
yes i know but linixmint 7.10 did not crash and also the updater did work
perfect.
i do not know how they did it it fixed it, but it works

aks them on the foum, they are very friendly

cheers

----- Original Message -----
From: "kevanf1" <email address hidden>
To: <email address hidden>
Sent: Wednesday, November 14, 2007 12:41 PM
Subject: Re: [Bug 154771] Re: Kubuntu 7.10 Upgrading to Kubuntu 7.10
andaftergives error and says Distribution is Up To Date

On 13/11/2007, Ernst <email address hidden> wrote:
> download linuxmint they already did fix it
>
> www.linuxmint.com i'm sure you like the software 7.10
>
> cheers
>

Right...... why would we do this when this is an Ubuntu/Kubuntu bug
list? The fact that Linuxmint is built on Ubuntu notwithstanding.
--
==============================================

Kevan Farmer
Linux user #373362
Staffordshire

--
Kubuntu 7.10 Upgrading to Kubuntu 7.10 and after gives error and says
Distribution is Up To Date
https://bugs.launchpad.net/bugs/154771
You received this bug notification because you are a direct subscriber
of a duplicate bug.

Yup, same problem.

not anymore

www.linuxmint.com 7.10

good luck
----- Original Message -----
From: "David McNeill" <email address hidden>
To: <email address hidden>
Sent: Sunday, December 02, 2007 10:32 AM
Subject: [Bug 154771] Re: Kubuntu 7.10 Upgrading to Kubuntu 7.10 and
aftergives error and says Distribution is Up To Date

Yup, same problem.

--
Kubuntu 7.10 Upgrading to Kubuntu 7.10 and after gives error and says
Distribution is Up To Date
https://bugs.launchpad.net/bugs/154771
You received this bug notification because you are a direct subscriber
of a duplicate bug.

For everyone who just installed Kubuntu 7.10. The bug you are referring to is located in the updater (adept) and it will surface when you try to update the first time, no matter whether the fix has been released.
Directly after installing and before updating with adept or anything else, you should open Konsole (in Kmenu>System>Konsole). First issue `apt-get update` and after that `apt-get upgrade`. When upgrading is completed, the update notification icon in the system tray will disappear and your system is completely up-to-date. You may wish to reboot, as the update contains new versions of some restricted drivers for wireless and the kind. The reason that this bug does not appear in LinuxMint, is because it has implemented the bug fix in the install-cd, whereas Kubuntu needs to be updated for the fix to be applied.

On 02/12/2007, Jeroen Maris <email address hidden> wrote:
> For everyone who just installed Kubuntu 7.10. The bug you are referring to is located in the updater (adept) and it will surface when you try to update the first time, no matter whether the fix has been released.
> Directly after installing and before updating with adept or anything else, you should open Konsole (in Kmenu>System>Konsole). First issue `apt-get update` and after that `apt-get upgrade`. When upgrading is completed, the update notification icon in the system tray will disappear and your system is completely up-to-date. You may wish to reboot, as the update contains new versions of some restricted drivers for wireless and the kind. The reason that this bug does not appear in LinuxMint, is because it has implemented the bug fix in the install-cd, whereas Kubuntu needs to be updated for the fix to be applied.
>

Shame this advice didn't come from Ubuntu/Kubuntu admin's :-(

Thank you, I'm sick of seeing the recurring update problem on my PC
running Kubuntu 7.10 I'll pass the tip onto some of my fellow LUG
members.
--
==============================================

Kevan Farmer
Linux user #373362
Staffordshire

I confirm this exact same problem.

Bakyt

Same here!!!!
(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1235892544 (LWP 17519)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6 0xffffe410 in __kernel_vsyscall ()
#7 0xb76aa875 in raise () from /lib/tls/i686/cmov/libc.so.6
#8 0xb76ac201 in abort () from /lib/tls/i686/cmov/libc.so.6
#9 0xb78b66e0 in __gnu_cxx::__verbose_terminate_handler ()
   from /usr/lib/libstdc++.so.6
#10 0xb78b3f65 in ?? () from /usr/lib/libstdc++.so.6
#11 0xb78b3fa2 in std::terminate () from /usr/lib/libstdc++.so.6
#12 0xb78b40ca in __cxa_throw () from /usr/lib/libstdc++.so.6
#13 0x0814d9a6 in ?? ()
#14 0x0814df1a in ?? ()
#15 0x0814df78 in ?? ()
#16 0x0814e7c5 in ?? ()
#17 0x0814c2bd in ?? ()
#18 0x08135ef9 in ?? ()
#19 0x0809ad6d in ?? ()
#20 0x0807349f in ?? ()
#21 0x080755d5 in ?? ()
#22 0xb6c6a893 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#23 0xb6ff68ec in QSignal::signal () from /usr/lib/libqt-mt.so.3
#24 0xb6c8a842 in QSignal::activate () from /usr/lib/libqt-mt.so.3
#25 0xb6c92258 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3
#26 0xb6c01af0 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#27 0xb6c0391f in QApplication::notify () from /usr/lib/libqt-mt.so.3
#28 0xb7309cd2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#29 0xb6b94209 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#30 0xb6bf453b in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#31 0xb6ba8d49 in QEventLoop::processEvents () from /usr/lib/lib...

On 08/04/2008, Spaccafighe <email address hidden> wrote:
> Same here!!!!
> (no debugging symbols found)
> Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
> (no debugging symbols found)
*Massive snip of irrelevant stuff*.

This should be sorted by now. It is on my PC anyhow. I have run
update god alone knows how many times since my original (and repeated,
sorry) bug report. I do not get the upgrade notification popping up
anymore. So, perhaps you simply need to accept the notification (I
assume you are installing from an official CD?) and bask in the
knowledge that by updating your system everything is put right in this
respect.
--
==============================================

Kevan Farmer
Linux user #373362
Staffordshire