Skip to content

QGIS crashes when opening print layout #64218

@larsks

Description

@larsks

What is the bug or the crash?

When I attempt to open a print layout in my project, QGIS crashes with the following traceback:

(qgis:4113683): Gtk-WARNING **: 20:56:12.400: Theme parsing error: <data>:1:0: Expected a valid selector
QGIS died on signal 11

...

#0  0x00007f0dc0888462 in __syscall_cancel_arch () at /lib64/libc.so.6
#1  0x00007f0dc087c75c in __internal_syscall_cancel () at /lib64/libc.so.6
#2  0x00007f0dc087c7a4 in __syscall_cancel () at /lib64/libc.so.6
#3  0x00007f0dc08ecc0f in wait4 () at /lib64/libc.so.6
#4  0x0000560bd5826d26 in qgisCrash(int) ()
#5  0x00007f0dc0828070 in <signal handler called> () at /lib64/libc.so.6
#6  0x00007f0dc0881e9c in __pthread_kill_implementation () at /lib64/libc.so.6
#7  0x00007f0dc0827f3e in raise () at /lib64/libc.so.6
#8  0x00007f0dc0828070 in <signal handler called> () at /lib64/libc.so.6
#9  0x00007f0dc1c1fefb in QgsLayoutItemElevationProfile::recreateCachedImageInBackground() () at /lib64/libqgis_core.so.3.44.5
#10 0x00007f0dc3455235 in void doActivate<false>(QObject*, int, void**) () at /lib64/libQt5Core.so.5
#11 0x00007f0dc345965d in QTimer::timeout(QTimer::QPrivateSignal) () at /lib64/libQt5Core.so.5
#12 0x00007f0dc344cb7f in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5
#13 0x00007f0dc4040ef7 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5
#14 0x00007f0dc19106d2 in QgsApplication::notify(QObject*, QEvent*) () at /lib64/libqgis_core.so.3.44.5
#15 0x00007f0dc341f778 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5
#16 0x00007f0dc347427c in QTimerInfoList::activateTimers() () at /lib64/libQt5Core.so.5
#17 0x00007f0dc3474ba9 in timerSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5
#18 0x00007f0db98eb863 in g_main_context_dispatch_unlocked.lto_priv () at /lib64/libglib-2.0.so.0
#19 0x00007f0db98f47a8 in g_main_context_iterate_unlocked.isra () at /lib64/libglib-2.0.so.0
#20 0x00007f0db98f4953 in g_main_context_iteration () at /lib64/libglib-2.0.so.0
#21 0x00007f0dc3474f67 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#22 0x00007f0dc341e0e2 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#23 0x00007f0dc34264c4 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5
#24 0x0000560bd5821beb in main ()

Steps to reproduce the issue

This crash seems easy to reproduce:

  1. Add an DEM layer to your project
  2. Create an elevation profile
  3. Create a print layout
  4. Add an elevation profile to the print layout
  5. Populate it by using "copy from elevation profile"
  6. Remove the elevation layer from the project

Now QGIS will crash when you attempt to open the print layout.

If the data required by the print layout is missing, it should render an empty elevation profile and log an error rather than crashing.

Versions

QGIS version3.44.5-Solothurn
QGIS code branchRelease 3.44
 
Libraries
Qt version5.15.18
Python version3.13.9
GDAL version3.10.3
PROJ version9.6.2
EPSG Registry database versionv12.013 (2025-05-26)
GEOS version3.13.0-CAPI-1.19.0
SQLite version3.47.2
PDAL version2.8.4
PostgreSQL client version16.4
SpatiaLite version5.1.0
QWT version6.2.0
QScintilla2 version2.14.1
OS versionFedora Linux 42 (Workstation Edition)
 
Active Python plugins
basemaps1.4
qgis-maptiler-plugin3.5.1
quick_map_services1.1.0
QuickOSM2.4.1
osminfo1.2.2
SRTM-Downloader3.3.1
MetaSearch0.3.6
db_manager0.1.20
grassprovider2.12.99
processing2.12.99

Supported QGIS version

  • I'm running a supported QGIS version according to the roadmap.

New profile

Additional context

No response

Metadata

Metadata

Assignees

Labels

BugEither a bug report, or a bug fix. Let's hope for the latter!Crash/Data CorruptionPrint LayoutsRelated to QGIS Print Layouts, Atlas or Reporting frameworksProfile toolRegressionSomething which used to work, but doesn't anymore

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions