You are not logged in.

Pages: 1

#1 2016-12-01 13:53:55

random_xyz
Member
Registered: 2015-07-01
Posts: 10

SOLVED: SDDM fails to start

After the upgrade of icu from 57.1 to 58.1, sddm refuses to start, and complains about missing shared libraries. Downgrading fixes the issue. Does anyone else have this problem?

Last edited by random_xyz (2016-12-01 16:23:31)

Offline

#2 2016-12-01 14:35:35

mrunion
Member
From: Jonesborough, TN
Registered: 2007-01-26
Posts: 1,938
Website

Re: SOLVED: SDDM fails to start

Post your pacman log from the update so we can see what was updated.

Matt

"It is very difficult to educate the educated."

Offline

#3 2016-12-01 15:41:20

random_xyz
Member
Registered: 2015-07-01
Posts: 10

Re: SOLVED: SDDM fails to start

Logs for the two upgrades I performed before I rebooted and noticed this problem.

[2016-11-29 20:45] [PACMAN] Running 'pacman -S -y -u --noconfirm'
[2016-11-29 20:45] [PACMAN] synchronizing package lists
[2016-11-29 20:46] [PACMAN] starting full system upgrade
[2016-11-29 20:56] [ALPM] transaction started
[2016-11-29 20:56] [ALPM] upgraded icu (57.1-1 -> 58.1-2)
[2016-11-29 20:56] [ALPM] upgraded boost-libs (1.62.0-3 -> 1.62.0-4)
[2016-11-29 20:57] [ALPM] upgraded boost (1.62.0-3 -> 1.62.0-4)
[2016-11-29 20:57] [ALPM] upgraded harfbuzz (1.3.3-1 -> 1.3.3-2)
[2016-11-29 20:57] [ALPM] upgraded libsystemd (232-3 -> 232-4)
[2016-11-29 20:57] [ALPM] upgraded llvm-libs (3.9.0-2 -> 3.9.0-3)
[2016-11-29 20:57] [ALPM] upgraded systemd (232-3 -> 232-4)
[2016-11-29 20:57] [ALPM] upgraded sonnet (5.28.0-1 -> 5.28.0-3)
[2016-11-29 20:57] [ALPM] upgraded kio-extras (16.08.3-1 -> 16.11.80-1)
[2016-11-29 20:57] [ALPM] upgraded poppler (0.47.0-1 -> 0.49.0-1)
[2016-11-29 20:57] [ALPM] upgraded poppler-qt5 (0.47.0-1 -> 0.49.0-1)
[2016-11-29 20:57] [ALPM] upgraded dolphin (16.08.3-1 -> 16.11.80-1)
[2016-11-29 20:57] [ALPM] upgraded hunspell (1.4.1-2 -> 1.5.3-1)
[2016-11-29 20:57] [ALPM] upgraded firefox (50.0-1 -> 50.0.1-1)
[2016-11-29 20:57] [ALPM] upgraded qt5-webkit (5.7.0-1 -> 5.7.0-2)
[2016-11-29 20:57] [ALPM] upgraded systemd-sysvcompat (232-3 -> 232-4)
[2016-11-29 20:57] [ALPM] transaction completed
[2016-11-29 20:57] [ALPM] running '99-linux.hook'...
[2016-11-29 20:57] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2016-11-29 20:57] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2016-11-29 20:57] [ALPM-SCRIPTLET] ==> Starting build: 4.8.11-1-ARCH
[2016-11-29 20:57] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2016-11-29 20:57] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2016-11-29 20:57] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2016-11-29 20:57] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2016-11-29 20:57] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2016-11-29 20:57] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2016-11-29 20:57] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2016-11-29 20:57] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2016-11-29 20:57] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2016-11-29 20:57] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
[2016-11-29 20:57] [ALPM-SCRIPTLET] ==> Image generation successful
[2016-11-29 20:57] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2016-11-29 20:57] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2016-11-29 20:57] [ALPM-SCRIPTLET] ==> Starting build: 4.8.11-1-ARCH
[2016-11-29 20:57] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2016-11-29 20:57] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2016-11-29 20:57] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2016-11-29 20:57] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2016-11-29 20:57] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: wd719x
[2016-11-29 20:57] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2016-11-29 20:57] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2016-11-29 20:57] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2016-11-29 20:57] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2016-11-29 20:57] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2016-11-29 20:57] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
[2016-11-29 20:57] [ALPM-SCRIPTLET] ==> Image generation successful
[2016-11-29 20:57] [ALPM] running 'gtk-update-icon-cache.hook'...
[2016-11-29 20:57] [ALPM] running 'udev-hwdb.hook'...
[2016-11-29 20:57] [ALPM] running 'update-desktop-database.hook'...
[2016-11-29 20:57] [ALPM] running 'update-mime-database.hook'...
[2016-11-30 19:33] [PACMAN] Running 'pacman -S -y -u --noconfirm'
[2016-11-30 19:33] [PACMAN] synchronizing package lists
[2016-11-30 19:34] [PACMAN] starting full system upgrade
[2016-11-30 19:36] [ALPM] transaction started
[2016-11-30 19:36] [ALPM] upgraded ca-certificates-mozilla (3.27.1-1 -> 3.27.2-1)
[2016-11-30 19:36] [ALPM] upgraded dbus (1.10.12-1 -> 1.10.14-1)
[2016-11-30 19:36] [ALPM] upgraded gstreamer (1.10.1-1 -> 1.10.2-1)
[2016-11-30 19:36] [ALPM] upgraded gst-plugins-base-libs (1.10.1+1+g1f4da6d-1 -> 1.10.2-1)
[2016-11-30 19:36] [ALPM] upgraded libdrm (2.4.73-1 -> 2.4.74-1)
[2016-11-30 19:36] [ALPM] upgraded mesa (13.0.1-1 -> 13.0.2-1)
[2016-11-30 19:36] [ALPM] upgraded mesa-libgl (13.0.1-1 -> 13.0.2-1)
[2016-11-30 19:36] [ALPM] upgraded gst-plugins-base (1.10.1+1+g1f4da6d-1 -> 1.10.2-1)
[2016-11-30 19:36] [ALPM] upgraded sqlite (3.15.1-2 -> 3.15.2-1)
[2016-11-30 19:36] [ALPM] upgraded nss (3.27.1-1 -> 3.27.2-1)
[2016-11-30 19:36] [ALPM] transaction completed
[2016-11-30 19:36] [ALPM] running 'update-ca-trust.hook'...

FWIW, the testing repos are enabled. I tried disabling them and running

pacman -Syyuu

but the problem still persisted.

The error I was talking about was

Dec 01 20:49:54 arch-testing sddm[290]: /usr/bin/sddm: error while loading shared libraries: libicui18n.so.57: cannot open shared object file: No such file or directory

I tried making a symbolic link from /usr/lib/libicui18n.so.57 to /usr/lib/libicui18n.so.58, but then it complained about other libraries.

Offline

#4 2016-12-01 15:50:09

Scimmia
Fellow
Registered: 2012-09-01
Posts: 13,729

Re: SOLVED: SDDM fails to start

What is the output of 

pacman -Qm

Offline

#5 2016-12-01 15:59:19

random_xyz
Member
Registered: 2015-07-01
Posts: 10

Re: SOLVED: SDDM fails to start

kishore@arch-testing ~ % pacman -Qm
baloo-widgets-git r417.7f94bb2-1
cower 16-1
log4cxx 0.10.0-4
okular-git r7458.fe6b5eb-1
pacaur 4.6.10-1
plasma5-applets-active-window-control-git r55.3b373e6-1
start-stop-daemon 1.17.27-1
ttf-oxygen-git 5.4.90.r170.5f935c7-1
vivaldi 1.5.658.44-1

Offline

#6 2016-12-01 16:07:15

Scimmia
Fellow
Registered: 2012-09-01
Posts: 13,729

Re: SOLVED: SDDM fails to start

I see 3 KDE related packages there, but I don't think any of them would be related to sddm.

Try installing the pax-utils package, then run 

lddtree /usr/bin/sddm

This should tell you exactly what file is linked to the old version.

Offline

#7 2016-12-01 16:12:40

random_xyz
Member
Registered: 2015-07-01
Posts: 10

Re: SOLVED: SDDM fails to start

This is from the affected machine

1 kishore@arch-testing ~ % lddtree /usr/bin/sddm                                                                                                                                               :(
sddm => /usr/bin/sddm (interpreter => /lib64/ld-linux-x86-64.so.2)
    libQt5DBus.so.5 => /usr/lib/libQt5DBus.so.5
        libpthread.so.0 => /usr/lib/libpthread.so.0
            ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2
        libdbus-1.so.3 => /usr/lib/libdbus-1.so.3
    libQt5Qml.so.5 => /usr/lib/libQt5Qml.so.5
        libm.so.6 => /usr/lib/libm.so.6
    libsystemd.so.0 => /usr/lib/libsystemd.so.0
        libresolv.so.2 => /usr/lib/libresolv.so.2
        libcap.so.2 => /usr/lib/libcap.so.2
        librt.so.1 => /usr/lib/librt.so.1
        liblzma.so.5 => /usr/lib/liblzma.so.5
        liblz4.so.1 => /usr/lib/liblz4.so.1
        libgcrypt.so.20 => /usr/lib/libgcrypt.so.20
        libgpg-error.so.0 => /usr/lib/libgpg-error.so.0
    libQt5Network.so.5 => /usr/lib/libQt5Network.so.5
        libz.so.1 => /usr/lib/libz.so.1
        libproxy.so.1 => /usr/lib/libproxy.so.1
            libdl.so.2 => /usr/lib/libdl.so.2
        libssl.so.1.0.0 => /usr/lib/libssl.so.1.0.0
        libcrypto.so.1.0.0 => /usr/lib/libcrypto.so.1.0.0
    libQt5Core.so.5 => /usr/lib/libQt5Core.so.5
        libicui18n.so.57 => /usr/lib/libicui18n.so.57
        libicuuc.so.57 => /usr/lib/libicuuc.so.57
            libicudata.so.57 => /usr/lib/libicudata.so.57
        libpcre16.so.0 => /usr/lib/libpcre16.so.0
        libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0
            libpcre.so.1 => /usr/lib/libpcre.so.1
    libstdc++.so.6 => /usr/lib/libstdc++.so.6
    libgcc_s.so.1 => /usr/lib/libgcc_s.so.1
    libc.so.6 => /usr/lib/libc.so.6
kishore@arch-testing ~ % pQ sddm
sddm 0.14.0-2

And this is from another machine. 

kishore@kishore-inspiron-3537 ~> lddtree /usr/bin/sddm
sddm => /usr/bin/sddm (interpreter => /lib64/ld-linux-x86-64.so.2)
    libQt5DBus.so.5 => /usr/lib/libQt5DBus.so.5
        libpthread.so.0 => /usr/lib/libpthread.so.0
            ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2
        libdbus-1.so.3 => /usr/lib/libdbus-1.so.3
    libQt5Qml.so.5 => /usr/lib/libQt5Qml.so.5
        libm.so.6 => /usr/lib/libm.so.6
    libsystemd.so.0 => /usr/lib/libsystemd.so.0
        libresolv.so.2 => /usr/lib/libresolv.so.2
        libcap.so.2 => /usr/lib/libcap.so.2
        librt.so.1 => /usr/lib/librt.so.1
        liblzma.so.5 => /usr/lib/liblzma.so.5
        liblz4.so.1 => /usr/lib/liblz4.so.1
        libgcrypt.so.20 => /usr/lib/libgcrypt.so.20
        libgpg-error.so.0 => /usr/lib/libgpg-error.so.0
    libQt5Network.so.5 => /usr/lib/libQt5Network.so.5
        libz.so.1 => /usr/lib/libz.so.1
        libproxy.so.1 => /usr/lib/libproxy.so.1                                                                                                                        
            libdl.so.2 => /usr/lib/libdl.so.2                                                                                                                          
        libssl.so.1.0.0 => /usr/lib/libssl.so.1.0.0                                                                                                                    
        libcrypto.so.1.0.0 => /usr/lib/libcrypto.so.1.0.0                                                                                                              
    libQt5Core.so.5 => /usr/lib/libQt5Core.so.5                                                                                                                        
        libicui18n.so.58 => /usr/lib/libicui18n.so.58                                                                                                                  
        libicuuc.so.58 => /usr/lib/libicuuc.so.58                                                                                                                      
            libicudata.so.58 => /usr/lib/libicudata.so.58                                                                                                              
        libpcre16.so.0 => /usr/lib/libpcre16.so.0                                                                                                                      
        libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0                                                                                                                  
            libpcre.so.1 => /usr/lib/libpcre.so.1
    libstdc++.so.6 => /usr/lib/libstdc++.so.6
    libgcc_s.so.1 => /usr/lib/libgcc_s.so.1
    libc.so.6 => /usr/lib/libc.so.6
kishore@kishore-inspiron-3537 ~> pQ sddm
sddm 0.14.0-2

Both have the same sddm version, so I'm not sure why they link to different library versions.

Offline

#8 2016-12-01 16:19:39

Scimmia
Fellow
Registered: 2012-09-01
Posts: 13,729

Re: SOLVED: SDDM fails to start

Read it again. sddm isn't linked to icu, it's linked to libQt5Core.so.5, which is then linked to the various icu libraries. That's the file you should be checking out.

Offline

#9 2016-12-01 16:22:18

random_xyz
Member
Registered: 2015-07-01
Posts: 10

Re: SOLVED: SDDM fails to start

So the version of qt5-base I had on the problem machine was one I'd built with debug flags a few days ago. Installing the version from repos fixed the problem, although it was the same version number!

Last edited by random_xyz (2016-12-01 16:22:39)

Offline

#10 2016-12-01 16:24:14

random_xyz
Member
Registered: 2015-07-01
Posts: 10

Re: SOLVED: SDDM fails to start

Thanks for the help!

Offline

Pages: 1

Board footer

Powered by FluxBB