[SOLVED] cannot login to GNOME classic - "Oh No..."

[doktor5000]

Hey,

I attempted to use the Gnome Classic instead of the default Gnome and got this

"Oh No, Something has gone wrong!
A problem has occurred and the system can not
recover.:
Please log out and try again."


Why do you think I would get this Message each time I try to use Gnome Classic, and is there a workaround? I get the same results, so far, when I log out and try again.

Anyone else have this issue?

kadmus

[doktor5000]

What Mageia release do you use, and what graphics card and graphics driver do you use?
Please show the output of

Code: Select all

grep -i driver /var/log/Xorg.0.log
lspcidrake -v | grep VGA

[isadora]

Hey doktor5000,

I'm running Mageia 5. Here is what I came up with on those two commands:

Code: Select all

[billymo67@localhost ~]$     grep -i driver /var/log/Xorg.0.log
[    18.237]    X.Org Video Driver: 18.0
[    18.237]    X.Org XInput driver : 21.0
[    18.294] (II) Loading /usr/lib64/xorg/modules/drivers/v4l_drv.so
[    18.317]    ABI class: X.Org Video Driver, version 18.0
[    19.388]    Module class: X.Org Video Driver
[    19.407] (II) v4l driver for Video4Linux
[    19.408] (II) NVIDIA dlloader X Driver  304.125  Mon Dec  1 20:00:30 PST 2014
[    19.408] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[    20.954] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
[    21.524]    Module class: X.Org XInput Driver
[    21.524]    ABI class: X.Org XInput driver, version 21.0
[    21.524] (II) Using input driver 'evdev' for 'Power Button'
[    21.571] (II) Using input driver 'evdev' for 'Power Button'
[    21.573] (II) No input driver specified, ignoring this device.
[    21.574] (II) No input driver specified, ignoring this device.
[    21.574] (II) No input driver specified, ignoring this device.
[    21.575] (II) No input driver specified, ignoring this device.
[    21.576] (II) No input driver specified, ignoring this device.
[    21.577] (II) No input driver specified, ignoring this device.
[    21.578] (II) Using input driver 'evdev' for 'Logitech M510'
[    21.591] (II) No input driver specified, ignoring this device.
[    21.592] (II) Using input driver 'evdev' for 'Logitech K350'
[    21.595] (II) Using input driver 'evdev' for 'HD Webcam C525

t ~]$ lspcidrake -v | grep VGA
Card:NVIDIA GeForce 6100 to GeForce 7950: NVIDIA Corporation|G72 [GeForce 7300 LE] [DISPLAY_VGA] (vendor:10de device:01d1 subv:1028 subd:0405) (rev: a1)
[billymo67@localhost ~]$

[doktor5000]

Okay, so you're using the nvidia proprietary driver, should be fine.

When you login to gnome classic mode, and you get the "oh no..." message,
please switch to another tty via Ctrl+Alt+F2 to F8 and run the following command as root

Code: Select all

journalctl -ab | tail -150

and please post the output here.

[Kadmus]

Hey,

Did what you said, entered the line; 'journalctl -ab | tail -150', and pressed enter. Here is where a previous issue comes up and bites me. It does not accept my root password. In spite of my doing a complete reinstall of my Mageia. For couple of dayis the root password was accepted, and now???

I'll have to find the other post and....

8/2/15 06:45 AM

When I set my Mageia to use Gnome Classic and the "Oh No" message cam on the screen, I pressed 'Ctrl+Alt+F2 a terminal like screen opens up with:

“Mageia release 5 (Official) for x86_64
Kernel 3.19.8 – Desktop-3 mga5 on a Dual processor x86_64 / ttty2
local host login:”

I then entered 'journalcti -ab | tail -150 'and press Enter, which brings up a request for a password. I enter my Root password whereupon it tells me it is incorrect. I repeat the procedure a few more time getting the same results.

Fianlly, I press Alt+F1, which brings me back to the “Oh No” screen. I 'log out' and return to the Login Screen, I untick the spot next to Gnome Classic and 'tick' next to Gnome then proceed with a normal login.

When it did not accept my Root password I assumed it was because of the same issue I experienced before; 'Root password not accepted as Administrator' This assumption was further fueled when I tried to open the Mageia Control Center (MCC) which would not open.

I looked in the other thraed for a solution but did not implement it, rather I clicked the power icon in the upper right op the Monitor screen. A new window opens and I press the 'power icon' here I select 'restart' and it asks for my Administrator password which I enter and it is accepted and I 'reboot' to one of the other distros I have on my PC.

It dawns on e that if my Root/Administrator Password was not accepted when I was doing the 'journalctl' thing, it should not have accepted it when I logged out, but it did. Lates\r, a few hours, when I rebooted into Mageia and subsequently logged in regularly. I opened 'Activities' and scrolled down to the Mageia Control Center icon and left clicked on it, it opens a new window informing me I need to enter the Administrator password, or words to that effect. I enter the password and the MCC opens.

I wanted to get the 'wording correct' so I opened 'Activities' scrolled down to the MCC icon, left clicked and it did not open. This has happened before. Chances are if I reboot and come straight back to Mageia the MCC may open? If it does open there is a probability that later it will not open.

Wec come back to the question as to 'Why' did I not get any further than a request for a password with the 'journalcti' business, doktor5000 what did you expect me to find, if anything?

kadmus

[wintpe]

please accept my apologies if im getting this wrong, but the way i read your description, the system askes

local host login:
to which you reply journalcti -ab | tail -150
and then wonder why it wont accept your root password.

probably because there is no user named "journalcti -ab | tail -150"

perhaps at the

local host login:
reply->

root

followed by the root password.

then at the prompt
enter

journalcti -ab | tail -150

and referring to your previous issue, there is no user administrator in the unix/linux world, unless you create it.

that user would then be equivalent to every other non administrator user, unless you took steps to make it root.

there is only one administrator in the unix /linux world and thats the user "root" and yes thats confusing when we also refer to the root file system.
but they are all related.

regards peter

[Kadmus]

As mentioned at the start of tis thread, I was wondering why I was receiving the “Oh No, Something has gone Wrong” message each time I tried to use Gnome Classic. To find a possible reason why I get the Error message. I was asked upon receiving said message to enter 'Ctrl+Alt+F2' and which point I was to type, 'journlctl -ab | tail -150' and report what I saw.
Seeing no other place to put 'journalctl -ab | tail -150' I placed it in the most logical, to me, place 'local host login. As it asked for a password and since I figured it wanted my Root password so that is what I entered. I pressed the Enter key because it seemed the right thing to do.

If I want to open the Mageia Control Center, for example, it tells me:
“Authentication Required. Authentication is required to run Mageia Control Center GUI
Administrator
Password.”

Since the password to open this is my Root password it only made sense to equate Administrator/Password together, since whenever I see 'Administrator' it invariably asks for my 'root' password.
The question still remains, why can I not use Gnome Classic instead of Gnome 3.xxx or whatever? If there is a solution. I would be more than happy to hear of it?

[doktor5000]

Peter explained, when you press Ctrl+Alt+F2 you need to login first. Enter a user name, press enter and then enter your password and press enter.
Thought that was basic knowledge but was proven wrong - sorry for the omitment -.-

The question still remains, why can I not use Gnome Classic instead of Gnome 3.xxx or whatever? If there is a solution. I would be more than happy to hear of it?

Sorry but if you don't provide those logs nobody can tell you why it does not start in your case.

[Kadmus]

Sheesh.... When I decide to utilize Mageia, the first thing I see is the ‘splash screen’ It is here where I login. It is here as you well know that a person can select which de (desktop environment) he’ll be using and in my for instance it is; ‘Gnome, Gnome Classic, IceM and Gnome in Wayland. It is only when I select any of the other ones that get the “Oh No, Something is Wrong” message, after I have signed into Mageia. It is at this point with the error message still on the screen that I press Ctrl+Alt+F2.

You told me to enter “Journalctl -ab | tail -150“ as root”. Where it says local host login, I enter ‘su’ (You or someone is going to tell me I got it wrong) I am asked for a password and I enter my root password and it promptly tell me it is incorrect. I go through the thing again enter ‘su’ then my root password being careful that I type each letter correctly and I still am informed it is incorrect.

It is at this point that I press Alt+F1 which takes me back to the Error Message; “Oh No. . .
If the message is grayed out, I may need to left click the mouse. I press the Enter key which opens the “Splash Screen” and I select ‘Gnome’ using the small cog wheel in the lower left corner. I proceed to enter my password and press Enter. That's it.

I am still no closer to finding out how I can use gnome classic instead of gnome?

A frustrated kadmus

[benmc]

Where it says local host login, I enter ‘su’

You usually cannot login as root,"su".
So you have to login at the prompt using first your normal user login identity and then you should be able to change to "root".

[doktor5000]

Where it says local host login, I enter ‘su’ (You or someone is going to tell me I got it wrong) I am asked for a password and I enter my root password and it promptly tell me it is incorrect. I go through the thing again enter ‘su’ then my root password being careful that I type each letter correctly and I still am informed it is incorrect.

Nobody said to enter "su" at that prompt. It asks for a username to login, and "su" is not a username, it's a command.

You should read again the previous post from Peter:

perhaps at the

local host login:
reply->

root

followed by the root password.

[wintpe]

I think that sometimes some of us take for granted how a unix/linux system works
and dont realize the uphill struggle some people who have learned to used computers
the microsoft way, go through when , from their perspective bravely step into the unix world.

and yes we as experienced admins have laughed at some of the mistakes, and sometimes cried...
spending weekends recovering systems from people who have made a fatal error.

Kadmus, keep at it, the linux/unix way is well worth the effort.

gets some books and read, from dummies guides, to google.

Unix takes an age to grasp, but it rewards the effort.

Unix is essentially a command line operating system with a choice of too many user interfaces bolted on.

the original unix did not even have that.

you logged in an the login prompt: usually as a user, did your work editing files, and system administrators who needed
superuser (or root, same thing) ran "su -" to switch user to root. root is assumed if no other username is given.

the root file system is permissioned such that nothing but root can change anything, and in some cases only root can read something (the shadow file for example that contains your encrypted password).

the window system start screen and login prompt is run by root, but everything in the running window system once you login is run by you.

so you cant do any root things without elevating your priverlages, and this is usualy by opening a terminal and typing su -.

when you run something like MCC the people who coded it added a startup dialog box that prompts you for the root password, and if its right starts up mcc as root, so you can change things.

not everything has this dialog box in front of it, so will only run as you.

and all users other than root are classified the same, ie the same level as the nobody user, unless steps are taken to change that.

I hope this little primer helps.

regards peter

[Kadmus]

Okay, I've got something? This time around when I am faced with the local login 'thing'. I enter my username and password. It is at this point, it accepted both, that I enter 'su' followed by my root password, which this time is accepted. I then enter, 'journalctl -ab | tail -150' Then the screen began scrolling until it finally came to what I will be attaching here. I uploaded the images to Photobucket and it is from theer I will be downloading the images, taken win my cell phone camera, so take into account the pictures are not perfect. I tried to remember the order in which they were taken. Also the images were taken from left to right. I can not guarantee te viewability of the pictures.

[wintpe]

nope they are not very viewable

add the following to the end of the command.

Code: Select all

|tee -a /var/tmp/journallog.txt


then upload that somewhere

regards

peter

[Kadmus]

Which command are you referring to?

[wintpe]

Code: Select all

journalctl -ab | tail -150|tee -a /var/tmp/filename.log


or any other output file.

ill explain what the command tee does.

it takes the input and passes it back out, so in that way looks like a transparent program.

so you still see the output, but it also takes a copy of that and writes it to the file, in append mode ( thats what the -a is for)

now upload that file somewhere, like pastbin and past it here.

if you are having trouble getting the file somewhere, try putting a usb stick in the computer.

just before you do, run fdisk -l and note what harddrives come up.

then just after you insert it try again.

see anything new.

lets assume its a device called /dev/sdh for now, might not be, thats for you to find out.

it should also show a partition type ntfs or fat on /dev/sdh1

if so run the following.

mkdir /usbstick

mount /dev/sdh1 /usbstick

cp /var/tmp/filename.log /usbstick

umount /usbstick


now try that usbstick in another computer, that you can work with.

regards peter

[Kadmus]

Hey;
I went through the procedure with the extra at the end of the command (journal..etc). It quickly scrolled down to its end, so all that was viewable is what is there. Again using my cellphone camera I took four shots The top two I believe on the left side of the monitor and the bottom two are on the right side of the monitor screen.. I used ImageShack and I believe it will prove a good choice.

[doktor5000]

Sorry to say, but the screenshots are barely readable and do only contain a part of the screen, they're not useful.
Either try a different desktop environment apart from gnome classic, or attach the log so we can see what's going on.

[Kadmus]

Just forget about the whole thing. I can use another DE, That is not the bloody point, it is why i can not use Gnome Classic if that is one I want to use today tomorrow or a week from next Thursday.

[doktor5000]

Then please attach the requested log excerpt, otherwise we cannot tell you - as we already tried to tell you 4 times.

[doktor5000]

Frustration can lead to new insight; or make you a bigger ass than you were before?

/var/tmp/kdecache-billymo67.log

Code: Select all

Aug 06 13:19:15 localhost /etc/X11/gdm/Xsession[2157]: Couldn't find a perfect decorator match; trying all decorators
Aug 06 13:19:15 localhost /etc/X11/gdm/Xsession[2157]: Starting gtk-window-decorator
Aug 06 13:19:15 localhost /etc/X11/gdm/Xsession[2157]: /usr/bin/gtk-window-decorator: Screen 0 on display ":0.0" already has a decoration manager; try using the --replace option to replace the current decoration manager.
Aug 06 13:19:15 localhost /etc/X11/gdm/Xsession[2157]: Window manager warning: Failed to load theme "Adwaita": Failed to find a valid file for theme Adwaita
Aug 06 13:19:15 localhost /etc/X11/gdm/Xsession[2157]: /usr/bin/gtk-window-decorator: Ignoring unknown or already-used button name "appmenu"
Aug 06 13:19:15 localhost org.a11y.Bus[2265]: Activating service name='org.a11y.atspi.Registry'
Aug 06 13:19:15 localhost org.a11y.Bus[2265]: Successfully activated service 'org.a11y.atspi.Registry'
Aug 06 13:19:15 localhost org.a11y.atspi.Registry[2328]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Aug 06 13:19:15 localhost org.a11y.atspi.Registry[2328]: Xlib:  extension "XEVIE" missing on display ":0".
Aug 06 13:19:16 localhost gnome-session[2157]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Aug 06 13:19:16 localhost gnome-session[2157]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Aug 06 13:19:16 localhost gnome-session[2157]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Aug 06 13:19:16 localhost gnome-session[2157]: GPG_AGENT_INFO=/run/user/1000/keyring/gpg:0:1
Aug 06 13:19:16 localhost gnome-session[2157]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Aug 06 13:19:16 localhost gnome-session[2157]: GPG_AGENT_INFO=/run/user/1000/keyring/gpg:0:1
Aug 06 13:19:16 localhost dbus[752]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Aug 06 13:19:16 localhost dbus[752]: [system] Activating via systemd: service name='org.freedesktop.NetworkManager' unit='dbus-org.freedesktop.NetworkManager.service'
Aug 06 13:19:16 localhost dbus[752]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.NetworkManager.service': Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory.
Aug 06 13:19:16 localhost dbus[752]: [system] Successfully activated service 'org.freedesktop.hostname1'
Aug 06 13:19:16 localhost gnome-session[2157]: (gnome-settings-daemon:2354): rfkill-plugin-WARNING **: Failed to acquire NetworkManager proxy: Error calling StartServiceByName for org.freedesktop.NetworkManager: GDBus.Error:org.freedesktop.systemd1.LoadFailed: Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory.
Aug 06 13:19:16 localhost colord[1588]: Profile added: icc-7924ad5d6d40102d2e64afd8ffb41baf
Aug 06 13:19:17 localhost dbus[752]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service'
Aug 06 13:19:17 localhost gdm-Xorg-:0[912]: (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (CRT-0)) does not support NVIDIA
Aug 06 13:19:17 localhost gdm-Xorg-:0[912]: (II) NVIDIA(GPU-0):     3D Vision stereo.
Aug 06 13:19:17 localhost gdm-Xorg-:0[912]: (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
Aug 06 13:19:17 localhost gdm-Xorg-:0[912]: (**) NVIDIA(0):     device Samsung SyncMaster (CRT-0) (Using EDID frequencies
Aug 06 13:19:17 localhost gdm-Xorg-:0[912]: (**) NVIDIA(0):     has been enabled on all display devices.)
Aug 06 13:19:17 localhost dbus[752]: [system] Successfully activated service 'org.freedesktop.locale1'
Aug 06 13:19:17 localhost gnome-session[2157]: Window manager warning: Screen 0 on display ":0" already has a window manager; try using the --replace option to replace the current window manager.
Aug 06 13:19:17 localhost kernel: gnome-shell[2366]: segfault at 18 ip 00007fcefa952da5 sp 00007ffe160db290 error 4 in libmutter.so.0.0.0[7fcefa8c6000+138000]
Aug 06 13:19:18 localhost gnome-session[2157]: gnome-session[2157]: WARNING: Application 'gnome-shell-classic.desktop' killed by signal 11
Aug 06 13:19:18 localhost gnome-session[2157]: WARNING: Application 'gnome-shell-classic.desktop' killed by signal 11
Aug 06 13:19:18 localhost gdm-Xorg-:0[912]: (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (CRT-0)) does not support NVIDIA
Aug 06 13:19:18 localhost gdm-Xorg-:0[912]: (II) NVIDIA(GPU-0):     3D Vision stereo.
Aug 06 13:19:18 localhost gdm-Xorg-:0[912]: (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
Aug 06 13:19:18 localhost gdm-Xorg-:0[912]: (**) NVIDIA(0):     device Samsung SyncMaster (CRT-0) (Using EDID frequencies
Aug 06 13:19:18 localhost gdm-Xorg-:0[912]: (**) NVIDIA(0):     has been enabled on all display devices.)
Aug 06 13:19:18 localhost gnome-session[2157]: (gnome-settings-daemon:2354): GLib-GIO-CRITICAL **: g_dbus_proxy_call_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed
Aug 06 13:19:19 localhost gnome-session[2157]: Window manager warning: Screen 0 on display ":0" already has a window manager; try using the --replace option to replace the current window manager.
Aug 06 13:19:19 localhost kernel: gnome-shell[2385]: segfault at 18 ip 00007ff37fe01da5 sp 00007ffeaa851620 error 4 in libmutter.so.0.0.0[7ff37fd75000+138000]
Aug 06 13:19:19 localhost gnome-session[2157]: gnome-session[2157]: WARNING: Application 'gnome-shell-classic.desktop' killed by signal 11
Aug 06 13:19:19 localhost gnome-session[2157]: WARNING: Application 'gnome-shell-classic.desktop' killed by signal 11
Aug 06 13:19:19 localhost gnome-session[2157]: WARNING: App 'gnome-shell-classic.desktop' respawning too quickly
Aug 06 13:19:19 localhost gnome-session[2157]: Unrecoverable failure in required component gnome-shell-classic.desktop
Aug 06 13:19:19 localhost gnome-session[2157]: gnome-session[2157]: WARNING: App 'gnome-shell-classic.desktop' respawning too quickly
Aug 06 13:19:19 localhost org.gtk.Private.AfcVolumeMonitor[2265]: Volume monitor alive
Aug 06 13:19:20 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:20 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:20 localhost gnome-session[2157]: (gnome-settings-daemon:2354): GLib-GIO-CRITICAL **: g_dbus_proxy_call_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed
Aug 06 13:19:20 localhost mgaapplet[2417]: ### Program is starting ###
Aug 06 13:19:20 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: failed to bind pixmap to texture
Aug 06 13:19:21 localhost net_applet[2430]: ### Program is starting ###
Aug 06 13:19:21 localhost gnome-session[2157]: Entering running state
Aug 06 13:19:21 localhost gnome-session[2157]: (uint32 2,)
Aug 06 13:19:21 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: failed to bind pixmap to texture
Aug 06 13:19:22 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: failed to bind pixmap to texture
Aug 06 13:19:22 localhost gnome-session[2157]: Failed to play sound: File or data not found
Aug 06 13:19:24 localhost org.gnome.OnlineAccounts[2265]: goa-daemon-Message: goa-daemon version 3.14.3 starting
Aug 06 13:19:25 localhost gnome-session[2157]: Subroutine Gtk3::main redefined at /usr/lib/perl5/vendor_perl/5.20.1/Gtk3.pm line 296.
Aug 06 13:19:25 localhost acpid[759]: client 912[0:0] has disconnected
Aug 06 13:19:25 localhost acpid[759]: client 912[0:0] has disconnected
Aug 06 13:19:25 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: failed to bind pixmap to texture
Aug 06 13:19:26 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: failed to bind pixmap to texture
Aug 06 13:19:26 localhost gnome-session[2157]: Subroutine Gtk3::main redefined at /usr/lib/perl5/vendor_perl/5.20.1/Gtk3.pm line 296.
Aug 06 13:19:27 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: failed to bind pixmap to texture
Aug 06 13:19:27 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: failed to bind pixmap to texture
Aug 06 13:19:28 localhost gnome-session[2157]: Ignore the following Glib::Object::Introspection & Gtk3 warnings
Aug 06 13:19:29 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: failed to bind pixmap to texture
Aug 06 13:19:29 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:29 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:29 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:30 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:30 localhost gnome-session[2157]: (tracker-extract:2431): Tracker-WARNING **: Call to gst_discoverer_discover_uri() failed: Your GStreamer installation is missing a plug-in.
Aug 06 13:19:30 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:30 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:30 localhost gnome-session[2157]: (tracker-extract:2431): Tracker-WARNING **: Task for 'file:///home/billymo67/Pictures/Object%20in%20night%20sky.%20d.xcf' finished with error: Could not get any metadata for uri:'file:///home/billymo67/Pictures/Object%20in%20night%20sky.%20d.xcf' and mime:'image/x-xcf'
Aug 06 13:19:30 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:30 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:30 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:31 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:31 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:31 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: failed to bind pixmap to texture
Aug 06 13:19:31 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:31 localhost gnome-session[2157]: Unable to get Terminal Size. The TIOCGWINSZ ioctl didn't work. The COLUMNS and LINES environment variables didn't work. The resize program didn't work. The stty program didn't work. at /usr/lib/perl5/vendor_perl/5.20.1/x86_64-linux-thread-multi/Term/ReadKey.pm line 451.
Aug 06 13:19:31 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:32 localhost /etc/X11/gdm/Xsession[2157]: compiz (decor) - Warn: No default decoration found, placement will not be correct
Aug 06 13:19:33 localhost mgaapplet[2417]: running: ionice -p 2417 -n7
Aug 06 13:19:37 localhost systemd-timesyncd[596]: interval/delta/delay/jitter/drift 64s/-0.000s/0.089s/0.000s/+0ppm
Aug 06 13:19:55 localhost login[2505]: pam_tcb(login:auth): Authentication passed for billymo67 from LOGIN(uid=0)
Aug 06 13:19:55 localhost systemd-logind[749]: New session c3 of user billymo67.
Aug 06 13:19:55 localhost login[2505]: pam_tcb(login:session): Session opened for billymo67 by LOGIN(uid=0)
Aug 06 13:19:55 localhost login[2505]: LOGIN ON tty2 BY billymo67
Aug 06 13:20:19 localhost su[2649]: pam_tcb(su:auth): Authentication passed for root from billymo67(uid=1000)
Aug 06 13:20:19 localhost su[2649]: (to root) billymo67 on tty2
Aug 06 13:20:19 localhost su[2649]: pam_tcb(su:session): Session opened for root by billymo67(uid=1000)
Aug 06 13:20:41 localhost systemd-timesyncd[596]: interval/delta/delay/jitter/drift 128s/-0.001s/0.087s/0.001s/-4ppm

kadmus

[doktor5000]

I see at least 3 issues, one of them is critical.

- adwaita (the default theme) does not seem to be installed
- networkmanager does not seem to be installed

- the critical issue is this one:

Aug 06 13:19:17 localhost gnome-session[2157]: Window manager warning: Screen 0 on display ":0" already has a window manager; try using the --replace option to replace the current window manager.
Aug 06 13:19:17 localhost kernel: gnome-shell[2366]: segfault at 18 ip 00007fcefa952da5 sp 00007ffe160db290 error 4 in libmutter.so.0.0.0[7fcefa8c6000+138000]
Aug 06 13:19:18 localhost gnome-session[2157]: gnome-session[2157]: WARNING: Application 'gnome-shell-classic.desktop' killed by signal 11
Aug 06 13:19:18 localhost gnome-session[2157]: WARNING: Application 'gnome-shell-classic.desktop' killed by signal 11
[...]
Aug 06 13:19:17 localhost kernel: gnome-shell[2366]: segfault at 18 ip 00007fcefa952da5 sp 00007ffe160db290 error 4 in libmutter.so.0.0.0[7fcefa8c6000+138000]
Aug 06 13:19:18 localhost gnome-session[2157]: gnome-session[2157]: WARNING: Application 'gnome-shell-classic.desktop' killed by signal 11
Aug 06 13:19:18 localhost gnome-session[2157]: WARNING: Application 'gnome-shell-classic.desktop' killed by signal 11

Please see https://bugs.mageia.org/show_bug.cgi?id=16033#c11 for a workaround.

[Kadmus]

I have found another way to get 'gnome classic' in all but name. I installed the Mate DE. Prior to the new install I had as an alternative installed desktop environments; Cinnamon and Enlightenment. Cinnamon works fine, Enlightenment not so much and when I removed it along with it went components that were apparently part of gnome classic. They were referred to as orphan packages which have since been removed.

I installed Mate (Mah tay) desktop environment, and was pleasantly surprised to see the way it was set up, like the Gnome 2.xx I remembered.

I have three choices as to which 'de' I can use, so each and any time it will be a new experience.

[isadora]

Kadmus, something seems to have gone wrong, when marking the topic [SOLVED].
You replaced the original topic-title.
Great your issue has been solved, but anyone may wonder which problem?

[doktor5000]

The title "Something has gone wrond" is not any better either.