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

Thread: KDE 4.7 Serious Issue

  1. #1

    Default KDE 4.7 Serious Issue

    So I just installed KDE 4.7 via the 1-click installer while I still had the default openSUSE KDE that comes packed with 11.4 installed. I figured the installer would just update from the old one, but I guess I was wrong. There were a ton of dependency issues along the way, butI thought I resolved them (I picked everything that installed over the old files, uninstalled the old files, or installed new things). At the end I got an error that said the installation was partially successful, and that kdebase or kdebase4.7 (I don't remember exactly and can't check now) could not be installed.

    Nothing had changed on my desktop so I logged out to log back in, and bam! No more GUI. Okay, that was predictable, I probably just messed something up installing it. I was going to navigate to the 1-click installer file and run it from the command line to fix my problems as the dependency issues would likely no longer be there, but I didn't know the command to run one, so before I restarted and booted into Windows to check I decided to try to just sudo zypper install the kde package I was missing. I was using search to try to find the package and then suddenly my internet cut out.

    I restarted my computer to see if the internet would be back on, and then when I started openSUSE there was nothing but an odd grey box in the center asking for my username, a very primitive console in the bottom left, and openSUSE written in bland writing in the background. I tried to log in, but when I do, the screen flashes to a console and text whizzes by too fast to see, and it goes back to the login page. It's not a wrong log in, because if I type something other than my own or root and root's password, it says login incorrect.

    Does anybody know how to fix this other than by reinstalling openSUSE? I'd much rather not do that. If I can access the command line I think I can just run the 1-click installed because I've since looked up the command, but I can't think of a way to do it. I also tried the failsafe boot and it does not work either.

  2. #2
    Join Date
    Jun 2008
    Location
    The English Lake District. UK - GMT/BST
    Posts
    36,729
    Blog Entries
    20

    Default Re: KDE 4.7 Serious Issue

    If you are hard wired, you could boot to level 3 and start yast from there
    Boot to Level 3, then Yast and More....

    You can work on your packaging from there.

    But, when you had:
    There were a ton of dependency issues along the way, butI thought I resolved them
    Your best approach would have been to ask here first, rather than guess.
    Leap 15.1_KDE
    My Articles Was I any help? If yes: Click the star below

  3. #3
    Join Date
    Jun 2008
    Location
    Earth - Denmark
    Posts
    10,730

    Default Re: KDE 4.7 Serious Issue

    On 07/29/2011 03:36 AM, laplacian13 wrote:
    >
    > Does anybody know how to fix this other than by reinstalling openSUSE?


    the easiest way would be to restore from the pre-upgrade system backup..

    --
    DD
    Caveat-Hardware-Software
    openSUSE®, the "German Engineered Automobiles" of operating systems!

  4. #4
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    24,973

    Default Re: KDE 4.7 Serious Issue

    Quote Originally Posted by DenverD View Post
    On 07/29/2011 03:36 AM, laplacian13 wrote:
    >
    > Does anybody know how to fix this other than by reinstalling openSUSE?


    the easiest way would be to restore from the pre-upgrade system backup..

    --
    DD
    Caveat-Hardware-Software
    openSUSE®, the "German Engineered Automobiles" of operating systems!
    Isn't that the same thing?
    Henk van Velden

  5. #5
    Join Date
    Jun 2008
    Location
    Delta Quadrant
    Posts
    1,442

    Default Re: KDE 4.7 Serious Issue

    At the grey box login try doing a Control+ALT+F1 and see if you can access
    TTY1 which is the console.



  6. #6

    Default Re: KDE 4.7 Serious Issue

    Quote Originally Posted by caf4926 View Post
    If you are hard wired, you could boot to level 3 and start yast from there
    Boot to Level 3, then Yast and More....

    You can work on your packaging from there.

    But, when you had: Your best approach would have been to ask here first, rather than guess.
    Yeah, I know I should have asked here first, but linux is about learning, right? No way to learn better than to really **** up

    Anyways, what do you mean by hard wired? I'm still new to all this stuff. I installed it alongside windows off the DVD I burned and had it shrink the windows partition, I'm not sure if that makes me hard wired or not. Otherwise, I'll check that link out and definitely give it a shot. Would I just go into YaST and just look for all the kde 4.6 files and install them over my 4.7? Or should I try to find the 4.7 files I'm missing? I'm not sure what would be the better approach.

    the easiest way would be to restore from the pre-upgrade system backup..
    Does it automatically back up my system when I do a 1-click installer like that? I've never heard of that, and I didn't back up my system beforehand. I know it's really stupid, but I'm generally too lazy and just hope for the best. Sometimes it works and I save the time I would have wasted backing up, sometimes I wreck my computer like now, it's a trade off

    At the grey box login try doing a Control+ALT+F1 and see if you can access
    TTY1 which is the console.
    So if I'm able to do this, and assuming that I didn't cause some other problem with openSUSE by messing up the install, if I were to just run the 1-click 4.7 installer through the command line do you think it would install everything properly? I would imagine the dependency issues would be gone because the files it was conflicting with are now deleted, but I'm a noob and really don't know how it would turn out.


    Anyways, thanks for the help everybody, once these two above questions I'll give all this a shot and let you guys know how it goes. Hopefully I'll have 4.7 up and running some time this weekend.

  7. #7
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    24,973

    Default Re: KDE 4.7 Serious Issue

    I didn't back up my system beforehand.
    That is what we were pointing to. If you think that doing all sorts of things with your system will teach you (which it will), one of the first things you will learn is to have a good backup schema in general and backup extra when going for trials and testing.
    Henk van Velden

  8. #8
    Join Date
    Jun 2008
    Location
    The English Lake District. UK - GMT/BST
    Posts
    36,729
    Blog Entries
    20

    Default Re: KDE 4.7 Serious Issue

    Hardwired means a ethernet cable as opposed to wireless
    Leap 15.1_KDE
    My Articles Was I any help? If yes: Click the star below

  9. #9

    Default Re: KDE 4.7 Serious Issue

    What does "zypper -v dup" have to say? Presumbably he's got a repo added and there's a chance it'll finish installing what's needed?

  10. #10

    Default Re: KDE 4.7 Serious Issue

    Here's the update - I got into the terminal using cntrl+alt+f1 and was able to do some stuff from there. Running the one-click didn't fix it, but I edited my repositories so that all I had was the defaults, packman, and kde47. I did a sudo zypper -v dup, everything for kde 4.7 installed successfully, but nothing changed. I checked my display manager settings in yast and it was set to kdm. I tried setting it to kdm4, but it still didn't work.

    Seeing as kde 4.7 didn't work, I removed the kde47 repository and did another sudo zypper -v dup. As expected, this downgraded everything to kde 4.6. Same problem persist, though. I have kde 4.6 installed fine, both kdm and kdm4 settings for display manager don't change anything. Am I missing something here? If it's installed and set to run, shouldn't it work?

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
  •