Bug 1255757

Summary:	transmission-qt crashes after Qt 5.5.0 update
Product:	[Fedora] Fedora	Reporter:	Markus S. <kamikazow>
Component:	transmission	Assignee:	Gwyn Ciesla <gwync>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	22	CC:	abdulkarimmemon, charles, gwync, helio, jspaleta, kumarpraveen.nitdgp, raghusiddarth, rajeeshknambiar, sanjay.ankur
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-25 12:43:27 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1256572
Bug Blocks:

Description Markus S. 2015-08-21 13:22:31 UTC

Description of problem:
“transmission-qt” terminated by signal SIGSEGV (Address boundary error)

Fedora 22 - x86_64

Version-Release number of selected component (if applicable):
transmission-qt: 2.84-7.fc22
qt5-qtbase: 5.5.0-15.fc22

How reproducible:
Every launch

Comment 1 Rajeesh 2015-08-24 16:09:01 UTC

Same issue, after upgrading to Qt 5.5. Stack trace:

Program received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()
(gdb) bt
#0  0x0000000000000000 in  ()
#1  0x00007ffff61eb970 in QMenuPrivate::syncPlatformMenu() () at /lib64/libQt5Widgets.so.5
#2  0x00007ffff63e0b65 in QSystemTrayIconPrivate::addPlatformMenu(QMenu*) const () at /lib64/libQt5Widgets.so.5
#3  0x00007ffff63e0c37 in QSystemTrayIconPrivate::updateMenu_sys_qpa() () at /lib64/libQt5Widgets.so.5
#4  0x00005555555bac97 in TrMainWindow::TrMainWindow(Session&, Prefs&, TorrentModel&, bool) ()
#5  0x000055555558b745 in MyApp::MyApp(int&, char**) ()
#6  0x0000555555586f85 in main ()
(gdb)

Comment 2 Raphael Groner 2015-08-25 10:44:27 UTC

Not sure, should this bug block the update to Qt5.5, also in Fedora 21?

Comment 3 Helio Chissini de Castro 2015-08-25 12:43:27 UTC


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