Bug 348262

Summary:	Parley doesn't start
Product:	[Applications] parley	Reporter:	Niklas <kde>
Component:	general	Assignee:	parley bug tracker <parley-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	j_hdorf, nate
Priority:	NOR	Keywords:	drkonqi
Version:	unspecified
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	New crash information added by DrKonqi

Description Niklas 2015-05-26 19:13:36 UTC

Application: parley (2.1.0)

Qt Version: 5.4.1
Operating System: Linux 4.0.4-301.fc22.x86_64 x86_64
Distribution: "Fedora release 22 (Twenty Two)"

-- Information about the crash:
- What I was doing when the application crashed:
Everytime I want to start Parley on Fedora 22 x64 it immediately crashes.
The system is more or less in its default state. I just installed Fedora 22 from scratch, updated the packages and installed a few tools. But I haven't changed any configurations.

The crash can be reproduced every time.

-- Backtrace:
Application: Parley (parley), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6f03c5e900 (LWP 2301))]

Thread 2 (Thread 0x7f6ee4819700 (LWP 2302)):
#0  0x00007f6efc45466d in poll () from /lib64/libc.so.6
#1  0x00007f6ef3c70182 in _xcb_conn_wait () from /lib64/libxcb.so.1
#2  0x00007f6ef3c71cff in xcb_wait_for_event () from /lib64/libxcb.so.1
#3  0x00007f6ee63615e9 in QXcbEventReader::run() () from /usr/lib64/qt5/plugins/platforms/libqxcb.so
#4  0x00007f6efd05eede in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5
#5  0x00007f6ef9f83555 in start_thread () from /lib64/libpthread.so.0
#6  0x00007f6efc45ff3d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f6f03c5e900 (LWP 2301)):
[KCrash Handler]
#5  0x00007f6efd782990 in QScreen::handle() const () from /lib64/libQt5Gui.so.5
#6  0x00007f6ee63721d8 in QXcbWindow::setParent(QPlatformWindow const*) () from /usr/lib64/qt5/plugins/platforms/libqxcb.so
#7  0x00007f6efd76374c in QWindow::setParent(QWindow*) () from /lib64/libQt5Gui.so.5
#8  0x00007f6efdf37a84 in QWidgetPrivate::setParent_sys(QWidget*, QFlags<Qt::WindowType>) () from /lib64/libQt5Widgets.so.5
#9  0x00007f6efdf4296a in QWidget::setParent(QWidget*, QFlags<Qt::WindowType>) () from /lib64/libQt5Widgets.so.5
#10 0x00007f6efdf438bc in QWidget::setParent(QWidget*) () from /lib64/libQt5Widgets.so.5
#11 0x00007f6efdf1f7fb in QLayout::addChildWidget(QWidget*) () from /lib64/libQt5Widgets.so.5
#12 0x00007f6efdf1f80f in QLayout::addWidget(QWidget*) () from /lib64/libQt5Widgets.so.5
#13 0x00000000004787ad in ParleyMainWindow::switchComponent(ParleyMainWindow::Component) ()
#14 0x000000000047961d in ParleyMainWindow::ParleyMainWindow(QUrl const&) ()
#15 0x0000000000476bc6 in main ()

Reported using DrKonqi

Comment 1 Johannes Herrnsdorf 2015-06-18 14:07:38 UTC

Created attachment 93224 [details]
New crash information added by DrKonqi

parley (2.1.0) using Qt 5.4.2

- What I was doing when the application crashed:
Parley crashes due to segmentation fault every time I try to start it in Fedora 22 workstation 64bit

-- Backtrace (Reduced):
#5  0x00007ffb2f1519f0 in QScreen::handle() const () from /lib64/libQt5Gui.so.5
#6  0x00007ffb17d3f4c8 in QXcbWindow::setParent(QPlatformWindow const*) () from /usr/lib64/qt5/plugins/platforms/libqxcb.so
#7  0x00007ffb2f13275c in QWindow::setParent(QWindow*) () from /lib64/libQt5Gui.so.5
#8  0x00007ffb2f906d05 in QWidgetPrivate::setParent_sys(QWidget*, QFlags<Qt::WindowType>) () from /lib64/libQt5Widgets.so.5
#9  0x00007ffb2f911bca in QWidget::setParent(QWidget*, QFlags<Qt::WindowType>) () from /lib64/libQt5Widgets.so.5

Comment 2 Andrew Crouthamel 2018-10-31 03:59:38 UTC

Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!

Comment 3 Niklas 2018-10-31 08:32:42 UTC

current version doesn't have the bug anymore. Ticket can be closed

Comment 4 Nate Graham 2021-02-08 19:24:07 UTC


*** This bug has been marked as a duplicate of bug 341497 ***