Bug 424800

Summary:	K3b crashes when adding a file with only a slash as name to a data project.
Product:	[Applications] k3b	Reporter:	Hugo <hugo>
Component:	Data Project	Assignee:	k3b developers <k3b>
Status:	RESOLVED WORKSFORME
Severity:	minor	CC:	aacid, michalm, trueg
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Hugo 2020-07-29 14:17:18 UTC

SUMMARY

K3b crashes when adding a file with only a slash as name to a data project.

The file that caused this problem for me is from 2009. I'm fairly certain that I have burned this file to disc with K3b before in the last decade. Probably even with this operating system.

Nevertheless, the filename was a mistake, so my immediate problem is fixed by renaming the file.


STEPS TO REPRODUCE
1. Create a file with a slash as name. E.g. `echo "hello" >> "\\"`.
2. Start a new data project.
3. Drag the file into the project.


OBSERVED RESULT

K3b crashes:

ASSERT: "i >= 0" in file /usr/include/qt4/QtCore/qstring.h, line 885
KCrash: Application 'k3b' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
KCrash: Connect sock_file=/home/hugo/.kde/socket-ubuntu32/kdeinit4__1


EXPECTED RESULT
K3b should burn the file.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Ubuntu 16.04.6 LTS
(available in About System)
KDE Plasma Version: ?
KDE Frameworks Version: ?
Qt Version: ?

ADDITIONAL INFORMATION

About K3b:
Version 2.0.3
Using KDE Development Platform 4.14.16

Yeah this version is probably pretty old, but it seems this problem has been introduced only recently, so I thought it might be worthwhile to mention anyway.

Comment 1 Albert Astals Cid 2020-07-29 22:32:19 UTC

Your k3b version is terribly old. I can not reproduce it with a modern version.

Comment 2 Hugo 2020-07-30 10:47:19 UTC

2.0.3 is the latest k3b version of the oldest Ubuntu LTS (16.04). But that is not your problem, maybe I should file the bug with Ubuntu. (And apparently Kubuntu 16.04 is not supported anymore, that would make the problem a bit more relevant.)

It could be interesting to know what made this problem suddenly appear though. But well, not really worth it to dig into this if other versions are not affected.

Thanks for checking and resolving Albert. I didn't know how to easily install a newer k3b version without breaking everything. Thanks for this wonderful piece of software.