Announcement

Collapse
No announcement yet.

Cannot log into Kubuntu after upgrade

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

    Cannot log into Kubuntu after upgrade

    Hi
    I have upgraded and I am unable log in I get the following message:-
    "no welcome plugin found-check configuration"
    How do I check the configuration/cure this problem?
    Any help would be appreciated.
    Best regards
    lurch

    #2
    Re: Cannot log into Kubuntu after upgrade

    It sounds like you are running into a case where /etc/nologin did not get removed. Normally this file gets created when the system starts and is then removed after everything is running and users are welcome to login. If the file still exists attempts to login are refused and the user sees a message in the /etc/nologin file.

    Now the interesting part. Root logins are the only ones allowed in this case. Unless you enabled them, root logins are disabled on Ubuntu/Kubuntu systems. The standard fix is to login as root and remove the file, after which other users can login.

    I think in this case you probably will have to use the rescue boot option and get a root shell to remove the file. It is also quit likely that rebooting will fix it.

    Comment


      #3
      Re: Cannot log into Kubuntu after upgrade (apt-get hold problem)

      Hi
      Thanks for the reply.
      I have had a look at your suggestion, but /etc/nologin does not exist if I click ok at the problem in recovery mode it sends me to the command line and I can log in.
      I think the problem is with apt-get I have discovered it is holding back 48 packages several of these are to do with KDE.
      How do I get apt-get to install held packages?
      It must be something to do with the "--ignore-hold" option but I cannot work out how to use it.
      any help would be appreciated

      Comment


        #4
        Re: Cannot log into Kubuntu after upgrade

        The problem seem to be that the kde 4.2.4 updates depends on packages with newer versions than there exist in the repos... Someone made a big mistake. For example kdebase-bin depends on alot of qt stuff version 4.5.1 but the latest in the repos are 4.5.0-0ubuntu4.1.

        The packages really can't have been tested properly before released. I just installed kubuntu yesterday evening... My kde installation is already pretty much unusable!

        Comment


          #5
          Re: Cannot log into Kubuntu after upgrade

          To get the upgrades install run
          Code:
          sudo aptitude update
          sudo aptitude -f full-upgrade

          Comment


            #6
            Re: Cannot log into Kubuntu after upgrade

            Hi
            I have used the aptitude commands and the repair broken packages in the recovery login.
            I can now login but Kde freezes on the start screen the "drive appears, crossed screwdriver and spanner
            and the world the next symbol starts to appear but the screen freezes at this point.
            looks to be in NASA speak a major malfunction.
            Any ideas apart from a big hammer would be appreciated

            Comment


              #7
              Re: Cannot log into Kubuntu after upgrade

              Don't use aptitude

              I thought it solved some conflicts but in fact it just removed the applications, one at a time... I ran it about 40 times using a loop and "-y" argument, now I pretty much have no kde installation anymore. The updatemessage have been removed from the kubuntu mainpage (Although the message still is accesible by clicking june to the right.)

              Hopefully someone will fix it soon. If you want a working computer, install some other window manager or reinstall. Also don't add the ppa archive again

              Comment


                #8
                Re: Cannot log into Kubuntu after upgrade

                Originally posted by Rizado
                Don't use aptitude

                I thought it solved some conflicts but in fact it just removed the applications, one at a time... I ran it about 40 times using a loop and "-y" argument, now I pretty much have no kde installation anymore. The updatemessage have been removed from the kubuntu mainpage (Although the message still is accesible by clicking june to the right.)

                Hopefully someone will fix it soon. If you want a working computer, install some other window manager or reinstall. Also don't add the ppa archive again
                This post is nonsense. Do not pay attention to it and certainly do not use the -y.

                Comment


                  #9
                  Re: Cannot log into Kubuntu after upgrade

                  It is not nonsense, there is a problem with the update repositories for kde 4.2.4 which have now been removed from the kubuntu webpage. The problem was that some packages where depending on some qt4.1 packages that does not exist in ubuntu jauntys regular repos. This #&%$s everything up and aptitude tries to correct the problems by "downgrading", but that is not possible for some reason so it seem to just remove them instead. After every fix there's another dependency confict and after running it a few times it will have removed loads of packages. (eg dolphin, kdm, etc etc)

                  Please don't speak out about something in this way when you have no idea what the problem is. Why would aptitude manage to install broken packages from the repos when apt-get cannot? The reason why I used -y was because every time a conflict is found it asks what to do and I don't like to sit and press y for an hour.

                  Comment


                    #10
                    Re: Cannot log into Kubuntu after upgrade

                    Originally posted by Rizado
                    It is not nonsense, there is a problem with the update repositories for kde 4.2.4 which have now been removed from the kubuntu webpage. The problem was that some packages where depending on some qt4.1 packages that does not exist in ubuntu jauntys regular repos. This #&%$s everything up and aptitude tries to correct the problems by "downgrading", but that is not possible for some reason so it seem to just remove them instead. After every fix there's another dependency confict and after running it a few times it will have removed loads of packages. (eg dolphin, kdm, etc etc)

                    Please don't speak out about something in this way when you have no idea what the problem is. Why would aptitude manage to install broken packages from the repos when apt-get cannot? The reason why I used -y was because every time a conflict is found it asks what to do and I don't like to sit and press y for an hour.
                    You have provided no confirmation of any of this and your use of aptitude -y is not smart and hardly an indication that aptitude should not be used. The most likely reason for packages not being found is that the user has not updated their system, followed by the repositories them selves not having updated yet. Then there is the chance that the developers have not configured the dependencies correctly, something that is much more common with Ubuntu and Kubuntu than Debian, unfortunately.

                    By no means does this imply that not using aptitude is the solution for this. In fact using aptitude will quite likely provide a solution but not always. Your problem was from ignorant misuse of aptitude and your post is not providing good information to anyone.

                    Comment


                      #11
                      Re: Cannot log into Kubuntu after upgrade

                      That Kubuntu updates repo's packages ARE broken precisely because of the dependencies upon the updated qt versions. KDE is not installable or upgradeable from that repo at the moment.

                      It's possible that there is an experimental qt repo I am not aware of. OpenSUSE went through a situation similar to this one a while back, when upgrading using their KDE 4 Build Service repos meant also including their Build Service qt repo.

                      It can be fixed by the repo maintainers by either reducing the qt dependencies down back to the versions Ubuntu has in their main repos or by including the necessary qt updates in that kubuntu ppc repo.

                      I have tried adding the backports and pre-official updates repos but neither contain the qt updates necessary.

                      I did not proceed with any updates, preferring to uncheck the kubuntu ppc repo for the moment so I could get the security updates provided today (mostly cups stuff) from the normal update channels.

                      Actually, Aptitude is a bit more adept at resolving conflicts and stuff than is apt-get. I'm a Debian user who swears by Aptitude and so have done all my upgrading and installing of software using it in Ubuntu/Kubuntu as well, running in VirtualBox on my Debian Lenny system. I just use Synaptic to access the GUI for repository adjustment while in Ubuntu/Kubuntu. I don't use that thing in Debian, but there are so many entries in /etc/apt/sources.list and sources.list.d on the 'buntu's that it's just easier to use the GUI which sorts it out in a more legible manner.

                      Just as a helpful hint, when seeing so many dependency conflicts it is generally better to quit out of the upgrade after reading what the problem is and waiting to see if it gets resolved by the repo maintainers. It usually gets resolved pretty quickly once folks see there's a problem. Better backing out than borking ones system, trying to "make it fit."

                      Edit -

                      All is well now. The maintainers modified the packages to install with qt 4.5.0. I upgraded successfully with an aptitude full-upgrade. No conflict resolving was necessary. Nice that it was fixed up so quickly!

                      Comment


                        #12
                        Re: Cannot log into Kubuntu after upgrade

                        ...and here we go again. The latest update contains dependency errors to

                        Code:
                        kdebase-runtime-bin-kde4: Conflicts: kdebase-bin (< 4:4.2.85) but 4:4.2.4-0ubuntu1~jaunty1~ppa2 is to be installed
                        kdebase-runtime-data: Conflicts: kdebase-data (< 4:4.2.85) but 4:4.2.4-0ubuntu1~jaunty1~ppa2 is to be installed
                        This is ridicolous! Well, atleast this time kde can still start even though much functionallity is lefty out. This like background, loads of plugins, konqueror...

                        There's a very high cpu utilization too, xorg uses about 70% and plasma 40% according to top. This is on a C2D.

                        Why don't they test the packages before releasing them? By testing I mean test to install. It's done in 5 minutes in a virtual machine.

                        EDIT: Seems this is a known problem... http://kubuntuforums.net/forums/inde...4115#msg184115

                        EDIT2: Okay, the repos are ready now and updating is working. However konqueror is no longer the default webbrowser so that's not in the repos (yet?).

                        Comment

                        Working...
                        X