On Mon, 04 Aug 2025 12:17:22 -0700 Damien <[email protected]> wrote:
Package: kaffeine
Version: 2.0.19-1
Severity: important
X-Debbugs-Cc: [email protected]

Issue: While configuring kaffeine, scanning and adding channels to the channel list, I discovered an issue. Here's the steps to recreate: 1. From the main menu [Television]->[Channels]->[Start Scan]-> wait till scan completed.
2. From the "Scan Results" sub-window on the right hand side, highlight one 
single channel
3. While a single channel in the scan results highlighted, click on [Add 
Selected]
4. Click [Ok] button the in the righ lower corner to return the main application view. The issue - only one single channel can be added to the channel list. If an attempt is made to add more the one single channel from the "Scan results" to the channel list, Kaffeine application crashes as soon the [Ok] button is clicked, system logs showing a "segfault" message from kernel.
See log below:

Aug 04 12:06:40 debian-dvbs kernel: kaffeine[2991]: segfault at 18 ip 
000055729281b8e8 sp 00007ffd7605d030 error 4 in 
kaffeine[468e8,55729280a000+dd000] likely on CPU 0 (core 0, socket 1)
Aug 04 12:06:40 debian-dvbs kernel: Code: 00 00 e9 ec fa ff ff 0f 1f 00 48 8b 85 80 
00 00 00 be 01 00 00 00 8b 50 04 85 d2 0f 84 a8 fb ff ff 48 8d 78 08 e8 48 27 ff ff 
<8b> 70 18 48 8b 85 80 00 00 00 48 8b 40 10 83 c6 01 48 85 c0 74 75
Aug 04 12:06:40 debian-dvbs systemd[1508]: 
app-gnome-org.kde.kaffeine-2991.scope: Consumed 5.429s CPU time, 123M memory 
peak.
Hello,
the kernel message points to this line:

  0x00005626a74b78e8 in SqlInterface::sqlFindFreeKey<QMap<SqlKey, ExplicitlySharedDataPointer<DvbChannel 
const> > >(QMap<SqlKey, ExplicitlySharedDataPointer<DvbChannel const> > const&) const at 
/usr/include/c++/14/bits/stl_iterator_base_funcs.h:175

The template of SqlInterface::sqlFindFreeKey lives here:

  https://sources.debian.org/src/kaffeine/2.0.19-1/src/sqlinterface.h#L85

This upstream bug may be related:

  https://bugs.kde.org/show_bug.cgi?id=503740

Kind regards,
Bernhard

Reply via email to