You are not logged in.

Pages: 1

#1 2016-03-11 17:39:38

adhokshajm
Member
From: India
Registered: 2015-12-02
Posts: 5
Website

LightDM fails to load after system upgrade

UPDATE: I have downgraded the kernel, and it solved the issue. Seems the kernel itself is buggy.

Today morning I performed system upgrade (07:44 AM IST). However, after restart (kernel was also updated from 4.4.3-1 to 4.4.5-1), lightdm fails to load. I am not even able to "startx" from shell (it just sits there waiting for X server to accept connections). However, lightdm starts if I disable and enable lightdm from root, and restart. Next reboot, and again it won't load.

Anyone suffering from this? How to fix it? Any help wil be appreciated.

Pacman log: 

[2016-03-11 07:44] [PACMAN] Running 'pacman -Syu'
[2016-03-11 07:44] [PACMAN] synchronizing package lists
[2016-03-11 07:44] [PACMAN] starting full system upgrade
[2016-03-11 08:03] [ALPM] transaction started
[2016-03-11 08:03] [ALPM] upgraded perl (5.22.1-1 -> 5.22.1-2)
[2016-03-11 08:03] [ALPM] upgraded gtk-update-icon-cache (3.18.8-1 -> 3.18.9-1)
[2016-03-11 08:03] [ALPM] upgraded hwids (20150717-1 -> 20160306-1)
[2016-03-11 08:03] [ALPM] upgraded flashplugin (11.2.202.569-1 -> 11.2.202.577-1)
[2016-03-11 08:03] [ALPM] upgraded gtk3 (3.18.8-1 -> 3.18.9-1)
[2016-03-11 08:03] [ALPM] upgraded tevent (0.9.26-1 -> 0.9.28-1)
[2016-03-11 08:03] [ALPM] upgraded ldb (1.1.24-1 -> 1.1.26-1)
[2016-03-11 08:04] [ALPM] upgraded libvirt (1.3.2-2 -> 1.3.2-3)
[2016-03-11 08:04] [ALPM-SCRIPTLET] >>> You may need to run 'rm -rf ~/.libvirt'
[2016-03-11 08:04] [ALPM] upgraded libwbclient (4.3.5-1 -> 4.3.6-1)
[2016-03-11 08:04] [ALPM] upgraded linux (4.4.3-1 -> 4.4.5-1)
[2016-03-11 08:04] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2016-03-11 08:04] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2016-03-11 08:04] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2016-03-11 08:04] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2016-03-11 08:04] [ALPM-SCRIPTLET] ==> Starting build: 4.4.5-1-ARCH
[2016-03-11 08:04] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2016-03-11 08:04] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2016-03-11 08:04] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2016-03-11 08:04] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2016-03-11 08:04] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2016-03-11 08:04] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2016-03-11 08:04] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
[2016-03-11 08:04] [ALPM-SCRIPTLET]   -> Running build hook: [encrypt]
[2016-03-11 08:04] [ALPM-SCRIPTLET]   -> Running build hook: [lvm2]
[2016-03-11 08:04] [ALPM-SCRIPTLET]   -> Running build hook: [resume]
[2016-03-11 08:04] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2016-03-11 08:04] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2016-03-11 08:04] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2016-03-11 08:04] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
[2016-03-11 08:04] [ALPM-SCRIPTLET] ==> Image generation successful
[2016-03-11 08:04] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2016-03-11 08:04] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2016-03-11 08:04] [ALPM-SCRIPTLET] ==> Starting build: 4.4.5-1-ARCH
[2016-03-11 08:04] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2016-03-11 08:04] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2016-03-11 08:04] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2016-03-11 08:04] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2016-03-11 08:04] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2016-03-11 08:04] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: wd719x
[2016-03-11 08:04] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2016-03-11 08:04] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
[2016-03-11 08:04] [ALPM-SCRIPTLET]   -> Running build hook: [encrypt]
[2016-03-11 08:04] [ALPM-SCRIPTLET]   -> Running build hook: [lvm2]
[2016-03-11 08:04] [ALPM-SCRIPTLET]   -> Running build hook: [resume]
[2016-03-11 08:04] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2016-03-11 08:04] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2016-03-11 08:04] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2016-03-11 08:04] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
[2016-03-11 08:04] [ALPM-SCRIPTLET] ==> Image generation successful
[2016-03-11 08:04] [ALPM] upgraded linux-headers (4.4.3-1 -> 4.4.5-1)
[2016-03-11 08:04] [ALPM] warning: /etc/pacman.d/mirrorlist installed as /etc/pacman.d/mirrorlist.pacnew
[2016-03-11 08:04] [ALPM] upgraded pacman-mirrorlist (20160227-1 -> 20160310-5)
[2016-03-11 08:04] [ALPM] upgraded smbclient (4.3.5-1 -> 4.3.6-1)
[2016-03-11 08:04] [ALPM] installed spice-glib (0.30-3)
[2016-03-11 08:04] [ALPM] upgraded spice-gtk3 (0.30-2 -> 0.30-3)
[2016-03-11 08:04] [ALPM] upgraded vim-runtime (7.4.1386-1 -> 7.4.1529-1)
[2016-03-11 08:04] [ALPM] upgraded vim (7.4.1386-1 -> 7.4.1529-1)
[2016-03-11 08:04] [ALPM] transaction completed

dmesg output from failed lightdm:

[   31.070653] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready
[   31.072207] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[   31.282177] r8169 0000:03:00.0 enp3s0: link down
[   31.282308] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[   85.918699] systemd-journald[286]: File /var/log/journal/c4397d915dd544a7bb2aeab40044fce4/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
[  240.291139] INFO: task kworker/0:2:298 blocked for more than 120 seconds.
[  240.293194]       Not tainted 4.4.5-1-ARCH #1
[  240.295577] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  240.297934] kworker/0:2     D ffff880036d07d28     0   298      2 0x00000000
[  240.297950] Workqueue: events output_poll_execute [drm_kms_helper]
[  240.297954]  ffff880036d07d28 0000000000000000 ffffffff81810500 ffff88003698b200
[  240.297959]  ffff880036d08000 ffff8800967e4a04 ffff88003698b200 00000000ffffffff
[  240.297963]  ffff8800967e4a08 ffff880036d07d40 ffffffff815935ec ffff8800967e4a00
[  240.297968] Call Trace:
[  240.297980]  [<ffffffff815935ec>] schedule+0x3c/0x90
[  240.297985]  [<ffffffff815939c5>] schedule_preempt_disabled+0x15/0x20
[  240.297991]  [<ffffffff81594e6e>] __mutex_lock_slowpath+0xce/0x140
[  240.297996]  [<ffffffff81594ef7>] mutex_lock+0x17/0x30
[  240.298003]  [<ffffffffa05627a0>] output_poll_execute+0x60/0x1e0 [drm_kms_helper]
[  240.298014]  [<ffffffff8108f5bb>] process_one_work+0x14b/0x480
[  240.298019]  [<ffffffff8108f938>] worker_thread+0x48/0x4a0
[  240.298023]  [<ffffffff8108f8f0>] ? process_one_work+0x480/0x480
[  240.298028]  [<ffffffff8108f8f0>] ? process_one_work+0x480/0x480
[  240.298032]  [<ffffffff810953d8>] kthread+0xd8/0xf0
[  240.298036]  [<ffffffff81095300>] ? kthread_worker_fn+0x170/0x170
[  240.298040]  [<ffffffff8159743f>] ret_from_fork+0x3f/0x70
[  240.298044]  [<ffffffff81095300>] ? kthread_worker_fn+0x170/0x170
[  240.298056] INFO: task Xorg.wrap:581 blocked for more than 120 seconds.
[  240.300371]       Not tainted 4.4.5-1-ARCH #1
[  240.302683] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  240.304285] Xorg.wrap       D ffff880092baf8a8     0   581    568 0x00000000
[  240.304288]  ffff880092baf8a8 0000c619cdcdcdcd ffffffff81810500 ffff8800963a2580
[  240.304291]  ffff880092bb0000 ffff880152bdb148 ffff880152bdb208 0000000000000000
[  240.304293]  ffff880092baf900 ffff880092baf8c0 ffffffff815935ec ffff880152bdb098
[  240.304295] Call Trace:
[  240.304298]  [<ffffffff815935ec>] schedule+0x3c/0x90
[  240.304303]  [<ffffffff813f9bb5>] rpm_resume+0x215/0x6c0
[  240.304309]  [<ffffffff810b8cc0>] ? wake_atomic_t_function+0x60/0x60
[  240.304311]  [<ffffffff813fa09f>] __pm_runtime_resume+0x3f/0x60
[  240.304338]  [<ffffffffa078dda6>] radeon_dvi_detect+0x36/0x570 [radeon]
[  240.304348]  [<ffffffff8108e6f3>] ? __queue_delayed_work+0x83/0x180
[  240.304352]  [<ffffffffa056306a>] drm_helper_hpd_irq_event+0xaa/0x160 [drm_kms_helper]
[  240.304364]  [<ffffffffa076991c>] radeon_resume_kms+0x21c/0x3d0 [radeon]
[  240.304374]  [<ffffffffa076713f>] radeon_pmops_runtime_resume+0x6f/0xa0 [radeon]
[  240.304378]  [<ffffffff8131069b>] pci_pm_runtime_resume+0x7b/0xa0
[  240.304381]  [<ffffffff813e6c70>] ? vga_switcheroo_set_dynamic_switch+0x80/0x80
[  240.304383]  [<ffffffff813e6cbd>] vga_switcheroo_runtime_resume+0x4d/0x50
[  240.304386]  [<ffffffff813f8a42>] __rpm_callback+0x32/0x70
[  240.304388]  [<ffffffff813e6c70>] ? vga_switcheroo_set_dynamic_switch+0x80/0x80
[  240.304390]  [<ffffffff813f8aa4>] rpm_callback+0x24/0x80
[  240.304392]  [<ffffffff813e6c70>] ? vga_switcheroo_set_dynamic_switch+0x80/0x80
[  240.304394]  [<ffffffff813f9e4f>] rpm_resume+0x4af/0x6c0
[  240.304397]  [<ffffffff813fa09f>] __pm_runtime_resume+0x3f/0x60
[  240.304409]  [<ffffffffa076b616>] radeon_driver_open_kms+0x36/0x1b0 [radeon]
[  240.304418]  [<ffffffffa04fc834>] drm_open+0x1c4/0x410 [drm]
[  240.304427]  [<ffffffffa0502f29>] drm_stub_open+0xa9/0x100 [drm]
[  240.304430]  [<ffffffff811e5b2e>] chrdev_open+0xae/0x1d0
[  240.304434]  [<ffffffff811df18f>] do_dentry_open+0x1ff/0x300
[  240.304436]  [<ffffffff811e5a80>] ? cdev_put+0x30/0x30
[  240.304439]  [<ffffffff811e02f6>] vfs_open+0x56/0x60
[  240.304441]  [<ffffffff811ee80c>] path_openat+0x17c/0x1150
[  240.304448]  [<ffffffffa0517eb6>] ? drm_modeset_unlock_all+0x36/0x60 [drm]
[  240.304450]  [<ffffffff811f0cd1>] do_filp_open+0x91/0x100
[  240.304454]  [<ffffffff811fff5c>] ? mntput_no_expire+0x2c/0x1b0
[  240.304456]  [<ffffffff811fd967>] ? __alloc_fd+0xc7/0x190
[  240.304461]  [<ffffffff811e06c6>] do_sys_open+0x146/0x230
[  240.304463]  [<ffffffff811e07ce>] SyS_open+0x1e/0x20
[  240.304466]  [<ffffffff815970ee>] entry_SYSCALL_64_fastpath+0x12/0x6d

dmesg output after successful login:

[   32.898396] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready
[   32.899629] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[   33.006858] r8169 0000:03:00.0 enp3s0: link down
[   33.006981] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[   42.321102] fuse init (API version 7.23)
[   44.432029] snd_hda_intel 0000:01:00.1: Disabling via vga_switcheroo
[   53.632445] traps: lightdm-webkit2[657] trap invalid opcode ip:402120 sp:7ffe52af0ba0 error:0 in lightdm-webkit2-greeter[400000+3000]
[   74.967609] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[  125.675306] usb 2-1.2: new high-speed USB device number 5 using ehci-pci
[  125.764498] usb-storage 2-1.2:1.0: USB Mass Storage device detected
[  125.765118] scsi host7: usb-storage 2-1.2:1.0
[  125.765582] usb-storage 2-1.2:1.1: USB Mass Storage device detected
[  125.765818] scsi host8: usb-storage 2-1.2:1.1
[  126.514094] usb 2-1.2: USB disconnect, device number 5
[  126.698633] usb 2-1.2: new high-speed USB device number 6 using ehci-pci
[  126.784364] usb-storage 2-1.2:1.3: USB Mass Storage device detected
[  126.784551] scsi host9: usb-storage 2-1.2:1.3
[  127.786406] scsi 9:0:0:0: Direct-Access     USBModem Mass storage     2.31 PQ: 0 ANSI: 2
[  127.786969] scsi 9:0:0:1: Direct-Access     USBModem Mass storage     2.31 PQ: 0 ANSI: 2
[  127.793090] sd 9:0:0:0: [sdc] Attached SCSI removable disk
[  127.793706] sd 9:0:0:1: [sdd] Attached SCSI removable disk
[  135.474419] usb 2-1.2: USB disconnect, device number 6
[  135.741946] usb 2-1.2: new high-speed USB device number 7 using ehci-pci
[  135.864859] usbcore: registered new interface driver cdc_ether
[  135.875854] rndis_host 2-1.2:1.0 usb0: register 'rndis_host' at usb-0000:00:1d.0-1.2, RNDIS device, b2:84:29:ba:05:de
[  135.875880] usbcore: registered new interface driver rndis_host
[  135.882463] rndis_host 2-1.2:1.0 enp0s29u1u2: renamed from usb0
[  135.903141] IPv6: ADDRCONF(NETDEV_UP): enp0s29u1u2: link is not ready

Last edited by adhokshajm (2016-03-12 06:17:46)

I have become death, the destroyer of worlds.

Offline

#2 2016-03-13 14:07:35

saae
Member
From: Paris
Registered: 2016-03-13
Posts: 1

Re: LightDM fails to load after system upgrade

Same problem here while updating to kernel 4.4.5, only solution was to downgrade.

I see you are also using radeon, maybe this comes from there.

Offline

#3 2016-03-14 10:03:44

robin67
Member
From: the Netherlands
Registered: 2012-02-18
Posts: 45

Re: LightDM fails to load after system upgrade

No issues here

Running without issues these packages now
  linux 4.4.5-1
  lightdm 1:1.16.7-3
  lightdm-gtk-greeter 1:2.0.1-2

Offline

#4 2016-03-15 08:03:32

francistw
Member
From: Taiwan
Registered: 2016-01-27
Posts: 1

Re: LightDM fails to load after system upgrade

Also stuck in login screen after upgrade the kernel to 4.4.5 with ati driver, but mine is SDDM rather than LightDM.

Downgrading the kernel just solved it.

Offline

#5 2016-03-24 09:22:03

hellmelt
Member
Registered: 2016-03-24
Posts: 4

Re: LightDM fails to load after system upgrade

I had the same issue, had to downgrade the kernel.

Since I'm quite new to Arch, I wonder what will happen with this bug in the future? When the next kernel version is available, will pacman -Syu upgrade the kernel, even though I have explicitly downgraded? And if the bug still is there, I have to downgrade again, I suppose.

Offline

#6 2016-03-24 10:18:41

fredbezies
Member
Registered: 2011-07-28
Posts: 353

Re: LightDM fails to load after system upgrade

So it is not a kernel issue but an ATI driver one. Again ?!

Offline

#7 2016-03-25 06:27:19

robin67
Member
From: the Netherlands
Registered: 2012-02-18
Posts: 45

Re: LightDM fails to load after system upgrade

hellmelt wrote:

I had the same issue, had to downgrade the kernel.

Since I'm quite new to Arch, I wonder what will happen with this bug in the future? When the next kernel version is available, will pacman -Syu upgrade the kernel, even though I have explicitly downgraded? And if the bug still is there, I have to downgrade again, I suppose.

If you're worried it will not be updated by then you can use the option IgnorePkg=linux as described here

Last edited by robin67 (2016-03-25 06:27:52)

Offline

#8 2016-04-08 08:15:18

hellmelt
Member
Registered: 2016-03-24
Posts: 4

Re: LightDM fails to load after system upgrade

Does anyone know if this bug is reported, and if it will be fixed in some future release?

Last edited by hellmelt (2016-04-08 08:16:23)

Offline

#9 2016-04-17 10:18:52

Sarai
Member
From: Alaska
Registered: 2010-02-20
Posts: 62

Re: LightDM fails to load after system upgrade

Is this the same problem as here? I posted a fix for the lightDM greeter failing to load there.

Offline

Pages: 1

Board footer

Powered by FluxBB