Announcement

Collapse
No announcement yet.

10.10 upgrade problems not really with 10.10!!

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    10.10 upgrade problems not really with 10.10!!

    There are many reports of miseries with the 10.10 upgrade, including some by me. But the problem is not really with the 10.04 -> 10.10 transition. I made the transition a while ago and had at most minor problems. But the recent updates are a disaster. My problems started only after I updated a running 10.10 system. If you upgraded to 10.10 too late in the game, you got the problematic updates and all the difficulties that went with them, and there would be no indication that the problem lies with the updates.

    I've gotten past most of that, but I'm still stuck with the gnome desktop. The recommended desktop-switching procedure simply doesn't do it.

    #2
    Re: 10.10 upgrade problems not really with 10.10!!

    Originally posted by pwabrahams
    There are many reports of miseries with the 10.10 upgrade, including some by me. But the problem is not really with the 10.04 -> 10.10 transition. I made the transition a while ago and had at most minor problems. But the recent updates are a disaster.
    Which updates? There have been few updates to 10.10, other than the ones available via the kubuntu-ppa's. Were there any errors? What specifically is happening when you try to log in to KDE?

    My problems started only after I updated a running 10.10 system. If you upgraded to 10.10 too late in the game, you got the problematic updates and all the difficulties that went with them, and there would be no indication that the problem lies with the updates.

    I've gotten past most of that, but I'm still stuck with the gnome desktop. The recommended desktop-switching procedure simply doesn't do it.
    I am not completely sure what you mean by "recommended desktop-switching procedure"

    Need more information overall to help with this.

    Comment


      #3
      Upgrades

      I'm indeed referring to the updates from the ppa's, and they indeed were pretty extensive. Here are the ones from 11/4:
      Removed the following packages:
      kde-window-manager
      kdebase-bin
      kdebase-workspace
      kdebase-workspace-bin
      kdepasswd
      kdm
      kinfocenter
      konqueror
      ksysguard
      kubuntu-desktop
      kubuntu-konqueror-shortcuts
      libplasmaclock4b
      plasma-dataengines-workspace
      plasma-desktop
      plasma-netbook
      plasma-widgets-addons
      plasma-widgets-workspace
      rekonq

      Upgraded the following packages:
      gwenview (4:4.5.2-0ubuntu1~ppa1) to 4:4.5.3-0ubuntu1~maverick1~ppa1
      kamera (4:4.5.2-0ubuntu1~ppa1) to 4:4.5.3-0ubuntu1~maverick1~ppa1
      kdebase-data (4:4.5.2-0ubuntu1~ppa1) to 4:4.5.3-0ubuntu1~maverick1~ppa1
      kdebase-runtime-data (4:4.5.2-0ubuntu1~ppa1) to 4:4.5.3-0ubuntu1~maverick1~ppa1
      kdebase-workspace-data (4:4.5.2-0ubuntu1~ppa1) to 4:4.5.3-0ubuntu1~maverick1~ppa1
      kdebase-workspace-kgreet-plugins (4:4.5.2-0ubuntu1~ppa1) to 4:4.5.3-0ubuntu1~maverick1~ppa1
      kdegraphics-libs-data (4:4.5.2-0ubuntu1~ppa1) to 4:4.5.3-0ubuntu1~maverick1~ppa1
      kdegraphics-strigi-plugins (4:4.5.2-0ubuntu1~ppa1) to 4:4.5.3-0ubuntu1~maverick1~ppa1
      klipper (4:4.5.2-0ubuntu1~ppa1) to 4:4.5.3-0ubuntu1~maverick1~ppa1
      kmag (4:4.5.1-0ubuntu1) to 4:4.5.3-0ubuntu1~maverick1~ppa1
      kmousetool (4:4.5.1-0ubuntu1) to 4:4.5.3-0ubuntu1~maverick1~ppa1
      krosspython (4:4.5.1-0ubuntu3) to 4:4.5.3-0ubuntu1~maverick1~ppa1
      ksnapshot (4:4.5.2-0ubuntu1~ppa1) to 4:4.5.3-0ubuntu1~maverick1~ppa1
      ksudoku (4:4.5.2-0ubuntu1~ppa1) to 4:4.5.3-0ubuntu1~maverick1~ppa1
      ksysguardd (4:4.5.2-0ubuntu1~ppa1) to 4:4.5.3-0ubuntu1~maverick1~ppa1
      libkdcraw8 (4:4.5.2-0ubuntu1~ppa1) to 4:4.5.3-0ubuntu1~maverick1~ppa1
      libkdecorations4 (4:4.5.2-0ubuntu1~ppa1) to 4:4.5.3-0ubuntu1~maverick1~ppa1
      libkdegames5 (4:4.5.2-0ubuntu1~ppa1) to 4:4.5.3-0ubuntu1~maverick1~ppa1
      libkephal4 (4:4.5.2-0ubuntu1~ppa1) to 4:4.5.3-0ubuntu1~maverick1~ppa1
      libkexiv2-8 (4:4.5.2-0ubuntu1~ppa1) to 4:4.5.3-0ubuntu1~maverick1~ppa1
      libkipi7 (4:4.5.2-0ubuntu1~ppa1) to 4:4.5.3-0ubuntu1~maverick1~ppa1
      libkonq5-templates (4:4.5.2-0ubuntu1~ppa1) to 4:4.5.3-0ubuntu1~maverick1~ppa1
      libkscreensaver5 (4:4.5.2-0ubuntu1~ppa1) to 4:4.5.3-0ubuntu1~maverick1~ppa1
      libksgrd4 (4:4.5.2-0ubuntu1~ppa1) to 4:4.5.3-0ubuntu1~maverick1~ppa1
      libksignalplotter4 (4:4.5.2-0ubuntu1~ppa1) to 4:4.5.3-0ubuntu1~maverick1~ppa1
      libokularcore1 (4:4.5.2-0ubuntu1~ppa1) to 4:4.5.3-0ubuntu1~maverick1~ppa1
      libplasma-geolocation-interface4 (4:4.5.2-0ubuntu1~ppa1) to 4:4.5.3-0ubuntu1~maverick1~ppa1
      libprocesscore4a (4:4.5.2-0ubuntu1~ppa1) to 4:4.5.3-0ubuntu1~maverick1~ppa1
      libprocessui4a (4:4.5.2-0ubuntu1~ppa1) to 4:4.5.3-0ubuntu1~maverick1~ppa1
      libsolidcontrol4a (4:4.5.2-0ubuntu1~ppa1) to 4:4.5.3-0ubuntu1~maverick1~ppa1
      libsolidcontrolifaces4 (4:4.5.2-0ubuntu1~ppa1) to 4:4.5.3-0ubuntu1~maverick1~ppa1
      libtaskmanager4a (4:4.5.2-0ubuntu1~ppa1) to 4:4.5.3-0ubuntu1~maverick1~ppa1
      linux-alsa-driver-modules-2.6.35-22-generic (2.6.35-22.201011021600) to 2.6.35-22.201011031600
      linux-alsa-driver-modules-2.6.35-22-server (2.6.35-22.201011021600) to 2.6.35-22.201011031600
      okular (4:4.5.2-0ubuntu1~ppa1) to 4:4.5.3-0ubuntu1~maverick1~ppa1
      okular-extra-backends (4:4.5.2-0ubuntu1~ppa1) to 4:4.5.3-0ubuntu1~maverick1~ppa1
      plasma-scriptengine-python (4:4.5.2-0ubuntu1~ppa1) to 4:4.5.3-0ubuntu1~maverick1~ppa1
      python-kde4 (4:4.5.1-0ubuntu3) to 4:4.5.3-0ubuntu1~maverick1~ppa1
      system-config-printer-kde (4:4.5.2-0ubuntu1~ppa1) to 4:4.5.3-0ubuntu1~maverick1~ppa1
      xserver-xorg-video-intel (2:2.12.0-1ubuntu5) to 2:2.12.0-1ubuntu5.1
      Apparently there was a packaging problem with that group; as a result, my next reboot hung on the "checking battery state" message. In addition, there were about four updates within the preceding five days of linux-alsa-driver-modules.

      My story is that the first update to the alsa modules killed my headphones. A later update in the sequence killed my local speakers also. The 11/4 collection seemed to restore the headphones but as I mentioned above, caused the next reboot to hang. At the moment I'm mostly back to where I was before the first of the updates in late October, except that my wireless connection is gone. (It was working fine before the updates, using networkmanager.)

      The "recommended procedure" for switching back to the KDE desktop is sudo dpkg-reconfigure kdm. That didn't work, but since my earlier post I've gotten back to KDE by using the facilities of the login screen. The headphone/internal switching is flaky but at least I can get it to work by fiddling around with the mixers. So at the moment my main problem is the lack of a wireless connection.

      There are many posts about problems with the 10.04->10.10 transition. My point was to let folks know that the problem is likely not with 10.10 per se but with the recent updates to it. Or at least that's what my experiences suggest.

      Comment


        #4
        Re: 10.10 upgrade problems not really with 10.10!!

        yes, there was a missing package that somehow was unsuccessfully copied over to the ppa from it's staging area, and that is what caused the package removals - the removed packages in your log were pretty much the heart of KDE, including KDM - probably why the 'dpkg-reconfigure kdm' did not work. GDM, however, is quite capable of loading KDE (when KDE is all there that is ). GDM and KDM by default log in to the last desktop environment used unless you choose something else at the login screen.

        If you still need to repair kde, from that apt log, installing kubuntu-desktop will pull in all the missing KDE bits.

        most upgrade issues from what I have seen are the (unfortunately) usual incompatibilities involving the move to a new Xorg stack in 10.10. and kmix's lack of usefulness with pulseaudio - installing pulseaudio's pavucontrol helps with that.

        Comment

        Working...
        X