This forum has been archived. All content is frozen. Please use KDE Discuss instead.

KDE Neon in emergency mode [solved]

Tags: None
(comma "," separated)
duns
Registered Member
Posts
78
Karma
0
OS

KDE Neon in emergency mode [solved]

Mon Nov 20, 2017 4:20 pm
Today emergency mode.
I tried from other so (pclos) this command, but it seems all ok
Code: Select all
[root@linux duns]# e2fsck -C0 -p -f -v /dev/sdb10
                                                                               
      308196 inodes used (14.64%, out of 2105344)
         250 non-contiguous files (0.1%)
         274 non-contiguous directories (0.1%)
             # of inodes with ind/dind/tind blocks: 0/0/0
             Extent depth histogram: 272255/58
     3202003 blocks used (38.10%, out of 8404992)
           0 bad blocks
           1 large file

      244129 regular files
       26911 directories
         109 character device files
          50 block device files
           0 fifos
          15 links
       36988 symbolic links (35716 fast symbolic links)
           0 sockets
------------
      308202 files
 


Looking at .xsession-errors I found that:
Code: Select all
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
startkde: Done.
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
bluedevil: Destroyed
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
QThread: Destroyed while thread is still running
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
KCrash: Attempting to start /usr/bin/kdeinit5 from kdeinit
Warning: connect() failed: : No such file or directory
KCrash: Attempting to start /usr/bin/kdeinit5 directly
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kdeinit5 path = /usr/bin pid = 1834
KCrash: Arguments: /usr/bin/kdeinit5
kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/libexec/kf5/klauncher'
kdeinit5: Launched KLauncher, pid = 5210, result = 0
QXcbConnection: Could not connect to display :0
kdeinit5: Communication error with launcher. Exiting!


I can "startx" as root (I have desktop grafic as root), but I cannot login as user (duns). If I type "exit" from textual screen, I get an error (something as "jobs still opened" or something similar, I don't remeber exactly)

In /tmp folder there is not any file (no "xauth-1000" and similar)

Can you help me?

Last edited by duns on Mon Nov 20, 2017 6:37 pm, edited 1 time in total.
gfielding
Registered Member
Posts
178
Karma
0
OS

Re: KDE Neon in emergency mode

Mon Nov 20, 2017 4:53 pm
If you can log in as root, try creating a new user. Then try the new user to log in.
duns
Registered Member
Posts
78
Karma
0
OS
Solved: the problem was a ntfs partition; now I commented in fstab, and I can login as user in the grafical desktop.
Thank you

p.s.
remain the problem of frequent crashes https://forum.kde.org/viewtopic.php?f=309&t=142937


Bookmarks



Who is online

Registered users: Bing [Bot], Evergrowing, Google [Bot], q.ignora, watchstar