| View previous topic :: View next topic |
| Author |
Message |
imesg
Guru
Joined: 12 Jul 2002
Posts: 445
|
 Posted: Thu Mar 04, 2021 6:53 pm Post subject: SOLVED -- gnome starts only partially |
 |
|
When I start gnome I get a desktop the has this message:
| Quote: |
Oh no! /something has gone wrong.
A problem has occurred and the system ca't recover.
Please log out and try again.
|
Then a 'logout button'.
The only thing on the desktop that starts is 'gnome-terminal'.
| Code: |
root@dt1:~# ps aux|grep gnome
gene 97550 0.0 0.0 411260 17892 tty1 Sl 12:43 0:00 /usr/libexec/gnome-session-binary
gene 97556 0.0 0.0 7764 2208 tty1 S 12:43 0:00 dbus-launch --exit-with-session /usr/libexec/gnome-session-binary
gene 97601 0.0 0.0 385784 8476 tty1 SLl 12:43 0:00 /usr/bin/gnome-keyring-daemon --start --components=pkcs11
gene 97665 0.0 0.1 237976 37696 tty1 Sl 12:43 0:00 /usr/libexec/gnome-session-failed --allow-logout
gene 97758 0.0 0.0 160632 6420 ? Sl 12:43 0:00 /usr/libexec/at-spi2-registryd --use-gnome-session
gene 97799 0.0 0.1 822008 47740 tty1 Sl 12:43 0:00 /usr/bin/gnome-software --gapplication-service
gene 97877 0.4 0.1 396864 46836 ? Sl 12:43 0:01 /usr/libexec/gnome-terminal-server
root 103259 0.0 0.0 8088 688 pts/4 S+ 12:49 0:00 grep -i --color=auto gnome
root@dt1:~#
|
I can run things from the terminal. Whatever is started this way has focus and nothing else can have focus.
I don't know where to start looking for clues. Help please.
Thanks
Last edited by imesg on Thu Mar 04, 2021 9:03 pm; edited 1 time in total |
|
| Back to top |
|
 |
eccerr0r
Watchman
Joined: 01 Jul 2004
Posts: 9691
Location: almost Mile High in the USA
|
| Posted: Thu Mar 04, 2021 7:53 pm Post subject: |
|
|
This is a very open ended query...
I can only give my experience when I got this before -- it was due to hardware failure. Turns out the hardware was causing gnome-shell to crash and it couldn't recover. Had to replace motherboard.
Check you dmesg for possible video or hardware issues.
If your hardware is good you should try re-merging gnome-shell to make sure it's not corrupt...caused by bad hardware...uh...
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching? |
|
| Back to top |
|
|
imesg
Guru
Joined: 12 Jul 2002
Posts: 445
|
| Posted: Thu Mar 04, 2021 8:48 pm Post subject: |
|
|
Thanks for the reply eccerr0r. I realize it is an open question but I have no clue so I throw myself on the mercy of gentooers everywhere.
re-emerge gnome-shell no workie.
dmesg - can't find errors.
| eccerr0r wrote: | This is a very open ended query...
I can only give my experience when I got this before -- it was due to hardware failure. Turns out the hardware was causing gnome-shell to crash and it couldn't recover. Had to replace motherboard.
Check you dmesg for possible video or hardware issues.
If your hardware is good you should try re-merging gnome-shell to make sure it's not corrupt...caused by bad hardware...uh... |
|
|
| Back to top |
|
|
imesg
Guru
Joined: 12 Jul 2002
Posts: 445
|
| Posted: Thu Mar 04, 2021 8:53 pm Post subject: |
|
|
This could be it:
| Code: |
[ 95.892388] traps: gnome-shell[807] general protection fault ip:7fa8dcdc8640 sp:7ffc29c3fd90 error:0 in libgjs.so.0.0.0[7fa8dcd96000+82000]
[ 96.319681] traps: gnome-shell[833] general protection fault ip:7fde775a7640 sp:7ffe5db6ea70 error:0 in libgjs.so.0.0.0[7fde77575000+82000]
[ 99.636554] logitech-hidpp-device 0003:046D:1028.0007: HID++ 1.0 device connected.
[ 2226.957540] gnome-shell[1496]: segfault at 39 ip 00007f715f7ab640 sp 00007ffd1eae0810 error 6 in libgjs.so.0.0.0[7f715f779000+82000]
[ 2226.957548] Code: 24 10 49 89 54 24 10 e8 2e e4 fc ff 80 3d 1f a1 0b 00 00 74 55 48 8b 05 fe 9f 0b 00 48 85 c0 74 1f 48 8b 50 30 48 85 d2 74 0d <4c> 89 62 38 48 8b 50 30 49 89 54 24 30 4c 89 60 30 49 89 44 24 38
|
|
|
| Back to top |
|
|
imesg
Guru
Joined: 12 Jul 2002
Posts: 445
|
| Posted: Thu Mar 04, 2021 9:00 pm Post subject: |
|
|
eccerr0r, thanks for your help. Perusing dmesg found libgjs segfault. Re-emerged gjs and all is well. Just looking at dmesg showed the solution.
Thanks again.
| eccerr0r wrote: | This is a very open ended query...
I can only give my experience when I got this before -- it was due to hardware failure. Turns out the hardware was causing gnome-shell to crash and it couldn't recover. Had to replace motherboard.
Check you dmesg for possible video or hardware issues.
If your hardware is good you should try re-merging gnome-shell to make sure it's not corrupt...caused by bad hardware...uh... |
|
|
| Back to top |
|
|
|
Desktop Environments
