Bug 411042 - try to edit channel in kaffeine 2.0.17 gives a crash
Summary: try to edit channel in kaffeine 2.0.17 gives a crash
Status: RESOLVED WORKSFORME
Alias: None
Product: kaffeine
Classification: Applications
Component: general (show other bugs)
Version: 2.0.17
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Mauro Carvalho Chehab
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-18 17:17 UTC by peter.schlaf
Modified: 2022-11-11 05:20 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description peter.schlaf 2019-08-18 17:17:09 UTC
Hello,

right-click on certain sat-channels from ASTRA 19.2°E + Hotbird 13°E in 
the dvb-channel list in kaffeine 2.0.17 and selecting "edit" crashes 
the program without opening the channel-editor.

gdb output says:

   Thread 1 "kaffeine" received signal SIGSEGV, Segmentation fault.
   0x00005555555a78c6 in DvbChannelEditor::DvbChannelEditor
   (this=0x5555574fce60, model_=<optimized out>, channel_=...,
   parent=<optimized out>)
        at
   /usr/src/debug/kaffeine-2.0.17-lp151.1.1.x86_64/src/dvb/dvbchanneldialog.cpp:961
   961                     QString text = QString::number(it.first);
   (gdb)


Distribution is openSuSE Leap 15.1
Comment 1 peter.schlaf 2020-08-19 22:42:18 UTC
kaffeine 2.0.18 has still the same error. It seems that the channel editor can't handle channels who don't have an audio pid (like sat-transponders with test-channels), so in /src/dvb/dvbchanneldialog.cpp starting at line 960:

	const QPair<int, QString> &it = pmtParser.audioPids.at(0);
	QString text = QString::number(it.first);

a crash is inevitable, because in this case "it" is NULL.
Comment 2 Justin Zobel 2022-10-12 03:50:15 UTC
Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Comment 3 Bug Janitor Service 2022-10-27 05:03:41 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2022-11-11 05:20:21 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

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