| View previous topic :: View next topic |
| Author |
Message |
pdraganov
n00b
Joined: 17 Oct 2014
Posts: 27
|
 Posted: Fri Oct 17, 2014 4:14 am Post subject: X stops refreshing screen and responding sometimes;SYSTEMD,X |
 |
|
I installed Gentoo for the first time. I selected the profile with gnome and systemd (and gdm). Everything is working fine until I leave the PC untouched so that power saving is activated or I switch to another user.
When I login with one user only (one X) the problem appears sometimes - actually the problem appears only when there are 2 X servers (if I select "Switch users" without logging in as another user). Not every power saving mode makes X unresponsive.
When I switch 2 users back and forth, there are 3 X servers - 1 for the first user, 1 for the second user and one for the gdm login screen. Sometimes one of these X servers stops refreshing (it has black or grey screen with moving mouse only), but it responds to mouse clicks and keyboard. For example, on gdm login screen if I click near the center, usernames appear for a second and if I enter the clicked user's password, gdm switches to that user's X. Sometimes X even does not respond to mouse and keyboard. If I switch consoles with Ctrl-Alt-F7, Ctrl-Alt-F2, Ctrl-Alt-F3, I can find some working X.
At the moment I have one logged in user on VT7 since yesterday, when I clicked "Switch user" and then Cancel. This created second X on VT3 for gdm login screen, which is not responding and has grey screen with moving mouse only.
| Quote: | localhost ~ # systemctl status gdm
● gdm.service - GNOME Display Manager
Loaded: loaded (/usr/lib64/systemd/system/gdm.service; enabled)
Active: active (running) since чт 2014-10-16 18:21:43 EEST; 11h ago
Main PID: 6064 (gdm)
CGroup: /system.slice/gdm.service
├─ 6064 /usr/sbin/gdm
├─ 6069 /usr/bin/Xorg :0 -background none -noreset -verbose 3 -logfile /dev/null -auth /run/gdm/auth-for-gdm-sDm5Gk/database -seat seat0 -nolisten tcp vt7
└─11245 /usr/bin/Xorg :1 -background none -noreset -verbose 3 -logfile /dev/null -auth /run/gdm/auth-for-gdm-XNJbam/database -seat seat0 -nolisten tcp
окт 16 21:13:52 localhost gdm-Xorg-:0[6069]: (II) RADEON(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
окт 16 21:13:52 localhost gdm-Xorg-:0[6069]: (II) RADEON(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
окт 16 21:13:52 localhost gdm-Xorg-:0[6069]: (II) RADEON(0): Modeline "1280x720"x60.0 74.48 1280 1336 1472 1664 720 721 724 746 -hsync +vsync (44.8 kHz e)
окт 16 21:13:52 localhost gdm-Xorg-:0[6069]: (II) RADEON(0): Modeline "1280x800"x0.0 83.50 1280 1352 1480 1680 800 803 809 831 -hsync +vsync (49.7 kHz e)
окт 16 21:13:52 localhost gdm-Xorg-:0[6069]: (II) RADEON(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
окт 16 21:13:52 localhost gdm-Xorg-:0[6069]: (II) RADEON(0): Modeline "1440x900"x0.0 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz e)
окт 16 21:13:52 localhost gdm-Xorg-:0[6069]: (II) RADEON(0): Modeline "1600x900"x60.0 119.00 1600 1696 1864 2128 900 901 904 932 -hsync +vsync (55.9 kHz e)
окт 16 21:13:52 localhost gdm-Xorg-:0[6069]: (II) RADEON(0): Modeline "1680x1050"x0.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e)
окт 17 05:57:16 localhost gdm[6064]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
окт 17 05:57:24 localhost gdm[6064]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
localhost ~ # equery l -po gnome
* Searching for gnome ...
[-P-] [ ] gnome-base/gnome-2.32.1-r2:2.0
[-P-] [ ] gnome-base/gnome-3.10.0:2.0
[IP-] [ ] gnome-base/gnome-3.12.0:2.0
localhost ~ # equery l -po gdm
* Searching for gdm ...
[-P-] [ ] gnome-base/gdm-2.20.11-r1:0
[IP-] [ ] gnome-base/gdm-3.12.2:0
[-P-] [ ~] gnome-base/gdm-3.12.2-r1:0 |
Apparently, Xorg :1 has no corresponding VT3 in front of it.
What additional information is needed in order to make some advices about resolving this problem?
In journalctl I have ocasionally such messages (there are Bugarian parts, which I do not know how to fix to be English):
| Quote: | | окт 16 21:59:57 localhost gnome-session[6204]: Предупреждение от мениджъра на прозорци: last_focus_time (53690144) is greater than comparison timestamp (53690137). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... |
Also there are many such:
| Quote: | окт 16 22:07:00 localhost gnome-session[6204]: (gnome-shell:6279): St-CRITICAL **: st_label_set_text: assertion 'text != NULL' failed
окт 16 22:08:00 localhost gnome-session[6204]: (gnome-shell:6279): St-CRITICAL **: st_label_set_text: assertion 'text != NULL' failed
окт 16 22:09:00 localhost gnome-session[6204]: (gnome-shell:6279): St-CRITICAL **: st_label_set_text: assertion 'text != NULL' failed
окт 16 22:10:00 localhost gnome-session[6204]: (gnome-shell:6279): St-CRITICAL **: st_label_set_text: assertion 'text != NULL' failed
окт 16 22:11:00 localhost gnome-session[6204]: (gnome-shell:6279): St-CRITICAL **: st_label_set_text: assertion 'text != NULL' failed
окт 16 22:12:00 localhost gnome-session[6204]: (gnome-shell:6279): St-CRITICAL **: st_label_set_text: assertion 'text != NULL' failed
окт 16 22:13:00 localhost gnome-session[6204]: (gnome-shell:6279): St-CRITICAL **: st_label_set_text: assertion 'text != NULL' failed
окт 16 22:14:00 localhost gnome-session[6204]: (gnome-shell:6279): St-CRITICAL **: st_label_set_text: assertion 'text != NULL' failed
окт 16 22:15:00 localhost gnome-session[6204]: (gnome-shell:6279): St-CRITICAL **: st_label_set_text: assertion 'text != NULL' failed |
Sometimes:
| Quote: | | окт 17 00:00:00 localhost gnome-session[6204]: (evolution-alarm-notify:6362): evolution-alarm-notify-WARNING **: alarm.c:253: Requested removal of nonexistent alarm! |
And at the end:
| Quote: | окт 17 05:54:00 localhost gnome-session[6204]: (gnome-shell:6279): St-CRITICAL **: st_label_set_text: assertion 'text != NULL' failed
окт 17 05:55:00 localhost gnome-session[6204]: (gnome-shell:6279): St-CRITICAL **: st_label_set_text: assertion 'text != NULL' failed
окт 17 05:56:00 localhost gnome-session[6204]: (gnome-shell:6279): St-CRITICAL **: st_label_set_text: assertion 'text != NULL' failed
окт 17 05:57:00 localhost gnome-session[6204]: (gnome-shell:6279): St-CRITICAL **: st_label_set_text: assertion 'text != NULL' failed
окт 17 05:57:16 localhost gdm[6064]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
окт 17 05:57:24 localhost gdm[6064]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
окт 17 05:57:24 localhost dbus[4673]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
окт 17 05:57:24 localhost systemd[1]: Starting Hostname Service...
окт 17 05:57:24 localhost dbus[4673]: [system] Successfully activated service 'org.freedesktop.hostname1'
окт 17 05:57:24 localhost systemd[1]: Started Hostname Service.
окт 17 05:58:40 localhost gnome-session[6204]: Предупреждение от мениджъра на прозорци: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1c0002a (Xcrash1 (/)
окт 17 05:58:40 localhost gnome-session[6204]: Предупреждение от мениджъра на прозорци: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
окт 17 05:58:58 localhost gnome-session[6204]: Предупреждение от мениджъра на прозорци: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1c0002a (*Xcrash1 ()
окт 17 05:58:58 localhost gnome-session[6204]: Предупреждение от мениджъра на прозорци: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. |
5:57 is, when I waked up X this morning.
Предупреждение от мениджъра на прозорци = Window manager warning
Last edited by pdraganov on Fri Oct 24, 2014 8:34 pm; edited 3 times in total |
|
| Back to top |
|
 |
Roman_Gruber
Advocate
Joined: 03 Oct 2006
Posts: 3846
Location: Austro Bavaria
|
| Posted: Fri Oct 17, 2014 10:18 am Post subject: |
|
|
Hi, please change your title of this topic:
Important: ADD SYSTEMD, X
thank you. personal rant and opinion: if you do not need systemd, stick to a stable solution like openrc |
|
| Back to top |
|
|
pdraganov
n00b
Joined: 17 Oct 2014
Posts: 27
|
| Posted: Fri Oct 17, 2014 6:44 pm Post subject: |
|
|
Hi tw04l124,
as I read, gnome 3.8+ requires systemd. Also systemd is accepted from more and more Linux distributions and some day we need to learn it.
Thank you for the advise, I added what you recomended |
|
| Back to top |
|
|
Roman_Gruber
Advocate
Joined: 03 Oct 2006
Posts: 3846
Location: Austro Bavaria
|
| Posted: Fri Oct 17, 2014 7:00 pm Post subject: |
|
|
AFAIK needed only for a few components of gnome, see this forum. there are even peeps who run current gnome without systemd ...
and there are other init systems which works and are less a hassle. not everyone uses the only one init system called systemd.
anyway thanks for adapting the title of your post |
|
| Back to top |
|
|
pdraganov
n00b
Joined: 17 Oct 2014
Posts: 27
|
| Posted: Fri Oct 24, 2014 8:58 pm Post subject: Found out another fact |
|
|
| The black/grey screen problem appears only when at least 2 X servers are started. With one X server, it runs without problems few days with multiple power savings on/off |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
