Error during 1-st start: No Exec in session file [SOLVED]

All Gurus once were Newbies
Forum rules
There are no such things as "stupid" questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Please stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions prefer the other forums within the support section.
Before you post please read this

Error during 1-st start: No Exec in session file [SOLVED]

Postby drvlas on Mon Jan 13, 2014 5:30 am

Hi everybody!

I'm a newbie in Linux. Installed Linux Mint Cinnamone 16 64 bit (full). During the startup I have a subj message (don't know the exact translation, my system writes in Ukrainian and I lack PC-Linux terminology) and starts a safemode session.
Afterwards there was a msg that I should solve the problem. So I'm afraid to do anything, to install programs and study Mint.

Please tell me what error is to be repaired and in what a way. In accordance with my zero level, for God's sake!
Thanks!
Last edited by drvlas on Mon Jan 13, 2014 6:48 pm, edited 1 time in total.
drvlas
Level 1
Level 1
 
Posts: 4
Joined: Mon Jan 13, 2014 2:44 am

Linux Mint is funded by ads and donations.
 

Additional info: sys log file

Postby drvlas on Mon Jan 13, 2014 7:59 am

I've guessed that some additional info would be useful.
So here is /var/log/syslog in attachment. At the 261-st line you can find WARNING in Ukrainian. That is the one I'm thinking about

...Well, what extention IS allowed? Aha, RAR. I post here a short seemingly relevant section of the file. The warning is in it. It goes as: Missing line Exec in session file: ubuntu. Starting a safemode session GNOME

Code: Select all
Jan 13 07:30:59 drvlas-desktop NetworkManager[875]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
Jan 13 07:30:59 drvlas-desktop NetworkManager[875]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
Jan 13 07:30:59 drvlas-desktop kernel: [   11.525368] e1000e 0000:00:19.0: irq 47 for MSI/MSI-X
Jan 13 07:30:59 drvlas-desktop kernel: [   11.525455] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jan 13 07:30:59 drvlas-desktop kernel: [   11.525651] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jan 13 07:30:59 drvlas-desktop acpid: client connected from 1257[0:0]
Jan 13 07:30:59 drvlas-desktop acpid: 1 client rule loaded
Jan 13 07:30:59 drvlas-desktop acpid: client connected from 1257[0:0]
Jan 13 07:30:59 drvlas-desktop acpid: 1 client rule loaded
Jan 13 07:30:59 drvlas-desktop mdm[1247]: GLib-CRITICAL: g_key_file_get_string: assertion 'key_file != NULL' failed
Jan 13 07:30:59 drvlas-desktop mdm[1247]: GLib-CRITICAL: g_key_file_free: assertion 'key_file != NULL' failed
Jan 13 07:30:59 drvlas-desktop mdm[1247]: GLib-CRITICAL: g_key_file_free: assertion 'key_file != NULL' failed
Jan 13 07:30:59 drvlas-desktop dbus[773]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper)
Jan 13 07:30:59 drvlas-desktop dbus[773]: [system] Successfully activated service 'org.freedesktop.ConsoleKit'
Jan 13 07:30:59 drvlas-desktop mdm[1337]: WARNING: session_child_run: Відсутній рядок Exec у файлі сеансу: ubuntu.  Запускається безпечний сеанс GNOME.
Jan 13 07:30:59 drvlas-desktop mdm[1342]: Gtk-WARNING: Ignoring the separator setting
Jan 13 07:31:00 drvlas-desktop NetworkManager[875]: <info> (eth0): carrier now ON (device state 20)
Jan 13 07:31:00 drvlas-desktop NetworkManager[875]: <info> (eth0): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
Attachments
LinuxMint_Error_Startup_20130113.log.rar
(8.8 KiB) Downloaded 16 times
drvlas
Level 1
Level 1
 
Posts: 4
Joined: Mon Jan 13, 2014 2:44 am

The solution

Postby drvlas on Mon Jan 13, 2014 6:47 pm

drvlas wrote:So here is /var/log/syslog in attachment. At the 261-st line

It seems that the problem emerges when MDM is launched. So I decided to install LightDM instead MDM - and it solved my problem.
drvlas
Level 1
Level 1
 
Posts: 4
Joined: Mon Jan 13, 2014 2:44 am

Re: Error during 1-st start: No Exec in session file [SOLVED

Postby clem on Fri Sep 26, 2014 4:56 am

The problem is quite simple:

- By default MDM selects your last used session
- Say your last session was GNOME or Unity and you kept your home directory intact... well, your .dmrc is still telling MDM to choose the gnome or the ubuntu session.

The solution is quite simple too:

- In the greeter (i.e. the login screen), click on the session button (usually beside the language flag) and choose a valid session.. Cinnamon, MATE, Xfce, KDE.. whatever's installed.

If you can't find that button, drop to console, remove your ~/.dmrc file and restart the computer (or the MDM service).
Image
User avatar
clem
Level 15
Level 15
 
Posts: 5553
Joined: Wed Nov 15, 2006 8:34 am

Re: Error during 1-st start: No Exec in session file [SOLVED

Postby clem on Fri Sep 26, 2014 5:03 am

From a dev. point of view, note also that we understand the situation can be confusing and we'll take action in MDM 1.8 to automatically resolve it.
Image
User avatar
clem
Level 15
Level 15
 
Posts: 5553
Joined: Wed Nov 15, 2006 8:34 am

Re: Error during 1-st start: No Exec in session file [SOLVED

Postby clem on Fri Sep 26, 2014 5:30 am

Image
User avatar
clem
Level 15
Level 15
 
Posts: 5553
Joined: Wed Nov 15, 2006 8:34 am

Re: Error during 1-st start: No Exec in session file [SOLVED

Postby PatH57 on Fri Sep 26, 2014 5:40 am

/* Ugly workaround for migration */


love the honest statement :lol:
People disagree with me. I just ignore them.
(Linus Torvalds, regarding the use of C++ for the Linux kernel.)

Please Add [Solved] to the topic-title of your first post when appropriate so others know they might find a solution here.
User avatar
PatH57
Level 13
Level 13
 
Posts: 4603
Joined: Tue Mar 25, 2014 12:11 pm
Location: here and there

Linux Mint is funded by ads and donations.
 

Return to Newbie Questions

Who is online

Users browsing this forum: Bing [Bot], Hecubus and 23 guests