Page 1 of 2 12 LastLast
Results 1 to 10 of 13

Thread: Unable to log in to graphical interface after upgrade from 12.3 to 13.1

  1. #1

    Default Unable to log in to graphical interface after upgrade from 12.3 to 13.1

    For a bit of background see my previous posting http://forums.opensuse.org/english/g...-3-13-1-a.html

    When I boot OS 13.1, I get the login screen, however when I try to log on (either as root or my own user id), the login dialogue box disappears and just left with a green chemelion grinning at me inanely, then nothing.

    I can switch to a text console using Ctrl-Alt-1 and then log in as root OK.

    I've tried selecting both the 'KDE Plasma Workspace' and also the 'Failsafe' login options but both hang.

    Also, if I issue a 'shutdown -r now' command from the command line (or try to shut it down from the login screen), the screen goes black, but it doesn't shut down.

    Any ideas?

    Many thanks again.

    Gary

  2. #2

    Default Re: Unable to log in to graphical interface after upgrade from 12.3 to 13.1

    OK, so I had a go at adding the 'nomodeset' option to the default kernel boot command line in yast and that made things even worse - I counldn't even log in using the tui!

    Fortunately, I could get in using the recovery boot.

    Cheers,

    Gary

  3. #3
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: Unable to log in to graphical interface after upgrade from 12.3to 13.1

    On 2014-01-07 16:56, dn312sr wrote:
    >
    > For a bit of background see my previous posting
    > http://tinyurl.com/pde3xp4


    Was it an offline system upgrade (boot dvd, choose upgrade) or online
    system upgrade (zypper dup)?

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 12.3 x86_64 "Dartmouth" at Telcontar)

  4. #4
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    16,287

    Default Re: Unable to log in to graphical interface after upgrade from 12.3 to 13.1

    Also what graphics card/chip?

  5. #5

    Default Re: Unable to log in to graphical interface after upgrade from 12.3to 13.1

    Quote Originally Posted by robin_listas View Post
    On 2014-01-07 16:56, dn312sr wrote:
    Was it an offline system upgrade (boot dvd, choose upgrade) or online
    system upgrade (zypper dup)?
    Hi Carlos,

    It was an offline upgrade from DVD.

    Best regards,

    Gary

  6. #6

    Default Re: Unable to log in to graphical interface after upgrade from 12.3 to 13.1

    Quote Originally Posted by gogalthorp View Post
    Also what graphics card/chip?
    Hi Gogalthorp,

    The machine is a Dell Latitude E6530 with an Intel HD Graphics 4000 adapter (dual boots W7).

    Best regards,

    Gary

  7. #7
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: Unable to log in to graphical interface after upgrade from 12.3to 13.1

    On 2014-01-10 11:26, dn312sr wrote:

    > Hi Carlos,
    >
    > It was an offline upgrade from DVD.


    As the DVD is too small, it can not contain the entire OSS repository
    and the Offline System Upgrade procedure can not upgrade everything. You
    have to run after it completes, this:

    Code:
    zypper dup
    zypper up
    zypper patch
    Make sure you only have the 4 official repos active before running that.
    Then, verify:


    Code:
    rpm -q -a --queryformat "%{INSTALLTIME};%{INSTALLTIME:day}; \
    %{BUILDTIME:day}; %{NAME};%{VERSION}-%-7{RELEASE};%{arch}; \
    %{VENDOR};%{PACKAGER};%{DISTRIBUTION};%{DISTTAG}\n" \
    | sort | cut --fields="2-" --delimiter=\; \
    | tee rpmlist.csv | less -S
    
    or
    
    rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \
    %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \
    %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \
    | sort | cut --fields="2-" | tee rpmlist | less -S
    or

    rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \
    %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \
    %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \
    | sort | cut --fields="2-" | tee rpmlist \
    | egrep -v "openSUSE.12\.3" | less -S

    (not containing 12.3)



    With that query, you find listed at the top old packages that may have
    to be upgraded manually, because they belong to the previous release, or
    perhaps came from extra repositories and no equivalent was found in the
    active repos. In that case you have to start at this phase to add the
    needed extra repositories and update those packages.

    Many of them show in red in YaST,



    And after that, run "rcrpmconfigcheck" and verify the resulting list of
    config files. I suggest backing up both the active and the old/new file
    somewhere, and then edit both with "meld". Choose what to keep or not of
    the config.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 12.3 x86_64 "Dartmouth" at Telcontar)

  8. #8

    Default Re: Unable to log in to graphical interface after upgrade from 12.3 to 13.1

    Hi,

    I am replying to this thread to track - i installed as an upgrade from the internet using zypper to v3.1 and the application were not stable for KDE.

    I have a Dell Inspiron 660s - with Intel graphics - so i think as per other posts regarding stability - there is an Intel driver issue.

    Regards,

    Shadders.

  9. #9

    Default Re: Unable to log in to graphical interface after upgrade from 12.3to 13.1

    Quote Originally Posted by robin_listas View Post
    On 2014-01-10 11:26, dn312sr wrote:
    As the DVD is too small, it can not contain the entire OSS repository
    and the Offline System Upgrade procedure can not upgrade everything. You
    have to run after it completes, this:

    Code:
    zypper dup
    zypper up
    zypper patch
    Make sure you only have the 4 official repos active before running that.
    I guess the official repos are on the Internet?

    Internet access will be difficult with this machine.
    Is it possible to download the repositories I need, then do it all from a USB memory stick?

    Many thanks,

    Gary

  10. #10
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: Unable to log in to graphical interface after upgrade from 12.3to 13.1

    On 2014-01-13 14:06, dn312sr wrote:
    >
    > robin_listas;2614883 Wrote:
    >> On 2014-01-10 11:26, dn312sr wrote:
    >> As the DVD is too small, it can not contain the entire OSS repository
    >> and the Offline System Upgrade procedure can not upgrade everything. You
    >> have to run after it completes, this:
    >>
    >>>

    > Code:
    > --------------------
    > > >

    > > zypper dup
    > > zypper up
    > > zypper patch
    > >

    > --------------------
    >>>

    >>
    >> Make sure you only have the 4 official repos active before running
    >> that.


    > I guess the official repos are on the Internet?


    Yes, of course.


    > Internet access will be difficult with this machine.


    Oh :-(

    That's very unfortunate.

    > Is it possible to download the repositories I need, then do it all from
    > a USB memory stick?


    Well, yes, it is possible... but those repos are quite large. Hold on....


    Ok, I connected to "ftp://ftp5.gwdg.de/pub/opensuse/" with midnight
    commander, marked all files to find out the total sizes, and the results
    are:

    (64 bit only data)

    Code:
    oss
    x86_64:	6,791,349K bytes in 11790 files
    noarch:       8,918,625K bytes in 9580 files
    
    non.oss:
    x86_64:     56,519,067 bytes in 23 files
    noarch:    103,076,075 bytes in 13 files
    
    update:
    x86_64:   1,680,969K bytes in 2668 files
    noarch:   1,449,114K bytes in 849 files
    nosrc:       534,605 bytes in 1 file
    
    update-non-oss:
    x86_64:   27,502,685 bytes in 21 files
    nosrc:    flash-player-11.2.202.332-22.1.nosrc.rpm
    noarch:   does not exist.
    (plus the small repodata directories on each one)

    So you see, the sizes needed are quite large. Not huge, but large
    enough; and you need all of them to be sure, because you do not know in
    advance what you really need.




    There is another route, though. You can run this query:


    Code:
    rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \
    %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \
    %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \
    | sort | cut --fields="2-" | tee rpmlist | less -S
    which lists all the installed packages, sorted by installation date. you
    have to look at the lines at the top, but they can be hundreds. You have
    to take down the list of packages that say they belong to the previous
    version, then manually download the corresponding new version on another
    computer, and finally update them using the rpm command on the target
    computer.

    This may need several iterations if you do mistakes or if the packages
    have dependencies that you have not downloaded yet.

    In fact, you can add a local directory as repository to yast, instead of
    the internet repos you can't access, and use yast to install those.
    Doing this will make it easier to handle dependencies than plain rpm,
    but still, if those packages needed on the local dir, dependencies can
    not be satisfied...


    --
    Cheers / Saludos,

    Carlos E. R.
    (from 12.3 x86_64 "Dartmouth" at Telcontar)

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •