Announcement

Collapse
No announcement yet.

Deleted 24gb ./xsession-errors file in home, now stuck at login :(

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

    Deleted 24gb ./xsession-errors file in home, now stuck at login :(

    Hi i Deleted a huge 24gb ./xsession-errors file in home and am now now stuck at login . I type my pass and click to log in then it goes back to the log in screen.

    Although i can log in via the command prompt (but i need my GUI!).

    Please help, i researched deleting this file on forums, i gathered it was safe to do so .

    Any thoughts?

    #2
    Re: Deleted 24gb ./xsession-errors file in home, now stuck at login

    it is safe to delete .xsession-errors.
    you must have a problem elsewhere.
    log in from a tty (command prompt, as you call it), then enter:
    Code:
    startx
    see what it says...
    hth
    gnu/linux is not windoze

    Comment


      #3
      Re: Deleted 24gb ./xsession-errors file in home, now stuck at login

      the XKEYBOARD keymap controller (xkbcomp) reports a 'bad length in compatMap' error.

      plus this error"

      (EE) intel(0): IB830 Vblank Pipe Setup failed 0
      (EE) intel(0): IB830 Vblank Pipe Setup failed 0
      (EE) intel(0): IB830 Vblank Pipe Setup failed 0

      FreeFontPath: FPE "/usr/share/fonts/X11/misc" refcount is 2, should be 1; fixing"

      Comment


        #4
        Re: Deleted 24gb ./xsession-errors file in home, now stuck at login

        looks like a driver issue to me.
        we need a few things, i guess:
        - the details of your graphics card (brand and model)
        - what kind of setup you have (single/dual monitor, ...)
        - the content of your /etc/X11/xorg.conf file

        EDIT:
        and the output of the lspci command.
        gnu/linux is not windoze

        Comment


          #5
          Re: Deleted 24gb ./xsession-errors file in home, now stuck at login

          As already mentioned, .xsession-errors is just a log file, so removing it is not causing your issues (the fact that it was 24gb, seems to suggest a vocal error filling up the log file).

          I concur with jankushka, probably a problem with the intel video driver, so the information requested are likely to help solving the problem. In the mean time, you may find some help by googling with the error:
          "(EE) intel(0):" "Vblank Pipe Setup failed 0"
          or with something like:
          intel xorg "vblank pipe setup failed"

          Comment


            #6
            Re: Deleted 24gb ./xsession-errors file in home, now stuck at login

            OK i found out that the problem was most likey caused by lack of disk space.

            I found the recyle bin and deleted xsessions-errors from there. Now i have disk space.

            Trouble is now after loging in, i get the desktop wallpaper and a command prompt

            nothing else.

            Tried $ sudo dpkg-reconfigure kdm-desktop

            no change .

            Comment


              #7
              Re: Deleted 24gb ./xsession-errors file in home, now stuck at login

              <<<UPDATE>>>

              i managed to get back onto the desktop, after i changed a few settings on the login page after the kde reconfigure.

              however the war is not over.

              xsession-errors is growing again .

              every minute it gets a gig larger?

              that gives me 20 minutes.

              Comment


                #8
                Re: Deleted 24gb ./xsession-errors file in home, now stuck at login

                It is probably repeating the same message over and over. It would help to see what that message is.

                Comment


                  #9
                  Re: Deleted 24gb ./xsession-errors file in home, now stuck at login

                  it's the first time i see .xsession-errors growing so much and so rapidly.
                  it has to be something macroscopic.
                  yeah, it would help to see what that log file says.
                  you could run the following command:
                  Code:
                  tail -1111 .xsession-errors > /tmp/xxx
                  then post /tmp/xxx as an attachment here.
                  gnu/linux is not windoze

                  Comment


                    #10
                    Re: Deleted 24gb ./xsession-errors file in home, now stuck at login

                    tail Xsession: X session started for daniel at Tue May 19 16:04:58 BST 2009
                    startkde: Starting up...
                    startkde: kpersonalizer not found! Please install to properly configure your user.
                    kbuildsycoca running...
                    *** attempt to put segment in horiz list twice
                    kbuildsycoca running...
                    Reusing existing ksycoca
                    Ignored duplicate item: KArm
                    Ignored duplicate item: KDE Groupware Wizard
                    Ignored duplicate item: KNotes
                    Ignored duplicate item: Kontact
                    Ignored duplicate item: KDE Groupware Wizard
                    Ignored duplicate item: Strigi
                    Could not find 'guidance-power-manager.py' executable.
                    kdecore (KProcess): WARNING: _attachPty() 13
                    kdecore (KAction): WARNING: KAction::insertKAccel( kaccel = 0x80d3d70 ): KAccel object already contains an action name "file_quit"
                    kdecore (KAction): WARNING: KAction::insertKAccel( kaccel = 0x80d3d70 ): KAccel object already contains an action name "file_quit"
                    kdecore (KProcess): WARNING: _attachPty() 11
                    konsole: WARNING: Unable to use /usr/share/apps/konsole/mc.desktop
                    konsole: WARNING: Unable to use /usr/share/apps/konsole/sumc.desktop


                    head:
                    Xsession: X session started for daniel at Tue May 19 16:04:58 BST 2009
                    startkde: Starting up...
                    startkde: kpersonalizer not found! Please install to properly configure your user.
                    kbuildsycoca running...
                    *** attempt to put segment in horiz list twice
                    kbuildsycoca running...
                    Reusing existing ksycoca
                    Ignored duplicate item: KArm
                    Ignored duplicate item: KDE Groupware Wizard
                    Ignored duplicate item: KNotes
                    Ignored duplicate item: Kontact
                    Ignored duplicate item: KDE Groupware Wizard
                    Ignored duplicate item: Strigi
                    Could not find 'guidance-power-manager.py' executable.
                    kdecore (KProcess): WARNING: _attachPty() 13
                    kdecore (KAction): WARNING: KAction::insertKAccel( kaccel = 0x80d3d70 ): KAccel object already contains an action name "file_quit"
                    kdecore (KAction): WARNING: KAction::insertKAccel( kaccel = 0x80d3d70 ): KAccel object already contains an action name "file_quit"
                    kdecore (KProcess): WARNING: _attachPty() 11
                    konsole: WARNING: Unable to use /usr/share/apps/konsole/mc.desktop
                    konsole: WARNING: Unable to use /usr/share/apps/konsole/sumc.desktop
                    X Error: BadWindow (invalid Window parameter) 3
                    Major opcode: 19
                    Minor opcode: 0
                    Resource id: 0x18000a6



                    ----------------

                    Note the problem may be now complicated by me using dpkg-reconfigure kdm

                    Comment


                      #11
                      Re: Deleted 24gb ./xsession-errors file in home, now stuck at login

                      This looks to me like you have multiple attempts to configure KDE, like maybe you have remnants of an older system in a newer system. Are you using 7.10? Have you recently upgraded KDE? X? Have you possibly installed KDE4 on a system where ~/.kde was set for KDE 3.5?

                      Comment


                        #12
                        Re: Deleted 24gb ./xsession-errors file in home, now stuck at login

                        how would i check? Ive been installing alot of stuff recently, obviously as my above post states i used dpkg-reconfigure kdm, but the problem existed before this.

                        Comment


                          #13
                          Re: Deleted 24gb ./xsession-errors file in home, now stuck at login

                          A couple of things you should check to know what your situation is.
                          Code:
                          cat /etc/issue
                          will show you which release you are running. Look in the file /etc/apt/sources.list to see which release is referred to in your sources. If /etc/issue refers to Gutsy and sources.list refer to hardy you are probably in the middle of an upgrade.

                          You probably should upgrade to Hardy at least, but in any case you need to make sure your system has a consistent set of software, which means running
                          Code:
                          sudo aptitude update
                          and
                          Code:
                          sudo aptitude -f full-upgrade
                          until you do.

                          The problem of the growing .xsession-errors file can probably be solved by moving your .kde directory to something else. After you do that a new one will be created when you login again. Something like. logout.
                          Code:
                          Ctl-Alt-F1
                          login at a terminal
                          Code:
                          mv .kde bad.kde
                          Alt-F7
                          Login.

                          At that point you will have tested whether or not the problem is in your .kde directory. If that fixed it then you can start moving your customizations back into .kde, or recreating them from the GUI, and watch to see if the problem comes back.

                          Even if this is fixed you should update your software and make sure it is in a consistent state.

                          Comment

                          Working...
                          X