Bug 365174

Summary:	Crashed on start
Product:	[Applications] rkward	Reporter:	Ben <bwbees0>
Component:	general	Assignee:	RKWard Team <rkward-devel>
Status:	RESOLVED UPSTREAM
Severity:	crash	CC:	thomas.friedrichsmeier
Priority:	NOR	Keywords:	drkonqi, investigated, triaged
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Ben 2016-07-06 22:05:19 UTC

Application: rkward (0.6.5)
KDE Platform Version: 4.14.21
Qt Version: 4.8.7
Operating System: Linux 4.6.3-300.fc24.x86_64 x86_64
Distribution: "Fedora release 24 (Twenty Four)"

-- Information about the crash:
- What I was doing when the application crashed:

I just clicked the icon to start the application and it crashed.  Nothing else going on.

-- Backtrace:
Application: RKWard (rkward), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  0x00007f6afcd48e50 in  ()
#7  0x00007f6b23d6f3ef in QFactoryLoader::instance(QString const&) const () at /lib64/libQtCore.so.4
#8  0x00007f6b22aadce1 in QIcon::addFile(QString const&, QSize const&, QIcon::Mode, QIcon::State) () at /lib64/libQtGui.so.4
#9  0x00007f6b22aae02a in QIcon::QIcon(QString const&) () at /lib64/libQtGui.so.4
#10 0x000055dcac16017c in RKStandardIcons::initIcons() ()
#11 0x000055dcac02bc54 in RKWardMainWindow::RKWardMainWindow() ()
#12 0x000055dcac022221 in main ()

Reported using DrKonqi

Comment 1 Thomas Friedrichsmeier 2017-06-04 12:16:14 UTC

Thanks for taking the time to report this, and sorry for the extraordinarily long delay.

This looks like a distribution-specific issue. Should the problem persist, please take it up with the fedora package maintainer(s):
http://rpms.remirepo.net/rpmphp/zoom.php?rpm=rkward .

Of course, feel free to re-open, if you disagree with this assessment.

Comment 2 Andrew Crouthamel 2018-09-19 14:30:15 UTC

This bug has had its resolution changed, but accidentally has been left in NEEDSINFO status. I am thus closing this bug and setting the status as RESOLVED to reflect the resolution change.