Bug 171704

Summary:	Adding file association with use of file dialog crashes Konqueror
Product:	[Applications] konqueror	Reporter:	Morten Bo Johansen <mbj>
Component:	general	Assignee:	Konqueror Bugs <konqueror-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	finex, frank78ac
Priority:	NOR
Version First Reported In:	4.1.1
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	Valgrind log of Konqueror crash

Description Morten Bo Johansen 2008-09-26 15:24:32 UTC

Version:            (using KDE 4.1.1)
OS:                Linux
Installed from:    Debian testing/unstable Packages

This could be a duplicate of #154542, not sure so I report anyway.
The crash is completely reproducible in this sequence, click:

- Settings
- Configure Konqueror
- File Associations
- (select a file type)
- in the "Application Preference Order" window click "Add" to add a   new handler
- click on the file dialog icon to open the file dialog
- in the location entry field type in the name of a directory, e.g. "bin" to get a listing of that directory and click enter
- Konqueror crashes.

It is important to note that it is typing "enter" on the keyboard that produces the crash. If you use the mouse to select the directory Konqueror survives.

The crash does not invoke the KDE crash handler that produces the backtrace. I ran Konqueror in gdb, but when I enter "bt" after the crash, gdb reports "no stack". Can you tell me how to produce a backtrace from Konqueror in gdb?

Meanwhile I am attaching a Valgrind log.

Packages are from Debian's experimental repository. Plugins are disabled.

Comment 1 Morten Bo Johansen 2008-09-26 15:26:40 UTC

Created attachment 27579 [details]
Valgrind log of Konqueror crash

Valgrind log of the crash described above. Command line was:

valgrind --suppressions=src/kdesdk/scripts/kde.supp --num-callers=50 --log-file=konqcrash.log konqueror

Comment 2 FiNeX 2008-09-27 01:47:50 UTC

I'm not able to reproduce it using current trunk. I cannot reproduce anymore the bug #154542 too :-)

Comment 3 Frank Reininghaus 2008-09-29 00:03:21 UTC

Maybe both bug reports are duplicates of bug 171395 which was fixed a week ago?

Comment 4 FiNeX 2008-09-29 01:06:43 UTC

Probably yes. If you agree I set this like a dup of 171395 ok?

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