Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
gdm no longer starts at boot (systemd)
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
azp
Guru
Guru


Joined: 16 Nov 2003
Posts: 354
Location: Stockholm, Sweden

PostPosted: Sat Jun 28, 2014 1:32 pm    Post subject: gdm no longer starts at boot (systemd) Reply with quote

For some reason, gdm doesn't automatically start anymore. I'm running systemd-214, but I think it stopped working at the end of May. gdm's last login was the 28:th of May, so I think I was using systemd-212 at the time.

I can't start gdm from the terminal either, it just seems to wait for something. No log or anything. I tried running it with
Code:
gdm --fatal-warnings --timed-exit

but the same thing happened. It just sits and waits for a while, and then quits (the latter probably because of --timed-exit).

I can start Gnome via startx, so thankfully I can still use my computer.

No logs are present at all..

Code:
root@skare$ ll /var/log/gdm/
totalt 0


Any clues?
_________________
Weeks of coding can save you hours of planning.
Back to top
View user's profile Send private message
eccerr0r
Advocate
Advocate


Joined: 01 Jul 2004
Posts: 4098
Location: USA

PostPosted: Sat Jun 28, 2014 4:27 pm    Post subject: Reply with quote

Bear with me, I'l trying to learn this as well. If you could post output so that I could look at them as well, perhaps both of us could learn something. I have not seen this issue show up before so I can't pinpoint an exact issue here.

As you're running systemd, systemd keeps its own log files. Try running

journalctl --since=today|grep gdm

See if there are any interesting data there related to gdm.
_________________
Intel Core i7 2700K@ 4.1GHz/HD3000 graphics/8GB DDR3/180GB SSD
What am I supposed to be advocating?
Back to top
View user's profile Send private message
azp
Guru
Guru


Joined: 16 Nov 2003
Posts: 354
Location: Stockholm, Sweden

PostPosted: Sat Jun 28, 2014 4:45 pm    Post subject: Reply with quote

Removed entry.
_________________
Weeks of coding can save you hours of planning.


Last edited by azp on Sat Jun 28, 2014 9:24 pm; edited 1 time in total
Back to top
View user's profile Send private message
azp
Guru
Guru


Joined: 16 Nov 2003
Posts: 354
Location: Stockholm, Sweden

PostPosted: Sat Jun 28, 2014 4:47 pm    Post subject: Reply with quote

Removed entry.
_________________
Weeks of coding can save you hours of planning.


Last edited by azp on Sat Jun 28, 2014 9:24 pm; edited 1 time in total
Back to top
View user's profile Send private message
azp
Guru
Guru


Joined: 16 Nov 2003
Posts: 354
Location: Stockholm, Sweden

PostPosted: Sat Jun 28, 2014 4:49 pm    Post subject: Reply with quote

Thank you for an answer, any help I can get is great! =)

Thank you for pointing me to the command to find systemd logs, I fiddled around with journalctl but didn't get logs this good from that by myself. Here is the log for gdm:

(here's a pastebin with the whole log, had to cut it down to the first crash: http://pastebin.com/y8YwKRna)

Code:
root@skare$ journalctl --since=today|grep gdm
jun 28 15:16:46 skare gdm[581]: Child process 586 was already dead.
jun 28 15:16:46 skare gdm[581]: GdmDisplay: display lasted 0,188398 seconds
jun 28 15:16:46 skare gdm[581]: Child process 591 was already dead.
jun 28 15:16:46 skare gdm[581]: GdmDisplay: display lasted 0,035269 seconds
jun 28 15:16:46 skare gdm[581]: Child process 592 was already dead.
jun 28 15:16:46 skare gdm[581]: GdmDisplay: display lasted 0,032254 seconds
jun 28 15:16:46 skare gdm[581]: Child process 593 was already dead.
jun 28 15:16:46 skare gdm[581]: GdmDisplay: display lasted 0,030918 seconds
jun 28 15:16:46 skare gdm[581]: Child process 594 was already dead.
jun 28 15:16:46 skare gdm[581]: GdmDisplay: display lasted 0,030527 seconds
jun 28 15:16:46 skare gdm[581]: Child process 595 was already dead.
jun 28 15:16:46 skare gdm[581]: GdmDisplay: display lasted 0,030869 seconds
jun 28 15:16:46 skare gdm[581]: GdmLocalDisplayFactory: maximum number of X display failures reached: check X server log for errors
jun 28 15:16:46 skare gdm-Xorg-:0[586]: X.Org X Server 1.15.1
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Release Date: 2014-04-13
jun 28 15:16:46 skare gdm-Xorg-:0[586]: X Protocol Version 11, Revision 0
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Build Operating System: Linux 3.14.1-gentoo x86_64 Gentoo
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Current Operating System: Linux skare 3.14.4-gentoo #2 SMP PREEMPT Wed Jun 18 19:14:57 CEST 2014 x86_64
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.14.4-gentoo root=/dev/sdd1 ro init=/usr/lib/systemd/systemd rootfstype=ext4 nomodeset libahci.ignore_sss=1 raid=noautodetect selinux=0 fastboot
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Build Date: 26 April 2014  06:28:06PM
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Current version of pixman: 0.32.4
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Before reporting problems, check http://wiki.x.org
jun 28 15:16:46 skare gdm-Xorg-:0[586]: to make sure that you have the latest version.
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Markers: (--) probed, (**) from config file, (==) default setting,
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (++) from command line, (!!) notice, (II) informational,
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (++) Log file: "/dev/null", Time: Sat Jun 28 15:16:46 2014
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (==) Using config file: "/etc/X11/xorg.conf"
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (==) Using config directory: "/etc/X11/xorg.conf.d"
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (==) Using system config directory "/usr/share/X11/xorg.conf.d"
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (==) ServerLayout "aticonfig Layout"
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (**) |-->Screen "Radeon-0" (0)
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (**) |   |-->Monitor "<default monitor>"
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (==) No device specified for screen "Radeon-0".
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Using the first device section listed.
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (**) |   |-->Device "aticonfig-Device[0]-0"
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (==) No monitor specified for screen "Radeon-0".
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Using a default monitor configuration.
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (==) Automatically adding devices
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (==) Automatically enabling devices
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (==) Automatically adding GPU devices
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (==) FontPath set to:
jun 28 15:16:46 skare gdm-Xorg-:0[586]: /usr/share/fonts/misc/,
jun 28 15:16:46 skare gdm-Xorg-:0[586]: /usr/share/fonts/TTF/,
jun 28 15:16:46 skare gdm-Xorg-:0[586]: /usr/share/fonts/OTF/,
jun 28 15:16:46 skare gdm-Xorg-:0[586]: /usr/share/fonts/Type1/,
jun 28 15:16:46 skare gdm-Xorg-:0[586]: /usr/share/fonts/100dpi/,
jun 28 15:16:46 skare gdm-Xorg-:0[586]: /usr/share/fonts/75dpi/
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (==) ModulePath set to "/usr/lib64/xorg/modules"
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (II) The server relies on udev to provide the list of input devices.
jun 28 15:16:46 skare gdm-Xorg-:0[586]: If no devices become available, reconfigure udev or disable AutoAddDevices.
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (II) Loader magic: 0x801c60
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (II) Module ABI versions:
jun 28 15:16:46 skare gdm-Xorg-:0[586]: X.Org ANSI C Emulation: 0.4
jun 28 15:16:46 skare gdm-Xorg-:0[586]: X.Org Video Driver: 15.0
jun 28 15:16:46 skare gdm-Xorg-:0[586]: X.Org XInput driver : 20.0
jun 28 15:16:46 skare gdm-Xorg-:0[586]: X.Org Server Extension : 8.0
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (--) PCI:*(0:2:0:0) 1002:67b1:1458:228f rev 0, Mem @ 0xd0000000/268435456, 0xef800000/8388608, 0xfbd80000/262144, I/O @ 0x0000ee00/256, BIOS @ 0x????????/131072
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Initializing built-in extension Generic Event Extension
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Initializing built-in extension SHAPE
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Initializing built-in extension MIT-SHM
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Initializing built-in extension XInputExtension
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Initializing built-in extension XTEST
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Initializing built-in extension BIG-REQUESTS
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Initializing built-in extension SYNC
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Initializing built-in extension XKEYBOARD
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Initializing built-in extension XC-MISC
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Initializing built-in extension XINERAMA
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Initializing built-in extension XFIXES
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Initializing built-in extension RENDER
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Initializing built-in extension RANDR
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Initializing built-in extension COMPOSITE
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Initializing built-in extension DAMAGE
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Initializing built-in extension MIT-SCREEN-SAVER
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Initializing built-in extension DOUBLE-BUFFER
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Initializing built-in extension RECORD
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Initializing built-in extension DPMS
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Initializing built-in extension Present
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Initializing built-in extension DRI3
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Initializing built-in extension X-Resource
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Initializing built-in extension XVideo
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Initializing built-in extension XVideo-MotionCompensation
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Initializing built-in extension XFree86-VidModeExtension
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Initializing built-in extension XFree86-DGA
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Initializing built-in extension XFree86-DRI
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Initializing built-in extension DRI2
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (II) "glx" will be loaded by default.
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (II) LoadModule: "glx"
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (II) Module glx: vendor="Advanced Micro Devices, Inc."
jun 28 15:16:46 skare gdm-Xorg-:0[586]: compiled for 6.9.0, module version = 1.0.0
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Loading extension GLX
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (II) LoadModule: "fglrx"
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (II) Loading /usr/lib64/xorg/modules/drivers/fglrx_drv.so
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (II) Module fglrx: vendor="FireGL - AMD Technologies Inc."
jun 28 15:16:46 skare gdm-Xorg-:0[586]: compiled for 1.4.99.906, module version = 14.20.7
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Module class: X.Org Video Driver
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (EE)
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (EE) Backtrace:
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (EE) 0: /usr/bin/Xorg (xorg_backtrace+0x48) [0x581888]
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (EE) 1: /usr/bin/Xorg (0x400000+0x185459) [0x585459]
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (EE) 2: /lib64/libpthread.so.0 (0x7fe4e9d51000+0xfeb0) [0x7fe4e9d60eb0]
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (EE) 3: /usr/lib64/xorg/modules/drivers/fglrx_drv.so (0x7fe4e663c000+0x44af34) [0x7fe4e6a86f34]
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (EE) 4: /usr/lib64/xorg/modules/drivers/fglrx_drv.so (0x7fe4e663c000+0x44aacf) [0x7fe4e6a86acf]
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (EE) 5: /usr/bin/Xorg (0x400000+0x66fea) [0x466fea]
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (EE) 6: /usr/bin/Xorg (xf86LoadModules+0xba) [0x47682a]
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (EE) 7: /usr/bin/Xorg (InitOutput+0x7bf) [0x47705f]
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (EE) 8: /usr/bin/Xorg (0x400000+0x3a48b) [0x43a48b]
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (EE) 9: /lib64/libc.so.6 (__libc_start_main+0xf5) [0x7fe4e89d1a65]
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (EE) 10: /usr/bin/Xorg (0x400000+0x25e9e) [0x425e9e]
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (EE)
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (EE) Segmentation fault at address 0x0
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (EE)
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Fatal server error:
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (EE) Caught signal 11 (Segmentation fault). Server aborting
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (EE)
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (EE)
jun 28 15:16:46 skare gdm-Xorg-:0[586]: Please consult the The X.Org Foundation support
jun 28 15:16:46 skare gdm-Xorg-:0[586]: at http://wiki.x.org
jun 28 15:16:46 skare gdm-Xorg-:0[586]: for help.
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (EE) Please also check the log file at "/dev/null" for additional information.
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (EE)
jun 28 15:16:46 skare gdm-Xorg-:0[586]: (EE) Server terminated with error (1). Closing log file.


So there seems to be some crashes in there...
_________________
Weeks of coding can save you hours of planning.
Back to top
View user's profile Send private message
eccerr0r
Advocate
Advocate


Joined: 01 Jul 2004
Posts: 4098
Location: USA

PostPosted: Sat Jun 28, 2014 9:41 pm    Post subject: Reply with quote

Ugh... Now you've gotten into a very weird problem - as you mentioned that startx works but gdm won't pull up X11...

Can't really think of a good explanation for this at all... Hardware issue? I don't know...

Only things I could suggest is trying to re-emerge ati-drivers and xorg-server, but no guarantee that will do anything. Hope someone else has some ideas...
_________________
Intel Core i7 2700K@ 4.1GHz/HD3000 graphics/8GB DDR3/180GB SSD
What am I supposed to be advocating?
Back to top
View user's profile Send private message
azp
Guru
Guru


Joined: 16 Nov 2003
Posts: 354
Location: Stockholm, Sweden

PostPosted: Sun Jun 29, 2014 8:22 am    Post subject: Reply with quote

eccerr0r wrote:
Ugh... Now you've gotten into a very weird problem - as you mentioned that startx works but gdm won't pull up X11...

Can't really think of a good explanation for this at all... Hardware issue? I don't know...

Only things I could suggest is trying to re-emerge ati-drivers and xorg-server, but no guarantee that will do anything. Hope someone else has some ideas...


I've tried re-emerging ati-drivers several times, but that doesn't help. I will try running an emerge -e gdm during the day, and see if anything improves.
_________________
Weeks of coding can save you hours of planning.
Back to top
View user's profile Send private message
azp
Guru
Guru


Joined: 16 Nov 2003
Posts: 354
Location: Stockholm, Sweden

PostPosted: Sun Jun 29, 2014 4:24 pm    Post subject: Reply with quote

azp wrote:
eccerr0r wrote:
Ugh... Now you've gotten into a very weird problem - as you mentioned that startx works but gdm won't pull up X11...

Can't really think of a good explanation for this at all... Hardware issue? I don't know...

Only things I could suggest is trying to re-emerge ati-drivers and xorg-server, but no guarantee that will do anything. Hope someone else has some ideas...


I've tried re-emerging ati-drivers several times, but that doesn't help. I will try running an emerge -e gdm during the day, and see if anything improves.


... 628 of 784 complete...
_________________
Weeks of coding can save you hours of planning.
Back to top
View user's profile Send private message
costel78
Apprentice
Apprentice


Joined: 20 Apr 2007
Posts: 208

PostPosted: Mon Jun 30, 2014 9:05 am    Post subject: Reply with quote

Well, how the things goes after recompile ? I don't want to be pessimistic but I'm 99% sure that there will be no change.... at, least it wasn't for me.
I am in the same boat and seems that the culprit is ati-drivers. gdm it's working fine with radeon kms open-sources drivers. I switched to slim and I'm waiting for better ati drivers.
Gdm is working only with xorg-server-14* and ati-drivers-13*
Code:
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8400 / R3 Series]
CPU Model name:            AMD Athlon(tm) 5350 APU with Radeon(tm) R3

If you have any luck, please post here.
_________________
Sorry for my English. I'm still learning this language.
Back to top
View user's profile Send private message
eccerr0r
Advocate
Advocate


Joined: 01 Jul 2004
Posts: 4098
Location: USA

PostPosted: Mon Jun 30, 2014 11:58 pm    Post subject: Reply with quote

Oh.. I think I sort of remember now. ati-drivers crashed on me or something as well, or it was behaving very poorly with my dual head system.

Try unmasking the latest ati-drivers and emerge that.
_________________
Intel Core i7 2700K@ 4.1GHz/HD3000 graphics/8GB DDR3/180GB SSD
What am I supposed to be advocating?
Back to top
View user's profile Send private message
azp
Guru
Guru


Joined: 16 Nov 2003
Posts: 354
Location: Stockholm, Sweden

PostPosted: Wed Jul 02, 2014 7:03 pm    Post subject: Reply with quote

costel78 wrote:
Well, how the things goes after recompile ? I don't want to be pessimistic but I'm 99% sure that there will be no change.... at, least it wasn't for me.
I am in the same boat and seems that the culprit is ati-drivers. gdm it's working fine with radeon kms open-sources drivers. I switched to slim and I'm waiting for better ati drivers.
Gdm is working only with xorg-server-14* and ati-drivers-13*
Code:
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8400 / R3 Series]
CPU Model name:            AMD Athlon(tm) 5350 APU with Radeon(tm) R3

If you have any luck, please post here.


You are (sadly) completely right, as expected. No difference from before. I tried with the new 14.6_beta driver, but that didn't help either. I think I tried using Slim before, but had some issues with it. Can't remember which ones now though, it was at least a year ago I tried it.
_________________
Weeks of coding can save you hours of planning.
Back to top
View user's profile Send private message
junkY_San
n00b
n00b


Joined: 19 Jul 2006
Posts: 3

PostPosted: Fri Jul 04, 2014 8:45 am    Post subject: Reply with quote

i can confirm the gdm issue on my ~amd64 system. gdm only started once but never again afterwards.
journalctl looks like this:

Code:

gdm-Xorg-:5[16157]: (II) LoadModule: "glx"
gdm-Xorg-:5[16157]: (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
gdm-Xorg-:5[16157]: (II) Module glx: vendor="Advanced Micro Devices, Inc."
gdm-Xorg-:5[16157]: compiled for 6.9.0, module version = 1.0.0
gdm-Xorg-:5[16157]: Loading extension GLX
gdm-Xorg-:5[16157]: (II) LoadModule: "fglrx"
gdm-Xorg-:5[16157]: (II) Loading /usr/lib64/xorg/modules/drivers/fglrx_drv.so
gdm-Xorg-:5[16157]: (II) Module fglrx: vendor="FireGL - AMD Technologies Inc."
gdm-Xorg-:5[16157]: compiled for 1.4.99.906, module version = 14.20.7
gdm-Xorg-:5[16157]: Module class: X.Org Video Driver
gdm-Xorg-:5[16157]: (EE)
gdm-Xorg-:5[16157]: (EE) Backtrace:
gdm-Xorg-:5[16157]: (EE) 0: /usr/bin/Xorg (xorg_backtrace+0x4f) [0x595a8f]
gdm-Xorg-:5[16157]: (EE) 1: /usr/bin/Xorg (0x400000+0x199a49) [0x599a49]
gdm-Xorg-:5[16157]: (EE) 2: /lib64/libpthread.so.0 (0x7f5df3e52000+0x10250) [0x7f5df3e62250]
gdm-Xorg-:5[16157]: (EE) 3: /usr/lib64/xorg/modules/drivers/fglrx_drv.so (0x7f5df0718000+0x44af34) [0x
gdm-Xorg-:5[16157]: (EE) 4: /usr/lib64/xorg/modules/drivers/fglrx_drv.so (0x7f5df0718000+0x44aacf) [0x
gdm-Xorg-:5[16157]: (EE) 5: /usr/bin/Xorg (0x400000+0x6a9eb) [0x46a9eb]
gdm-Xorg-:5[16157]: (EE) 6: /usr/bin/Xorg (xf86LoadModules+0xa9) [0x47ad89]
gdm-Xorg-:5[16157]: (EE) 7: /usr/bin/Xorg (InitOutput+0x7d7) [0x47b5d7]
gdm-Xorg-:5[16157]: (EE) 8: /usr/bin/Xorg (0x400000+0x3b0eb) [0x43b0eb]
gdm-Xorg-:5[16157]: (EE) 9: /lib64/libc.so.6 (__libc_start_main+0xf0) [0x7f5df2ab5f90]
gdm-Xorg-:5[16157]: (EE) 10: /usr/bin/Xorg (0x400000+0x24f0e) [0x424f0e]
gdm-Xorg-:5[16157]: (EE)
gdm-Xorg-:5[16157]: (EE) Segmentation fault at address 0x0
gdm-Xorg-:5[16157]: (EE)
gdm-Xorg-:5[16157]: Fatal server error:
gdm-Xorg-:5[16157]: (EE) Caught signal 11 (Segmentation fault). Server aborting
gdm-Xorg-:5[16157]: (EE)
gdm-Xorg-:5[16157]: (EE)
gdm-Xorg-:5[16157]: Please consult the The X.Org Foundation support
gdm-Xorg-:5[16157]: at http://wiki.x.org
gdm-Xorg-:5[16157]: for help.
gdm-Xorg-:5[16157]: (EE) Please also check the log file at "/dev/null" for additional information.
gdm-Xorg-:5[16157]: (EE)
gdm-Xorg-:5[16157]: (EE) Server terminated with error (1). Closing log file.
gdm[16146]: Child process 16157 was already dead.
gdm[16146]: GdmDisplay: display lasted 0,046069 seconds


package versions are currently:

x11-drivers/ati-drivers-14.6_beta1
x11-base/xorg-server-1.15.1
gnome-base/gdm-3.12.2
sys-apps/systemd-214
Back to top
View user's profile Send private message
azp
Guru
Guru


Joined: 16 Nov 2003
Posts: 354
Location: Stockholm, Sweden

PostPosted: Wed Jul 09, 2014 5:38 pm    Post subject: Reply with quote

Has somebody filed a bug regarding this?

Edit: Nevermind, I reported one here: https://bugs.gentoo.org/show_bug.cgi?id=516816
_________________
Weeks of coding can save you hours of planning.
Back to top
View user's profile Send private message
eccerr0r
Advocate
Advocate


Joined: 01 Jul 2004
Posts: 4098
Location: USA

PostPosted: Fri Aug 01, 2014 3:38 pm    Post subject: Reply with quote

Ouch. I just got the Gnome 3.12 update and am seeing a very similar problem now.

X11 starts if I run it manually but running it through gdm fails. I think it is indeed an ati-drivers bug but gdm is exacerbating it.

Hmm...

Everyone here having issues when running dual head or are single monitor users having problems as well?

I wonder if it's possible to backtrack to gdm 3.10 ... Probably not but... worth a try.

[EDIT]
I did this to workaround the problem: SLiM works to start Gnome:

Code:
emerge slim
systemctl disable gdm
systemctl enable slim


The next boot (or systemctl stop gdm; systemctl start slim) SLiM seems to come up just fine, except the thing I dislike about SLiM at least it its default config: I think I have to hit F1 until Gnome (or XFCE on my other machines) comes up before finishing typing my password else it brings up a dead desktop environment and kicks you back to the login screen...

Still trying to figure out how to make the default to a functional DE like Gnome or anything else - I found a way to hardcode it to xfce in slim.conf but that isn't exactly what I wanted (but works well enough for my low disk space, single-DE machines...)

One of my machines SLiM just brings up an xterm with no windowmanager... Another just kicks back to the login screen. Sigh.

[EDIT 2]

Though SLiM let me log into Gnome and gnome-session works fine, it seems to stop after logging out - either SLiM is not restarting itself after the session stopped, or systemd isn't restarting SLiM... Or possibly SLiM is crashing fglrx as well on the second time around...

Sigh.
Back to top
View user's profile Send private message
franhait
n00b
n00b


Joined: 02 Aug 2014
Posts: 1

PostPosted: Sat Aug 02, 2014 10:39 pm    Post subject: Reply with quote

Hi all,

This is my first post, so I hope it can be usefull :D

Based on all entries and https://bugs.gentoo.org/show_bug.cgi?id=516816, I tried masking the latest gdm-3.12.2 to check if the issue is from ATI driver or gdm:

# echo "=gnome-base/gdm-3.12.2" >> /etc/portage/package.mask/gdm

then, I reinstalled gdm, so this downgrade GDM version:

[ebuild R ] gnome-base/gdm-3.10.0.1-r1 USE="branding introspection ipv6 systemd tcpd -accessibility -audit -debug -fprint -plymouth (-selinux) -smartcard {-test} -xinerama" 0 kB

Now GDM is working great.
Back to top
View user's profile Send private message
eccerr0r
Advocate
Advocate


Joined: 01 Jul 2004
Posts: 4098
Location: USA

PostPosted: Sun Aug 03, 2014 12:49 am    Post subject: Reply with quote

Ahh strange I thought that there was a minimum version dependency of gdm needed. I suppose not.
In any case, drivers are not supposed to segfault so though gdm appears to be the problem software, the culprit really is ati-drivers.

I think I found a solution to SLiM if anyone decided to go this route. Unfortunately the login window pops up and is split in half with dual monitors, but does not affect functionality.

To use SLiM you need to simply need to add

export XSESSION=gnome-session

in your ~/.profile

This will let the default auto-chooser do the right thing instead of dumping you back to the login prompt (usually) on default... Not exactly the best solution (the system should select a default and not force the user to make a selection) but it works...
_________________
Intel Core i7 2700K@ 4.1GHz/HD3000 graphics/8GB DDR3/180GB SSD
What am I supposed to be advocating?
Back to top
View user's profile Send private message
azp
Guru
Guru


Joined: 16 Nov 2003
Posts: 354
Location: Stockholm, Sweden

PostPosted: Tue Aug 05, 2014 7:16 am    Post subject: Reply with quote

eccerr0r wrote:

I did this to workaround the problem: SLiM works to start Gnome:

Code:
emerge slim
systemctl disable gdm
systemctl enable slim



I didn't seem to get the SLiM systemd startup script, but I will try this when I have the chance. I had to start SLiM manually, which wasn't much better than starting X manually.
_________________
Weeks of coding can save you hours of planning.
Back to top
View user's profile Send private message
eccerr0r
Advocate
Advocate


Joined: 01 Jul 2004
Posts: 4098
Location: USA

PostPosted: Tue Aug 19, 2014 12:33 pm    Post subject: Reply with quote

Just another test...

I tried x11-misc/lightdm as well, and it looks like it also works well as a substitute for GDM, except it knows how to handle multiple displays - and the login greeter shows up on one of the two monitors instead of being straddled.

Anyone running into the ati-drivers bug with gdm should try lightdm, and it can be enabled in systemd similarly to slim except using lightdm.

And the new problem: fast user switching is borked... Looks like Gnome/GDM has a slightly different API.

More info about lightdm: Installing in Gentoo: http://wiki.gentoo.org/wiki/LightDM
Controlling LightDM: https://wiki.archlinux.org/index.php/LightDM
_________________
Intel Core i7 2700K@ 4.1GHz/HD3000 graphics/8GB DDR3/180GB SSD
What am I supposed to be advocating?
Back to top
View user's profile Send private message
heheman3000
n00b
n00b


Joined: 22 Oct 2006
Posts: 18

PostPosted: Wed Sep 03, 2014 2:47 am    Post subject: Reply with quote

I am having this issue too. What a strange error. I've also tried the 14.6 beta driver.

I don't think switching to another display manager is a reasonable solution for this. How do you start gnome with startx?

EDIT: Followed the instructions here: https://wiki.gentoo.org/wiki/GNOME/Configuration#First_Impressions

franhait wrote:
Hi all,

This is my first post, so I hope it can be usefull :D

Based on all entries and https://bugs.gentoo.org/show_bug.cgi?id=516816, I tried masking the latest gdm-3.12.2 to check if the issue is from ATI driver or gdm:

# echo "=gnome-base/gdm-3.12.2" >> /etc/portage/package.mask/gdm

then, I reinstalled gdm, so this downgrade GDM version:

[ebuild R ] gnome-base/gdm-3.10.0.1-r1 USE="branding introspection ipv6 systemd tcpd -accessibility -audit -debug -fprint -plymouth (-selinux) -smartcard {-test} -xinerama" 0 kB

Now GDM is working great.


If this worked before, it doesn't work now; the gnome-base/gnome-3.12.0 now requires >=gdm-3.12 as well.

Maybe another solution is to downgrade ati-drivers and xorg, but I haven't tried that myself.
Back to top
View user's profile Send private message
eccerr0r
Advocate
Advocate


Joined: 01 Jul 2004
Posts: 4098
Location: USA

PostPosted: Wed Sep 03, 2014 7:30 am    Post subject: Reply with quote

Why do you think using another display manager is not a 'reasonable' workaround?

The real solution is to get ATI/AMD to fix their driver, pretty much everything else is just a workaround. Lightdm produces a very clean graphical login interface that does everything that gdm does, and presents a proper login menu on the two displays.
_________________
Intel Core i7 2700K@ 4.1GHz/HD3000 graphics/8GB DDR3/180GB SSD
What am I supposed to be advocating?
Back to top
View user's profile Send private message
heheman3000
n00b
n00b


Joined: 22 Oct 2006
Posts: 18

PostPosted: Wed Sep 03, 2014 9:03 pm    Post subject: Reply with quote

I must have been mistaken - I thought that changing the display manager would be changing the window manager as well. Would I still be able to use GNOME 3?
Back to top
View user's profile Send private message
eccerr0r
Advocate
Advocate


Joined: 01 Jul 2004
Posts: 4098
Location: USA

PostPosted: Thu Sep 04, 2014 3:27 am    Post subject: Reply with quote

That's exactly what I'm doing, lightdm is presenting the login and I get the Gnome 3 desktop environment (or any other). I was unsatisfied with SLiM (and xdm) because it didn't appear to have an easy way to shutdown the computer on the login screen (perhaps there's a plugin but didn't look...), but LightDM was able to do that and also offer a user chooser that shows up on one of the two displays. I don't think I really lost any functionality without using GDM other than possibly fast user switching, but oh well. Blame ATI/AMD...
_________________
Intel Core i7 2700K@ 4.1GHz/HD3000 graphics/8GB DDR3/180GB SSD
What am I supposed to be advocating?
Back to top
View user's profile Send private message
heheman3000
n00b
n00b


Joined: 22 Oct 2006
Posts: 18

PostPosted: Thu Sep 11, 2014 7:58 pm    Post subject: Reply with quote

LightDM is working for me now, too.
Back to top
View user's profile Send private message
JohnY
Apprentice
Apprentice


Joined: 26 Jul 2002
Posts: 284

PostPosted: Thu Sep 25, 2014 5:36 am    Post subject: Reply with quote

heheman3000 wrote:
LightDM is working for me now, too.


I have the same problem with gdm and the radeon opensource drivers xf86-video-ati-7.4.0
and an ati Radeon HD 6670. Both LightDM and KDM work for starting gnome 3.12, xfce4, e17, and kde here on ~x86 with a asrock 939sli32esata2, AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ with 4gb (3mb visable). (3.8 gnome and gdm ran fine, 3.10 was also a miss)

On my other machine, an hp xw8600, ati 7980 xf86-video-ati-7.4.0 64bit stable gentoo, dual quad xenon 5405's and 12gb ram, gdm and gnome 3.12 run fine ..... go figure ...

JohnY
Back to top
View user's profile Send private message
eccerr0r
Advocate
Advocate


Joined: 01 Jul 2004
Posts: 4098
Location: USA

PostPosted: Fri Sep 26, 2014 12:23 am    Post subject: Reply with quote

Odd that the OSS driver exhibits the same behavior on some setups. I'd imagine the OSS driver should not crash like the closed source driver with the same behavior... Weird.

I've yet to try the OSS driver. Once I get a PCIe board that I can play with I might have to see how well the OSS driver works on my old HD3650 and X800.
_________________
Intel Core i7 2700K@ 4.1GHz/HD3000 graphics/8GB DDR3/180GB SSD
What am I supposed to be advocating?
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
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