Your message dated Thu, 22 Sep 2016 18:48:12 -0700
with message-id <3fc60b5e-2dfd-ab44-37a0-e04edcfc2...@aoi.dyndns.org>
and subject line Re: sddm: Greeter segfaults on startup
has caused the Debian Bug report #837552,
regarding sddm: Greeter segfaults on startup
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
837552: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837552
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sddm
Version: 0.13.0-1
Severity: important
After updating to this version, the greeter now segfaults on start. `startx`
into Plasma works fine (I'm reporting this bug from there).
gdb backtrace of the crashing thread:
#0 QFontconfigDatabase::populateFontDatabase (this=<optimized out>) at
fontdatabases/fontconfig/qfontconfigdatabase.cpp:500
#1 0x00007f73dca696d9 in initializeDb () at text/qfontdatabase.cpp:889
#2 0x00007f73dca6e5c5 in QFontDatabase::findFont (request=...,
script=script@entry=2) at text/qfontdatabase.cpp:2633
#3 0x00007f73dca6f0c7 in QFontDatabase::load (d=d@entry=0x95dc90,
script=script@entry=2) at text/qfontdatabase.cpp:2788
#4 0x00007f73dca44c8a in QFontPrivate::engineForScript (this=0x95dc90,
script=script@entry=2) at text/qfont.cpp:212
#5 0x00007f73dca7676d in QTextEngine::fontEngine
(this=this@entry=0x7fff78a4dd20, si=..., ascent=ascent@entry=0xb6f074,
descent=descent@entry=0xb6f070, leading=leading@entry=0xb6f078) at
text/qtextengine.cpp:2084
#6 0x00007f73dca774a7 in QTextEngine::shapeText
(this=this@entry=0x7fff78a4dd20, item=item@entry=0) at text/qtextengine.cpp:994
#7 0x00007f73dca781d0 in QTextEngine::shape (this=this@entry=0x7fff78a4dd20,
item=item@entry=0) at text/qtextengine.cpp:1528
#8 0x00007f73dca7e870 in QTextEngine::boundingBox
(this=this@entry=0x7fff78a4dd20, from=from@entry=0, len=<optimized out>) at
text/qtextengine.cpp:1865
#9 0x00007f73dca62451 in QFontMetrics::boundingRect (this=<optimized out>,
text=...) at text/qfontmetrics.cpp:673
#10 0x00007f73c61e92c0 in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/core/libcorebindingsplugin.so
#11 0x00007f73c61e969e in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/core/libcorebindingsplugin.so
#12 0x00007f73c61c4f56 in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/core/libcorebindingsplugin.so
#13 0x00007f73dd26a07a in QQmlThread::internalCallMethodInThread
(this=0x982a20, message=<optimized out>) at qml/ftw/qqmlthread.cpp:315
#14 0x00007f73dd203195 in QQmlThread::callMethodInThread<QQmlDataBlob*,
QQmlDataBlob*, QQmlTypeLoaderThread> (arg=<synthetic pointer>,
Member=<optimized out>, this=<optimized out>) at
../../include/QtQml/5.6.1/QtQml/private/../../../../../src/qml/qml/ftw/qqmlthread_p.h:159
#15 QQmlTypeLoaderThread::load (this=<optimized out>, b=b@entry=0x0) at
qml/qqmltypeloader.cpp:754
#16 0x00007f73dd211799 in PlainLoader::load (this=<optimized out>,
loader=0xb43f10, blob=0x0) at qml/qqmltypeloader.cpp:921
#17 QQmlTypeLoader::doLoad<PlainLoader> (this=0xb43f10, loader=..., blob=0x0,
mode=QQmlTypeLoader::PreferSynchronous) at qml/qqmltypeloader.cpp:985
#18 0x00007f73dd20a4d1 in QQmlTypeLoader::load
(mode=QQmlTypeLoader::PreferSynchronous, blob=0xb43f10, this=0x9b8ed8) at
qml/qqmltypeloader.cpp:1008
#19 QQmlTypeLoader::getType (this=0x9b8ed8, url=...,
mode=QQmlTypeLoader::PreferSynchronous) at qml/qqmltypeloader.cpp:1644
#20 0x00007f73dd1ec079 in QQmlComponentPrivate::loadUrl (this=0xb43de0,
newUrl=..., mode=QQmlComponent::PreferSynchronous) at qml/qqmlcomponent.cpp:672
#21 0x00007f73dd5e510a in QQuickViewPrivate::execute (this=0x97ef50) at
items/qquickview.cpp:125
#22 0x00007f73dd5e529a in QQuickView::setSource (this=this@entry=0x96ffb0,
url=...) at items/qquickview.cpp:256
#23 0x0000000000428abe in SDDM::GreeterApp::addViewForScreen
(this=this@entry=0x7fff78a50cf0, screen=0x93cae0) at
/build/sddm-Wa20od/sddm-0.13.0/src/greeter/GreeterApp.cpp:199
#24 0x0000000000429b98 in SDDM::GreeterApp::GreeterApp (this=0x7fff78a50cf0,
argc=<optimized out>, argv=<optimized out>) at
/build/sddm-Wa20od/sddm-0.13.0/src/greeter/GreeterApp.cpp:134
#25 0x0000000000414833 in main (argc=5, argv=0x7fff78a50e78) at
/build/sddm-Wa20od/sddm-0.13.0/src/greeter/GreeterApp.cpp:231
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.7.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages sddm depends on:
ii adduser 3.115
ii debconf [debconf-2.0] 1.5.59
ii libc6 2.24-2
ii libgcc1 1:6.2.0-3
ii libpam0g 1.1.8-3.3
ii libqt5core5a 5.6.1+dfsg-3+b1
ii libqt5dbus5 5.6.1+dfsg-3+b1
ii libqt5gui5 5.6.1+dfsg-3+b1
ii libqt5network5 5.6.1+dfsg-3+b1
ii libqt5qml5 5.6.1-8
ii libqt5quick5 5.6.1-8
ii libstdc++6 6.2.0-3
ii libsystemd0 231-6
ii libxcb-xkb1 1.11.1-1.1
ii libxcb1 1.11.1-1.1
ii qml-module-qtquick2 5.6.1-8
ii sddm-theme-breeze [sddm-theme] 4:5.7.4-1
ii sddm-theme-circles [sddm-theme] 0.13.0-1
ii sddm-theme-elarun [sddm-theme] 0.13.0-1
ii sddm-theme-maldives [sddm-theme] 0.13.0-1
ii sddm-theme-maui [sddm-theme] 0.13.0-1
Versions of packages sddm recommends:
ii libpam-systemd 231-6
Versions of packages sddm suggests:
ii libpam-kwallet5 5.7.4-1
-- debconf information:
* shared/default-x-display-manager: sddm
sddm/daemon_name: /usr/bin/sddm
--- End Message ---
--- Begin Message ---
I have found the cause of the problem: my system had excessively strict
resource limits set in /etc/security/limits.conf, which was preventing
sddm-greeter from allocating enough memory. After removing the limits,
sddm works correctly.
A segfault isn't really the most intuitive response to running out of
memory. However, I gather it is fairly commonplace to not check for
memory allocation failure, so sddm can hardly be blamed for following
that practice.
So, I'm closing this bug. Sorry for the mostly-false alarm.
--- End Message ---
